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.
Help developers fix missing SDK events during setup.
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.
Implementation checklist
How to apply this debug mobile analytics events guide
Treat this article as an instrumentation brief before adding or changing analytics code. The goal is not to send more events. The goal is to make every event answer a specific product, revenue, privacy, or debugging question for your app team.
Define the decision first
Write down the decision this troubleshooting work should support. Good examples are whether onboarding is leaking users, whether a paywall variant changes purchase intent, or whether a provider webhook is missing subscription lifecycle events.
Map the smallest event set
Choose the fewest event names and payload fields that answer the decision. Prefer stable names such as App.launch, Paywall.viewed, Purchase.completed, Subscription.renewed, and Error.occurred over ad hoc labels that only one release understands.
Verify in test mode
Send events from a debug build first, inspect the live event stream, and confirm that environment, platform, app version, product ID, paywall variant, and revenue fields appear where expected before counting the data in production dashboards.
Run a privacy pass
Review every payload key before launch. Remove email addresses, names, advertising IDs, phone numbers, precise location, free-form user text, raw payment tokens, and other fields that make analytics harder to defend during an app privacy review.
In AppMetricsKit, the safest workflow is to create an ingest key, install the iOS or Android SDK in test mode, send the first event, review Live Events, then promote the same taxonomy to production. After events are stable, connect RevenueCat, Adapty, Superwall, or server-side sources so subscription changes that happen outside the app are reconciled with client events.
Revisit this checklist whenever a new paywall, onboarding step, plan, trial offer, release channel, or data export is introduced. Most analytics quality problems come from small schema changes that were never reviewed, not from the dashboard itself.
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.