ASOhack
Back to Blog
Methodology

How to Read App Store Connect & Google Play Console Analytics (2026)

The native analytics dashboards from Apple and Google are powerful but confusing. The working guide to understanding the data, what to measure, and what to ignore.

ASOhack TeamMay 19, 20266 min read

Apple's App Store Connect and Google's Play Console give you the most accurate data on your app's discovery + conversion. They're also confusing — many metrics, multiple dimensions, unclear what to action.

This is the working guide.

App Store Connect

Where the data lives

App Store Connect → App Analytics → Your app.

You'll see tabs:

  • Sources: where users came from.
  • Engagement: how they used the app.
  • Acquisition: install funnel.
  • Sales and Trends: revenue.
  • Trends: aggregate metrics.

Sources

Shows where users discovered + installed your app:

Users who installed after searching. Most reliable signal for ASO effectiveness.

What to look for:

  • Impressions (number of times your app appeared in search).
  • Product Page Views (taps to your product page).
  • Conversion Rate (impressions → installs).

App Store Browse

Users who installed from category browsing / featured.

  • Lower volume usually.
  • Indicator of editorial / category fit.

App Referrer

Users who installed from a link in another app (or web).

  • Often from your marketing, social, or organic mentions.

Web Referrer

Users who installed from web links.

  • Your website, blog, paid ads to web → App Store.

App Store Connect

  • Direct from search results or product page (no specific referrer captured).

What "impressions" means

In App Store Connect: number of times your app appeared in a context that COULD lead to install (search, browse, featured).

Important: impressions includes appearances where users didn't engage. So a high impressions number doesn't mean you're being clicked.

What "conversion rate" means

Impressions → Product Page Views → Installs.

App Store Connect shows:

  • Impressions to Product Page Views: % who clicked through.
  • Product Page Views to Installs: % who installed after viewing.
  • Combined conversion: end-to-end.

The combined rate is what matters for ASO comparison.

What "engagement" shows

Daily / Weekly / Monthly Active Users + Sessions per device + Time-spent.

Track over weeks; spot trends. Don't react to daily noise.

What "acquisition" shows

Funnel breakdown: from impression to install.

Spot drop-off:

  • Impression → Product Page View: icon/title/snippet issue.
  • Product Page View → Install: screenshots/video/description/pricing issue.

Sales and Trends

Revenue data:

  • Daily / monthly / quarterly sales.
  • Per-country breakdown.
  • Per-product (if multiple IAPs).
  • Refunds.

For subscription apps, use RevenueCat / Adapty / Apphud for richer subscription analytics. Sales and Trends gives you the basics.

What App Store Connect doesn't show clearly

  • Per-keyword performance (use Apple Search Ads dashboard or paid tools).
  • Cohort retention (use Mixpanel / Amplitude / RevenueCat).
  • LTV (calculate yourself).
  • Causality (correlation only; causation requires testing).

Google Play Console

Where the data lives

Google Play Console → Your app → Statistics + Acquisition.

You'll see:

  • Statistics: installs, ratings, etc.
  • Acquisition reports: store-listing acquisition.
  • Search and discovery: keyword performance.
  • Conversion analysis: per-country, per-source.

Acquisition reports

Shows installs by:

  • Store listing source (search, browse, deep link).
  • Country.
  • Device type.

Useful for identifying where traffic comes from.

Search and discovery

Per-keyword performance. Google Play exposes this directly (unlike Apple, which mostly requires paid tools or ASA).

You can see:

  • Which keywords brought users.
  • How many installs per keyword.
  • Impressions per keyword.

This is one of Google Play's advantages over App Store for ASO insight.

Conversion analysis

Detailed per-country / per-store-listing conversion data.

If you've A/B tested store listings, you'll see results here.

What Google Play Console doesn't show

  • LTV (calculate yourself).
  • Subscription cohort details (use RevenueCat or similar).
  • Per-user behavior in-app (use Mixpanel / Amplitude).

What to actually look at

Daily

  • Yesterday's installs (compare to recent days).
  • New reviews + ratings.
  • Crash-free sessions (App Store Connect's Vitals).

5 minutes.

Weekly

  • Last 7 days conversion rate trend.
  • Top 5 keywords by installs.
  • New review themes.
  • Source breakdown (organic vs paid).

15-30 minutes.

Monthly

  • 30-day trends across major metrics.
  • Per-country performance.
  • A/B test results.
  • Acquisition cost per channel (if running paid).
  • Subscription cohort retention.

1-2 hours.

Quarterly

  • 90-day trends.
  • Year-over-year comparisons.
  • Major category benchmark comparison.

Half day.

Common analytics mistakes

Mistake 1: looking at daily / weekly noise

App Store Connect data has 24-48 hour lag + daily noise. Don't react to single-day movements.

Mistake 2: ignoring per-source data

Looking at total conversion misses that "Search" converts differently than "Browse" or "Referrer."

Mistake 3: ignoring per-country data

US conversion at 5% but Japan at 1% means localization is broken in Japan, even if global average is fine.

Mistake 4: skipping retention

Native analytics show installs well; retention requires deeper analytics tools (RevenueCat, Mixpanel, etc.).

Mistake 5: trusting algorithm-driven numbers

Some numbers (like "active users") have methodology differences. Don't compare across data sources without checking definitions.

Cross-store comparison

Apple App Store Connect and Google Play Console show:

  • Different attribution models.
  • Different aggregation methods.
  • Different lag times.

Don't combine them directly. Treat as separate datasets.

Setting up analytics correctly

Even with native tools, layer in:

  • RevenueCat / Adapty / Apphud for subscriptions.
  • Mixpanel / Amplitude for product analytics.
  • Crashlytics / Sentry for crash monitoring.
  • Apple Search Ads dashboard for paid Apple data.

This stack covers 95% of indie analytics needs. See analytics tools comparison.

Asking the right question

When looking at analytics:

❌ "How did we do last week?" (vague) ✅ "What's our conversion rate trend over 30 days?" (specific)

❌ "Are we losing users?" (vague) ✅ "Is D7 retention declining? Is it specific to a market or all?" (specific)

Specific questions get specific answers.

When metrics conflict

Sometimes App Store Connect shows different numbers than your other tools:

  • Different attribution windows.
  • Different definitions of "installed."
  • Different aggregations.

Trust App Store Connect for store-specific metrics (search, listing conversion).

Trust RevenueCat / similar for subscription metrics.

Trust Mixpanel / Amplitude for in-app behavior.

Run an ASO audit to compare

The free ASO audit provides external benchmarks against category. Cross-reference with your analytics.

Related reading

Try the tools

Ready to Optimize Your App Store Listing?

Try our free ASO tools — no signup required.

Keyword Density CheckerView All Tools