PennyPost decides who stalled by looking at a few pages and events in your app. With PostHog it guesses them; you can change them on the From PostHog card on Activation (Change) or on Setup.
The results page
This is the page where a new user sees their first result: a finished headshot set, a scan report, a rendered video. It's the most important setting. Opening it is what "reached their first result" and "came back" mean everywhere in PennyPost.
- You can set up to 3 results pages.
- A page covers itself and everything under it, so
/projectsalso covers/projects/42. *matches one part of the path, so/projects/*/resultsmatches/projects/42/results.
Pick it from the pages PennyPost has seen, or choose Not here? Type the page.
Do results take a while?
Activation asks "Does it take a while to get ready?"
- Yes, people wait for it if there's a render, scan or import that runs after they ask. PennyPost then needs to know when results are ready: the event from PostHog or Segment, or
results_readyfrom your server. - No, it's instant if results show up right away. The "left before their results were ready" moment is hidden, since nobody can leave before an instant result.
Setup pages
If new users go through onboarding before they get anywhere (a survey, a brand kit, connecting a site), set those pages, like /onboarding or /setup. You can set up to 3. They can't be your results page. They're used by the "stopped halfway through setup" moment.
The first action
The first real thing a user does: starting a scan, uploading photos, writing a first prompt. With PostHog it's an event name like scan_started. It's used by the "never did the first action" moment, and a person who does it no longer counts as stalled there.