We Hooked Up Traffic Data With Revenue… The Results Were Wild

Most US teams know their traffic sources. Few know which sources actually drive revenue. When we connected acquisition data to revenue events in a unified analytics platform, we discovered that our "best" channels were overfunded and our real revenue drivers were under-resourced. The insights rewrote our marketing strategy.

For years we ran traffic analytics in one place and revenue in another. We knew how many users came from Google Ads, organic search, and referrals. We knew our monthly revenue. What we didn't know: which traffic source actually drove the money.

That gap cost us. We doubled down on channels that looked good in GA4 but underperformed at the bottom of the funnel. We underinvested in channels that quietly drove our best customers.

Here's what happened when we finally connected the two.

The Setup We Had (And Why It Failed)

Before: Two Worlds

Traffic (GA4):

• Sessions by source/medium
• UTM parameters
• Landing pages
• Conversion events (when we could configure them)

Revenue (Stripe + internal DB):

• MRR, ARR
• Customer LTV
• Upgrade events
• Churn

The connection? Manual. We'd export GA4 data, try to match user IDs with our CRM, and hope the joins worked. Sometimes we got a report. Often we got noise. Never did we get a real-time view of "revenue by traffic source."

The Questions We Couldn't Answer

• Which ad campaign drives the highest LTV customers?
• Does organic search convert better than paid?
• Which referral source leads to expansion revenue?
• Are we spending on channels that don't pay back?

Without traffic and revenue in one place, we guessed. And we guessed wrong.

What We Did

We switched to a unified analytics platform. SingleAnalytics. that captures both:

• Traffic: Page views, source, medium, UTM, referrer (automatic)
• Events: Signup, trial start, purchase, upgrade (custom tracking)
• User identity: Anonymous visitor → identified user (seamless bridge)

Revenue events (purchase, upgrade, plan_change) include value. The platform ties every event to the user's acquisition source. No exports. No pipelines. No manual correlation.

The Results (What We Learned)

1. Google Ads Was Our Worst LTV Channel

We were spending $18K/month on Google Ads. Sessions were high. Signups were decent. We assumed it was working.

When we connected traffic to revenue, we saw: Google Ads customers had the lowest 90-day LTV of any channel. They signed up. They converted. They churned. Our CPA looked good. Our payback period did not.

Insight: We cut Google Ads by 40% and shifted budget to organic content. Revenue didn't drop. It grew. We'd been subsidizing a channel that didn't retain.

2. A Niche Forum Drove Our Best Customers

We had a small presence on an industry forum: maybe 5% of our traffic. We'd never considered it a priority.

Revenue attribution showed: forum users had 2.4x higher LTV than average. They converted slower but stuck around. They upgraded more. They referred others.

Insight: We invested in that community. More helpful posts. More engagement. Forum-sourced revenue doubled in 6 months.

3. "Direct" Traffic Was Undervalued

GA4 showed "direct" as a catch-all. We ignored it: couldn't attribute it, couldn't optimize it.

With unified analytics, we could segment direct traffic. A lot of it was returning visitors, bookmarkers, and email click-throughs (we hadn't tagged everything). Direct traffic had the highest conversion rate of any source.

Insight: We started tagging email campaigns properly. We improved our bookmark/share experience. "Direct" became a segment we could actually understand and nurture.

4. Our Top Referral Partner Was a Surprise

We had a referral program. We assumed our biggest partner by referrals would be our biggest by revenue.

Wrong. A smaller partner, a podcast with a niche audience: drove 3x more revenue per referred user than our top volume partner. Volume and quality were inversely correlated.

Insight: We restructured our referral incentives to reward revenue, not signups. We deepened the relationship with the podcast. Our CAC dropped.

The Framework We Use Now

| Metric | What We Track | |--------|---------------| | Revenue by source | First-touch and last-touch attribution | | LTV by channel | 30, 60, 90-day revenue per user by acquisition source | | Upgrade rate by source | Which channels drive expansion | | Payback period | CAC ÷ revenue per user by channel |

All of this lives in one dashboard. We don't export. We don't correlate. We click and see.

How to Connect Traffic and Revenue

Step 1: Track Revenue Events

Every revenue moment should be an event:

sa.track('purchase', { value: 99, plan: 'annual', currency: 'USD' });
sa.track('upgrade', { value: 199, from_plan: 'pro', to_plan: 'team' });
sa.track('trial_converted', { value: 49 });

Step 2: Ensure Attribution Is Captured

Your analytics platform should automatically attach source, medium, UTM, and referrer to every event. No configuration needed for page views. For server-side or in-app events, pass the attribution context.

SingleAnalytics captures attribution on the first touch and maintains it across the user journey.

Step 3: Segment and Report

Build views that show:

• Revenue by acquisition source
• LTV by channel
• Upgrade and expansion by traffic source

The insights will follow. Some will surprise you. All will inform better decisions.

The Bottom Line

Traffic without revenue context is a vanity metric. Revenue without traffic context is a blind spot. Connecting the two changes everything.

We thought we knew our channels. We didn't. The moment we hooked up traffic data with revenue, our strategy finally matched reality.

---

Ready to see which channels actually drive revenue? Connect traffic and revenue with SingleAnalytics and get the full picture.