Attribute Stripe revenue to its real source.
Paste one webhook URL into Stripe. Every payment then reaches Vero with the visit that produced it. You read revenue by source, campaign, referrer, channel and entry page, without a single cookie.
The visit travels with the payment.
The visit’s session travels with the payment and comes back in the signed webhook.
- 1The visit
The tracker gives each visit a session id, with no cookies.
window.vero.session() - 2The Stripe checkout
The checkout module adds the session to the Payment Link at the click.
client_reference_id - 3The signed webhook
Stripe posts the sale to Vero, signed with your site’s secret.
stripe-signature - 4Revenue by source
Vero joins the sale to its visit: source, campaign, referrer, channel and entry page, without tax and less refunds.
POST /api/revenue/stripe/SITE_TOKEN
Four steps, no code.
- 1In Vero, copy the Stripe webhook URL from the Connect your sales screen.
- 2In Stripe, add it as a webhook destination on the latest API version. Select the four events and paste its signing secret (
whsec_…) in Vero. - 3Turn on the tracker’s checkout module. A click on a Payment Link then carries the session as
client_reference_id. - 4Revenue rolls up by source, campaign, referrer, channel and entry page in your dashboard. Renewals and refunds are included.
https://[your-vero-host]/api/revenue/stripe/YOUR_SITE_TOKEN
checkout.session.completed checkout.session.async_payment_succeeded invoice.paid charge.refunded
What you get
- Revenue by channel, without tax and less refunds
- Renewals keep the source of the customer’s first attributed payment
- Profit per source with your COGS
- Signed webhooks, per-site secret stored encrypted, each event counted once
- IP never stored, and nothing stored identifies a visitor
One sale, from first payment to dispute.
- 1The first sale
In the fictional public demo, a visit from news.ycombinator.com ends in a €99 purchase. Stripe sends checkout.session.completed with the visit in client_reference_id, and Vero stores the sale without tax under that source. The Checkout Session and its first invoice are one sale, so it counts once.
- 2A renewal
If that customer renews, Stripe sends invoice.paid. When the invoice carries no visit, Vero matches the Stripe customer id and credits the renewal to the source of their first attributed payment. A trial’s first invoice that charged nothing is not stored.
- 3A refund
If that customer is refunded, charge.refunded arrives. Vero matches it to the sale by its charge, PaymentIntent or invoice, and subtracts it from that sale’s source, without tax and in the sale’s own proportion. A partial refund subtracts only its part.
- 4A dispute
Vero subtracts refunds only. A dispute or a chargeback is not deducted, so a disputed sale stays in its source’s revenue. Each event counts once, and if Vero fails while processing one it answers with a 5xx, so Stripe retries instead of the sale being lost.
When the numbers do not add up.
The card says “Last attempt rejected: invalid signature”
The signing secret saved in Vero is not the one of the destination Stripe is sending from. Each webhook destination has its own whsec_…, and a test-mode destination has a different one from live: paste the live one when you are done testing. Vero also refuses a signature whose timestamp is more than 5 minutes off.
A sale counts in the total but has no source
The payment reached Vero without a visit id. With Payment Links, turn on the tracker’s checkout module. If your server creates the Checkout Session, send window.vero.session() from the page and set it as client_reference_id. A visit id only counts if it names a visit of this same site.
A test purchase adds nothing to revenue
That is on purpose. A payment with livemode: false is acknowledged with a 200 and not counted, and the card shows “Last attempt ignored: test mode”. That line proves the URL and the secret work. A 404 instead means the site token in the URL is wrong.
Does connecting Stripe require cookies?
No. The tracker adds the session id to the Payment Link at the click, and it comes back in Stripe’s signed webhook. Vero stays cookie-free.
Do I need to write code?
Not with Payment Links. Paste the URL and the secret, and turn on the checkout module. If you create Checkout Sessions on your server, send window.vero.session() from the page. Then set it as client_reference_id.
Are refunds reflected?
Yes. A charge.refunded comes off the sale it reverses and off its source, without tax. A partial refund subtracts only its part. Channels are scored on what you keep.
Is the webhook secure?
Every event is checked against the destination’s signing secret with HMAC-SHA256. A signature older than 5 minutes is refused. The secret is stored encrypted, and a redelivered event counts once.
Keep reading
- Revenue webhooksEvents, signatures, refunds and test mode, provider by provider.
- Install the trackerAttribution starts at the visit: one tag on your site, no cookies.
- Connect your payment provider and pass the visit idPaste one webhook URL into Stripe, Lemon Squeezy or Paddle and pass the visit id at checkout. Each sale arrives with its source.
- How to attribute revenue without cookiesAttribution does not need a persistent identifier. It needs to connect a payment back to the visit that caused it, and that works server-side, at the moment of payment.
- Know which channel brings the paying customers.Cookie-free analytics built for SaaS: attribute trials, activations and revenue to the exact channel, no stored IP, a tracker from 1.2 KB and anomaly alerts.