UTM URL Builder
Build a tagged campaign URL, or process a batch of destinations with consistent UTM fields.
Tagged URL
No URL built yet.
Why use our UTM URL Builder?
The Rest of the Link Survives
Existing parameters such as lang=en keep their order and the #fragment stays at the end, so the tagged link still opens the same view of the page. A newsletter, partner page, and social post may need different destinations while sharing one campaign label. A CSV header maps row-specific source, medium, campaign, term, and content fields explicitly. Empty cells inherit the shared fields instead of silently erasing them. Single-link mode remains best when you only need one URL.
Old Tags Replaced, Not Stacked
Paste a link that already carries campaign parameters, even repeated ones, and building swaps them for your values instead of appending a second set. The tagged link keeps unrelated query parameters, including language or product variants, and leaves the fragment after the query. Existing UTM keys in any letter case are removed before new values are added. Review the finished link because the destination application may depend on its original parameters.
Built on This Page
The tagged link is put together in your browser. The builder does not shorten the link, open it, or check whether the destination resolves. Each row displays its CSV row number and either a completed link or an error. A malformed destination does not erase valid rows. The export contains valid rows only, so compare valid and invalid counts before you send a campaign file. The input stays available for editing.
What is a UTM URL Builder?
A UTM URL builder adds campaign parameters to a destination link so an analytics tool can tell which newsletter, ad or post sent the visit. Three are required here: utm_source, utm_medium and utm_campaign. Two are optional: utm_term and utm_content. utm_source names where a visit came from, such as a newsletter or partner. utm_medium describes the channel, such as email. utm_campaign groups links for a particular effort. Optional utm_content distinguishes placements, while utm_term can describe a paid search term. These values are labels you choose, not proof that an analytics account received a visit.
An email newsletter for a spring sale would use newsletter, email and spring-sale. Pasting https://example.com/shop?lang=en#offers with those values gives https://example.com/shop?lang=en&utm_source=newsletter&utm_medium=email&utm_campaign=spring-sale#offers. Analytics tools read the parameters literally, so keep the naming consistent across a campaign. Parameters appear in the destination URL and can be visible to anyone with the link. Do not put personal details, email addresses, secret tokens, or private note text into campaign values. This builder assembles links in the browser; it does not shorten them or visit the destinations. Attribution requires the destination to collect and interpret the tags after someone opens the link.
What each campaign field means
- utm_source:Names the specific place the visit came from: newsletter, google, or a network name.
- utm_medium:Names the channel type: email, cpc, or social. A short fixed list keeps channel rollups readable.
- utm_campaign:Names the promotion: spring-sale.
- utm_term:Optional. Holds a paid keyword. Fill it only when the analytics tool reading the link groups by term, since the ad platform often reports the keyword already.
- utm_content:Optional. Separates links inside one campaign, such as header-link and button-blue, or two subject lines in an A/B test. Use a short label, not a sentence.
- Newsletter:Tag several product pages with a shared campaign and different content labels when comparing placements. Check each destination before the newsletter goes out.
- Partner handoff:Use one destination per partner, with a row-specific source when each partner has its own naming convention. Blank cells use the shared source.
- QR print assets:Build the final tagged URL first and encode that exact result with the QR generator. A printed code cannot update when campaign values change.
- One-off reply:Use Single URL mode rather than preparing CSV for a link you only need once. The original single builder still supports copying its output.
Common Use Cases
Email Newsletters
Tag every link in an issue with the same source, medium and campaign, so the visits from that send land in one row.
Paid Search Ads
Set medium to cpc and, when your analytics groups by keyword, put the paid keyword in utm_term.
Social Posts
Give each network its own source with medium social, so a channel report splits the traffic by network.
A/B Subject Lines
Keep source, medium and campaign the same and change only utm_content, so the two versions report side by side.
Printed QR Codes
Tag the link before you turn it into a QR code, because a code on paper cannot be edited once the flyer is printed.
Retagging an Old Link
Paste a link copied from an earlier campaign. The old campaign parameters are replaced, and a note above the buttons says so.
Campaign Planning
Agree on the source and medium names before pasting destinations. Consistent spelling is more useful than collecting many inconsistent labels.
Review Before Distribution
Open representative completed destinations yourself and check any redirects. A builder cannot confirm that a destination page exists or retains tags after redirect.
Spreadsheet Handoff
Download reviewed valid rows as CSV. Cells beginning with formula characters after whitespace or control characters receive an apostrophe prefix for safer spreadsheet opening.
How to build and check campaign links
Paste the destination
Paste an absolute HTTP or HTTPS destination URL, including any existing query or fragment. Choose Batch URLs. Paste one absolute http or https destination per line, or use a CSV header beginning with destination and named optional field columns.
Fill the campaign fields
Enter source, medium, and campaign. Add term or content only when your reporting needs them, then select Build URL. Enter shared source, medium and campaign values. Fill row-specific CSV cells to override them; empty cells inherit shared values. Optional term and content work the same way.
Inspect the result
Inspect the destination path, existing parameters, and fragment in the tagged URL before you use it anywhere. Build and compare the row numbers, links, and errors. Fix an invalid URL or missing required tag in the retained input, then build again to refresh the output.
Copy and open it
Copy the link and open it to check any redirects; this builder does not request the destination, so only a real visit shows where it lands. Download CSV or prepare URLs to copy only after inspecting the results. The export excludes invalid rows; check the count so no planned link is silently forgotten.
Existing query strings and fragments
Order Kept
Parameters such as lang=en keep their order, and campaign parameters are appended after them.
Duplicates Replaced
Campaign parameters already on the destination, including duplicated ones, are replaced with your values rather than appended, because two utm_source values make reports ambiguous: some tools read the first, some the last.
Any Letter Case
Campaign keys are matched in any letter case, while lookalike names stay. Retagging ?UTM_SOURCE=old&utm_source_note=1 gives https://example.com/shop?utm_source_note=1&utm_source=newsletter&utm_medium=email&utm_campaign=spring-sale.
Fragment Last
A fragment after # is never sent to the server, so parameters placed after it are not campaign tracking at all. The builder keeps the fragment at the end and puts campaign parameters before it.
Spaces and Accents Encoded
Spaces are encoded as %20 or +; this builder writes spring sale as spring+sale. Accented characters are percent-encoded, so café becomes caf%C3%A9, and the browser decodes both when the page loads.
Unsafe Links Refused
Only absolute http and https destinations are accepted. A javascript: or data: link, or a URL with a username and password in it, gets an error instead of a tagged link.
Queries and Fragments
Inspect a link containing both a question mark and a fragment. The query gains campaign fields while unrelated keys and the fragment survive.
Existing UTM Keys
Repeated campaign keys with mixed case are replaced once. Lookalike names such as utm_source_note are unrelated keys and remain untouched.
CSV Boundaries
Quoted cells allow commas, embedded line breaks, and doubled quotes. Invalid columns or malformed quotes produce an error instead of plausible but misaligned campaign values.
Privacy After Sharing
Sharing a finished URL reveals its destination and campaign values to recipients and their systems. Browser-side assembly does not make a distributed link private.
Naming conventions that survive reporting
- •One style: Pick one case and one separator and keep them. Lowercase with hyphens is the common convention: newsletter, email, spring-sale.
- •Capitals split channels: Analytics tools commonly treat utm_source=Newsletter and utm_source=newsletter as two sources, so a single stray capital splits a channel.
- •No spaces: Avoid spaces, since some systems display the encoded form differently.
- •Literal matching: Values are matched literally. Changing utm_campaign mid-campaign starts a new row in reports.
- •Distinct campaigns: Two campaigns sharing source and medium without a distinct utm_campaign are lumped together.
- •Write it down: Keep a short document of the values for each channel; writing the convention down is what stops one person using email and another newsletter.
- •Read the Finished Link: Check that the destination path is the page you meant, unrelated parameters such as lang=en survived, and the fragment is still at the end.
- •Open It Privately: Open it in a private window and confirm the page loads with the parameters attached. A redirect on the destination can strip the query string before the analytics script runs, and this builder cannot detect that.
- •Test Before Launch: Test it in your analytics tool before launch. A misspelled name such as utm_sorce is not a campaign parameter, so the tool will not read it as the source, and the visit may be attributed to another channel instead.
- •Logs and Referrers: The parameters travel in the URL, so they appear in server logs, and may appear in analytics and referrer data, depending on the destination and its referrer policy.
- •No Personal Data: Do not put personal data such as an email address or customer ID in a campaign value; use a campaign-level value instead.
- •Old Links Keep Counting: Tags are visible in the address bar and survive bookmarking and sharing. A visitor who reshares a tagged link or returns to it months later is counted against the original campaign, which is why old links can keep reporting activity after a campaign ends.
- •Choose names: Decide whether email and newsletter are separate sources or two spellings for the same source. Keep a naming convention for later batches.
- •Use content deliberately: A content label can distinguish two placements within one campaign, but it is not mandatory for every destination.
- •Avoid identities: A campaign label should tell a teammate what was promoted without including a customer name or personal address.
- •Test real visits: The CSV itself creates no tracking. Test completed links on the destination and inspect reporting in the analytics system used there.
- •Store one copy: Keep one reviewed file next to the campaign asset, so the newsletter, ad and QR code use the exact approved strings.
- •Where campaign data ends up: URL parameters can enter browser history, destination logs and analytics. Avoid placing sensitive details in any campaign field.
Tag Your Next Campaign Link
Paste the destination, fill in source, medium and campaign, and copy a link whose query string and fragment are exactly as you left them, plus one clean set of campaign tags. Enter a single destination above for quick work, or paste a batch when row-level review and consistent naming save time. Fix errors before export and check representative links on the actual destination.
This page builds the link in your browser and does not shorten it, open it, or check whether it resolves. Vercel Analytics runs on this page, so treat the page as ordinary website traffic rather than an offline tool. The completed URL, not this page, is the artifact your audience opens. A saved CSV can be forwarded and opened by spreadsheet software, so review both its recipients and its contents before distributing it.
Related tools
Frequently Asked Questions
Are existing URL parameters kept?
Yes. Unrelated query parameters and the fragment remain. Existing UTM parameters are replaced.
What if the destination already has UTM tags?
The builder replaces UTM keys case-insensitively, including duplicates, rather than stacking them.
Can I paste relative URLs?
No. Each destination must be an absolute http or https URL without embedded credentials.
Does exporting CSV create tracking on its own?
No. The CSV contains tagged URLs for you to review and share. Attribution requires a destination configured to read those parameters and an actual visit.