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.
You getPhase 1, phase 2 and phase 3
Prompt
Act as a staff analytics engineer. Create an operational troubleshooting checklist for investigating unexpected KPI spikes or drops.
- Prioritize simple data collection and pipeline errors before assuming genuine user behavior changes.
- Include specific technical checks covering tracking code, data warehouse pipelines, bot traffic, and external factors.
- Keep every step practical, fast to verify, and checkable by junior analysts.
Output format:
1. Phase 1: Telemetry and Tracking Integrity (4 checklist items)
2. Phase 2: Pipeline and ETL Freshness (3 checklist items)
3. Phase 3: Traffic Composition and Slicing (4 checklist items)
4. Phase 4: Business and External Validation (3 checklist items)
5. Escalation Decision Rule (when to notify leadership vs. resolve silently)Example output
Copy and paste this prompt directly into ChatGPT, Claude, or Gemini without any edits. As a follow-up, ask the model to adapt Phase 1 specifically for mobile SDK event tracking.
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
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.
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.
Isolate regional or platform drivers behind KPI drops
Break down aggregate product or revenue declines across platform and geographic dimensions. Use this when global numbers drop and leadership needs the root driver.
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
- Estimate potential revenue recovery across funnel drop-off points
- Evaluate past forecast variances to set accurate targets
- Map inconsistent export columns to target schemas
- Sanity check revenue projections against past baselines
- Segment conversion funnel drop-offs by device and marketing channel