question_started
Shows that home or hall got the user to question framing.
Do not store the full private question in the event payload.
what to track
Event map
OmenHall event map: from first question to payment, save, email, refund, and repeat visit.
Events should show the user's path without reading their private secret.
method_selected
Shows which oracles users choose after a question.
Do not treat method choice as proof of response quality.
checkout_started
Shows the shift from interest to payment intent.
Separate test and live payments.
scroll_saved
Shows result value after delivery.
Do not store scroll content in analytics.
Collect the signal
Define the event, page, source, and moment where the user acted or stopped.
- The event does not contain a private question or full scroll text.
- There is a clear timestamp and route.
- The signal can be tied to an owner decision.
Compare against expectation
Every number must be read beside a hypothesis: what should have happened, what happened, and how much it matters.
- There is a baseline or first-week manual estimate.
- No conclusion is made from one random day.
- Devices are checked separately: mobile and desktop.
Turn into an edit
Analytics becomes useful only after action: rewrite a block, simplify a flow, add FAQ, fix an error, or close an extra door.
- There is an owner, priority, and expected effect.
- The change is written into the decision log.
- A re-check date is assigned after the change.
dashboard
- Daily event volume by route and device.
- Question start to method selection rate.
- Checkout start to success rate.
- Saved scroll and return-to-archive rate.
alerts
- checkout_started rises but checkout_success falls.
- question_started sharply drops on mobile after a hero change.
- reading_ready emails exist but scroll_opened is almost absent.
decisions
- Simplify hero or CTA if question_started is below expectation.
- Check Stripe and success page if checkout_success drops.
- Rewrite email if scroll_opened is low after inbox/email delivery.
red flags
- Events contain question text, email, or personal names unnecessarily.
- Payment affects supposedly random card selection.
- The team optimizes clicks by adding anxious pressure.
related doors