Direct traffic revenue attribution

Direct traffic is one of the most misunderstood rows in analytics.

Direct usually means the browser did not provide a useful referrer or campaign parameter. It does not always mean the person typed your URL from memory. It can come from bookmarks, email apps, messaging apps, documents, private browsing, privacy tools, redirects, and missing UTMs.

Why direct takes too much credit

Revenue often happens after a return visit. A customer might first arrive from a newsletter, think for a day, then come back directly and pay.

If your attribution system overwrites the source with every new session, the newsletter loses credit and direct gets the revenue. That makes campaign performance look worse than it is.

The fix is to keep multiple views:

• First-touch source: the earliest known source.
• Last known non-direct source: the latest meaningful source before conversion.
• Session-touch source: the source of the payment session.

Direct can appear in the session-touch view without erasing useful acquisition history.

Exclude payment processor redirects

Payment systems can create misleading referrers. A checkout redirect from checkout.stripe.com is not a marketing source. It is checkout infrastructure.

Exclude payment processor domains from acquisition credit:

• checkout.stripe.com
• Customer portal domains.
• Hosted billing pages.
• Payment confirmation redirects.

Keep those domains in debug logs if useful, but do not let them become source rows in revenue reports.

Use direct as a signal

Direct is not bad. High direct revenue can mean strong brand demand, repeat visits, word of mouth, or private sharing.

But if direct dominates all revenue, investigate:

• Are campaign links missing UTMs?
• Are email links tagged consistently?
• Are internal links incorrectly tagged with UTMs?
• Is checkout metadata missing?
• Are app and marketing domains configured as allowed hosts?
• Are payment redirects excluded?

Attribution rule example

A simple rule works well for early SaaS:

If a session source is direct and the visitor has a known prior campaign, keep the prior campaign for first-touch and last-known-non-direct reports. Still show direct for the payment session.

This makes reports honest. It does not hide that checkout happened in a direct session, but it also does not discard the campaign that introduced the customer.

Next steps

Read first-touch vs last-touch attribution to decide which model answers each question. Use UTM revenue attribution to reduce preventable direct traffic.