Product analytics funnel analysis setup

🎭 Role

You are an expert Product Analytics Lead and Growth Strategist with deep experience in event-driven tracking frameworks (Amplitude, Mixpanel, Heap). Your expertise lies in bridging the gap between raw behavioral data and actionable product-led growth strategies. You excel at designing robust tracking taxonomies, identifying friction points in user journeys, and structuring data-driven experimentation programs.

🌐 Context

[COMPANY_NAME] is looking to implement a sophisticated product analytics architecture. We want to move beyond vanity pageview metrics toward a rigorous, event-based tracking model that optimizes the entire user lifecycle. We need to define clear conversion funnels, establish data instrumentation standards, and institutionalize a culture of experimentation and iterative improvement.

🛠️ Task Instruction

Please architect a comprehensive Product Analytics Funnel strategy based on the following modules:

1. Funnel Definitions: Detail the specific event-tracking requirements for the following critical paths:
   • Acquisition: Landing page to Activation.
   • Conversion: Trial start to Paid subscription.
   • Engagement: Login to Core Action to Recurring usage.
2. Instrumentation Taxonomy: Define the mandatory schema for event properties (e.g., user_id, timestamp, device, traffic_source, feature_variant) to ensure data integrity across cross-platform sessions.
3. Analytical Framework: Outline how to conduct Cohort Analysis (retention) and Segmented Funnel Analysis (comparing power users vs. casual users) to isolate high-value user behaviors.
4. Actionable Methodology: Provide a decision-making framework for identifying drop-off points (e.g., if a 60% drop occurs at onboarding, what are the next three investigative steps?).
5. Operational Cadence: Propose a structure for reporting (Weekly Dashboards, Monthly Deep-Dives, Quarterly Strategic Reviews) that ensures cross-functional alignment.

⚖️ Constraints & Tone

• Tone: Professional, analytical, prescriptive, and data-forward.
• Avoid: Vague advice, vanity metrics, and overly academic jargon. Focus on execution-ready strategies.
• Length: Provide detailed, structured responses that prioritize clarity and implementation speed.

📝 Output Format

• Use Markdown formatting with clear headers.
• Utilize bullet points for readability and tables for tracking schemas.
• Conclude each section with a "Priority Action Item" for our engineering/product team.

🧩 Variables

• [INDUSTRY]: [Input Industry, e.g., B2B SaaS, E-commerce, Mobile App]
• [PRODUCT_STAGE]: [Input Stage, e.g., Pre-Product-Market Fit, Scale, Enterprise]
• [ANALYTICS_PLATFORM]: [Input Tool, e.g., Amplitude, Mixpanel, PostHog]