A UTM builder example is a complete walk-through that shows the full transformation from a plain destination URL to a tagged campaign link, naming every value that goes in and every character that comes out. The example below uses a real landing page address and the three required core campaign fields — source, medium, and campaign — so the mechanics of manual campaign tagging become concrete instead of abstract. The builder accepts a complete http or https address, adds the five traditional UTM parameters, preserves the destination path, the URL fragment, and any unrelated query values, and returns a finished link ready to paste into an ad, newsletter, QR code, or partner placement. A second example shows how an existing tagged link can be refreshed without losing parameters such as gclid or ref. The output is a constructed URL only — the tool does not inspect analytics, redirects, attribution, or signed URL signatures — and nothing leaves the browser.
From Plain URL to Tagged Link: A Worked Example
Picture a small marketing team that needs to send paid search traffic to a pricing page for a spring product launch. The destination starts as a clean address with no campaign information:
https://example.com/pricing
The team opens the UTM Link Builder, pastes the address, and enters three labels that match their reporting convention: utm_source as google, utm_medium as cpc, and utm_campaign as spring-launch. Term and content are left blank because the search ads do not break out keywords or creative variants in their reporting setup. The builder returns a finished link immediately:
https://example.com/pricing?utm_source=google&utm_medium=cpc&utm_campaign=spring-launch
The path stayed the same. Three query parameters were appended. The result is a single line that can be pasted into a Google Ads final URL field, a newsletter template, a QR code, or a partner placement spreadsheet without further editing. The builder shows this exact output so the team can confirm the labels are spelled correctly and in the right slots before the link goes live.
Three Steps to Build a Campaign Link
- Paste the complete http or https destination URL into the builder. Relative paths, mailto links, and non-web protocols are rejected because the tool is scoped to web campaign destinations only.
- Enter campaign source, medium, and name. Add utm_term or utm_content only when the reporting convention actually uses them. The three core fields are required so the generated link is never missing the manual-campaign fields described in Google Analytics guidance.
- Build the URL, review the preserved parameters and fragment, then copy the result into an ad, email, social post, or QR code. The link is shown immediately and stays in the browser.
The optional fourth and fifth parameters behave differently from the required three. When a term or content field is blank, the builder leaves that parameter out of the output instead of adding an empty value. A shorter link is easier to inspect and reduces accidental label variations across reports. Values are URL-encoded so a space inside a campaign term becomes a valid character sequence in the final address.
Anatomy of the Tagged Campaign URL
| Parameter | Purpose | Example value used above | Required? |
|---|---|---|---|
| utm_source | Where the traffic comes from | Yes | |
| utm_medium | The marketing channel | cpc | Yes |
| utm_campaign | The campaign name | spring-launch | Yes |
| utm_term | Paid keyword (legacy) | (left blank) | No |
| utm_content | Ad creative or placement variant | (left blank) | No |
Source identifies the referrer — a search engine, a newsletter, a social network, or a partner site. Medium identifies the channel such as cpc, email, social, or affiliate. Campaign identifies the initiative, often including a season, launch, or product name. Term is most often used for paid keyword tracking. Content is most often used to differentiate creatives, placements, or A/B variants inside the same campaign. The builder manages only these five keys, which is the reason the next section focuses on what happens to the rest of the URL.
Updating a Tagged Link Without Losing Other Parameters
Many landing pages already carry query parameters that must survive any campaign refresh. A page might include ref=homepage for the referral slot, a language switcher, or a Google click identifier such as gclid. Start with a tagged link that already has those values:
https://example.com/pricing?ref=homepage&gclid=abc123&utm_source=facebook&utm_medium=social&utm_campaign=winter-sale
The team wants to relaunch the link for a new campaign and replace only the three core labels. They paste the existing link into the UTM Link Builder and enter newsletter as the source, email as the medium, and march-sale as the campaign name. The builder removes only the three UTM keys it owns, keeps ref=homepage and gclid=abc123 in place, and appends the new values:
https://example.com/pricing?ref=homepage&gclid=abc123&utm_source=newsletter&utm_medium=email&utm_campaign=march-sale
The destination path, fragment, and any unrelated parameters stay intact. This is the practical reason the builder is scoped to exactly the five traditional keys: it can refresh a campaign without rebuilding the destination address by hand. For a workflow that does this often, see how to create UTM links without breaking existing tags.
Limits of a UTM Builder Example
A builder example shows construction, not validation. The finished URL is ready to copy, but the tool itself does not check whether an analytics property exists, whether auto-tagging is active, whether a redirect strips query parameters, whether consent settings suppress the hit, or whether future traffic will appear in a specific report. Test an important campaign link in a real browser with a reporting view open before publishing it.
Signed or pre-signed URLs should not be passed through the builder. The browser URL API can normalize query encoding, which would invalidate a signature. Start from an ordinary destination URL instead.
Campaign labels should describe the placement, not a person. Query parameters can be stored in browser history, referral logs, analytics systems, and shared links, so names, email addresses, phone numbers, and account numbers belong outside any UTM field. A simple team convention — for example google as the source, cpc as the medium, spring-launch as the campaign — keeps reports consistent and easier to read than freeform values. The builder preserves the text supplied after trimming accidental outer spaces, rather than inventing a taxonomy or changing case.
Finally, the tool makes no network request. The destination URL and campaign labels stay in the browser, which is the main reason a builder like this works for sensitive internal destination addresses that should not be sent to a third-party server. For a short public-facing URL, use a trusted redirect or short-link service only after verifying that the service preserves the query string through the redirect chain.
If you're weighing options, Avoid Bulk URL Generator Mistakes Before You Export covers this in detail.