Store analytics · coming soon
We're building one view from store impressions to installs for both stores. It isn't available yet. Today you can import supported Apple Downloads and Google acquisition reports in Listing updates. Join the waitlist for the rest.
Not available yet · Free waitlist
How it will work
The planned flow. Details may change before launch.
App Store Connect API key, Google Play service account, Apple Search Ads OAuth. All read-only. Five minutes, done.
Impression → product page view → tap → install → retention → revenue. Every step, every store, one chart.
30- and 90-day revenue forecasts with confidence bands. Scheduled CSV and email exports for the whole team.
Features
What we're building: the dashboard you wish App Store Connect and Google Play Console made together.
Will put App Store Connect and Google Play Console in a single funnel view, so you stop tab-switching to answer “why did installs drop?”
Organic search, paid search, browse, referrer, and app referrer will be broken out per funnel step, so you know which channels drive which behaviors.
Will compare any two periods side-by-side with percentage deltas at every funnel step. Did your new screenshots help? The chart will tell you.
Planned 30- and 90-day forward revenue projections with confidence bands, modeled from your last 90 days, to catch trend breaks before they hit the P&L.
Read-only pulls from Adjust, AppsFlyer, Branch, Kochava, Singular, and Tenjin are on the roadmap, layering campaign-level attribution on top of your ASO funnel.
Every chart will export to CSV, and any view will be schedulable as a weekly or monthly email — so you stop writing the same update by hand.
FAQ
The plan: impressions, product page views, taps, installs, retention, revenue, and ad spend — pulled from App Store Connect, Google Play Console, and Apple Search Ads into a single cross-store funnel, so you stop flipping between three dashboards to answer one question.
Planned integrations are App Store Connect (API key), Google Play Console (service account), Apple Search Ads (OAuth), and read-only exports from mobile measurement partners: Adjust, AppsFlyer, Branch, Kochava, Singular, and Tenjin. All of them will be read-only.
It will, at the channel level: organic search, paid search, browse, referrer, and app referrer, each shown as a share of your funnel. MMP integrations will layer in campaign-level attribution if you route it to AppDrift.
That's the plan — any two periods, side-by-side. Compare last week vs. four weeks ago, or the week after a metadata change vs. the week before, with percentage deltas at every step of the funnel.
Apple Search Ads is planned to pull every 4 hours. App Store Connect and Google Play Console will pull daily (Apple's and Google's data is itself delayed by ~24h, so a more frequent pull wouldn't add freshness). Refresh cadence will be visible on every chart.
It's planned. Based on the last 90 days of install and revenue data, AppDrift will project a 30- and 90-day forward revenue window with confidence bands — useful for planning paid budgets and catching trend breaks early.
Mixpanel and Amplitude analyze in-app behavior. Store Analytics will analyze the pre-install funnel — everything that happens before a user is in your app. Most ASO and growth teams run both; they answer different questions.
In development
We're wiring up App Store Connect, Google Play Console, and Apple Search Ads into a single dashboard. Drop your email and we'll let you in as soon as it's ready.
Every ASO or growth team has the same ritual. You open App Store Connect to check yesterday's product page views. Then you open Google Play Console to see how Android held up. Then you open Apple Search Ads to see how your paid placements did. By the time you've pieced together the three views, you've lost the thread of what you were actually trying to figure out — and the numbers don't quite line up anyway because each dashboard aggregates the funnel differently. AppDrift Store Analytics, now in development, is designed to fix this by pulling all three into a single funnel, with consistent definitions and a single time axis.
The unified funnel will go from impression to product page view to tap to install to retention to revenue — every step visible for App Store and Google Play in one chart, with Apple Search Ads overlaid as a paid layer. You'll see at a glance that your iOS conversion dropped 12% last week because your Search tab impression share fell, not because your screenshots got worse. That kind of causal clarity is almost impossible to reach inside Apple's and Google's separate tools.
Channel attribution inside App Store Connect is coarse: organic, paid, browse, referrer. Useful, but it stops short of telling you which specific campaigns or content are driving which slice of your funnel. AppDrift will layer mobile measurement partner data on top — Adjust, AppsFlyer, Branch, Kochava, Singular, or Tenjin — so your campaign-level attribution and your store-level funnel live in the same view. A spike in paid traffic that doesn't translate to retention becomes one hover away from becoming a specific campaign you can pause.
The analytics integrations will be read-only. Nothing in the analytics view will be able to change a campaign or push a listing update you didn't intend, which matters for security reviews and for trust.
Forecasting app revenue usually means a senior data analyst rebuilding the same Sheets file every quarter. AppDrift's forecast will run off the last 90 days of your actual install-to-revenue curve and project the next 30 and 90 days with confidence bands. When the band narrows or widens unexpectedly, you know the underlying trend is shifting — usually a better leading indicator than raw DAU or download counts.
Forecasts will pair especially well with the rest of the AppDrift stack. If the forecast dips after you ship a new metadata set, you'll see the link inside the same dashboard. If it improves after you launch a Custom Product Page targeted at a new audience, you'll see that too — with per-variant attribution flowing from the CPP module, which is also in development.
Store Analytics doesn't replace in-app analytics. Mixpanel and Amplitude answer questions about what users do inside your app. AppDrift Store Analytics will answer questions about what happens before they're ever in your app — the pre-install funnel, the channel attribution, the conversion-rate regressions. Most growth teams run both because they answer fundamentally different questions. For a deeper look at how AppDrift compares to the broader ASO stack, see our comparison of ASO tools in 2026 and our guide to what actually moves App Store rankings.