SaaS revenue attribution: how to connect a visit to a payment

What must be connected?

A useful attribution report has three links: payment → visitor → recorded visit → source. A Stripe payment by itself contains an amount and customer context, but it does not automatically reveal which website visit brought that customer to you. A UTM tag on a visit says where that visit came from, but it does not automatically connect to a later payment.

For example, suppose a customer first visits from a comparison article, returns directly a week later, and pays $49 through Stripe. To credit the article under a first-known-source rule, you need a reliable way to connect that Stripe payment to the same tracked visitor. Without that link, the $49 is real revenue with an unknown acquisition source.

Graytower uses eligible net Stripe revenue, reducing a payment's contribution when it is refunded. It keeps currencies separate. Its revenue attribution documentation explains the matching evidence and reporting rules in detail.

How do you improve the payment link?

Carry a trusted identifier from your site into checkout. For a custom Stripe Checkout flow, that can mean placing the Graytower visitor ID in Stripe metadata. If a customer signs in, an identified user can provide another supported link. An observed checkout_started event can help connect a specific Stripe ID to a browser visit, but the event itself is not proof of a completed payment.

Set up the connection before checkout and verify it with a real or test payment. Check that the payment appears in total revenue, then inspect whether Graytower can assign a visitor and source. The payment matching guide covers the supported fields and fallback paths.

Do not treat an email address that happens to look similar, a recent anonymous visit, or a popular campaign as enough evidence to assign a source. A plausible guess makes the chart look complete while hiding an integration problem.

Which source gets credit?

The answer depends on your attribution rule. Graytower's acquisition view uses the visitor's first-known source. If the first recorded visit came from search and a later visit was direct, the acquisition source remains search. “First-known” matters: tracking may have started after the customer's actual first encounter with your product.

That rule makes the report consistent, but it cannot describe every influence on a purchase. An experiment outcome and an acquisition source can both be associated with the same payment; they are different views of that one payment. Read first touch vs last touch attribution for a practical comparison of attribution rules.

What should the report show?

Start with total eligible revenue, then separate it into attributed and unattributed revenue for each currency. Show matching coverage alongside source rankings so readers can judge how much of the revenue is represented. If coverage changes after you improve checkout metadata, source totals may rise without total revenue changing.

Use the attributed portion to investigate patterns, then look at goals, funnels, customer interviews, and experiments before making a causal marketing decision. If the unknown portion is large, diagnose unattributed revenue before comparing channel performance.

The practical goal is a report that makes its evidence visible: what was paid, how it was linked, which source rule was applied, and what remains unknown.