The DataSpice RevenueCat integration reads mobile subscription revenue into the same workspace as your web traffic and your App Store data. Choose it instead of Stripe when your money comes from in-app purchases rather than from web checkout: one revenue source per project, and RevenueCat is the one that covers subscriptions across stores.
When to choose RevenueCat rather than Stripe
Choose RevenueCat when your revenue is in-app purchase revenue. Choose Stripe when your revenue is web checkout. If you have both, pick the one that carries the majority, because a project reads one revenue source and not two.
RevenueCat is also the right choice if you sell on both Apple and Google, because it reports across stores where the App Store Connect integration is Apple only.
How to connect RevenueCat to DataSpice
In RevenueCat, create a read-only API key for the project.
Add it in DataSpice workspace settings as the project's revenue source.
Revenue backfills and then updates as RevenueCat reports it.
What it reads
It reads the subscription revenue figures needed to report money against time and against acquisition source. It writes nothing back, and it cannot change a subscription, issue a refund or alter an entitlement.
The credential is encrypted before storage and used only by the backend.
The limits worth knowing
The attribution caveat is the same as it is everywhere else: a customer who arrived with no referrer is unattributable by any tool. On mobile it is more pronounced, because the path from a web page to an in-app purchase crosses the App Store and loses the referrer on the way.
DataSpice reports the join it can make honestly and does not model the part it cannot.