Integrations·Payments
Connect Stripe with a restricted key. One-off purchases, subscription charges and refunds then arrive in Spreelytics by themselves, each credited to the channel that brought the buyer in.
stripe · payments · 30d
revenue by channel · last-touch · 30-day window
What it does
Payments arrive as purchase events and flow into goals, the overview and the acquisition reports.
Connecting creates the webhook in your Stripe account. From then on, each payment arrives by itself. You do not need to send revenue events.
Put the visitor id in the payment’s metadata. Each payment, including renewals, is then tied to the visit that led to it and credited by last-touch or linear.
Charge in as many currencies as you like. Each payment is converted once into your reporting currency at the rate for the day it happened, then frozen.
How it works
01
In Settings → Revenue, paste a restricted key that can write Webhook Endpoints and read your payments. Connecting creates the webhook for you.
02
Put Spreelytics.getVisitorId() in the metadata as spreelytics_visitor_id: payment_intent_data for one-off payments, subscription_data for subscriptions.
03
From the moment you connect, payments land on the Revenue page, with MRR and ARR for subscriptions, and as purchase events in goals, the overview and the acquisition reports.
Read next
Web analytics
Follow each sale back to the channel that earned it.
Read moreWeb analytics
Turn any page or event into a conversion to track.
Read moreWeb analytics
Break down visitors and revenue by where they came from.
Read moreFAQ
What people ask before they switch it on.
A restricted key with Webhook Endpoints set to Write, and Checkout Sessions, PaymentIntents, Invoices and Charges set to Read. The Open Stripe button in the app picks all five for you. We use the key to create the webhook that delivers your payments and to look up product names. It also reads your past payments when you import them. It never moves money. Use a live key, because test-mode payments would be counted as revenue.
For a one-off Checkout payment, in both the Checkout Session’s metadata and payment_intent_data.metadata. For a subscription, in subscription_data.metadata, so every renewal carries it too.
Payment Links, Buy Buttons and Pricing Tables cannot take a value per visitor, so payments through them are counted without a channel.
It is still recorded and counts toward your totals. It just cannot be traced to a channel. The Channels list counts it as Direct and the Sources list as Direct/None. The URLs and UTM lists leave it out.
Each payment counts as one event, the same as a custom event. Refunds do not count. Payments you import from before you connected do not count either.
Yes, for payments Stripe does not see. The revenue API is in the docs. If you also send a Stripe payment that way under a different id, it is counted twice.
Free up to 100k events a month · no credit card
