event_category
Allows behavior analysis without question text.
Do not replace category with full user input.
route_and_state
Shows where the flow breaks.
Do not record answer content.
consent_status
Helps respect user choice.
Do not treat tracking refusal as user error.
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
- Tracked event inventory and payload review.
- PII risk scan by event family.
- Consent mode status and gaps.
- Data deletion request coverage.
alerts
- Event payload suddenly contains question text.
- Session replay is enabled on sensitive routes.
- Analytics stores email where anonymous id is enough.
decisions
- Remove a payload field if it is not needed for a decision.
- Close sensitive routes to replay and unnecessary logs.
- Update privacy page if a new tracking type is introduced.
red flags
- The team wants full questions for product insight.
- Logs are used as a substitute for consent.
- Sensitive data goes into third-party analytics without review.
related doors