DataSpice reads three sources: its own first-party web analytics script, Apple App Store Connect, and revenue from Stripe or RevenueCat. Each works independently, none is a prerequisite for another, and only the web script is required. This page is the complete list; anything not on it is not supported.
The web analytics script
The web script is the one source every workspace has, and it is one tag in your page head. It sets no cookies, so no consent banner goes in front of it, and it reports a pageview as soon as the first visitor arrives.
The App Store Connect integration reads your own downloads, proceeds and country breakdown using a read-only API key you create in your Apple account. It puts app performance beside the web traffic that produced it.
The Stripe integration reads your paid revenue so a customer can be traced back to the acquisition source that produced them. It is a read-only authorisation and it is optional.
RevenueCat is the alternative to Stripe for products whose money comes from mobile subscriptions. Choose one revenue source per project; RevenueCat is the one that covers in-app purchases across stores.
The globe is a live country breakdown you can put on your own site as an iframe. Because it runs on the same cookieless data as the rest of the workspace, embedding it adds no tracking to the page it sits on.
What is not supported
Named plainly so nobody has to discover it after signing up.
There is no Google Play integration, and none is planned.
Paddle, Lemon Squeezy, Chargebee and Braintree are not supported as revenue sources.
There is no conversion feedback to Google Ads, Meta Ads or any other ad platform.
There is no data warehouse export. No BigQuery, no Snowflake, no S3.
There is no public API. The API authenticates with a session cookie, so you cannot call it from your own code.