Every payment, traced to the visit that started it.

Through a chain: payment to customer, customer to your user id or email, user id to the visitor who called identify, and visitor to their first touch. ProductLense tries the user id in provider metadata first, then the customer email, then a visitor id in metadata, and stores the result on the payment.

First touch: the source, medium, campaign, referrer and landing page of the visitor’s first recorded event get full credit for every payment that customer makes. Each payment is attributed exactly once, so revenue by channel adds up to what you were paid.

Their payments are imported by the 12-month backfill and count in revenue totals, but they have no first touch, so they show as unattributed. If that customer later visits and identifies, a nightly job re-resolves their payments and credits the channel of the first visit ProductLense recorded.

It is strongly recommended. Without it, ProductLense can only match payments to visitors by email or a visitor id placed in provider metadata, and cookieless visitors on different days are separate. One identify call after signup or login links all of a user’s visits and payments.

Yes. On Growth and Scale, the Revenue page shows net revenue retention cohorts split by channel, source or campaign, from month 0 to month 12, as a percentage of month 0. Channels whose customers expand rise above 100%; channels whose customers cancel fall away.