Assemble campaign tracking URLs with utm_source, medium, campaign, term, and content parameters, correctly encoded for analytics.
Content last reviewed
Enter the page on your site that the campaign link should open.
Set source, medium, and campaign name; add term and content when you need to tell ads or variants apart.
The finished link builds live below the form — copy it into your email, ad, or post.
The three core parameters appended to a clean URL.
Input
URL: https://motifuse.com/pricing · source: newsletter · medium: email · campaign: spring-saleOutput
https://motifuse.com/pricing?utm_source=newsletter&utm_medium=email&utm_campaign=spring-saleBecause the destination already contains ?, the UTM parameters join with & instead.
Input
URL: https://motifuse.com/pricing?ref=partner · source: partner-site · medium: referral · campaign: co-promoOutput
https://motifuse.com/pricing?ref=partner&utm_source=partner-site&utm_medium=referral&utm_campaign=co-promoAnalytics can usually tell you a visitor came "from Facebook" — but not whether it was the paid campaign or an organic post, the launch email or the monthly newsletter. UTM parameters close that gap: five standardized query parameters that stamp each link with exactly where and why it was shared. This builder assembles them into a correctly encoded URL so the tagging step never introduces typos or broken query strings.
The form mirrors the parameters themselves. Three do the core work: utm_source names the platform (newsletter, facebook, google), utm_medium names the channel type (email, social, cpc), and utm_campaign names the initiative (spring-sale, product-launch). The optional two add precision — utm_term for paid keywords and utm_content for distinguishing two ads, two buttons, or A/B variants pointing at the same page. Empty fields are simply left out of the URL rather than appended as blank parameters.
The output updates live as you type, with values percent-encoded through the browser's standard URL machinery and the query string joined correctly — if your destination URL already has a ?, the parameters are appended with & instead of creating a second question mark. One discipline the tool cannot do for you: consistency. Analytics treats Facebook, facebook, and FB as three different sources, so pick lowercase conventions once and reuse them — the builder outputs exactly what you type.
Paste the destination page into Website URL — the full address including https://.
Fill in the three core parameters:
newsletter, facebook, or google.email, social, or cpc.spring-sale or launch.Add Campaign Term (paid search keywords) and Campaign Content (ad or variant identifier) when you need to distinguish creatives pointing at the same page.
The Generated URL builds live below the form. Click Copy and use the link in your campaign.
Record the names you used in a shared document so the next campaign uses the same spellings — consistent naming is what makes the reports readable.
Source, medium, campaign, term, and content — the full standard set, with the optional two omitted from the URL when left blank.
Values are percent-encoded through the browser's standard URL API, so spaces and special characters cannot corrupt the query string.
If the destination URL already contains a ?, parameters are appended with & — no double question marks.
The tagged URL rebuilds on every keystroke, ready to copy at any moment.
Tag newsletter links so email traffic is attributed to the specific send, not lumped into referral or direct.
Give the same destination different source/medium combinations so ads and organic posts report separately.
Use utm_content to tell two ad variants or two button placements apart in analytics.
Issue each partner a distinctly tagged URL to measure who actually drives traffic.
Tag the URL behind a printed QR code so scans are attributable — pair with the QR Code Generator.
The builder collects the five parameter values, skips any that are empty, and encodes the rest with the browser's URLSearchParams API — the same machinery browsers use for real query strings, so spaces, ampersands, and non-ASCII characters are percent-encoded safely. It then checks whether your destination URL already contains a ? and joins the parameter string with & in that case, or ? otherwise.
When the tagged link is clicked, your analytics platform reads the utm_* parameters from the landing URL and attributes the session to that source, medium, and campaign. The parameters are plain text in the URL — visible to the visitor and to anyone they share the link with — which is why campaign names should be things you are comfortable displaying publicly.
A standard URL with utm_* query parameters, compatible with Google Analytics and every major analytics platform that reads UTM tags.
The destination page. Required — with it empty, no output is generated.
The three core parameters. Each is included only when filled in.
Optional parameters for paid keywords and creative/variant identification, omitted when blank.
Capitalization or spelling drift — Facebook, facebook, and FB are three different sources to analytics. The builder outputs exactly what you type, so adopt one lowercase spelling and reuse it.
UTM-tagged links were used in internal navigation. Clicking an internal tagged link restarts the session with a fake source. Tag only external links that point in — emails, posts, ads, partner sites.
Parameters are appended to the end of whatever you enter, and query parameters placed after a #fragment are ignored by browsers. Remove the fragment, generate the tagged URL, then re-add #section at the very end if you need it.
The builder constructs the URL; it does not validate that the destination exists, shorten the link, or store a history of the links you have built — keep your own record of campaign naming conventions. Values are encoded but not normalized: capitalization and spelling are preserved exactly, so consistency remains your responsibility. URLs containing a # fragment need the fragment removed before tagging, since parameters are appended at the end. UTM tracking itself also depends on the visitor's browser reaching your page with the parameters intact — aggressive redirect chains or privacy tools can strip them.
The URL and parameter values you enter are processed entirely in your browser — nothing is uploaded, logged, or saved by the tool. Remember that the finished UTM parameters are visible in the shared link itself, so anyone who receives it can read your source, medium, and campaign names.
Use all-lowercase, hyphenated values everywhere — analytics is case-sensitive and Facebook ≠ facebook.
Keep a shared spreadsheet of the source, medium, and campaign names your team has used.
Tag only external links pointing at your site; internal UTM links corrupt session attribution.
Name campaigns something you are comfortable being publicly visible — the parameters travel with the link.
Click every tagged link once before launch and confirm the parameters survive to the landing page.
Decide the vocabulary before the first link. Choose a fixed list of mediums (email, social, paid-social, cpc, referral) and one canonical spelling per source, all lowercase with hyphens instead of spaces. Write it down where the whole team can see it — the discipline costs a minute per campaign and is the entire difference between reports you can read and rows of near-duplicates.
Match granularity to the question you will ask later. Campaign names should group everything you want compared as a unit; use content, not campaign, to distinguish creatives inside a campaign. If you find yourself creating a new campaign name per ad, the reports will be sliced too thin to say anything.
Before launch, click each tagged link and watch it arrive: parameters intact in the URL bar, session attributed correctly in a real-time analytics view. Redirects, shorteners, and typos are all caught by this thirty-second test.
Parameter encoding uses the browser's URLSearchParams API, which percent-encodes reserved characters and spaces per the URL standard. Empty fields are excluded before encoding, so the query string contains only populated parameters in the fixed order source, medium, campaign, term, content. The separator is chosen by checking the destination for an existing ?. The component is fully client-side with no history or storage.
| Parameter | Answers | Example values |
|---|---|---|
utm_source | Where does the link live? | newsletter, facebook, google |
utm_medium | What kind of channel? | email, social, cpc, referral |
utm_campaign | Which initiative? | spring-sale, launch |
utm_term | Which paid keyword? | running+shoes |
utm_content | Which creative or variant? | banner-a, footer-link |
Source, medium, and campaign are the trio worth filling every time; term and content earn their place in paid search and A/B tests.
Marketers running email, social, and paid campaigns; founders and small teams who want channel-level attribution without a marketing platform; agencies issuing distinctly tagged links to partners; and analysts cleaning up the tagging conventions behind messy acquisition reports. If you have ever wondered whether the newsletter or the ad drove the signups, UTM tags are how you find out.
Source is the specific place the link lives — facebook, newsletter, a partner's site. Medium is the type of channel — social, email, cpc, referral. Together they let you separate facebook/paid-social from facebook/social, which is exactly the distinction the parameters exist to make.
The parameters do not change page content, but tagged URLs can be indexed as duplicates of the clean URL if they end up in crawlable places. Use UTMs on distributed links (emails, ads, posts) and make sure your pages declare a canonical URL, which resolves the ambiguity.
No. Clicking an internal UTM-tagged link restarts the visitor's session with a fake new source, destroying the original attribution. UTMs belong only on external links pointing at your site.
Yes — they are part of the URL, visible in the address bar and preserved when the link is forwarded. Name campaigns accordingly, and avoid putting anything sensitive in the values.
Inconsistent values. Analytics treats every distinct spelling and capitalization as a separate entry, so Facebook, facebook, and FB become three sources. Standardize on lowercase spellings and the rows merge going forward.
Yes — the builder detects the existing ? and appends the UTM parameters with & so the query string stays valid. Just avoid tagging a URL that already carries utm_ parameters from an earlier pass.