Here’s a concise, Mixpanel‑aligned analytics ticket template you can copy into your tracker.
User Story
- As a: Product analyst
- I want to: Measure which option users select when clicking the plan selection button
- So that: I can compare default vs premium selection and optimize conversion
Key Deliverables
- Single, action-oriented event with clear name
- Properties that capture option type (default vs premium) and relevant context
- Consistent naming convention and data types
- Documentation in tracking plan and Lexicon
- Code implementation and validation
Required Update
- Event Name: plan_selected (Object Verb; snake_case) (Use clear, consistent names; Mixpanel is case-sensitive) (Events best practices)
- Description: Fires when a user clicks the plan selection button to choose an option
- Trigger: User clicks the plan select/CTA button
- Required Event Properties:
- option_type: default | premium (use a property instead of separate events; keeps actions grouped) (Keep events as actions; Group similar actions via properties)
- page_name or screen_name: e.g., /pricing (useful for breakdowns) (Events and properties examples/use cases)
- experiment_variant (if applicable): control | variant_a (optional)
- source: ui | deep_link (optional; consider as a super property if global) (Super properties)
- Distinct ID: Use your authenticated user ID when available; ensure proper identification on login/sign-up to stitch sessions across devices (Identify users; Events require distinct_id)
- Naming & Data Quality:
- Use snake_case; avoid dynamic event names; use properties for variable values (Naming, avoid dynamic names)
- Keep property values consistent (e.g., “default”, not “Default”) and omit properties rather than sending null/empty (Property conventions)
- Tracking Plan & Governance:
