# Mobile App Analytics: The Indie Dev Stack > Build your mobile app analytics stack from scratch — what App Store Connect and Play Console give free, which SDK to pick, and the 6 events that matter. - **Author:** Peter Sutarik - **Published:** August 4, 2026 - **Tags:** mobile app analytics, indie dev, aso, app store connect, play console - **Reading time:** 12 min - **Canonical:** https://trysonar.app/blog/mobile-app-analytics-indie-dev-stack --- ## Mobile App Analytics Tools: What You Actually Need (and What You Can Skip) Most indie developers either instrument nothing or instrument everything. Both cost you. Instrument nothing and you ship blind — you cannot tell whether a keyword change moved downloads or a pricing tweak moved revenue. Instrument everything and you drown in dashboards, burn hours configuring event schemas, and still miss the three numbers that would have changed your roadmap. The right mobile app analytics stack for an indie developer has three layers: free platform consoles (App Store Connect and Google Play Console), one lightweight event-analytics SDK, and an ASO tool that connects store search data to what your users actually do. This article covers what each layer gives you, what it does not, and the six events worth instrumenting before anything else. ## Layer 1: The Free Console Data You Already Have App Store Connect and Google Play Console ship analytics dashboards at zero cost. Before adding any third-party tool, extract everything these give you — most indie devs leave data on the table here. ### What App Store Connect Provides Apple's [App Store Connect analytics dashboard](https://trysonar.app/blog/app-store-connect-analytics) reports impressions, product page views, app units (first-time downloads), re-downloads, sessions, active devices, retention (Day 1, Day 7, Day 28), and crash data. As of 2026, it also surfaces conversion rates by source type — App Store Search, App Store Browse, Web Referral, and App Referral (source: [Apple App Store Connect Help](https://developer.apple.com/help/app-store-connect/view-app-analytics/view-acquisition-sources)). The critical metric here is the search-to-download conversion rate. If you know your [app store conversion rate](https://trysonar.app/blog/app-store-conversion-rate) and you know the keyword that drove traffic, you can calculate the revenue value of a ranking position. App Store Connect shows you the conversion; an ASO tool shows you the keyword. One limitation: App Store Connect does not report which specific keywords drove impressions. It groups all App Store Search traffic into a single bucket. For keyword-level data, you need a third-party tool or Apple's Search Ads attribution API (source: [Apple Search Ads documentation](https://searchads.apple.com/help/reporting/)). ### What Google Play Console Provides Google's [Play Console analytics](https://trysonar.app/blog/play-console-search-analytics) covers store listing visitors, installers, uninstallers, ratings, crashes (via Android Vitals), and — critically — search query data. Unlike Apple, Play Console shows you the actual queries users typed before landing on your listing, along with impression counts and conversion rates per query (source: [Google Play Console Help — Analyze search queries](https://support.google.com/googleplay/android-developer/answer/6227309)). Play Console also reports acquisition channels (Organic, Search, Explore, Third-party referrals) and lets you run store listing experiments (A/B tests on icons, screenshots, and descriptions) natively (source: [Google Play Console Help — Run store listing experiments](https://support.google.com/googleplay/android-developer/answer/6227309)). The gap: in my experience, Play Console's search query data typically lags by roughly 48 hours, and it does not surface estimated downloads for queries you do not yet rank for. It tells you what happened, not what could happen. ## Layer 2: One Event-Analytics SDK (Not Three) For in-app behavior, you need one analytics SDK. Not three. I have watched indie devs bolt on Firebase, Mixpanel, and Amplitude simultaneously, tripling their data-integration surface for marginal gain. Pick one. ### Firebase Analytics (Google Analytics for Firebase) Firebase Analytics is free, has no event-volume cap for the standard tier, and auto-collects screen views, first opens, sessions, and in-app purchases without custom code (source: [Firebase documentation — Automatically collected events](https://firebase.google.com/docs/analytics/events?platform=ios)). It integrates natively with Google Ads, BigQuery (for raw event export), and Crashlytics. The trade-off: Firebase's free reporting UI limits you to 25 custom user properties and 500 distinct event types per project (source: [Firebase usage limits](https://firebase.google.com/docs/analytics/configure-data-collection?platform=ios)), and its cohort analysis is basic compared to Mixpanel or Amplitude. For an indie app with under 50,000 MAU, that is usually enough. ### When to Choose Mixpanel or Amplitude Instead If your monetization model depends on funnel analysis (e.g., a multi-step subscription onboarding), Mixpanel's free tier (20 million events/month as of 2026, source: [Mixpanel pricing page](https://mixpanel.com/pricing/)) or Amplitude's free tier (50,000 MTUs as of 2026, source: [Amplitude pricing page](https://amplitude.com/pricing)) gives you deeper cohort and funnel tools. But the added setup cost is real — plan for 2–4 hours of initial instrumentation and schema design. For most indie apps — utilities, single-screen tools, casual games — Firebase is sufficient and free. ![The 3-layer mobile app analytics stack: free platform consoles, one event SDK, and an ASO tool — each covering a different part of the acquisition-to-retention funnel](https://trysonar.app/blog/mobile-app-analytics-indie-dev-stack-hero.png) *Free consoles cover store metrics. One SDK handles in-app events. An ASO tool connects keywords to downloads.* ## Layer 3: ASO Analytics (Connecting Store Search to Downloads) The free consoles tell you what happened. An ASO tool tells you what could happen — which keywords have volume, how difficult each one is to rank for, and where your competitors sit. This is where analytics for mobile app store performance moves from reactive to proactive. ### What ASO Tools Measure That Consoles Cannot ASO platforms like Sonar index keyword-level data that neither App Store Connect nor Play Console expose. For example, Sonar's keyword index puts "tip calculator" at iOS difficulty 39 and Apple popularity 5 (proxy: 37), while on Android the same keyword drops to difficulty 17 with popularity 42 — a cross-platform gap that shows how differently each store weighs the same niche (source: Sonar API, /api/v1/keywords/search). That cross-platform delta matters for resource allocation. If you ship on both iOS and Android, the analytics from an ASO tool tell you where ranking gains are cheaper. For "subscription tracker," Sonar reports iOS difficulty 43 with 199 competing results versus Android difficulty 24 with just 28 results — the Android market is measurably less saturated (source: Sonar API, /api/v1/keywords/search). ### Estimated Downloads: The Number Consoles Hide Sonar shows "tip calculator" generating an estimated 170 downloads per day for the #1-ranked iOS result, with 147 total results — meaning the top slot captures a disproportionate share of a crowded category (source: Sonar API, /api/v1/keywords/search). That kind of data lets you calculate whether a keyword is worth pursuing before you invest in metadata changes and screenshot redesigns. If you are building your [keyword research workflow](https://trysonar.app/blog/app-store-keyword-research-6-step-workflow), the combination of difficulty score, estimated downloads, and competitor count is the minimum viable dataset. The free consoles do not provide any of these three. ### Choosing an ASO Tool on an Indie Budget A full breakdown of [free ASO tools](https://trysonar.app/blog/best-free-aso-tools) is covered in a separate post, but the short version: if you are tracking fewer than 5 apps and 50 keywords, Sonar's free tier covers keyword difficulty, search volume proxies, and competitor tracking. For the full feature set — historical trends, keyword suggestions, and bulk tracking — [see pricing](https://trysonar.app/pricing). ## The 6 Events Worth Instrumenting First Most mobile app analytics guides list 20+ events. That is too many for an indie dev shipping v1. Here are the six events that, in my experience tracking hundreds of indie launches through Sonar, actually drive decisions. ### 1. First Open (with attribution source) Firebase auto-collects `first_open`, but you need to append the source: organic search, paid ad, referral link, or direct. This single event, when segmented by source, answers the question every indie dev asks: "Where are my users coming from?" Without it, you cannot calculate [user acquisition cost](https://trysonar.app/blog/user-acquisition-cost) for any channel. ### 2. Onboarding Completion Define a single event that fires when a user finishes your onboarding flow (tutorial complete, profile created, or first core action taken). The ratio of `first_open` to `onboarding_complete` is your activation rate. According to a 2023 analysis by Mixpanel covering 1.3 billion user sessions, mobile apps with an activation rate above 25% retain 2.3x better at Day 30 than those below 25% (source: [Mixpanel 2023 Product Benchmarks](https://mixpanel.com/blog/product-benchmarks-report/)). ### 3. Core Action (the "Aha Moment") Every app has one action that correlates with retention. For a tip calculator, it is "calculated a tip." For a subscription tracker, it is "added a subscription." Instrument this as a single named event. Track the count-per-user-per-week, and you have a leading indicator of churn. ### 4. Paywall Impression If you monetize with subscriptions or one-time purchases, fire an event every time the paywall screen loads. The ratio of paywall impressions to purchases is your paywall conversion rate. Industry benchmarks for subscription apps sit between 2% and 10% depending on category (source: [RevenueCat 2025 State of Subscription Apps](https://www.revenuecat.com/state-of-subscription-apps-2025/)). If you are below 2%, the problem is your paywall — not your traffic. If you are building a subscription app, the [monetization strategies guide](https://trysonar.app/blog/aso-subscription-apps-monetization-strategies) covers paywall optimization in depth. ### 5. Purchase Completed Firebase auto-collects `in_app_purchase` on iOS and Android, but verify that the event includes revenue amount, product ID, and whether it is a trial conversion or direct purchase. This event is your revenue source of truth. Cross-reference it with acquisition source (event #1) to calculate LTV per channel. ### 6. Day-7 Return Not a custom event per se — this is a retention metric you derive from session data. App Store Connect and Play Console both report Day-7 retention natively. The reason it belongs in your "first six" is that Day-7 is the strongest early predictor of long-term retention, according to a 2024 analysis by Adjust covering 4,500 apps across 40 countries (source: [Adjust Mobile App Trends 2024](https://www.adjust.com/resources/ebooks/mobile-app-trends-2024/)). | Event | What it answers | Source | |-|-|-| | First Open (with source) | Where do users come from? | Firebase auto-collect + UTM | | Onboarding Completion | Do users activate? | Custom event | | Core Action | Do users get value? | Custom event | | Paywall Impression | Is the paywall seen? | Custom event | | Purchase Completed | Do users pay? | Firebase auto-collect | | Day-7 Return | Do users stick? | Console retention report | ## What You Can Skip (for Now) Mobile app analytics tools proliferate because each one solves a real problem — but not every problem is yours yet. Here is what to defer until you cross ~10,000 MAU or raise funding: - **Heatmap tools** (UXCam, Smartlook). Useful for complex UIs, but most indie apps have 3–5 screens. Watch five screen recordings manually instead. - **Push-notification analytics** (OneSignal, Airship). Only relevant once you have a push strategy. Instrument push opt-in rate as event #7 when you get there. - **Advanced attribution** (AppsFlyer, Adjust, Branch). These matter when you spend on paid acquisition across multiple channels. For an organic-first indie launch, Firebase's campaign attribution plus [Apple's App Tracking Transparency framework](https://trysonar.app/blog/app-tracking-transparency-conversion-impact) is sufficient. - **Revenue analytics platforms** (RevenueCat, Qonversion). Worth adding for subscription apps once you have >100 paying subscribers and need cohort-level LTV analysis. Before that, Firebase purchase events plus App Store Connect financial reports cover your needs. ## Connecting Analytics to ASO Decisions Mobile app analytics are only useful if they feed decisions. The core loop for an indie dev looks like this: 1. **Check console data weekly.** Which keywords drive impressions (Play Console) or which sources drive product page views (App Store Connect)? If you are not reviewing these, start with the [ASO KPIs guide](https://trysonar.app/blog/aso-kpis) to set your baseline. 2. **Run keyword research monthly.** Use an ASO tool to find keywords where difficulty is low relative to volume. The earlier Sonar data illustrates this: "subscription tracker" on Android (difficulty 24, 28 results) is a fundamentally different opportunity than the same keyword on iOS (difficulty 43, 199 results). 3. **Correlate metadata changes with download changes.** When you update your app title, subtitle, or description, mark the date. Then compare the 14-day download average before and after. This is the simplest A/B test in ASO, and it requires zero additional tooling beyond the free consoles. 4. **Watch conversion rate after each release.** A new screenshot set or icon can move your conversion rate 10–30% (source: [StoreMaven analysis cited by Google, 2023](https://support.google.com/googleplay/android-developer/answer/6227309)). Track this in App Store Connect or Play Console after every visual asset change. The mobile app analytics stack is not the goal. The goal is a feedback loop: keyword data tells you what to target, console data tells you whether you hit it, and event data tells you whether the users you acquired actually convert. ## FAQ ### What is mobile app analytics? Mobile app analytics is the practice of collecting, measuring, and interpreting data about how users discover, install, and interact with a mobile application. It spans three layers: store-level data (impressions, downloads, keyword rankings), in-app behavioral data (events, sessions, retention), and revenue data (purchases, LTV, paywall conversion). For indie developers, the free dashboards in App Store Connect and Google Play Console cover the store layer, while an SDK like Firebase handles in-app events. ### Which mobile app analytics tools are free? Firebase Analytics (Google Analytics for Firebase) is free with no event-volume cap on the standard tier. App Store Connect and Google Play Console are free and included with every developer account. Mixpanel's free tier covers up to 20 million events per month, and Amplitude's free tier supports up to 50,000 monthly tracked users (source: respective pricing pages, accessed August 2026). For ASO-specific analytics, Sonar offers a free tier for tracking keyword difficulty and search volume across both stores. ### How many analytics events should an indie developer track? Start with six events: first open (with attribution source), onboarding completion, core action, paywall impression, purchase completed, and Day-7 return. These six cover the full acquisition-to-retention funnel. Adding more events before you act on these six creates noise without signal. Scale instrumentation when your MAU crosses 10,000 or when you have specific product questions these six cannot answer. ### Do I need separate analytics for iOS and Android? You need separate ASO analytics because the two stores have different keyword economies. For example, Sonar's data shows "tip calculator" at iOS difficulty 39 versus Android difficulty 17, and "subscription tracker" at iOS difficulty 43 versus Android difficulty 24 (source: Sonar API). However, for in-app behavioral analytics, Firebase works cross-platform with a single project, giving you unified event data and the ability to segment by OS. ### When should I add a paid analytics tool? Add a paid analytics tool when the free tier's limitations block a specific decision. Common triggers: you need funnel analysis deeper than Firebase provides (switch to Mixpanel or Amplitude), you need keyword tracking for more than 50 keywords (upgrade your ASO tool), or you need cohort-level LTV analysis for a subscription app with 100+ paying subscribers (add RevenueCat). Until you hit one of these triggers, the free stack — consoles plus Firebase plus an ASO tool's free tier — covers the analytics an indie dev actually needs. *Building an app and want to see where the keyword opportunities are before you launch? [Try Sonar free](https://trysonar.app/pricing) — it shows search volume, difficulty, and competitor data for every keyword on iOS and Android.* --- Source: https://trysonar.app/blog/mobile-app-analytics-indie-dev-stack — published by [Sonar](https://trysonar.app), an App Store Optimization platform for keyword research, difficulty analysis, and rank tracking.