Docs

Android Developer Verification: What to Track

Android's developer verification rollout changes how unverified apps install — track verified vs unverified paths before install attribution fragments.

Acquisition

Google’s Android developer verification requirement starts enforcement on 30 September 2026 in Brazil, Indonesia, Singapore, and Thailand, with a global rollout planned for 2027. Any app installing on a certified Android device from a developer who hasn’t verified their identity — legal name, address, and in most cases a government-issued ID — now hits extra friction at install time, whether that app came from Google Play or was sideloaded directly. For years, “sideloaded” and “Play Store” were the two install paths product teams cared about. This adds a third axis: verified-developer versus unverified-developer, and it cuts across both channels.

That matters for attribution because install friction isn’t evenly distributed. A verified developer’s APK still installs with a single tap; an unverified one now requires the user to click through additional warnings, and in some device configurations may not install at all. If your app or an SDK dependency you ship isn’t from a verified publisher, your sideload conversion rate can drop for reasons that have nothing to do with your landing page, your APK size, or your onboarding flow — and without a way to separate “user abandoned at the new verification warning” from “user abandoned for an unrelated reason,” that install-rate dip looks identical to every other kind of funnel drop-off in your dashboards. Teams that distribute outside Play — enterprise app catalogues, direct-download funnels, alternative Android app stores under EU Digital Markets Act rules — are the most exposed, since they don’t get Play’s install analytics as a fallback.

Data Points to Track

  • Install source flagged as Play Store, verified sideload, or unverified sideload, captured at first-open rather than inferred later, since the distinction only exists at install time
  • Verification-warning exposure, if your distribution page or APK host can detect whether the user’s device surfaced the new identity-check screen before install
  • Region of the installing device, since enforcement is currently limited to four countries and will roll out unevenly through 2027
  • Time-to-first-open after download, to catch a lengthening gap that suggests users are hitting friction between download and successful install
  • Developer account verification status for any SDK or bundled component distributed separately, not just your primary app package

Setup Steps

  1. Confirm your Android Developer Console account has completed verification ahead of the region-by-region enforcement dates, so your own installs aren’t the ones hitting the warning screen.
  2. Tag install events with a source dimension that distinguishes Play Store installs from direct-download or sideload installs, if you don’t already carry this split.
  3. Add a region field to install and first-open events, since the same install funnel will behave differently in enforcement regions versus everywhere else for the next several months.
  4. Monitor sideload conversion rate by region separately from your blended global number, so a Brazil- or Indonesia-specific drop doesn’t get averaged away by unaffected markets.
  5. Audit any third-party APKs or plugin installers you distribute (SDKs, companion apps, enterprise tools) for developer verification status, since an unverified dependency can add friction to a flow your own app doesn’t control.

Actionable Insights

Once install source and region are both tagged, a sideload conversion dip in an enforcement country becomes diagnosable rather than mysterious: pull the split between verified and unverified paths for that region and check whether the drop lines up with the 30 September enforcement date rather than anything you changed. For teams relying on direct distribution outside Play — which this requirement affects most directly — the data also tells you whether it’s worth pursuing Google’s free limited-distribution developer account tier (aimed at hobbyists and students) versus completing full verification, based on how much of your actual install volume comes from the newly-restricted regions.

Expert help

Need help tracking this in your app?

Our team sets up analytics pipelines for mobile and web teams every day. Talk to us and get your first events flowing in under an hour.

Talk to an expert