integrations
Connect payments. Attribute revenue.
Paste one webhook URL into your payment provider and each payment reaches Vero tied to the visit and the traffic source that brought it, without cookies.
- Payments
Stripe
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.
client_reference_id - Payments
Lemon Squeezy
Vero verifies every Lemon Squeezy webhook and records the order with the visit that brought it: the tracker adds the session to your checkout links.
checkout[custom][vero] - Payments
Paddle
Vero verifies every Paddle webhook and records the transaction. Pass the visit as custom data when you open the checkout, and the sale is credited to the source that earned it.
customData.vero - API
Your own checkout
Send each sale from your server to the ingest endpoint, with the session id of the visit.
POST /api/revenue
How it connects
All three providers take the same path. The only thing that changes is the field that carries the session.
- 1The visit
The tracker gives each visit a session id, with no cookies.
window.vero.session() - 2The checkout
The checkout module adds it to Stripe and Lemon Squeezy links; on Paddle.js you pass it yourself.
client_reference_idcheckout[custom][vero]customData.vero - 3The signed webhook
Your provider posts the sale to Vero, signed with your site’s secret.
stripe-signaturex-signaturepaddle-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/…
Ask for a place in the beta.
Anyone can join the list. The accounts we pick get Pro free for the whole beta.