Revenue attribution
Revenue attribution links each payment to the marketing channel, campaign or page that brought the paying customer. Analytics tools see visits and billing tools see money; attribution joins them so you can stop guessing which channel to spend more on.
Formula
payment → customer (email or user id) → identity → visitor → first touchMatch each payment’s customer to a user id or email you sent with identify, follow that identity to the visitor who signed up, and read the source, medium, campaign and landing page of that visitor’s first visit.
Worked example
| Payment | $49 from customer [email protected] |
|---|---|
| identify | user_123 with email [email protected] |
| user_123’s visitor | first touch: newsletter, /pricing |
- The email links the payment to user_123.
- user_123 links to the visitor, whose first touch is the newsletter.
The $49 is attributed to the newsletter channel and the /pricing landing page.
How ProductLense shows it
ProductLense resolves attribution when each payment is written, by user id, then email, then a visitor id in the provider’s metadata, and stores the result on the payment row. A nightly job re-resolves payments still unattributed so late identify calls are credited.
ProductLense needs the script, an identify call with your user id (and ideally email in traits) after signup, and a billing connection or the payment API. Putting pl_user_id in the provider’s customer metadata gives the strongest match.
Revenue attribution: questions
- What is revenue attribution?
- Revenue attribution links each payment to the marketing channel, campaign or page that brought the paying customer. Analytics tools see visits and billing tools see money; attribution joins them so you can stop guessing which channel to spend more on.
- How do you calculate revenue attribution?
- Match each payment’s customer to a user id or email you sent with identify, follow that identity to the visitor who signed up, and read the source, medium, campaign and landing page of that visitor’s first visit. For example, a $49 payment from [email protected] is linked through identify to a visitor who first arrived from the newsletter.
- Where does ProductLense show revenue attribution?
- ProductLense resolves attribution when each payment is written, by user id, then email, then a visitor id in the provider’s metadata, and stores the result on the payment row. A nightly job re-resolves payments still unattributed so late identify calls are credited.
- What does ProductLense need to calculate revenue attribution?
- ProductLense needs the script, an identify call with your user id (and ideally email in traits) after signup, and a billing connection or the payment API. Putting pl_user_id in the provider’s customer metadata gives the strongest match.
- How is revenue attribution different from first-touch attribution?
- Revenue attribution is the join between payments and visits; first touch is the rule for which visit gets the credit. ProductLense v1 joins every payment and credits first touch; last touch and linear are planned for v1.1.
Free up to 10k events a month. No card.
Add the script, connect Stripe or any of 14 other billing providers, and see revenue by channel the same day.