Revenue attribution guide
Revenue attribution answers the question that matters: which channel brought the customers who paid? DataEasy does it by linking each payment to the anonymous visitor who made it.
How it works
- The tracking script gives every visitor a random id, stored in the first-party
dataeasy_visitor_idcookie. - When you create a checkout, you read that cookie on your server and pass it to your payment provider as metadata (
dataeasy_visitor_id). - Your payment provider calls DataEasy's webhook when the payment succeeds. DataEasy verifies the signature, reads the metadata and records the payment on that visitor — with its source, campaign, landing page, country and device.
From then on, revenue, revenue per visitor and conversion rate are available in every breakdown, and the customer's full journey (first referrer → pages → goals → payment) appears in the Journey tab.
Pick your provider
| Provider | Metadata field | Guide |
|---|---|---|
| Stripe | metadata.dataeasy_visitor_id | Stripe Checkout |
| LemonSqueezy | checkout_data.custom.dataeasy_visitor_id | LemonSqueezy |
| Polar | metadata.dataeasy_visitor_id | Polar |
What gets recorded
- New payments, subscription renewals and refunds (refunds are subtracted from revenue).
- Amount and currency, plus the customer's name and email as sent by the provider.
- Each payment is stored once: webhook retries from your provider are ignored, so you don't get duplicates.
Payments without a
dataeasy_visitor_id are still recorded, but can't be attributed to a channel. Keep your checkout on the same root domain as your website (or a subdomain with data-domain set) so the cookie is readable.