UTM revenue attribution

UTM revenue attribution reports money by campaign fields.

Most teams already use UTMs to measure traffic. The gap is usually further down the funnel: did the campaign create paid accounts, and did those accounts renew, refund, or churn?

The UTM fields that matter

The standard fields are:

• utm_source: the platform or origin, such as newsletter, google, linkedin, partner, or producthunt.
• utm_medium: the broad channel, such as email, cpc, social, referral, or affiliate.
• utm_campaign: the named initiative, such as launch-week, black-friday, or q2-webinar.
• utm_content: the variant, creative, placement, or link.
• utm_term: the keyword or targeting term.

For early revenue reporting, source and campaign matter most. Medium helps group channels. Content and term are useful once paid ads or experiments become important.

Use a simple naming convention

Use lowercase names, hyphens, and stable campaign terms:

utm_source=newsletter
utm_medium=email
utm_campaign=launch-week
utm_content=pricing-link

Avoid mixing Newsletter, email-newsletter, and mail for the same source. Analytics becomes hard to read when naming is inconsistent.

Before publishing a link, check the failure states that most often split reports:

• Mixed case, such as LinkedIn and linkedin.
• A campaign renamed halfway through a launch.
• Spaces or punctuation that differ between tools.
• UTMs added to internal links, which replace useful acquisition context.
• A redirect that drops query parameters before the landing page loads.
• utm_source present but utm_campaign missing, leaving the initiative unclear.

Connect UTMs to checkout

When a visitor arrives with UTMs, AttribIQ stores the campaign context with the session and visitor. Before checkout, your app passes the AttribIQ visitor and session identifiers into Stripe metadata or the generic Payment API.

The payment event can then be joined back to the original campaign context.

campaign visit -> signup -> checkout -> Stripe webhook -> attributed revenue

The critical step is the checkout bridge. If the payment system never receives attribution identifiers, Stripe can tell you that someone paid, but not which campaign created that customer.

Do not let direct overwrite campaigns

A common attribution error is giving all credit to direct traffic because the customer returned later by typing the URL or using a bookmark.

For revenue reports, direct should usually not overwrite a known campaign source by default. If the first visit came from a newsletter and the payment happened two days later in a direct session, first-touch attribution should still credit the newsletter. Session-touch attribution can show that the checkout session was direct.

Both views are useful. They answer different questions.

How to read UTM revenue

Do not rank campaigns only by total revenue. Also look at:

• Paid conversion rate.
• Average revenue per paying customer.
• Refund rate.
• Renewal rate.
• Trial-to-paid conversion.
• Revenue per visit.

A small campaign with high revenue per visit may deserve more attention. A big campaign with high refunds may need better targeting.

For a complete example from tagged visit to paid invoice, renewal and refund, follow the Stripe revenue attribution setup and validation guide. If you are still measuring traffic, start with sources and referrers before adding payment data.

Next steps

Use landing page revenue attribution to see which pages convert campaign traffic. Read direct traffic revenue attribution if direct is taking too much credit.