Third-party app stores are live on Google Play in the US. A day-one UA playbook

Google Play began surfacing third-party Android app stores to US users today, July 22. This follows through on the notice Google sent developers on June 22, which set today as the opt-out deadline, and it happens under the 2024 Epic v Google injunction rather than any settlement. Epic and Google jointly withdrew their proposed deal on July 15, which leaves no ambiguity about whether this was coming. The only open question for a UA team is what to check first.

This third-party stores playbook: attribution before anything else

The most immediate risk is a broken or incomplete view of install source. A user who discovers an app through a third-party store listing surfaced inside Google Play may follow a different referral and click path than a direct Play Store install, depending on how that store implements its listing. Confirm with your MMP account team, this week rather than next, that install attribution logic accounts for the new listing surface, and check raw click and install logs for any unattributed spike once traffic starts moving. A gap here will not announce itself. It will just show up as organic installs that were not organic.

Store listing and creative implications

A user's first look at your app inside Google Play may now include competing storefront options nearby, which changes the job the store listing has to do. Think of it as competing on a shelf with several checkout counters rather than competing purely on search ranking against other apps. Screenshots and the icon carry more weight now, and so does the short description, when a user has a live alternative one tap away rather than a full app-switch away. Review these assets this week if nobody has touched them recently.

Budget and bidding, watch rather than react

Nothing on day one suggests this changes CPMs or auction dynamics inside Google's own ad products. Some volume will probably shift over time as third-party stores gain traction; Play Console's opt-out window closing today signals Google expects developer participation. But a same-day bidding response, made for the sake of resembling a response, would react to a theory rather than to data. The useful move now is to instrument. Not to reallocate.

What comes next

Google's compliance obligations from the withdrawn settlement extend beyond store listings, including tighter child-safety rules and restrictions on READ_CALL_LOG verification that took effect from the same July 15 policy cycle. None of that is a UA concern directly, but if your app touches user data categories affected by those rules, a compliance review this week covers more ground than the store-listing question alone. The Epic v Apple track sits on its own slower calendar and has no bearing on anything happening on Android today.

The realistic first-week checklist

Treat today as the start of an observation window, not a one-off task. Pull baseline install-source and organic-share numbers from before July 22 so there is something to compare against once a week of new data has accumulated. Flag the change internally to anyone who reads acquisition dashboards regularly, so a shift in the numbers gets read as a known event rather than an unexplained anomaly that triggers a separate investigation. And hold off on any conclusions about third-party store traffic volume until there is at least two full weeks of data. Day-one and day-two numbers on a rollout like this tend to reflect curiosity and press coverage more than settled user behaviour.

None of this requires a large team response. It requires someone owning the question for the coming fortnight and a shared understanding that the absence of an obvious problem today doesn't mean the change has finished landing.

Related archive reading

These articles provide related context and remain subject to their stated review status.

• The Ledger #6: Play policy, stores, and a quiet Apple
• Creative for third-party stores: what changes when the install button is not Google's