Debug Missing Events in Amplitude
Trace one known action from the application to the intended Amplitude project, then distinguish capture failure from ingestion, governance and reporting issues. A blank chart is not enough to identify which layer failed.
Before you start: Have a synthetic test account, engineering access to the relevant integration and a precise event name. Do not expose API keys in screenshots or shared notes.
Worked example: A report_saved event appears in development but not in the production funnel. The cause could be a different project key, blocked event or a filter excluding the test user.
Step-by-step guide
Reproduce one action
Record the time, account and expected event. Use synthetic content so the debug evidence can be shared safely.
Check the outgoing payload
Confirm event name, project routing, timestamp and required identifiers. A spelling or environment mismatch can look like lost data.
Inspect ingestion context
Review transport errors and any batching or delivery delay. Do not treat a successful client call as proof that the intended project accepted the event.
Check governance controls
Inspect hidden, blocked or other data-management settings appropriate to your permissions. Distinguish an event unavailable in a picker from one dropped at ingestion.
Check identity and query
Look for the event under the relevant user and device history. Remove unnecessary chart filters in a diagnostic copy, keeping production reports intact.
Fix and verify end to end
Repeat the exact journey after the correction. Record the coverage date and explain any historical gap that the fix does not repair.
Common mistakes
Production and test mixed
A correct payload sent to another project will not appear here.
Hide equals delete
Different governance controls have different effects.
Backfill assumed
A capture fix does not automatically reconstruct missing history.
Tips
Use one timestamped test journey for the investigation.
Keep a diagnostic chart separate from the shared metric.
Record the first verified successful event after the fix.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.