Setup Guide
Your Stripe dashboard shows total revenue. But it can't answer the question that matters: which marketing channel generated that revenue? This guide walks you through setting up Stripe revenue tracking by traffic source — from script tag to live dashboard — in under 5 minutes.
Stripe is excellent at processing payments. It shows you gross revenue, net revenue, MRR, churn, and customer counts. But it was built as a payment processor, not a marketing analytics tool. There are four critical revenue metrics that Stripe cannot provide.
Not available
Google Organic: $4,212 · Twitter: $1,780 · Ads: $960
Stripe processes payments server-side. It has no visibility into browser sessions, referrers, or UTM parameters.
Not available
$1.80 from SEO · $4.50 from newsletter · $0.80 from ads
Stripe doesn't know how many visitors each channel sends. Without visitor counts, you can't calculate revenue efficiency.
Not available
Customer first visited via LinkedIn Ad, returned via direct, converted on day 12
Stripe sees the payment but not the marketing journey that led to it.
Not available
utm_campaign=spring-launch: $2,340 revenue from 12 conversions
UTM parameters exist in the browser. Stripe webhooks don't carry UTM data.
Stripe tells you how much money came in. It cannot tell you where that money came from. For any SaaS or ecommerce business spending money on marketing, this gap makes it impossible to calculate ROI by channel — which means budget decisions are based on traffic volume, not revenue.
Before diving into the setup, here's how the available approaches compare. The right choice depends on your technical resources and what metrics you need.
No
No
0 min
$0
Partial
No
4-8 hours
$0
Yes
No
2-5 days
$50-200
Yes
Yes
2 min
$0-29
This walkthrough uses Attrifast as the attribution layer, but the concepts apply to any tool that connects browser sessions to Stripe payments.
Paste a single script tag before your closing </head> tag. The 4KB script captures traffic source data — referrer, UTM parameters, landing page, and channel — for every visitor. No cookies are set, so no consent banner is needed.
<!-- Add to your <head> -->
<script
defer
data-tracking-id="your-tracking-id"
src="https://api.attrifast.com/af.js"
></script>Go to Settings → Integrations → Stripe and click Connect. This uses Stripe OAuth — Attrifast gets read-only access to your payment data. No API keys to copy, no webhook URLs to configure.
When a customer completes a Stripe payment, Attrifast matches the Stripe customer to their original visitor session server-side. Within seconds, the revenue appears in your dashboard attributed to the marketing channel that brought them.
Open the Channels tab to see revenue broken down by traffic source. The RPV column shows the dollar value each visitor from that channel is worth — the single most actionable number for budget allocation.
No webhook configuration. No Measurement Protocol. No BigQuery. No developer time beyond pasting one script tag. The Stripe OAuth connection handles all payment data import automatically — including one-time charges, subscription renewals, refunds, and plan changes.
Once the script is installed and Stripe is connected, here's the kind of data you see in the Channels view. This example is from a SaaS product with $19,562 in monthly revenue across 6 traffic sources.
2,340
$4,212
$1.80
2.1%
890
$1,780
$2.00
1.8%
1,560
$3,900
$2.50
3.2%
1,200
$960
$0.80
0.9%
3,100
$6,820
$2.20
2.8%
420
$1,890
$4.50
5.1%
Look at the RPV column. Google Ads sends 1,200 visitors but generates only $0.80 per visitor. Newsletter sends only 420 visitors but generates $4.50 per visitor — 5.6x more revenue-efficient. Without Stripe revenue tracking by channel, Google Ads looks like a top performer (high traffic). With it, you see Newsletter is where to double down.
If you run a SaaS business with monthly or annual subscriptions, one-time payment tracking only tells half the story. The initial $29 payment matters — but so do the 11 subsequent renewals that turn it into $348 of annual revenue. Effective Stripe revenue tracking must handle the full subscription lifecycle.
checkout.session.completedAttributed to the marketing channel that brought the visitor. If a customer first arrived via a Google Ad and signed up for a $49/month plan, the first $49 is attributed to Google Ads.
invoice.payment_succeededEach renewal is attributed to the same original channel. The second, third, and twelfth payment all count toward Google Ads revenue — building a true LTV picture per channel.
customer.subscription.updatedWhen a customer upgrades from $49/month to $99/month, the revenue increase is attributed to the original acquisition channel. This shows which channels bring customers who expand.
charge.refundedRevenue adjustments are subtracted from the attributed channel. If a Google Ads customer requests a refund, your Google Ads revenue accurately reflects the net amount.
The result: you see not just which channels acquire customers, but which channels acquire customers who stay and grow. This is the difference between optimizing for signups and optimizing for revenue. For more on acquisition attribution models, see First Touch vs Last Touch Attribution.
Even with the right tools, these mistakes create gaps in your revenue data.
Some teams store UTM parameters in Stripe metadata via client_reference_id. This works for direct payment links but fails completely when customers browse your site before paying, start a trial, or return days later. At best, you capture 20-30% of attributions.
Counting trial signups per channel is not revenue tracking. If Google Ads drives 100 trial signups but only 5 convert to paid, while organic drives 30 signups with 15 conversions, the channel with fewer signups is actually 3x more valuable. Track the payment event, not the signup.
Stripe test mode payments can pollute your analytics if your tracking tool doesn't filter them. Verify that your setup only processes live mode webhook events (event.livemode === true).
If you only track the first payment, you miss the 80-90% of subscription revenue that comes from renewals. A channel that brings high-churn customers looks the same as one that brings loyal customers. Track lifetime revenue per channel, not just first-payment revenue.
Revenue tracking without refund tracking overstates channel performance. A channel with a 15% refund rate is significantly less valuable than one with a 2% refund rate — but you can't see this without tracking charge.refunded and charge.dispute.created events.
The best time to set up revenue tracking is before you start spending on marketing. The second best time is now. Here's a simple decision framework.
Without revenue tracking, you cannot calculate ROAS (Return on Ad Spend) by channel. You are flying blind on budget allocation.
Content marketing takes months to compound. If you start tracking now, you'll have revenue data per article/channel by the time you need to decide what to create next.
Referral attribution is notoriously unreliable with UTMs alone. Server-side tracking catches referral revenue that cookie-based tools miss.
Your first 30 days of traffic is the most valuable data you'll ever have. Don't lose those attribution signals — they tell you which launch channels convert.
Source: Stripe webhooks reference + Stripe Billing webhook documentation
Every numbered citation in this article links to its primary source below.
One script tag. One Stripe connection. See which channels drive payments in under 2 minutes.
Start tracking revenue →Loved by 500+ users