UTM tags and campaign tracking explained

A UTM parameter is nothing more than extra text appended to the end of a URL, that GA4 reads and uses to label the visit. ?utm_source=facebook&utm_medium=social&utm_campaign=spring_promo tells GA4 exactly where, how and why that specific click happened. Otherwise, GA4 is left to guess from whatever technical referrer information the browser happens to pass along. The name is a historical leftover. UTM stands for Urchin Tracking Module, from Urchin Software — the analytics company Google acquired and turned into the product that became Google Analytics.

What the UTM parameters actually mean: source, medium and campaign

Parameter	What it specifies	Example
utm_source	Where the click came from	facebook, newsletter, flyer
utm_medium	The type of channel	social, email, print
utm_campaign	Which specific campaign or promotion	spring_promo, winter_sale
utm_content (optional)	Distinguishes between multiple links in the same campaign	header_button vs footer_link
utm_term (optional)	Historically used for paid search keyword tracking	Rarely needed for most small-business use

Why UTM source, medium and campaign parameters only help on links you actually control

UTM tags only do anything if they are attached to the specific link being clicked. They cannot be retrofitted onto traffic that has already arrived without them. This means they matter for links placed in an email newsletter, links shared in a paid social ad, a QR code printed on a flyer or a van, and links placed in a guest post or a partner’s website. They do nothing for organic search clicks, which GA4 already attributes correctly from the search engine referrer. They also do nothing for genuine direct traffic, since typed URLs have no parameters to carry.

The UTM parameter mistakes that quietly break attribution

Tagging internal navigation links. Adding UTM parameters to a link from the homepage to a service page, inside your own site, tells GA4 that a brand new session has started from that campaign the moment someone clicks an internal link. That fragments what should be one continuous session into two. It misattributes the visit’s real original source. UTM tags belong only on links pointing in from outside the site.

Inconsistent naming. utm_source=Facebook and utm_source=facebook are treated as two different sources in most standard reports, because the parameter values are case-sensitive in practice. Establishing a simple, consistent naming convention before tagging multiple campaigns avoids the same channel splitting into several near-duplicate rows in every report.

Losing the parameters through a redirect or a URL shortener. Not every link-shortening or redirect service preserves the full query string through to the final destination automatically. A campaign link that looks correctly tagged in the shortener’s dashboard can arrive at GA4 with no parameters at all, if the redirect strips them. It is worth testing the full click path once before a campaign goes live, not after it has been running for a month.

Building the link with Google’s free UTM builder, without introducing a typo

Google publishes a free Campaign URL Builder tool that generates a correctly formatted tagged URL from a set of form fields, which removes the most common source of error in manual UTM tagging: a missing ampersand, an extra question mark, or a parameter name misspelled by hand. For a business tagging more than the occasional one-off link, using a consistent tool (Google’s own, or an internal spreadsheet with a formula that assembles the URL from separate source, medium and campaign fields) is worth the small extra step, because a malformed parameter typically fails silently — the link still works, it simply is not attributed the way it was intended to be, and the mistake is only found later, if at all, when the numbers do not add up.

Where to check a tagged link in your analytics campaigns

Once a tagged link has been live for genuine traffic, the source, medium and campaign values it carries show up in GA4’s Acquisition reports, broken down at increasing levels of detail — Traffic acquisition shows the session source and medium, and a dedicated Campaigns view groups traffic specifically by the utm_campaign value across every source it was used on. Checking a newly tagged campaign here within the first day or two of it going live is the practical way to confirm the tagging actually worked as intended, rather than waiting until a monthly report and discovering a formatting mistake after most of the traffic has already arrived and been misattributed.

Auto-tagging and manual UTM tracking can conflict

Google Ads has its own automatic tagging mechanism, appending a gclid parameter to a destination URL when auto-tagging is enabled in the ad platform, which GA4 reads to attribute the click without needing manual UTM parameters at all. Manually adding UTM parameters to a Google Ads destination URL on top of auto-tagging is redundant at best, and at worst can conflict with or override the more precise, ad-platform-native attribution auto-tagging already provides. The practical rule: let Google Ads auto-tagging handle Google Ads traffic, and reserve manual UTM tagging for the channels that have no equivalent auto-tagging mechanism of their own — email, organic social posts, print, and links placed on partner sites.

A practical starting convention for UTM source and medium

Channel	Source	Medium
Email newsletter	newsletter	email
Facebook or Instagram post (unpaid)	facebook or instagram	social
Paid social ad	facebook or instagram	paid_social
Printed material with a QR code	flyer (or a specific name per print run)	print
Partner or guest post link	The partner’s name	referral

What to do next

Before the next email send, social post or print run goes out, build the link with consistent, lowercase UTM parameters rather than a plain URL — this is the fix for the “direct traffic looks unexpectedly high” pattern covered on traffic sources explained. If campaign tracking of this kind is being set up as part of a larger build, web development services covers where this typically sits in project scope.