Data Panda brings your App Store Connect 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.
The App Store opened in July 2008 alongside iPhone OS 2.0 and is now the only mainstream distribution channel for iOS and iPadOS apps, with separate storefronts for macOS, tvOS, watchOS and visionOS. Developer-facing data lives in App Store Connect: sales and trend reports, financial reports per territory, subscription reports, product page analytics, ratings and reviews, and crash and performance metrics.
Apple takes a commission on paid apps and in-app purchases. The headline rate is 30 percent, with a reduced 15 percent rate for developers enrolled in the Small Business Program (revenue under one million US dollars per calendar year) and for the second year and beyond of an auto-renewable subscription. The same App Store Connect surface is also where Apple Search Ads attribution lands, which is the only first-party way to see paid installs separate from organic ones.
Our connector pulls a metadata table out of App Store Connect today, the Product Type Identifiers reference. That covers what kind of transaction each line in a downloaded sales or financial report is (paid app, in-app purchase, subscription renewal, refund, and so on), which is the join key you need before deeper sales, subscription and analytics data is worth ingesting. Sales reports, subscription reports and Search Ads attribution are available through App Store Connect's reporting APIs and we extend the pull on request, but the default scope is intentionally narrow. The point is to land App Store revenue and install data next to your CRM, your accounting package and your other ad channels, so the iOS line in the group P&L stops being a separate spreadsheet.
Gross sales, Apple commission and net proceeds on the same row, per territory and product.
Let App Store events trigger work in the rest of your stack.
Use App Store data to score paid acquisition and predict churn before the renewal.
Internal tools on App Store data that App Store Connect's UI does not give you.
A list of concrete reports, automations and AI features we have built on Apple App Store data. Pick the one that matches your situation.
How much of our App Store gross lands in the bank?
Gross sales reconciled against Apple's monthly payout per territory and entity, with the commission line broken out. Removes the gap between the App Store Connect headline number and the figure finance has to book, especially across multi-currency payouts.
Which subscriber cohorts survive the year-two commission step?
Year-one paid subscribers tracked into year two, with churn split by acquisition territory and plan. Surfaces the cohorts where the move from 30 percent to 15 percent commission arrives, and the ones that cancel before it does.
Are Apple Search Ads paying for installs we would have got organically?
Search Ads attributed installs joined to subscription and IAP revenue twelve months out, next to organic installs in the same territories. Separates the keywords where paid spend is producing net new paying users from the ones where it is bidding on people who would have downloaded anyway.
App Store gross, Apple commission and net payout joined per territory and entity. The iOS revenue line in the consolidated P&L matches the bank, not the App Store Connect headline.
iOS subscribers and in-app buyers showing up in the CRM with their plan, territory and lifetime value, so account teams stop treating App Store users as a separate database.
Crash, rating and review data tied to the version that shipped them, with paid and organic install volume in the same view. Product-ops stops chasing three dashboards when a release goes wrong.
App Store install and IAP events sit next to GA4 app and web events in the warehouse, joined where consented. Marketing sees cross-platform behaviour from the first website visit through the iOS install to the first paid renewal, instead of separate paid-install reports per surface.
Paid app 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 iOS lifecycle the App Store records, not on a separate export.
For products that sell through both App Store IAP 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.
Subscription starts, renewals, cancels and refund events trigger Klaviyo flows where the matching contact exists, with the iOS plan and territory available as segmentation fields. Win-back and onboarding stop being timed off a webhook from one tool while sending blind on the others.
These are the 1 tables we currently pull from Apple App Store into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.
Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.
You keep the reporting tool you already have. We connect it to the warehouse where your Apple App 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.
The default sync is the Product Type Identifiers reference, the metadata that explains what each line in a sales or financial report represents (paid app, in-app purchase, subscription start, renewal, refund and so on). Sales reports, subscription reports, product page analytics and Apple Search Ads attribution are all available through App Store Connect's reporting and Ads APIs and we extend the pull on request, but the default is intentionally narrow so the connector lands cleanly before the deeper data is wired up.
Apple's standard commission on paid apps, in-app purchases and the first year of an auto-renewable subscription is 30 percent, dropping to 15 percent for developers in the Small Business Program (annual proceeds under one million US dollars) and for the second year and beyond of an auto-renewing subscription. Once sales and financial reports are pulled, every revenue line in the warehouse carries the gross amount, the commission rate that applied and the net proceeds, so finance and product see the same number.
We review your Apple App Store setup and the systems around it. Together we pick the first thing worth building.