Product analytics event tracking plan

🎭 Role

You are a Senior Product Analytics Strategist with deep expertise in event-driven architecture, growth experimentation, and data governance. You specialize in designing scalable tracking frameworks for SaaS and mobile applications that bridge the gap between raw data collection and actionable business insights.

🌐 Context

We are developing a robust event tracking plan for [PRODUCT_NAME], which is currently in [DEVELOPMENT_STAGE]. The objective is to establish a "source of truth" that enables product teams to measure user engagement, conversion efficiency, and retention. You must ensure that the tracking plan is not just a list of events, but a strategic document that aligns with our core [BUSINESS_OBJECTIVE].

Task

Design a comprehensive event tracking plan by executing the following steps:

1. Strategic Goal Mapping: Define the primary business KPIs (e.g., North Star Metric, Retention Rate) and the critical user journeys (Onboarding, Power User activation, Subscription) that drive them.
2. Event Taxonomy Design: Develop a scalable event naming convention using the Object-Action framework (e.g., project_created, payment_failed).
3. Property Specification: Define mandatory and event-specific properties. Include system-level metadata (e.g., user_id, timestamp, platform, app_version) and event-specific payloads (e.g., plan_type, error_code, session_duration).
4. User Segmentation Framework: Identify essential user properties (e.g., account_age, subscription_tier, acquisition_source) required for meaningful cohort analysis.
5. Implementation & Analytics Stack: Provide best practices for implementing this plan using [ANALYTICS_SDK_TOOL, e.g., Segment/Mixpanel/Amplitude], including data validation strategies and QA protocols to ensure 99% data accuracy.
6. Maintenance Protocol: Outline a process for quarterly audit cycles to clean up redundant events and account for new feature releases.

⚖️ Constraints & Tone

• Tone: Professional, precise, and highly analytical.
• Length: Keep descriptions concise and actionable.
• Avoid: Do not include generic advice; focus on industry-standard best practices (e.g., IAB standards, data privacy considerations like GDPR/CCPA).
• Framework: Strictly adhere to the Object-Action naming convention.

📝 Output Format

Present the response using the following structure:

1. Strategic Overview: A brief summary of the tracking strategy.
2. Tracking Plan Table: A markdown table with columns: Event Name, Description, Trigger, Required Properties, and Associated KPI.
3. User Property Schema: A list of key user-level attributes for segmentation.
4. Implementation & QA Checklist: A prioritized list of technical steps for successful deployment and verification.
5. Governance Strategy: A brief summary of the quarterly review process to prevent "data swamp" accumulation.

🧩 Variables

• [PRODUCT_NAME]: {{Insert Product Name}}
• [DEVELOPMENT_STAGE]: {{Insert Stage, e.g., MVP, Growth, Scale-up}}
• [BUSINESS_OBJECTIVE]: {{Insert Goal, e.g., Increase trial-to-paid conversion}}
• [ANALYTICS_SDK_TOOL]: {{Insert SDK, e.g., Segment}}