Triage sudden metric spikes for event tracking bugs
Diagnose whether an unexpected surge in product analytics is real user activity or broken telemetry. Use this before sharing anomalous growth numbers.
You getMost Likely Technical Culprits, immediate Diagnostic Checks and validation Criteria
Prompt
Act as a senior analytics engineer. Analyze the anomalous metric spike described below to determine whether it indicates genuine user behavior or an instrumentation error.
- List the most common tracking failure patterns that create this specific pattern (such as duplicate event firing, loop conditions, or bot traffic).
- Define specific queries or segmentation cuts the analyst should immediately run to isolate the anomaly.
- Provide a rule of thumb for when to discard the data versus when to escalate to engineering.
Output format:
1. Most Likely Technical Culprits (ranked list of 3 items)
2. Immediate Diagnostic Checks (numbered queries or dimension filters to run)
3. Validation Criteria (how to prove it is real user demand)
4. Immediate Containment Action
Metric details, timing, and baseline behavior are below:Example output
Paste the metric name, percentage increase, timeframe, and relevant deployment dates into ChatGPT, Claude, or Gemini. If you suspect bot traffic, follow up by asking for specific SQL queries to inspect IP and User-Agent distributions.
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
Create an anomaly investigation checklist for analytics teams
Run a disciplined diagnostic process before investigating metric shifts. Use this checklist whenever unexpected data spikes or drops appear in reports.
Differentiate structural null values from missing data
Identify whether null values represent expected business logic or export dropouts. Use it when auditing schema quality or preparing datasets for modeling.
Separate true anomalies from pipeline data errors
Classify extreme values as either legitimate business events or pipeline errors. Use it when high or low metrics distort downstream reporting.
Build standardized KPI definition templates for teams
Standardize team metrics and eliminate conflicting calculations for critical business KPIs. Use this before building dashboards or quarterly reports.
Screen survey data for duplicate and low-effort responses
Audit raw survey records for gibberish, straightlining, rapid completion times, and duplicate entries to clean your dataset.
Audit driver-based models for compounding optimism bias
Expose subtle, compounding growth assumptions across pipeline stages and conversion metrics. Use this during quarterly budget reviews and board deck prep.
- Compare cumulative customer lifetime value across monthly cohorts
- Diagnose circular loops and friction steps in signup funnels
- Evaluate past forecast variances to set accurate targets
- Isolate regional or platform drivers behind KPI drops
- Rank survey satisfaction drivers by loyalty impact
- Resolve split device identities into single user records