How to Debug Mobile Analytics Events When Nothing Shows Up
Debug missing mobile analytics events by checking ingest URLs, keys, test mode, simulator networking, payload validation, and Live Events filters.
Summary
A troubleshooting guide for the frustrating moment when the SDK is installed but the dashboard still looks empty.
Start with network reachability and key validity.
Check Live Events filters before changing code.
Use one App.launch event as the setup smoke test.
Start with the smallest possible event
Do not debug a full purchase flow first. Configure the SDK and send App.launch with no custom payload. If that arrives, the SDK, key, endpoint, and basic network path work.
If App.launch does not arrive, check the ingest URL, environment, test mode, and whether the key belongs to the selected app. Many setup failures are caused by using a key from a different app or a localhost URL that the device cannot reach.
Check filters before code
Live Events may have environment and mode filters. If you are sending test-mode events but looking only at live events, the page can appear empty even though ingest is working.
Also check whether the app switcher is pointing to the app that owns the ingest key. This is especially important after creating multiple test apps during onboarding.
Payload validation can reject events
A privacy-first ingest pipeline may reject events with invalid names, oversized payloads, unsupported value types, or risky keys. Keep your first payload empty or extremely small.
Once delivery is confirmed, add one payload key at a time. This makes it clear which field is breaking validation.
FAQ
Common questions
Why do events work in the simulator but not on a physical device?
The physical device may not be able to reach a localhost URL on your development machine. Use a LAN address, tunnel, or deployed ingest endpoint.
What is the best first analytics event to test?
Use App.launch because it is simple, has no required payload, and confirms the SDK can send to the ingest endpoint.