The DataSpice Stripe integration reads your paid revenue into the same workspace as your web traffic, so a paying customer can be traced back to the acquisition source that produced them. It is a read-only authorisation made from workspace settings, it takes about a minute, and it is entirely optional.
What connecting Stripe gives you
It gives you the revenue ranking of your traffic sources, which is almost never the same as the visit ranking. A source that sent four hundred visitors and no customers and a source that sent forty visitors and three customers are ten to one on a traffic report and reversed on a revenue one.
Without the integration this is an export from two tools and a match on dates, which is slow enough that most founders do it once and never again.
How to connect Stripe to DataSpice
Open workspace settings and choose the revenue integration.
Authorise DataSpice against your Stripe account. The authorisation is read-only.
Pick one revenue source per project: Stripe or RevenueCat, not both.
Historical revenue backfills, and new payments appear as they happen.
What DataSpice reads from Stripe, and what it does not
It reads the revenue figures needed to report money against time and against acquisition source. It does not write anything to your Stripe account, does not create charges, refunds or customers, and does not touch card details. Those never leave Stripe.
The credential is held by the backend and never reaches the browser.
The limits of the join
The join is only ever as good as the attribution underneath it. A customer who arrived with no referrer cannot be attributed by DataSpice or by any other tool, and that is a real share of traffic rather than an edge case. Every visit from an AI assistant app, an email client or a messaging app arrives that way.
Use RevenueCat if your money comes from mobile subscriptions. If you bill through Paddle, Lemon Squeezy, Chargebee or Braintree, there is no integration and the web analytics still works on its own.