Audit Feature Adoption Tracking Across User Workflows
Get a complete analytics audit mapping exposure, first-run completion, and habitual milestones to spot blind spots in your feature tracking.
You getFunnel Health Diagnostic, instrumentation Audit Table and 3 Diagnostic Questions
Prompt
Act as a principal product analytics architect. I want to audit telemetry for an existing product workflow to detect tracking gaps across user adoption stages.
First, ask me 3 brief questions and wait for my reply before creating the audit:
1. What is the feature, its core value event, and who uses it?
2. What user actions are currently tracked as analytics events?
3. What defines regular, habitual use (for example: twice weekly, monthly billing run)?
Once I reply, generate an instrumentation audit following these rules:
- Break the funnel into three strict tiers: Exposure (discovery/entry points), First Complete Cycle (initial time-to-value), and Habitual Retention (repeated usage).
- Compare currently tracked events against critical missing events required to diagnose user drop-off.
- Name every suggested event with snake_case naming (object_action format) and include 2-3 required payload properties.
Output format:
- Funnel Health Diagnostic: 2-sentence summary of tracking maturity and main blind spot.
- Instrumentation Audit Table: Columns for Stage, Milestone Goal, Currently Tracked, Missing Recommended Events, and Essential Event Properties.
- 3 Diagnostic Questions: Questions product managers can answer only after implementing the missing events.
- Implementation Risks: One short note on telemetry load or event volume risks.Example output
Tips and common edits
Why this works
- Forces a strict 3-tier structure to uncover hidden gaps between first discovery and sustained weekly usage.
- Mandates snake_case event names and payload properties so results can be pasted straight into engineering specs.
- Includes diagnostic questions to verify that the recommended data actually answers core retention problems.
Paste this prompt into ChatGPT, Claude, or Gemini when preparing analytics specs or diagnosing why an existing feature shows low retention numbers.
Common edits
- Add a requirement to map existing events to specific platforms like Mixpanel, Amplitude, or PostHog.
- Request server-side versus client-side tagging recommendations for each missing event row.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Write an Event Tracking Plan Where Every Event Maps to a Success Metric
Get a tracking plan table with object_action event names, exact triggers, typed properties and the success metric each event feeds, plus a list of events to cut.
Define a North Star and Success Metrics for a New Feature with Guardrails
Get a North Star metric, up to three primary metrics each paired with a guardrail, exact formulas from your existing data, targets, and ship or roll-back rules.
Classify onboarding drop-offs into cognitive and value friction
Audit user onboarding funnels by separating confusion from missing value motivation. Use it to prioritize growth experiments and UX redesigns.
Rewrite empty state copy to accelerate user activation
Turn passive placeholder screens into clear, action-oriented entry points that guide users to their first completed task. Use it during product design and copy polish.
Schedule phased customer communications for feature sunsetting
Create a structured, multi-channel communication timeline to retire a software feature without alarming customers or breaking workflows.
Analyze customer feedback using Jobs to Be Done
Extract functional, emotional, and social customer drivers from raw user feedback. Use this to separate true user motivations from reactionary feature requests.
- Reframe a feature request into a core user problem
- Audit Your Signup-to-Activation Flow and Find the Steps to Cut First
- Turn a Vague Founder Request into a Scoped Problem Brief with Trade-Offs
- Write a One-Page PRD for a Small Feature That Engineers Can Start From
- Define Granular Role-Based Access Control for Multi-Tenant Features
- Draft Multi-Tier SaaS Product Packaging and Feature Matrix