Google Play now reports a reach metric for total visibility, click-based store listing CTR, and engagement, retention, and monetization by traffic source, per Google’s I/O 2026 post and Play Console Help. The funnel is visible end to end. Teams reading it in separate silos are the bottleneck.

For years, the argument for keeping UA, ASO, and product metrics in separate dashboards was partly practical: the data lived in different places. Inside Google Play, that’s much less true now. Which means the remaining reason they’re separate is organizational, and that’s a harder thing to fix than a data pipeline.

What new funnel data does Google Play provide in 2026?

Google added a reach metric, click-based store listing reporting, traffic-source breakdowns of downstream value, and new monetization metrics.

From the I/O 2026 “What’s new in Google Play” post and the Play Console Help page on store listing performance, the pieces that matter for a funnel view:

• Reach: a new metric for your app’s total visibility on Play.

• Store listing indirect value: Google says store listing reporting now includes indirect value that wasn’t previously reported.

• Store listing visitors, Install clicks, and CTR: since July 2026, store listing pages count unique users who click Install, Open, or Pre-register, and CTR replaces the legacy conversion rate. We cover that change in detail in our breakdown of Google Play’s store listing metrics.

• Acquisitions by traffic source: the Grow users overview breaks acquisitions down by Google Play explore, Paid and direct, Pre-installs, and Not attributed.

• Downstream value by traffic source: new breakdowns let you analyze engagement, retention, and monetization by where users came from.

• Monetization signals: cart conversion rates in core performance metrics, plus subscriber tenure and churn reasons.

Feature availability can vary by account and rollout, so confirm what’s live in your own console before rebuilding reports around it.

What does the full funnel look like in Google Play now?

It runs from reach to revenue, with a Play metric at most stages and a paid-UA counterpart that lives outside Play Console.

The table is useful mostly because it forces a conversation teams avoid: the same user passes through every row, and no single team owns more than two of them.

Watch the traffic source names: they don’t mean the same thing everywhere

Google Play uses different traffic source categories on different pages, and “paid” in one report isn’t purely paid.

This one catches people. On the Grow users overview, acquisitions split into:

• Google Play explore: users who found you by browsing, including category searches like “racing game.”

• Paid and direct: users who came from an ad, a referral, or a search containing your app’s name or a closely associated brand.

• Pre-installs and Not attributed.

In store listing reports, the traffic sources are different:

• Google Play search: searches for your app’s name or closely associated brand.

• Google Play explore: browsing, including category searches and autocomplete suggestions.

• Ads and referrals: users from an ad or a referral, including the inline install overlay shown outside the Play Store.

Notice the trap. In the Grow overview, someone who searched your brand name sits inside “Paid and direct,” next to your ad traffic. In store listing reports, the same person sits in “Google Play search,” separate from ads. If your UA lead reads one page and your ASO lead reads the other, “how much of our traffic is paid?” gets two honest, different answers. Agree on which page answers which question before the meeting, not during it.

Why do siloed UA and ASO teams misread the same funnel?

Because a blended rate can fall from a traffic-mix change alone, and each team sees only the slice it owns.

Here’s the scenario, with numbers. Your store listing CTR drops from 30.5% to 23.4% over six weeks.

UA says: “Installs are flat because the listing isn’t converting. The screenshots are three months old.”

ASO says: “Search traffic converts exactly as before. UA started sending lower-intent traffic from a new campaign.”

Split CTR by store listing traffic source:

Search held at 31%. Ads and referrals quadrupled in volume and halved in CTR. The listing did nothing wrong; the traffic mix changed. ASO is right this time.

You can take it one step further inside Play Console. Filter traffic source to ads and referrals, and the UTM source and UTM campaign dimensions become available. If one campaign accounts for most of the new low-CTR traffic, you’ve found it. Then the question becomes a budget question: is that campaign’s traffic cheap enough, and valuable enough downstream, to justify its lower CTR? Play Console can’t answer that part. Which brings us to the gap.

The cross-platform gap: Google Play’s funnel ends at Google Play

