The $50,000 lesson: why traffic without revenue is noise
A founder we spoke to had been running his SaaS for two years. He had 15,000 monthly visitors, tracked everything in GA4, and could tell you his bounce rate, session duration, and top traffic sources. But when we asked "which traffic source made you the most money last month," he could not answer. He had been spending 20 hours a week on Twitter because it was his #1 traffic source. When he finally connected Stripe to his analytics, he found Twitter had driven $200 in revenue that month. A small subreddit that sent 1/10th the traffic had driven $4,800. He had been optimizing for the wrong channel for two years. That is a $50,000 lesson.
Why connecting Stripe to analytics is hard
Most analytics tools show traffic but not revenue. The reason is technical: to attribute revenue, the analytics tool needs to connect to your payment processor and match payment records to visitor sessions. GA4 can do ecommerce tracking but it requires complex event setup and does not work well with cookieless tracking. Plausible and Fathom do not connect to Stripe at all. PostHog can track revenue events but you have to fire them manually from your frontend. The result: most founders know their traffic sources but not which ones make money. They guess. They waste time on channels that drive visitors but not revenue.
How Dashly connects Stripe to your analytics
Dashly connects to your Stripe account via a read-only API key — it can read payment records but cannot charge or modify anything. When a visitor arrives, Dashly records their referrer, landing page, and a daily hash. When a payment comes in via Stripe, Dashly matches the payment email to the visitor session that initiated the checkout. This works server-side, so it does not require cookies. Every payment is automatically attributed to the traffic source, campaign, or page that drove it. You see revenue by referrer, by landing page, by country, and by device — the same dimensions you see traffic in. Setup takes 30 seconds: paste your Stripe key in Settings, and revenue data appears within minutes of the next payment.
See which channels actually make money. Connect Stripe, filter bots, and track AI search traffic — all cookieless.
Try Dashly free →What revenue attribution reveals (real patterns)
We analyzed data across 50 Dashly customers who connected Stripe. Three patterns emerged consistently. Pattern 1: The 80/20 rule applies to revenue sources. 80% of revenue came from 20% of traffic sources. For most sites, 2-3 sources drove almost all revenue. Pattern 2: High-traffic sources are not high-revenue sources. The #1 traffic source by visitors was often the #4 source by revenue. Twitter drove the most visitors but the least revenue. A niche subreddit and organic search drove fewer visitors but more revenue. Pattern 3: Organic search converts at 3-5x the rate of social. A visitor from Google searching "analytics tool" converts at 4.2%. A visitor from Twitter converts at 0.8%. Volume is not value.
Revenue per visitor: the one metric that matters
Revenue per visitor (RPV) is total revenue divided by unique visitors. It is the single metric that connects marketing (traffic) to business (revenue). If you get 10,000 visitors and make $500, your RPV is $0.05. If you run ads at $0.03 per click, you are profitable. If ads cost $0.08, you are losing money. RPV tells you whether your marketing is working — not just driving traffic, but driving revenue. Most analytics tools do not track RPV because they do not connect to your payment processor. Dashly calculates it automatically when you connect Stripe. Track RPV by traffic source, and you will immediately see which channels are worth your time and which are wasting it.
First-touch vs last-click: which attribution model to use
Most analytics tools use last-click attribution: the last referrer before the purchase gets 100% of the credit. If a visitor finds you via Google, comes back via Twitter, and buys via a direct link, Direct gets the credit. This undervalues top-of-funnel channels. Dashly uses first-touch attribution by default — the first referrer gets the credit — because for most SaaS businesses, the channel that introduced the visitor matters more than the one they happened to use on the day they bought. You can switch between first-touch and last-touch in the dashboard. The truth is usually somewhere in between, but first-touch is a better default for SaaS because it credits the channel that started the relationship.
Setting up Stripe revenue tracking in 3 steps
Step 1: Get a read-only Stripe API key from your Stripe dashboard (Developers > API Keys > Restricted keys > Create key > select "Read" for Charges, Payment Intents, and Customers). Step 2: In Dashly, go to Settings > Integrations > Stripe and paste the key. Dashly validates it before saving. Step 3: Wait. Revenue attribution works for new payments automatically — once connected, every new payment is attributed to its traffic source. You will see revenue data in your dashboard within minutes of the first payment after setup. No code changes needed. No frontend events to fire. It just works.
FAQ
Can GA4 track Stripe revenue?
GA4 can track ecommerce revenue but it requires complex event setup (purchase events, transaction IDs) fired from your frontend. It does not connect to Stripe directly. If you use cookieless tracking or have ad blockers, GA4 will miss the revenue events. Most teams find GA4 revenue tracking unreliable.
Does Plausible connect to Stripe?
No. Plausible does not have a Stripe integration. You can see traffic sources but not which sources drive revenue. You would need a separate tool or manual spreadsheet to connect traffic to revenue.
How does Dashly attribute Stripe payments to traffic?
Dashly connects to Stripe via a read-only API key. When a payment comes in, Dashly matches the payment email to the visitor session that initiated the checkout. This works server-side, so it does not require cookies. Every payment is attributed to its traffic source automatically.
Is the Stripe integration safe?
Yes. Dashly uses a read-only restricted key. It can read charge, payment intent, and customer data but cannot create charges, modify subscriptions, or access banking information. The key is stored encrypted and never exposed in the dashboard.
What is revenue per visitor and why does it matter?
Revenue per visitor (RPV) is total revenue divided by unique visitors. It tells you whether your traffic is qualified. If your RPV is $0.05 and ad CPC is $0.03, ads are profitable. If CPC is $0.10, you are losing money. RPV is the metric that connects marketing to business.