UTM builder & checker: campaign links you can trust

UTM parameters are how analytics attributes a click to a channel, campaign, and creative. Get them wrong and paid, email, and social all collapse into “direct” or a mess of near-duplicate sources. Get them right and your reports answer “which newsletter drove the trial?” without a spreadsheet archaeology dig.

This free tool does two jobs in one page: a UTM builder for utm_source, utm_medium, utm_campaign, utm_content, and utm_term, and a UTM checker that pastes any URL and validates the query params (encoding, missing pieces, common typos). Save shareable presets for agency or team naming conventions so every link uses the same vocabulary. Everything runs in your browser — no login, nothing sent to SiteLine, no analytics OAuth.

When you want those campaign dimensions next to cookieless analytics and a Search Console archive (~16 months backfill, up to 25k rows/day/report, retained while you subscribe) with read-only MCP, SiteLine is the product side. Start a 7-day trial (no card) · Pricing from $4.99/mo.

How to use the builder

1. Enter the base URL (landing page or path you actually want people to open).
2. Fill source (who sent the traffic: newsletter, google, linkedin), medium (how: email, cpc, social), and campaign (the named push: spring-sale-2026).
3. Optionally add content (creative or CTA variant: hero-a, footer-link) and term (paid keyword when you still use it).
4. Copy the finished URL. Prefer lowercase and hyphens; avoid spaces (the builder encodes them, but consistent naming beats encoding surprises).
5. Open a preset (or save one) so the next link reuses your source/medium vocabulary instead of inventing Email vs email vs e-mail.

How to use the checker

1. Paste any full URL that already has (or claims to have) UTM params.
2. Read the parsed fields: present vs missing, decoded values, and warnings (empty values, mixed case that will fragment reports, utm_source stuffed into the wrong key, double ?, broken encoding).
3. Fix in the builder, or edit the URL and re-check until the five fields you care about are clean.
4. Confirm the landing path still matches the page you intend — UTMs do not fix a wrong slug.

What each UTM parameter means

Analytics products (including SiteLine’s cookieless tracker) read these from the landing URL’s query string on first hit. Inconsistent casing or synonyms (fb vs facebook vs Facebook) create parallel rows that never roll up — presets stop that improvisation. Prefer lowercase and hyphens.

Encoding and URL hygiene

• Use a single ? then & between params. Nested query strings and hash-before-query mistakes break parsers.
• Prefer UTF-8 percent-encoding for non-ASCII; avoid hand-typed + for spaces unless every consumer agrees.
• Do not put PII in UTMs. Keep the canonical landing URL stable; do not invent a second taxonomy in the path.

Shareable presets (team naming)

Teams fail UTMs the same way: one person uses linkedin / social, another LinkedIn / organic-social. A preset locks source + medium (+ optional campaign prefix) and shares as a link or copyable blob so freelancers inherit the vocabulary.

Starter conventions:

• Email: source=newsletter (or list name), medium=email, campaign=<send-slug>, content=<subject-or-cta>.
• Paid search: source=google (or bing), medium=cpc, campaign=<ad-group-or-theme>, term=<keyword>.
• Organic social: source=linkedin|x|instagram, medium=social, campaign=<post-or-series>, content=<creative>.
• Partners: source=partner-<slug>, medium=referral, campaign=<collab-name>.

Document the preset once; regenerate links from the builder instead of editing last month’s URL by hand.

Step-by-step: ship a clean campaign link

1. Decide the three required fields before you open a doc: source, medium, campaign.
2. Build the URL here; copy once into the ad platform, ESP, or social scheduler — do not retype.
3. Paste the live published link back into the checker (esp. after a CMS or ESP “link wrapper”).
4. Click it in a private window; confirm the landing page and that your analytics shows the expected UTM dimensions on a test hit.
5. Archive the preset name next to the campaign brief so the next send matches.

If consent-gated GA4 is the only place you read campaigns, a banner decline can hide the same clicks — see the cookie banner traffic loss calculator and guide. Cookieless analytics keeps campaign dimensions without an analytics cookie on many setups; jurisdiction still matters — not legal advice.

When a free UTM tool is not enough

A builder answers “what string do I paste?” It does not archive Search Console, reconcile organic vs paid landers, or let an agent query campaign and query reports together.

SiteLine’s job: cookieless analytics (including UTM breakdowns) beside a GSC warehouse — ~16-month backfill, up to 25k rows/day/report, retention while you subscribe — with read-only MCP. MCP overview · Register with MCP intent · Connect GSC.

Start free for 7 days — no card · See pricing from $4.99/mo

Related free tools: Cookie banner traffic loss calculator · GSC data expiry calculator · GSC regex builder · GSC opportunity analyzer · All free tools

FAQ

Does this tool store my URLs or presets on SiteLine’s servers?

No. Building, checking, and (browser-local) presets run in your browser. Closing the tab clears what you did not deliberately export or bookmark. Nothing is sent to SiteLine for this free tool.

Which UTM parameters are required?

Practically: source, medium, and campaign. Content and term are optional but valuable for creatives and paid keywords. Empty or whitespace-only values help nobody — the checker flags them.

Can I use this for shortened links (bit.ly, etc.)?

Build and validate the destination URL with UTMs first, then shorten that full URL. Checking only the short link shows the wrapper, not the parameters your analytics will see after redirect — expand or paste the final landing URL into the checker.

Do UTMs work with cookieless analytics?

Yes, when the collector reads the landing page query string (SiteLine’s cookieless analytics does). UTMs are URL metadata, not cookies. Consent rules for other tags on the page are a separate question.

Will UTMs fix Search Console attribution?

No. Search Console measures Google Search clicks on Google’s side; it does not consume your utm_ tags. Use GSC for organic search performance and UTMs for marketing links into your site — then compare in a product that holds both. Related: GSC opportunity analyzer, GSC regex builder.

How is SiteLine different from this free builder?

This page builds and validates strings. SiteLine reports campaign traffic in cookieless analytics, archives Search Console (~16 mo backfill, 25k rows/day/report, while subscribed), and exposes read-only MCP. Trial is 7 days, no card; plans from $4.99/mo.