What Atlas reads from Stripe

DataDetails
PaymentsEvery charge in your full history, with the customer who paid it.
RefundsEach refund, on the charge and the buyer it came from.
Failed paymentsEach failed charge, with the reason it failed.
Plans and renewalsPlan payments and monthly renewals, beside one-off sales.
CustomersStripe customer IDs and emails: the strong IDs Keyring joins on.
Payment methodsHow each buyer paid, for the payment-method mix.

How a Stripe record finds its buyer

  1. 1Import the full historyOn the setup call Atlas brings in your whole Stripe history; webhooks keep it current after that.
  2. 2Join on strong IDsA Stripe customer ID or an email is a strong ID, so each payment joins its buyer automatically. A weak match, like a phone number, waits for a person to approve it.
  3. 3Follow the buyer back to the adPaper Trail lays out everything that buyer did before paying, from the first ad click, and credits the payment under six attribution models.
  4. 4Send the sale backThe sale goes back to Meta and Google as a conversion, matched to the click.

What it feeds

Limits

  • Atlas doesn't connect to accounting tools: it ties revenue to Stripe, and your books stay where they are.

Questions

What does Atlas read from Stripe?

Your full history of charges, refunds, failed payments, subscriptions and customers, kept current by webhook after the first import.

How is a Stripe payment matched to an ad?

Atlas joins each payment to its buyer on the Stripe customer ID or email, then follows that buyer's trail back to the first ad click and credits the sale under six attribution models.

Does Atlas count refunds and failed payments?

Yes. Each refund and failed charge sits on its buyer and offer, with the reason each payment failed, so ads and offers are ranked by the cash they kept.

How do I know the Stripe import is complete?

Data Health shows each import and marks one incomplete if Atlas couldn't fetch everything.