Every meaningful user action across onboarding, paywall, and beyond. To be plugged into GA4 + mirrored into User.com.
Status: Specification only. No events are firing yet — this page lists what needs to be instrumented when GA4 is wired in. Manage events with no code on the Settings page.
Onboarding events
These fire as a user moves through /v8/ from welcome to dashboard.
Event name
Trigger
Notes
Activation events (post-onboarding, in-trial)
These fire during days 1–7 of the trial.
Event name
Trigger
Notes
Paywall events
These fire as the user moves through /paywall/ from day 4 onward. (Paywall flow not yet built — events specced ahead of build.)
Event name
Trigger
Notes
User.com mirroring (parked)
Every event above should also fire into User.com so the marketing/CRM layer
has the same view of user state as analytics. Mapping events to User.com
attributes happens when GA4 is plugged in. This is a parked decision —
listed here so we don't forget.
Implementation notes
Events should fire once per session unless explicitly noted as "every time."
All events carry the user's anonymous ID before account creation, then merge with the authenticated user ID at account_created.
ST vs Ltd branch should be captured as a user property, not a per-event property, so cohort analysis works.
Deployment checklist: verify each event fires correctly in GA4 DebugView before signing off.