Starting 22 July 2026, Google Play makes US app and game listings — name, icon, description, screenshots, video — available to enrolled third-party US Android app stores by default, under a US court order. Developers can opt out per app through Play Console, but if you do nothing, your listing is shared. Downloads initiated through a third-party store still route through Google Play and still carry Play’s service fee, but the discovery surface just multiplied: the same listing can now be the entry point for an install from Google Play directly or from any number of third-party storefronts, each with its own policies and none governed by Play’s content rules.
For install attribution, this is a bigger deal than it looks. Most attribution stacks assume a single canonical source of truth for “how did this user find us” — one store, one referrer format, one set of install parameters. Multiply the storefronts and you multiply the ways an install can arrive with incomplete, inconsistent, or entirely absent attribution data, right as the volume of installs from unfamiliar sources starts climbing. Teams that don’t track store-of-origin separately from install source in the classic sense will see a growing “unknown” bucket and have no way to tell whether that’s organic third-party-store discovery, a broken referrer, or something worse.
Data Points to Track
- Install source split by originating storefront — Google Play direct versus each enrolled third-party store — not just the usual organic/paid/referral breakdown
- Referrer completeness rate per storefront, since third-party stores aren’t obligated to pass the same install-referrer parameters Play does
- Opt-out status per app/listing, logged alongside install data so a sudden shift in source mix can be checked against a preference change in Play Console rather than assumed to be organic
- Post-install activation and retention, segmented by storefront, to see whether third-party-store users behave differently from Play-direct users
- Unattributed/unknown-source install rate, tracked as its own trend line so growth there is caught early rather than absorbed into “organic”
Setup Steps
- Confirm your opt-in/opt-out preference in Play Console before 22 July 2026 for every app, and log that decision alongside your analytics config so it’s auditable later.
- Extend install-source tagging to capture storefront identity, not just the existing organic/paid categories — add a distinct property for “originating store” on the first-open event.
- Build a referrer-completeness check that flags installs missing expected parameters, rather than letting incomplete data fall silently into a default bucket.
- Segment your standard activation and retention dashboards by storefront from day one, so any difference is visible immediately rather than discovered weeks into a shift you can no longer diagnose.
- Set a threshold alert on the unattributed-install rate, since a sharp rise right around the 22 July rollout is the clearest early signal that referrer data isn’t surviving the third-party-store path.
Actionable Insights
A rising third-party-store install share with retention comparable to Play-direct traffic is a genuine new acquisition channel worth investing in deliberately. The same rising share paired with weak referrer completeness and poor early retention is a data-quality problem first and a channel-quality question second — fix the attribution gap before drawing conclusions about the channel itself.
If the unattributed bucket grows without a corresponding rise in tagged third-party-store installs, that’s a sign referrer data is being dropped somewhere in the funnel rather than a genuine increase in untraceable organic discovery — worth chasing down before it distorts every acquisition report downstream.
Related Resources
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