GA4 Source/Medium Cleanup: Fixing Fragmented Traffic Data

Wide monitor showing GA4 traffic report with data mapping notebook

Open your GA4 Traffic Acquisition report and count the distinct source/medium combinations. If you see more than 15-20, you have a fragmentation problem. We’ve seen accounts with 60+ source/medium entries where 8 clean channels would tell the full story.

Fragmented traffic data makes it impossible to answer basic questions: how much traffic comes from paid search vs. organic? Which campaigns drive conversions? Is email or social performing better? This guide covers how to clean it up.

Why Traffic Data Fragments

The most common causes:

  • Inconsistent UTM parameters: One team tags links as utm_source=google, another uses utm_source=Google, a third uses utm_source=google-ads. GA4 treats each as a different source.
  • Missing UTMs on paid campaigns: Google Ads auto-tags with gclid, but Meta, LinkedIn, and email platforms need manual UTM tagging. Without them, traffic shows as referral or direct.
  • Referral spam: Bot traffic from random domains showing up as legitimate referral sources.
  • Internal referrals: Your own subdomains (blog.example.com, shop.example.com) showing as referral traffic instead of being excluded.
  • Email client referrals: Gmail, Outlook, and Yahoo appearing as referral sources when email links don’t have UTMs.

Step 1: Audit Current State

In GA4, go to Reports > Acquisition > Traffic Acquisition. Set the date range to the last 90 days and look at the Session source/medium dimension. Export to a spreadsheet.

Group the entries into these categories:

  • Legitimate and clean: google / organic, google / cpc, (direct) / (none)
  • Fragmented but same source: google / cpc, Google / cpc, google-ads / cpc (these should all be one)
  • Missing UTMs: facebook.com / referral (should be facebook / paid_social if from ads)
  • Internal referrals: your own domains appearing as referral sources
  • Spam/bot: unfamiliar domains with high sessions and 0% engagement rate

Step 2: Fix at the Source

The only permanent fix is to standardize UTM tagging at the source:

Create a UTM naming convention document:

  • Always lowercase: utm_source=google, never Google
  • Use consistent medium values: cpc for paid search, paid_social for paid social, email for email campaigns, referral for organic referrals
  • Campaign names should follow a pattern: 2026-q2-brand-search

Tag every link that leaves a platform you control:

  • Email campaigns: every link gets UTMs
  • Social media posts: UTM all links, including organic posts
  • Paid campaigns on Meta, LinkedIn, TikTok: UTM template at the campaign level
  • Partner/affiliate links: provide pre-tagged URLs

Step 3: Fix Existing Data in GA4

You can’t retroactively change historical data in GA4, but you can clean up going forward:

Unwanted referrals: In GA4 Admin > Data Streams > your stream > Configure tag settings > List unwanted referrals. Add your own domains and any payment providers (stripe.com, paypal.com) that cause false referral sessions.

Internal traffic filtering: In Admin > Data Streams > Configure tag settings > Define internal traffic. Set your office IP ranges so internal testing doesn’t pollute production data.

Channel grouping: GA4’s default channel grouping uses rules to map source/medium pairs to channels. If your UTMs are consistent, the default grouping works well. For custom needs, create a custom channel group in Admin > Data display > Channel groups.

Step 4: Validate

After implementing UTM standards:

  1. Wait 7-14 days for new data to accumulate
  2. Check the Traffic Acquisition report again
  3. Compare the number of source/medium combinations: it should be significantly lower
  4. Verify that key channels (paid search, organic, email, paid social) are capturing all their traffic correctly
  5. Check for new fragmentation as teams launch new campaigns

Want Us to Handle This?

Source/medium cleanup touches UTM governance, GA4 configuration, team processes, and often historical data analysis to understand what went wrong. It’s one of the most common projects we do.

Our Custom Analytics & Reporting service includes source/medium cleanup as a core deliverable, along with Looker Studio dashboards and a UTM governance framework your team can follow.

Get Analytics Help

Scroll to Top