Play Console shows the Android funnel well, but it doesn’t report Google Ads costs, other ad networks, your MMP, or iOS.

Google is explicit about this. Per Play Console Help, all Google Ads visits are attributed to the ads and referrals traffic source, and Play Console doesn’t report Google Ads impressions or conversions; for those, it points you to your Google Ads account. It has no view of Meta, TikTok, or Apple Search Ads spend. Its retention and revenue breakdowns don’t reconcile with your MMP’s attribution windows. And for most gaming, fintech, and travel apps, iOS is a separate funnel in App Store Connect, with its own definitions.

So you can have excellent visibility into the Android funnel and still be guessing about the decision that matters most: where the next dollar should go.

This is the layer an AI Platform for User Acquisition is built for. Platforms like Appvertiser AI connect Play Console’s funnel signals with App Store Connect, paid network performance, and MMP revenue in one decision layer, then propose budget or creative changes for a person to approve. The native consoles stay essential. The point is reading them together, in context, instead of stitching spreadsheets every Monday. Google’s own AI is moving in a similar direction inside Play, as we covered in our piece on Gemini in Play Console, but by design it stops at Google’s edge.

How to run a full-funnel review every month

Hold one 60-minute monthly review with UA, ASO, and product, built around the funnel and ending with one documented decision.

Attendees: UA lead, ASO lead, product or growth PM, and ideally someone from monetization or data.

• Reach: did total visibility on Play move, and which surfaces drove it?

• Visit and intent: CTR by store listing traffic source. Is any source declining on its own, or is it a mix shift?

• Acquisition: click-to-acquisition rate. If clicks hold and acquisitions drop, look at technical causes, not the listing.

• Engagement and retention: downstream breakdowns by traffic source. Which sources bring users who stay?

• Revenue: cart conversion and churn reasons next to MMP ROAS by cohort. Flag cohorts that retain but don’t pay.

• Cross-platform: what did iOS and the other paid networks do in the same period? Same story or different?

• One decision: end with a single prioritized experiment or budget change, with an owner and a date. Not a status update.

For the ASO side of these decisions, see our ASO creative optimization playbook and AI-driven keyword clustering for ASO.

FAQ

What is the reach metric in Google Play Console? It’s a metric Google announced at I/O 2026 to show your app’s total visibility on Google Play. Google positions it as part of measuring your full marketing impact, alongside traffic-source breakdowns of downstream engagement, retention, and monetization.

Does Google Play show paid and organic store performance separately? Partly. Store listing reports split traffic into Google Play search, Google Play explore, and Ads and referrals. With ads and referrals selected, you can break results down by UTM source and campaign. Play Console doesn’t report Google Ads costs or conversions.

If D7 retention drops, is that a UA traffic quality problem? Not always. Break retention down by traffic source. If organic cohorts hold and paid cohorts drop, traffic quality is the likely cause. If every source drops together, look at the listing’s promise or the onboarding.

Can Play Console replace an MMP for full-funnel analysis? No. Play Console is authoritative for Google Play, but it doesn’t provide cross-network attribution, iOS data, or LTV modeling across channels. Treat it as one essential lens, not the whole picture.

How often should UA and ASO teams review funnel data together? At least monthly, with a short weekly async update during active experiments. The less often they look together, the more likely they are to draw opposite conclusions from the same data.

The handoff

Picture a relay team where every runner trains alone. One drills starts, one drills endurance, one drills pacing, and all of them are genuinely fast. Nobody practices the handoff. That’s most growth teams in 2026: the data for every leg is finally visible, inside Google Play at least, and the baton, your user, passes through every leg whether or not anyone is watching the exchange. Races get lost in the handoffs, not the straights. The fix is reading the funnel as one race, across teams and across platforms, so each handoff is something you can see and time. Making that the default view, instead of a monthly heroic effort, is the job we built Appvertiser AI for.

Sources

• Google — Android Developers Blog: I/O 2026: What’s new in Google Play

• Google — Play Console Help: Understand and grow your app’s user base

Part of our series on how the mobile growth stack is changing. Previous: Creative tagging setup for UA teams · Start of series: Google Play store listing metrics