Data Panda brings your Play Console data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your product, marketing and finance teams use every day.
Android Market launched on 22 October 2008 and was rebranded to Google Play in March 2012. The developer-facing portal is Play Console, where install and uninstall counts, ratings and reviews, sales reports, subscription analytics, store listing experiments, pre-launch reports and the Android vitals quality metrics all live.
Google's service fee on Play is 15 percent for the first one million US dollars of revenue per developer per year and 30 percent above that, with auto-renewing subscriptions sitting at 15 percent from day one. The structure differs from Apple in two ways that matter for reporting: the small-business break is automatic per developer account rather than enrolment-gated, and subscription commission does not step down at the year-two anniversary because it never started at 30 percent.
Play Console also exposes things App Store Connect does not, mostly because Android ships on thousands of device models. Reach and devices breaks installs and active users by Android version, OEM and form factor. Android vitals reports user-perceived crash rate and ANR rate against published bad-behaviour thresholds (1.09 percent crash, 0.47 percent ANR overall, 8 percent per individual phone model) that affect store visibility once an app crosses them. Internal, closed and open testing tracks each get their own install and feedback stream before a build moves to production. Pulled into a warehouse, that data sits next to your CRM, your accounting and your other paid channels, and the Android line in the group P&L stops being a separate spreadsheet.
Sales, subscription cohorts, crashes and ANR rate on the same row, per country and Android version.
Let Play Console events trigger work in the rest of your stack.
Use Play data to score Android acquisition and predict where the next bad-behaviour flag will land.
Internal tools on Play Console data that the console UI does not give you.
A list of concrete reports, automations and AI features we have built on Google Play Store data. Pick the one that matches your situation.
Which Android versions and device models are we one bad release away from being demoted on?
Crash and ANR rate per app version, broken down by Android version and device model, against the 1.09 and 0.47 percent overall thresholds and the 8 percent per-phone-model threshold. Surfaces the device classes where a single regression would push the app over Google's bad-behaviour line and into reduced store visibility.
How big is the gap between Android installs ever and Android users active last month?
Lifetime install count next to 28-day active devices, per app and per Android version. Reframes the install number that the marketing deck quotes against the active base that drives subscription revenue, and shows where the drop-off concentrates by Android version.
Did the last store listing experiment pay back?
Conversion lift from each store listing experiment joined to twelve months of subscription and IAP revenue from those installs. Separates the variants that won on first-install from the ones that won on paying-user yield, which is rarely the same shortlist.
Play gross, Google fee at the 15 or 30 percent rate that applied that month, and the net payout per country and entity. The Android revenue line in the consolidated P&L matches the bank, not the Play Console headline.
Android subscribers and in-app buyers showing up in the CRM with their plan, country and lifetime value, joined where consented to the website and ad-channel touches that brought them in.
Crash and ANR rates per Android version and device model in one view with install volume and review sentiment. Product-ops sees the bad-behaviour-threshold risk before Google's daily check finds it.
Play install, IAP and subscription events sit next to GA4 app and web events in the warehouse, joined where consented through the Firebase user id. Marketing sees behaviour from the first website visit through the Android install to the first paid renewal, instead of separate paid-install reports per surface.
Play and App Store sales, subscription cohorts, install volume and crash rate land on a shared schema in the warehouse. Product and finance compare Android and iOS on revenue, churn and quality without rebuilding a Google Sheet every quarter.
Paid Android installs, subscription starts, plan changes and cancellations land on the matching HubSpot contact, joined on the email or device id where available. Customer success and lifecycle email run on the same Android lifecycle Play Console records, not on a separate export.
For products that sell through both Play billing and Stripe on the web, the two revenue streams arrive in the warehouse with a shared customer key. MRR, churn and LTV are calculated across surfaces, instead of running two separate revenue reports that never quite reconcile.
You keep the reporting tool you already have. We connect it to the warehouse where your Google Play Store data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
Google Play charges 15 percent on the first one million US dollars of revenue per developer per year and 30 percent on revenue above that line, with auto-renewing subscriptions sitting at a flat 15 percent regardless of yearly revenue. Once sales and financial reports are pulled, every revenue line in the warehouse carries the gross amount, the rate that applied that month and the net payout, so finance and product see the same number.
Android vitals reports user-perceived crash rate and ANR rate against published thresholds: 1.09 percent crashes and 0.47 percent ANR's overall, 8 percent per individual phone model. Apps that cross those lines lose store visibility and may show warnings on the listing. Pulling vitals next to install and revenue data lets you see the device classes where a quality regression is also a paid-acquisition risk, before Google's daily check finds it.
We review your Google Play Store setup and the systems around it. Together we pick the first thing worth building.