UTM Campaign URL Builder
History stored locally in your browser, never uploadedAdd tracking parameters to any URL — source, medium, campaign — so analytics knows where each click came from. Templates for common channels included.
Channel templates
Click to pre-fill source and medium. You can still edit before generating.
Campaign details
Generated campaign URL
Fill in the required fields to generate your URL: Required
Batch mode
Runs entirely in your browser — nothing is uploaded
Runs in your browser
Next steps
QR Code Generator
RecommendedGenerate QR codes for URLs, WiFi, text, and more — download instantly.
Schema Markup Generator
RecommendedGenerate structured data markup that helps search engines understand your site.
Meta Tag Generator
Generate optimized meta tags that help your pages rank higher.
Title Tag Analyzer
Analyze your page title and meta description with a live Google SERP preview.
Runs entirely in your browser. No uploads. Your files stay private.
What is a UTM Campaign URL And Why Does It Matter?
A UTM-tagged URL is a regular URL with five extra query parameters that analytics tools — Google Analytics 4, Plausible, Fathom, Matomo — read to attribute the visit to a specific marketing source. Without UTM tags, GA4 sees a Facebook click and a newsletter click as the same generic referrer; with them, you get separate rows in the report.
The five parameters were defined by Urchin Software (the U in UTM) in the early 2000s. Three are required by convention: utm_source (where the click came from — facebook, newsletter, google), utm_medium (the kind of traffic — email, social, cpc, referral), and utm_campaign (the marketing initiative — black-friday-2026, product-launch, spring-promo). Two are optional: utm_term (search keyword for paid campaigns) and utm_content (distinguishes ads or links inside the same campaign).
GA4 is strictly case-sensitive on these values. Facebook and facebook produce separate rows, as do Newsletter and newsletter. The community convention is lowercase, hyphen-separated values (newsletter, spring-promo) and the builder here surfaces a casing hint when you deviate so you don't accidentally fragment your data.
The order of parameters in the resulting URL doesn't matter — analytics tools parse them as a key-value bag. What does matter is consistency across campaigns: if you use 'email' as the medium one quarter and 'newsletter' the next, GA4 reports them as different. Pick a vocabulary at the campaign-planning stage and stick to it.
UTM is for inbound external traffic only. Never tag internal links inside your own site — that overwrites the original source attribution and breaks reporting. If a user arrives from Facebook with utm_source=facebook and clicks an internal link tagged utm_source=blog, GA4 attributes the next pageview to blog and your Facebook campaign loses credit.
For offline campaigns — print ads, billboards, conference flyers — pair a UTM-tagged URL with a QR code so users can scan rather than type. The QR generator on this site reads UTMs straight from the URL. The print/QR template here pre-fills utm_medium=qr so those scans show up in their own segment.
Total URL length matters because some platforms truncate. Twitter trims at 280, Slack previews 200, some email-newsletter editors mangle anything over 250. A long URL with five UTM values can easily push past those limits — the builder warns when total length exceeds 200 characters.
Common Use Cases
01
Email newsletter analytics
Tag the article links in each newsletter so GA4 reports clickthrough rates per subject line, send time, and segment.
02
Social-media campaign tracking
Distinguish organic Instagram posts (medium=social) from paid promotion (medium=cpc) of the same product launch.
03
Influencer attribution
Each influencer gets a unique utm_content value (alice-vs-bob) so you see who actually drove conversions, not just clicks.
04
Print and offline campaigns
QR codes on conference flyers, magazine ads, and billboards point to UTM-tagged URLs that segment those scans by location and event.
Frequently Asked Questions
Yes — Google Analytics 4 treats utm_source=Facebook and utm_source=facebook as distinct sources, fragmenting your data. The community convention is lowercase, hyphen-separated. The builder surfaces a casing hint when your input deviates.
No. Analytics tools parse the query string as a key-value bag — utm_source can come before or after utm_campaign and the report is identical. The order in the URL is purely cosmetic.
Almost never. Internal UTM tags overwrite the original source attribution. If a user arrives from Twitter (utm_source=twitter) and clicks an internal link with utm_source=footer, GA4 credits the next pageview to footer and your Twitter campaign loses the conversion. Internal navigation should be untagged.
utm_term was designed for paid-search keywords (the search term someone typed before clicking your ad). utm_content distinguishes between similar links — two different button copies in the same email, two different ad creatives in the same campaign. They aren't interchangeable, even though both are optional.
There's no protocol limit but practical caps exist: Twitter shows the first ~280 characters, Slack previews 200, many email editors handle up to 2000 cleanly but some truncate at 250. The builder warns at 200 chars; consider shorter campaign names or a URL shortener for very long ones.
Yes — shorten the already-tagged URL. The shortener stores the full UTM-tagged URL on its server and redirects to it; the user's browser sees the redirect resolve and analytics records the UTM parameters from the final URL. The order matters: tag first, shorten second.
No, but consistently. Untagged clicks appear as "direct" or "referral" in GA4 — fine for casual organic posts. Tag every link you'd want to attribute revenue to: paid ads, scheduled email, sponsored content. Skip tagging organic engagement you don't measure (replies, mentions).
Both read the same UTM parameters; only the reporting interface changed when GA4 launched in 2023. You don't need to relabel old campaigns — historical UTM data continues to be parsed correctly in GA4 reports.
No. The builder runs entirely in your browser using the URLSearchParams API. The history feature uses localStorage on your device — nothing is sent to our servers because there are no servers behind this tool.
It deeplinks to our QR Generator with the campaign URL pre-filled. The QR points back to your tagged URL, so any scan is recorded in GA4 with the medium=qr segment (or whatever medium you set). Useful for conference handouts, print ads, and product packaging.
Advertisement