Google Play Console is in the middle of two changes that land in the same place: how a team explains where installs come from. The first is a new set of visibility metrics — Reach and Impressions — that go beyond Store Listing page views to show how often an app surfaces in search and browse results before anyone taps through. The second is a redefined traffic-source attribution model built to reflect multi-step acquisition journeys, replacing a simpler single-touch view with something closer to how users actually discover apps: an ad impression on one day, a search a week later, an install from a completely different session.
Neither change is disruptive on its own, but together they move the ground under any acquisition dashboard built on the old model. A team that has spent months tuning campaigns against last-touch install attribution will see the mix of “sources” shift once multi-touch logic kicks in, even with zero change in actual user behaviour. And a growth report that only tracks installs and conversion rate has no way to distinguish “fewer people are searching for this app” from “the app is being shown less often” — Reach and Impressions exist specifically to separate those two stories, but only for teams already pulling that data into their own reporting rather than glancing at Play Console once a quarter.
Data Points to Track
- Reach and Impressions, tracked weekly per app, alongside existing Store Listing visitors, so a drop in installs can be checked against visibility before anyone assumes a demand or creative problem
- Traffic-source mix under the new multi-touch model, compared against the old last-touch baseline for at least one full reporting cycle, to quantify how much of any “shift” is definitional rather than real
- Time-lag between first exposure and install, where the new attribution model exposes it, since multi-step journeys change how campaign performance should be read at all
- Impression-to-install conversion rate by surface (search, browse, similar-apps), which the new reach data makes possible to isolate for the first time
- Device-level pre-install activation data, relevant for OEM pre-load and device-bundling campaigns, which sits alongside but separate from organic reach
Setup Steps
- Pull Reach and Impressions into the same dashboard as install volume and conversion rate, rather than leaving them inside Play Console’s own UI where they won’t get checked against acquisition anomalies.
- Snapshot the current last-touch traffic-source breakdown before the multi-touch model fully rolls out, so there’s a clean baseline to compare against once the new model is live everywhere.
- Re-tag internal campaign attribution reports to note which attribution model (last-touch or multi-touch) produced a given number, so historical comparisons aren’t made across two incompatible methodologies without a flag.
- Build an alert on Reach or Impressions dropping sharply independent of install-volume alerting, since a visibility drop can precede an install drop by days or weeks.
- If a reporting API or MCP connector for Play performance data becomes available, wire it into the same pipeline as other acquisition sources rather than keeping Play data siloed in its own export.
Actionable Insights
If installs are flat but Reach or Impressions are declining, the problem is visibility — ASO, keyword ranking, or algorithmic surfacing — not demand, and campaign spend won’t fix it. If Reach and Impressions are stable but installs are dropping, look at the impression-to-install conversion rate by surface before touching acquisition budget; a falling conversion rate on a stable audience usually points at listing content, not traffic. And when the traffic-source mix moves after the attribution model change, resist the instinct to reallocate budget immediately — confirm first how much of the shift is the new multi-touch logic re-crediting existing behaviour rather than genuinely different user paths.
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