Blog
InstrumentationBy Marwan AkhandafJune 19, 20262 min read

Analytics SDK Test Mode: How to Debug Events Without Polluting Production Metrics

Use analytics SDK test mode to validate mobile events, setup keys, paywalls, purchases, and webhooks without confusing production dashboards.

Summary

A practical guide to test mode semantics, setup validation, and preventing development events from polluting analytics.

Test mode should be visible in Live Events.

Test events stay out of production rollups, metric alerts, billing, and production limits.

Privacy checks still inspect test payloads and can trigger privacy alerts.

Why test mode needs first-class UI

Developers need immediate feedback when installing an SDK. Live event debugging should show events as soon as they arrive, including test-mode events from simulators, emulators, and internal builds.

AppMetricsKit marks these events with isTestMode true and exposes them in Live Events. It excludes them from production rollups, rollup-based metric alerts, billable event counts, and production usage limits.

Common mistakes

The most common mistake is hardcoding testMode true and forgetting it before release. The second is sending production events while still changing event names. The third is checking only one event and assuming every downstream dashboard is ready.

A good setup flow explains which events unlock which pages. For example, retention needs repeat App.launch events from stable pseudonymous users, while experiments need Paywall.viewed with experiment and variant payload fields.

FAQ

Common questions

Should test events appear in Live Events?

Yes. Live Events is the right place to validate test delivery, as long as the mode is labeled clearly.

Should test events count toward production metrics?

No. AppMetricsKit excludes test events from production rollups, rollup-based metric alerts, billable event counts, and production usage limits. Privacy checks and privacy alerts still apply.