Member Preview
Member Preview answers one question: if I were this specific person, what would I actually see, and is any of it real?
It is a place to walk one member's real experience from inside Studio, not a dashboard about your members in aggregate. You pick a real person and the page shows you their profile and every rail they would be served, each one produced by running the real engine for that member right now. You never log into the product as them, and you never guess.
The job it does
You are about to defend a decision about the member experience: a new placement, a change to a shelf, a claim in a review that "cold-start members still get something useful." Member Preview lets you check that claim against one real person before you make it. Paste a member id or search a name, and you see their world the way the engine builds it, rail by rail.
Generated per project, like Opportunities
You do not configure any of this. Member Preview reads whatever your project's member source already declares and whatever placements you have already saved, and assembles the page from that. A thin member record and a rich one render through the same profile card. A project with three placements and a project with thirty each get exactly their own rails. Switch the project in the top-nav Project picker and the whole page re-scopes to that project's members, domain, and placements. There is no picker on this page; the site-wide one is the single source of scope.
The honesty contract
This page is only useful if you can trust every pixel of it, so it holds to a strict rule: it shows you what is real and says so plainly when something is not.
- Every field is read live — the profile is the member's declared record as it stands now, not a cached snapshot.
- Rankings run against the real engine — each rail is the actual placement, executed for this member, in the order the product would serve.
- Per-item scores are never shown — the product does not show a member a score, so neither does this page. You see the served order, not the math behind it.
- Nothing is fabricated — where your project has no model for something, or a member has no history, or a placement is not serving, the page says so rather than inventing a plausible-looking answer.
Next
- Finding a member — search by id, name, or email at any scale.
- The member profile — reading the profile card for a thin or a rich member.
- Reading the rails — one card per placement, the tiles, the served order, and View all.
- Rail signals — the cold-start fallback badge and the unavailable-rail state.