Skip to main content

Reading the rails

Below the profile, the page shows this member's rails: one card for each placement your project serves, filled with what the real engine returns for this person right now. This is the heart of Member Preview, the part that answers "what would this member actually see."

One card per placement​

Each rail is one saved placement — a scenario, a query you have already built — run for the selected member. The page shows the placements that belong to this project's own domain, so a video member's rails are the video placements and a wellness member's rails are the wellness ones. You are looking at the real set of shelves the product would assemble for this person, not a sample.

Reading one rail​

Every rail card carries the placement's title and its tiles in the order the engine served them. Each tile shows what the placement returned for this member:

  • Title — the name of the item.
  • Type — what kind of item it is.
  • Genre or topic — the item's category, read from its own metadata.

The tiles sit in served rank order, left to right: the first tile is what the engine ranked first for this member, and that ordering is the point. You are reading the engine's actual call for this person.

No scores, by design​

A rail never shows a per-item score. The product does not put a number on a tile in front of a member, so neither does this page. The order is the signal you can trust and act on; a raw score would be a number with no decision attached and a false sense of precision. See the honesty contract.

View all​

A rail shows the first several items, enough to read the engine's top picks at a glance. When a placement returns more, the rail ends with a View all card. Open it to see the full result for this member and this one rail on its own page, in the same served order. Everything on that page is the same live execution, not a second, differently ranked list.