Setup Guide
UTM parameters are the foundation of marketing attribution. Without them, every visitor who arrives from an ad, email, or social post looks identical in your analytics. This guide explains all five UTM parameters, shows you how to build tagged URLs correctly, and covers the naming conventions that keep your data clean for years — not just weeks.
UTM stands for Urchin Tracking Module — a naming convention inherited from Urchin Software, the analytics company Google acquired in 2005 to build what became Google Analytics. The name stuck, and UTM parameters are now a universal standard supported by every major analytics platform.
In practice, UTM parameters are key-value pairs you append to any URL as a query string. When a visitor clicks that URL, the analytics tool reads the parameters and records the session against the source, medium, and campaign you specified — instead of guessing from the HTTP referrer header, which is frequently absent, stripped, or misleading.
# A URL without UTM parameters:
https://yoursite.com/pricing
# The same URL with UTM parameters:
https://yoursite.com/pricing
?utm_source=newsletter
&utm_medium=email
&utm_campaign=march-digest-2026
&utm_content=pricing-ctaThe question mark starts the query string. Each parameter is separated by an ampersand. The analytics tool strips the parameters, records them against the session, and then shows you traffic reports broken down by source, medium, and campaign.
Without UTM parameters, roughly 30-40% of your referral traffic lands as Direct — sessions where the analytics tool could not determine the source. Dark social shares, link previews, and HTTPS-to-HTTP redirects all strip the referrer header. UTM parameters bypass the referrer entirely: the attribution data travels inside the URL itself.
Each parameter answers a specific question about the traffic source. Three are required for any meaningful attribution. Two are optional but valuable for paid campaigns and email marketing.
utm_sourceWhere did the traffic come from?
Identifies which site, platform, or publisher sent the traffic.
googlenewsletterfacebooklinkedinproduct-huntutm_mediumWhat channel or medium was used?
Identifies the marketing channel or type of link used.
cpcemailorganicsocialreferralaffiliateutm_campaignWhich campaign or initiative drove this traffic?
Identifies the specific campaign, promotion, or initiative driving the traffic.
spring-sale-2026product-launchweekly-newsletterbrand-awarenessutm_termWhich keyword or targeting term was used?
Identifies the paid search keyword or targeting term that triggered the ad.
utm+parametersstripe+revenue+trackingmarketing+attribution+toolutm_contentWhich specific link or creative drove the click?
Differentiates between links in the same ad or email — useful for A/B testing creatives.
blue-ctahero-bannerfooter-linkvariant-atext-linkutm_sourceRequiredWhere did the traffic come from?
Identifies which site, platform, or publisher sent the traffic.
googlenewsletterfacebooklinkedinproduct-huntutm_mediumRequiredWhat channel or medium was used?
Identifies the marketing channel or type of link used.
cpcemailorganicsocialreferralaffiliateutm_campaignRequiredWhich campaign or initiative drove this traffic?
Identifies the specific campaign, promotion, or initiative driving the traffic.
spring-sale-2026product-launchweekly-newsletterbrand-awarenessutm_termOptionalWhich keyword or targeting term was used?
Identifies the paid search keyword or targeting term that triggered the ad.
utm+parametersstripe+revenue+trackingmarketing+attribution+toolutm_contentOptionalWhich specific link or creative drove the click?
Differentiates between links in the same ad or email — useful for A/B testing creatives.
blue-ctahero-bannerfooter-linkvariant-atext-linkutm_term
Use for paid search campaigns to capture which keyword triggered the ad. In Google Ads, the ValueTrack parameter {keyword} auto-populates this field for every click — no manual tagging needed.
utm_content
Use to differentiate between multiple links pointing to the same destination within a single email or page. If your newsletter has three CTAs all pointing to your pricing page, tag them cta-top, cta-mid, and cta-footer.
Building tagged URLs is straightforward. The trap is inconsistency across campaigns and team members. Following this five-step process prevents the most common UTM tracking failures.
Create a shared spreadsheet with approved values for utm_source, utm_medium, and utm_campaign prefixes. Get team sign-off before any URLs go live. Retrofitting a UTM taxonomy after months of inconsistent tagging is expensive — disagreements about 'google' vs 'Google' cause double-counting in every report.
Use the Google Campaign URL Builder (campaign-url-builder.googl.com) or any URL builder tool to construct parameter strings without typos. Paste your destination URL, fill in the fields, and copy the generated link.
# Base URL:
https://yoursite.com/landing-page
# After tagging:
https://yoursite.com/landing-page
?utm_source=google
&utm_medium=cpc
&utm_campaign=brand-search-q1-2026
&utm_term=your%20target%20keyword
&utm_content=ad-variant-aUTM-tagged URLs are long and ugly. Use a link shortener (Bitly, Short.io, or your own domain redirect) before posting to social media or including in print. The short URL redirects to the full UTM-tagged destination. Never shorten the UTM string itself — only wrap the final URL.
Click your tagged URL in a private/incognito window, then open your analytics tool and check that the session appears with the correct source, medium, and campaign. Do this for every new campaign before spending budget on it.
Maintain a UTM log: destination URL, all five parameters, the shortened link, channel, date created, and campaign status. This prevents duplicate campaign names, enables historical reporting, and is essential when multiple team members are creating tags.
Build a Google Sheet with columns for each parameter and a CONCATENATE formula that assembles the final URL. This keeps your taxonomy visible to the whole team and produces consistently formatted links every time — no copy-paste errors from switching between a URL builder and your campaign management tool.
The most common UTM tracking failure is not technical — it is naming inconsistency. When different team members tag the same channel differently, your analytics data fragments across dozens of micro-sources. These six rules prevent that.
utm_source=Google
utm_source=google
Google and google are treated as two separate sources in most analytics tools. Lowercase prevents accidental data splitting.
utm_campaign=spring sale
utm_campaign=spring-sale
Spaces get URL-encoded as %20 or + and can break links. Hyphens are safe, readable, and consistent.
utm_campaign=ad
utm_campaign=google-ads-brand-q1-2026
Vague campaign names make it impossible to diagnose what's working when you have dozens of campaigns running.
utm_medium=paid, utm_medium=PPC, utm_medium=ads
utm_medium=cpc (for all paid search)
Without a standardized list, you end up with 10 medium values that mean the same thing — all siloed as separate channels.
Tagging links from /pricing to /checkout with UTMs
Only tag external traffic sources — ads, email, social, partners
UTM parameters reset the traffic source when clicked. Tagging internal links overwrites the original acquisition source for that session.
utm_campaign=email-launch
utm_campaign=email-launch-q1-2026
Campaign names like 'email-launch' are ambiguous after six months. Dates let you compare campaigns across periods without confusion.
Tagging internal links with UTM parameters is the single most destructive mistake in UTM tracking. When a visitor lands from Google Ads (utm_source=google) and then clicks an internally-tagged link, their source resets to whatever your internal tag says. Your Google Ads report loses the conversion. Your internal link gets false credit. This problem is invisible unless you specifically audit for it.
Different marketing channels have different tagging requirements and conventions. Here are correct UTM codes for the four most common paid and owned channels, with the full tagged URLs and channel-specific notes.
googlecpcbrand-search-2026utm+tracking+tool—Use ValueTrack {keyword} to auto-populate utm_term in Google Ads templates.
newsletteremailmarch-digest-2026—cta-buttonTag every link in your email separately using utm_content to see which links get clicks.
linkedinsocialq1-lead-gen—carousel-adLinkedIn auto-appends its own parameters — your UTMs take precedence in GA4 and most tools.
techcrunchreferralpress-mention-march——Use a unique utm_source per partner so you can compare individual referral performance.
googlecpcbrand-search-2026utm+tracking+toolhttps://example.com/?utm_source=google&utm_medium=cpc&utm_campaign=brand-search-2026&utm_term=utm+tracking+toolUse ValueTrack {keyword} to auto-populate utm_term in Google Ads templates.
newsletteremailmarch-digest-2026cta-buttonhttps://example.com/?utm_source=newsletter&utm_medium=email&utm_campaign=march-digest-2026&utm_content=cta-buttonTag every link in your email separately using utm_content to see which links get clicks.
linkedinsocialq1-lead-gencarousel-adhttps://example.com/?utm_source=linkedin&utm_medium=social&utm_campaign=q1-lead-gen&utm_content=carousel-adLinkedIn auto-appends its own parameters — your UTMs take precedence in GA4 and most tools.
techcrunchreferralpress-mention-marchhttps://example.com/?utm_source=techcrunch&utm_medium=referral&utm_campaign=press-mention-marchUse a unique utm_source per partner so you can compare individual referral performance.
UTM parameters are the most widely supported attribution mechanism on the web, but they have real, structural limitations. Understanding these gaps is essential for anyone making marketing budget decisions based on UTM data.
Links shared in WhatsApp, Telegram, Slack, iMessage, and private Facebook messages lose their UTM parameters when the recipient clicks. The session arrives as Direct, even if it originated from a tagged link you shared. Dark social is estimated to account for 20-30% of referral traffic for many B2B and developer-focused products.
A user clicks your LinkedIn ad on their phone (capturing utm_source=linkedin), then converts three days later on their laptop via Direct. The conversion is attributed to Direct — the LinkedIn ad gets no credit. GA4 attempts to stitch sessions with logged-in Google accounts, but this only works when the user is signed in on both devices.
UTM parameters land in the browser and are stored in cookies or localStorage for multi-session attribution. Safari ITP expires JavaScript-set cookies in as little as 24 hours. GDPR consent rejection rates in Europe run 30-40%. The result: a meaningful share of UTM-tagged sessions cannot be attributed to a later conversion.
UTM parameters tell you traffic volume and (if set up) conversion counts. They don't tell you which campaign generated $5,000 vs $500 in revenue. GA4's UTM reports show sessions and goal completions — not the dollar value of those conversions — unless you have a custom e-commerce or revenue integration.
Some platforms — notably Apple Mail, certain ad networks, and link preview scrapers — strip or ignore UTM parameters when the URL is fetched. Shortened URLs that redirect to UTM-tagged destinations generally survive this stripping. Raw UTM-tagged URLs in plain-text email clients are most vulnerable.
UTM reports in GA4 show you which campaigns drove sessions and goal completions. They don't show you which campaigns drove $10,000 vs $1,000 in actual revenue — because UTM parameters live in the browser, and your payment processor (Stripe) has no visibility into browser sessions. This gap is why teams with real marketing budgets need a layer between UTM data and payment data. For a deeper look at the GA4 limitation, see the traffic attribution complete guide.
UTM parameters answer "which campaign sent this visitor." First-party attribution answers "which campaign generated this revenue." These are different questions, and for most businesses making real marketing budget decisions, the second question is the one that matters.
The workflow looks like this: a visitor lands on your site from a Google Ad with utm_source=google&utm_medium=cpc&utm_campaign=brand-q1-2026. Your attribution layer captures and stores those parameters server-side. Two days later, that visitor returns directly, signs up for a trial, and pays $49 via Stripe. The payment is attributed to the Google Ad — not to Direct — because the attribution layer matched the Stripe customer to their original UTM-tagged session.
The tracking script captures utm_source, utm_medium, utm_campaign, referrer, and landing page. These are stored server-side, not in the browser — so they persist through cookie deletion, ITP expiry, and consent rejection.
On the final visit — which may arrive as Direct — the attribution layer recognizes the returning visitor via a server-side identifier and retrieves the original UTM data from session one.
The payment event is matched to the visitor session server-side. Revenue is attributed to the correct UTM source, medium, and campaign — not to the last-touch referrer.
You see not just which UTM campaigns drove clicks, but which campaigns drove $5,000 in revenue vs $200. This is the data that justifies budget increases and cuts.
Attrifast connects UTM data to actual Stripe revenue using this server-side matching approach. The result is a Revenue per Visitor (RPV) dashboard broken down by utm_source, utm_medium, and utm_campaign — showing the dollar value of each traffic source, not just the click volume. It takes two minutes to set up and requires no cookies or consent banners. For more on the UTM-to-revenue connection, see the UTM to revenue tracking feature overview.
For a detailed comparison of attribution models and how they interact with UTM data, see first-touch vs last-touch attribution and how to track which marketing channel drives revenue.
UTM parameters are query string tags you append to URLs to track where website traffic comes from. The five parameters are utm_source, utm_medium, utm_campaign, utm_term, and utm_content. When a visitor arrives via a UTM-tagged URL, analytics tools read these parameters and attribute the session to the correct marketing channel.
No. Only utm_source, utm_medium, and utm_campaign are considered required in practice. utm_term is optional and most useful for paid search keyword tracking. utm_content is optional and most useful for A/B testing ad creatives or differentiating multiple links in the same email.
Yes. GA4 reads UTM parameters natively and uses them to populate Traffic Acquisition and Campaign reports. However, GA4 only reports on session counts and conversion events — it does not connect UTM data to actual revenue from payment processors like Stripe unless you use Measurement Protocol or a third-party integration.
Always lowercase. UTM values are case-sensitive in most analytics tools. 'Google' and 'google' are counted as two separate traffic sources, which fragments your data. Standardizing on lowercase prevents accidental channel splitting.
utm_source identifies the specific publisher or platform that sent the traffic (e.g., google, newsletter, linkedin). utm_medium identifies the marketing channel type (e.g., cpc, email, social). Together they answer: where did the traffic come from, and through what kind of channel? For example: utm_source=google&utm_medium=cpc means paid search from Google.
UTM parameters themselves only capture click and session data. To connect UTM data to revenue, you need an attribution layer that stores the UTM parameters from the first visit and later matches them to payment events in Stripe. Tools like Attrifast do this server-side without cookies, giving you revenue-per-channel data directly from payment records.
Source: Composite of GA4 URL builder docs, Improvado naming-conventions analysis, and HubSpot UTM survey 2024
Every numbered citation in this article links to its primary source below.
Attrifast links every UTM-tagged session to Stripe payments. See which campaigns drive revenue in 2 minutes, no cookies required.
Start tracking UTM revenue →Loved by 500+ users