Most apps need three layers of analytics. Store analytics (App Store Connect and Google Play Console) cover impressions, page views, conversion, and downloads. Product analytics (such as Firebase, Amplitude, Mixpanel, or PostHog) cover in-app behavior, funnels, and retention. Attribution (a mobile measurement partner or platform tools) connects installs to marketing sources. Choose tools by the questions you need to answer, your team's skills, and data privacy requirements.
Layer 1: store analytics
App Store Connect and Google Play Console are free and essential. They show the top of the funnel: how often your app appears in search and browse, how many people view the product page or store listing, conversion to downloads, and sources such as search, browse, and referrals. They also report ratings, crashes, and, on Google Play, Android vitals.
These tools are the foundation of ASO measurement, and no third-party tool replaces them fully. Our guides to App Store Connect Analytics and Google Play Console store performance explain how to read their reports.
Layer 2: product analytics
Product analytics tools track what users do inside the app: events, funnels, retention, cohorts, and user paths. Firebase (Google Analytics for Firebase) is widely used, free at large scale, and integrates with Google's ad and BigQuery ecosystem. Amplitude and Mixpanel are known for powerful behavioral analysis and self-serve exploration for product teams. PostHog combines product analytics with session replay, feature flags, and experiments, and can be self-hosted.
Each tool has free tiers and paid plans that scale with event volume or users. The best choice depends on your questions, your team's skills, and how much you rely on a data warehouse. A small team may start with Firebase; a product-led company with complex funnels may prefer Amplitude or Mixpanel.
Layer 3: attribution and marketing measurement
Attribution tools connect installs and in-app events to marketing sources, such as ad networks, campaigns, influencers, and referral links. Mobile measurement partners (MMPs) such as AppsFlyer, Adjust, Branch, Singular, and Kochava specialize in this, including support for SKAdNetwork and AdAttributionKit on iOS. Our mobile measurement partners comparison covers selection.
If you do not run paid acquisition at scale, you may not need an MMP yet. Platform tools, campaign links, and store analytics can cover early needs. Once you spend across several ad networks, independent attribution becomes important for fair comparison and fraud protection.
Choosing by the questions you need to answer
Start with questions, not features. Where do users drop off in onboarding? Which channels bring users who stay? Which features predict retention? How much revenue does each cohort generate? Map each question to the layer and tool that answers it best.
Consider who will use the tool. Product managers and designers benefit from self-serve exploration; data teams may prefer raw exports to a warehouse. Also consider data residency, privacy requirements, and the cost of sending events at your scale.
Privacy and data quality
Analytics must comply with privacy laws and platform rules. Disclose data collection accurately in App Privacy details and the Data safety form, honor consent where required, and avoid collecting more than you need. Our guide to privacy labels and Data safety explains disclosure.
Data quality matters as much as the tool. Define a tracking plan with clear event names and properties, review it regularly, and test events before release. Broken or inconsistent tracking leads to wrong conclusions no matter how sophisticated the platform.
Connecting the layers
The most valuable insights come from combining layers: store conversion by source, product behavior by acquisition channel, and revenue by keyword theme or campaign. Many teams send data from product analytics and attribution to a warehouse, then build dashboards that connect the funnel end to end.
Our guide to setting up an ASO reporting dashboard shows how to bring store metrics and post-install metrics together. Annotate releases, store changes, and campaigns so analysts can interpret trends correctly.
Session replay, crash reporting, and experimentation
Beyond the three core layers, many teams add specialized tools. Crash reporting, such as Firebase Crashlytics, catches stability issues that affect ratings and retention. Session replay and heatmaps show where users struggle in a flow. Experimentation platforms and feature flags let you test changes with a share of users before rolling them out.
Add these when a specific need appears, not by default. Each tool adds SDK weight, privacy disclosure, and maintenance. Stability matters enough for ASO that crash reporting is usually worth adding early, as explained in crash rate and store ranking.
Common analytics stack mistakes
Teams often install several product analytics tools that overlap, sending the same events to each and creating conflicting numbers. Another mistake is tracking hundreds of events without a plan, making analysis slow and confusing. Many apps also neglect store analytics because they are not as flashy, missing the top of the funnel entirely.
Privacy shortcuts are risky. Collecting identifiers without consent or disclosure can lead to store rejection and legal exposure. Finally, buying an expensive tool before defining questions often leads to dashboards no one uses.
A worked example: a startup's analytics stack
A three-person startup launches with App Store Connect, Play Console, and Firebase. It defines 20 core events in a tracking plan, including onboarding steps, the aha moment, and purchases. Weekly reviews combine store conversion with onboarding funnels and day-7 retention.
A year later, with paid campaigns across three networks, it adds an MMP for attribution and exports data to a warehouse. Product managers adopt a behavioral analytics tool for deeper funnel exploration. The stack grows with the team's questions rather than ahead of them.
How to do it, step by step
- List your key questionsWrite the decisions you need data for, such as onboarding drop-off or channel quality.
- Set up store analytics properlyUse App Store Connect and Play Console, including campaign links and source reporting.
- Choose one product analytics toolPick a tool that fits your questions, team skills, budget, and privacy needs, and create a tracking plan.
- Add attribution when spending on adsIntroduce an MMP or platform measurement once you run paid campaigns across several networks.
- Connect and reviewCombine data in dashboards, annotate changes, and review weekly with decisions in mind.
Before and after examples
Illustrative examples written for a generic app in this category, not client results. Swap in your own product, audience, and data.
Install every popular tool at once.
Start with store analytics and Firebase, add an MMP when paid spend grows.
Why it works: A lean stack avoids conflicting data and cost.
Track every tap automatically.
Define 20 core events with consistent names and properties.
Why it works: A clear plan makes analysis fast and reliable.
Separate reports in each tool.
One dashboard linking store conversion, activation, retention, and revenue by source.
Why it works: Connected data reveals what drives growth.
Action plan
- Start from questions, not features
- Use store analytics as the foundation
- Pick one product analytics tool
- Write and maintain a tracking plan
- Add attribution when paid spend grows
- Disclose data collection accurately
Metrics to monitor
- Funnel from impressions to retained users
- Event tracking coverage and accuracy
- Retention and revenue by source
- Time to answer key questions
Record the baseline, release date, audience, markets, and external changes before interpreting movement. Rankings and conversion are useful signals, but a decision is stronger when activation, retention, and business value confirm that the page attracted the right users.
Frequently asked questions
What is the best analytics tool for mobile apps?
There is no single best tool. Most apps use store analytics, one product analytics tool such as Firebase, Amplitude, Mixpanel, or PostHog, and attribution when running paid campaigns.
Is Firebase enough for app analytics?
For many early-stage apps, yes. As questions and teams grow, some add behavioral analytics tools or a data warehouse.
Do I need an MMP?
If you run paid campaigns across several networks, an MMP provides independent attribution and fraud protection. Without paid spend, you may not need one yet.
Can analytics tools replace App Store Connect and Play Console?
No. Store analytics show impressions, page views, and store conversion that in-app tools cannot see.
Keep reading
More in Measurement
Browse all 15 Measurement guides
Work with ASOWin
Primary sources
Platform capabilities and limits can change. Verify current requirements in these official resources:
