Skip to content
AI Assistant

Guides

See which website tries became customers

Platform operators: read every website try with its instruments, the six-stage conversion funnel, and an honest outcome per try — converted, probable, or where it left.

On this page

Every time someone previews your mate on their own website (the hero quick start, /try/<host>), the platform keeps the try — and now answers the two questions a platform operator asks about it: did this try become a customer, and if not, where did it leave? Console → Platform → Previews shows every try with its instruments, a conversion funnel for the window, and one honest outcome line per try. Platform operators only; a workspace never sees another workspace's tries.

1. Read the funnel

The widget under the timeline is a sequence of six bars for the active range (last 7 / 30 / 90 days, or the whole retained window):

StageWhat proves it
TriedThe preview session exists
Reached a stepThe "Keep this assistant" flow reached at least one quick-start step
Signed upA platform account is known for the try — the scan-id stamp of a signed-in landing, or a signed-in session owner
Created tenantA workspace was created or joined after the try began, or the scan stamped one
PublishedThat workspace's runtime was published at least once
SubscribedThe account holds an active or trialing subscription, or paid an invoice

Each bar is labelled with its count and the share of the previous bar; the table under the bars repeats the numbers, and the per-site table lists tries, converted, probable and the conversion rate per host. A bar the platform could not prove (the account facts were unreadable) is drawn outlined with a ? — never a zero.

2. Read a try

Open Every try to list every try across hosts, newest first, or pick a site and then a session. Each row and the detail pane carry the same instruments:

  • OutcomeConverted → <workspace> (day N), Probably → <workspace>, or Left at: <stage> · last seen <when>.
  • Stages — the six chips, reached or not; an unproven chip says so.
  • Quick-start stepsstep N of 6 with the seconds each step took, and the verdict when a step failed.
  • Identity — the same badge model as the Inbox: no visitor id, anonymous, returning · N earlier tries, linked to <subject>, or seen with N accounts (a shared browser is never assigned to one account).
  • Account — the email, when it signed up, whether it existed before the try, the subscription status.
  • Client — country, device class, OS and browser, referrer, entry URL and the UTM campaign. No IP is stored or shown.
  • AI readiness — the cached scorecard for the host (checks passed, the missing ones) and how many pages the scan read.
  • Links — open the try (/try/<host>), open the visitor's cross-workspace journey, open the workspace.
  • Evidence — the named facts the verdict came from (scan_stamp, session_owner, domain_owner, sibling_session, runtime_receipt, subscription …).

3. Converted, probable, or left

The verdict is only as strong as the link:

  • Converted — unambiguous. The try's scan id was stamped by a signed-in landing, or the session's own signed-in owner created or joined the workspace.
  • Probable — a plausible but unproven link: the workspace merely owns the tried domain, the conversion was stamped on a sibling try of the same browser, or the account joined a workspace after the try without the scan stamp. It is shown as probable and counted separately; it is never called converted.
  • Left — no workspace is linked; the row says the furthest stage and when the visitor was last seen.

4. Filter, export, act

  • Filters — minimum stage reached, outcome (converted / probable / left), site, search, date range. The Subscribed stage filter narrows to tries with a workspace and then checks subscriptions.
  • Export CSV — every try in the current filter with all instruments as columns (bounded to 200 rows per export).
  • Realtime — a new try, a new quick-start step or a conversion updates the page on its own; nothing polls.
  • Actions — mark a lead, add a note, copy the invite link (unchanged from the Previews explorer).

From your AI tools (MCP)

  • list_platform_previews — every try with instruments; host, q, range_days, stage, outcome, limit, offset.
  • get_platform_preview — one try's full instrument set by session_id.
  • get_platform_preview_funnel — the rollup for days (optionally one host).

All three are platform-operator only and refuse a workspace caller before anything runs. The account facts come from get_platform_preview_conversion_facts, which re-checks the operator role on every call.

Reference