Revenue attribution
Find the traffic
that pays off.
Connect payments to the sources, campaigns and landing pages that bring customers. See what earns revenue alongside what brings visits.
Sign up with Google for a 7-day trial with up to 10,000 total events. One trial per Google account, no card needed. Team invitations and API keys require a paid plan.
- GoogleOrganic search
- RedditSocial
- DirectReturns to buy
The last non-direct source before the purchase.
Assumes a linked visitor in cookie mode and a 90-day lookback. Direct gets the credit when every eligible visit is direct.
From visit to payment
Give every linked payment a source
- 01
Track the visit
Install the traffic.cx tracker. It records the source, campaign and landing page for your visits.
- 02
Connect your checkout
Connect a payment provider in your site's revenue settings and pass traffic.cx's pageview ID in checkout metadata. In cookie mode, also pass the visitor ID.
- 03
Compare what converts
Open Revenue to compare sources by revenue, paying customers, conversion rate and revenue per visitor. Switch models to see how credit changes.
A provider connection brings in payments; the checkout IDs link them to visits. Missing IDs can leave payments unattributed. Read the setup and attribution guide.
Last non-direct
The default model credits the most recent non-direct visit before the payment, within the lookback window. A direct return does not overwrite an earlier campaign. If all eligible visits are direct, Direct receives the credit.
First touch
Credit the earliest visit in the lookback window. Use it to see what first brought a linked visitor to your site. The default window is 90 days; revenue settings let you choose between 7 and 365 days.
Payment connections
Bring the payments you already collect
Stripe
Checkout, Payment Links, PaymentIntents and subscriptions. Setup guide
Dodo Payments
One-off payments and subscriptions. Setup guide
Lemon Squeezy
Orders and subscriptions. Setup guide
Polar
Orders and subscriptions. Setup guide
Using another checkout?
Send payments from your server through the Payments API, or report purchases from the tracking script. API keys require a paid plan. A verified provider payment can replace a script-reported payment with the same payment ID to avoid counting it twice.
Make the numbers useful
Compare value, not just volume
Revenue per visitor divides net revenue by unique visitors. Compare it across sources and campaigns to spot traffic that brings value, even when its visitor count is small.
Keep refunds in the picture
Revenue is payments minus refunds. Refunds reduce revenue on the date they happen and keep the original payment's attribution. A busy sales day can look different after refunds.
Follow repeat purchases
When a new payment has no visit link, traffic.cx can use the same customer's earlier payment attribution. This helps renewals retain their acquisition source.
Keep missing links visible
A payment without a matching visit or earlier customer payment stays in the totals as Unattributed. You can see the gap instead of assigning a source without evidence.
Start without visitor cookies
In the default cookieless mode, a pageview ID can link a payment to a recorded visit. Cookieless visitor identities rotate daily, so they do not establish a visitor's journey across days.
Optional cookie mode lets a visitor ID link visits across days within your lookback window. It changes your privacy and consent responsibilities. Read the privacy details.
Know what attribution can tell you
Blocked tracking, missing checkout metadata, another device or an expired identifier can leave gaps. Attribution describes the recorded journey; it does not prove that a campaign caused a purchase.
Use it alongside your other business evidence. The worked example above shows how the two models interpret the same linked journey.
See what brings your customers in
Revenue attribution is included in every paid plan. Choose a volume tier that fits your pageviews and custom events.