UTM Tracking Mistakes That Wreck Your Data (and How to Fix Them)

The state of most UTM data

Pull up any Google Analytics account that's been running campaigns for more than six months. Filter by source. You'll find something like this:

• facebook
• Facebook
• fb
• FB-Ads
• facebook.com
• fb_paid

Six entries. One source. And every report that groups by source now treats these as separate channels. Your "Facebook drove 2,000 clicks this quarter" is actually scattered across six rows, and the real number might be 8,000.

This isn't an edge case. It's the default state of every analytics account without enforced naming conventions.

Mistake 1: Case sensitivity

The most common and the easiest to fix. UTM parameters are case-sensitive. Facebook and facebook are different values in GA4, Mixpanel, and every other analytics tool.

The fix: lowercase everything. No exceptions. No "but we capitalize brand names." Lowercase. If your team can't remember, use a tool that forces it. Attri's parameter resolver normalizes case automatically before the data hits your analytics.

Mistake 2: No naming convention document

Every team starts tagging links with whatever feels right. Someone uses paid-social as a medium. Someone else uses social-paid. A third person uses cpc for the same thing.

Without a document that says "these are the allowed values for utm_medium," you're going to end up with dozens of variations that mean the same thing. And merging them after the fact in GA4 is painful. You can create channel groupings, but that's a patch, not a fix.

Write it down. A Google Doc is fine. A shared Notion page works. A two-column table: parameter name on the left, allowed values on the right. Share it with everyone who touches campaign links. Review it quarterly.

Or use naming conventions that enforce the values at link creation time so nobody can deviate.

Mistake 3: Tagging internal links

We covered this in the UTM guide but it deserves its own section here because the damage is severe.

When you add UTM parameters to links between pages on your own site, GA4 creates a new session for each click. A visitor who arrived from Google, clicked three pages, and converted now looks like three separate visits from three different sources. Your attribution is destroyed.

The knock-on effects are worse than the immediate data corruption. Your bounce rate drops (looks great!), your session count spikes (looks like growth!), and your actual conversion paths become invisible. You're making decisions on data that's actively misleading you.

The rule: UTM parameters are for links from external sources pointing to your site. Never for links within your site. Use GA4 event tracking or Attri's pageview tracking for internal navigation data.

Mistake 4: Inconsistent mediums

Most teams use the five default mediums that GA4 recognizes: organic, cpc, email, social, referral. But real marketing is more nuanced than five buckets.

Should influencer partnerships be social or referral? Is a Slack community post social or community? What about a co-marketing webinar link: is that referral, partner, or webinar?

There's no universal right answer. But there's a wrong answer: using different values for the same thing across campaigns. If influencer links are sometimes social and sometimes influencer and sometimes paid-influencer, your channel-level reporting becomes useless.

Pick your mediums. Document them. Stick with them. If you need more granularity than social, that's what utm_content is for. The medium stays consistent, the content differentiates.

Mistake 5: Not auditing existing data

You set up conventions. You shared the doc. You trained the team. Then six months pass and someone new joins, doesn't read the doc, and starts tagging links with "LinkedIn" instead of "linkedin."

Without periodic audits, naming drift is inevitable. Pull your UTM data quarterly and look for:

• Values that look like duplicates (fb vs facebook)
• Values that don't match your convention doc
• Unexpected sources or mediums you didn't define

This takes 30 minutes per quarter. The alternative is discovering the problem in an end-of-year report when it's too late to fix.

Attri tracks corrections in real time. When the resolver auto-corrects "fb" to "facebook," it logs the change. You can see drift as it happens, not months later.

Mistake 6: Ignoring cross-platform attribution

You're running ads on Google, Meta, and LinkedIn simultaneously. Each platform reports conversions. You add them up and get 300. But your actual conversions were 180.

The overlap problem. A visitor sees your LinkedIn ad, clicks it, doesn't convert. Two days later they search your brand on Google, click the ad, and convert. Both LinkedIn and Google claim the conversion. Your UTM data tells a different story: it shows the first touch (LinkedIn) and the last touch (Google), and you can decide which one gets credit.

Without UTMs, you're trusting each platform's self-reported numbers. Platforms are incentivized to claim credit. Your own first-party data isn't.

The fix that scales

All six mistakes come down to the same root cause: relying on humans to follow rules consistently across every link, every campaign, every quarter.

Documentation helps. Training helps. But the only thing that actually prevents naming drift at scale is a system that enforces the rules at the point of link creation.

That's why we built parameter resolution into Attri. Aliases, normalization, and curated value lists mean the wrong value can't make it into your data. Not because your team memorized the convention doc, but because the tool won't let them type "fb" without correcting it to "facebook."

If you're still building links manually, use the free UTM builder. If you're managing campaigns across a team, start with Attri's free plan.