Traffic is a proxy. Revenue is the point. This guide connects your payment provider and passes the visit id with each checkout. Vero then ties every sale to the visit that started it. You rank channels by money instead of clicks.
Traffic and revenue by referrer
Profit by source
Revenue by campaign
Send sales with their visit id
Paste one URL into your payment provider and its signing secret into Vero. Stripe, Lemon Squeezy and Paddle then post every sale, renewal and refund straight to Vero. Each one is verified with a per-site signing secret. Next, turn on the tracker’s checkout module. A click on a Stripe Payment Link or a Lemon Squeezy checkout link then carries the visit id with it. The sale arrives attributed. On Paddle, pass the visit id as customData.vero in your checkout.
Renewals keep the source of the customer’s first attributed payment. A refund comes off the source of the sale it reverses. If you build your own checkout, read the visit id in the browser with vero.session(). Your server then posts each sale to the ingest endpoint with it. The docs show the request.
How does attribution work without cookies?
The visit id leads Vero to the visitor. It gets there through the same salted hash it uses to count visitors. No cookie or stored identifier is involved. From there Vero finds the visit and credits its first touch. The hash rotates daily, so a sale is credited to a visit from the same day. The blog explains why first-touch attribution works without cookies.
The result is a revenue breakdown by source, campaign, referrer, channel and entry page. It shows how much each one earned, not just how many visits it sent.
Reading the revenue view
Sort sources by revenue to find the one that pays. Then read the same money by campaign, by channel and by referrer. A channel with modest traffic but high revenue per visit is usually your best acquisition lever.
Unsure of a term? Read the glossary