Find what makes money
Attribute Stripe revenue to traffic sources
Stop guessing which channel pays. Put revenue next to every source of traffic.
Updated · 1 min read
Most dashboards rank channels by visitors. But a channel that sends a thousand visitors and no customers is worth less than one that sends fifty buyers. To know where to spend your time, you need revenue per source.
Why this matters
Your marketing budget is your time and money. When you can see that a newsletter mention brought $400 and a viral post brought $0, you know what to do more of. Revenue per source also catches slow channels early, before you spend another month on them.
Why most analytics tools can't tell you
Stripe knows who paid but not where they came from. Your analytics tool knows where visitors came from but not who paid. Joining the two usually means UTM spreadsheets, exports and guesswork, so most people never do it.
How MetricRaven does it
MetricRaven imports payments from Stripe with a read-only restricted key. When you pass the visitor ID into your Checkout Session metadata, or link signed-in users, each payment is credited to the visit that first brought that customer. Channels, referrers, campaigns, pages and countries can then be sorted by revenue instead of visitors.
Revenue by first-touch source
Orbit Analytics · synthetic data · last 30 days
How to do it
- Install the tracking script on your site.
- In Settings → Integrations → Stripe, paste a live restricted key with read-only permissions (Connect Stripe).
- Pass the visitor ID as metadata when you create the Checkout Session (Stripe Checkout guide). Payment Links and PaymentIntents have their own guides.
- Call identify when people sign in, so later renewals stay linked to them.
- Open Traffic → Acquisition, switch the sort to revenue and compare channels, referrers and campaigns.
Not on Stripe? The same attribution works with Lemon Squeezy, Paddle, Polar, RevenueCat and the Payments API.