Decode and validate any UTM-tagged URL. Parses all 5 UTM parameters (source, medium, campaign, term, content), flags common errors (spaces, uppercase, missing required fields), shows GA4 report preview, and checks for best-practice compliance.
Paste any URL that contains UTM parameters — from an email campaign, paid ad, social media post, or any tracked link. The tool supports all 5 official Google Analytics UTM parameters as well as custom parameters.
Each UTM parameter (utm_source, utm_medium, utm_campaign, utm_term, utm_content) is extracted and displayed with its value. The tool also strips and shows the clean base URL separately from the tracking parameters.
Common errors are flagged: spaces in parameter values (which GA4 splits into separate dimensions), uppercase letters (which create duplicate rows in reports), missing utm_source or utm_medium (required), and special characters that may cause encoding issues. A GA4 report preview shows how the session would appear in Acquisition reports.
UTM parameters (Urchin Tracking Module) are tags added to URLs that tell analytics tools where traffic came from and how it was acquired. The five standard UTM parameters are: utm_source (the specific platform or publisher, e.g. "linkedin"), utm_medium (the marketing channel, e.g. "email"), utm_campaign (the campaign name, e.g. "spring_2024_promo"), utm_term (the keyword for paid search), and utm_content (differentiates ads or links within the same campaign). Without UTM tags, all traffic from links outside Google search appears as "Direct" in GA4, making attribution impossible.
Google Analytics 4 treats UTM parameter values as case-sensitive strings. "LinkedIn" and "linkedin" and "LinkedIn" appear as three separate sources in your Acquisition reports, fragmenting data across multiple rows and making it impossible to see total campaign performance at a glance. The industry standard is always lowercase with hyphens or underscores instead of spaces. This is the single most common UTM mistake and the hardest to fix retroactively once campaigns are live.
utm_source identifies WHO sent the traffic — the specific publisher, platform, or partner. Examples: google, facebook, newsletter-jan-2024, the-guardian. utm_medium identifies HOW the traffic arrived — the broad channel or method. Examples: cpc (paid search), email, social, organic, referral, affiliate. In GA4 reports, source and medium are combined as "source / medium" — a session tagged utm_source=google&utm_medium=email would appear as "google / email" which is technically wrong (you do not email from Google). Keep source and medium logically consistent.
No. Google has confirmed that UTM parameters are ignored by Googlebot during indexing. They do not create duplicate content issues, do not split PageRank, and do not affect page rankings. Search engines recognise UTM parameters as analytics tags and always attribute the content to the canonical URL without the query string. You can safely add UTMs to any URL you share externally without any SEO risk.
Strictly required for meaningful attribution: utm_source and utm_medium — without these, GA4 cannot properly categorise the session in acquisition reports. Highly recommended: utm_campaign — essential for comparing campaign performance. Optional: utm_term (mainly useful for paid search keyword tracking), utm_content (useful when running A/B tests with multiple ad variations or link versions). Missing utm_source or utm_medium means the session may be classified as Direct or fall back to the last non-direct session, leading to incorrect attribution.
Spaces in URLs must be encoded as %20 or +. When UTM values contain raw spaces, different browsers and platforms handle encoding differently — some encode as %20, some as +, some pass them unencoded. This means "summer sale" might appear in GA4 as "summer sale", "summer%20sale", and "summer+sale" as separate campaign values, fragmenting your data into three separate rows. Always use underscores or hyphens: summer_sale or summer-sale.
