UTM Builder
Enter a page address and three tags, and the builder appends them as a query string: for the example, https://example.com/pricing?plan=pro&utm_source=old#compare with source “Newsletter”, medium “Email” and campaign “Spring Sale” becomes https://example.com/pricing?plan=pro&utm_source=newsletter&utm_medium=email&utm_campaign=spring_sale&utm_content=header_button#compare. The existing ?plan=pro and the #compare fragment are kept, the old utm_source is replaced, and the values are lowercased with spaces turned into underscores so “Email” and “email” never show up as two rows in your reports. utm_source, utm_medium and utm_campaign are required; utm_id, utm_term, utm_content and utm_source_platform are optional. You can also paste a tagged URL to read its parts back, or tag a list of up to 500 URLs at once. Nothing you type leaves your browser.
Updated Runs in your browser: nothing you enter is uploadedHow this tool works
Your URLs and tags are processed on this device and never uploaded or saved.
Tagged URL
Added 4 utm_ parameters to the link.
Typical GA4 default channel: Email.
| Parameter | Value | In the URL |
|---|---|---|
| utm_source | newsletter | newsletter |
| utm_medium | ||
| utm_campaign | spring_sale | spring_sale |
| utm_content | header_button | header_button |
Checks
- NoteReplaced existing utm_source in the link.
- NoteThe #compare fragment stays at the end, after the query string, where it belongs.
- Noteutm_source: “Newsletter” was lowercased to “newsletter”.
- Noteutm_medium: “Email” was lowercased to “email”.
- Noteutm_campaign: “Spring Sale” was lowercased to “spring_sale”.
- Noteutm_campaign: spaces in “Spring Sale” became _.
- Noteutm_content: “Header Button” was lowercased to “header_button”.
- Noteutm_content: spaces in “Header Button” became _.
Nothing to report: the tags are lowercase, free of spaces and need no special encoding.
Parts of the tagged URL
Found 4 utm_ parameters.
| Parameter | Value |
|---|---|
| utm_source | |
| utm_medium | paid_social |
| utm_campaign | Summer Sale |
| utm_id | (not set) |
| utm_term | (not set) |
| utm_content | Video_A |
| utm_source_platform | (not set) |
Typical GA4 default channel: Paid Social.
URL without the utm_ parameters
https://shop.example.com/sale?ref=home#top
The rest of the URL keeps 1 other query parameter.
Checks
- Warningutm_source=“Facebook” has capital letters. Reports treat “Facebook” and “facebook” as different values.
- Warningutm_campaign=“Summer Sale” has capital letters. Reports treat “Summer Sale” and “summer sale” as different values.
- Warningutm_campaign=“Summer Sale” contains spaces. They travel as + or %20 depending on the tool; use _ or - instead.
- Warningutm_content=“Video_A” has capital letters. Reports treat “Video_A” and “video_a” as different values.
No problems found in the campaign tags.
Tagged URLs
3 URLs tagged; 1 line could not be read.
Lines that could not be tagged
- Line 4not a url: This is not a valid web address. Use a full URL such as https://example.com/page.
Every line was tagged.
Checks
- Noteutm_source: “Newsletter” was lowercased to “newsletter”.
- Noteutm_medium: “Email” was lowercased to “email”.
- Noteutm_campaign: “Spring Sale” was lowercased to “spring_sale”.
- Noteutm_campaign: spaces in “Spring Sale” became _.
- Noteutm_content: “Header Button” was lowercased to “header_button”.
- Noteutm_content: spaces in “Header Button” became _.
Nothing to report: the tags are lowercase, free of spaces and need no special encoding.
The campaign parameters
| Parameter | Required | What it holds | Example |
|---|---|---|---|
| utm_source | Yes | Where the link is placed: newsletter, google, linkedin. | newsletter |
| utm_medium | Yes | The kind of channel: email, cpc, social. | |
| utm_campaign | Yes | The promotion this link belongs to: spring_sale. | spring_sale |
| utm_id | No | Matches the ID in uploaded campaign cost data. | abc123 |
| utm_term | No | The paid-search keyword. | running shoes |
| utm_content | No | Tells links or ads apart: header_button. | header_button |
| utm_source_platform | No | The platform that bought or placed the traffic: Google Ads. | Google Ads |
Medium values and GA4 channels
| utm_medium | Example utm_source | Typical channel | Note |
|---|---|---|---|
| cpc | Paid Search | Paid search ads (ppc and paid_search work too, with a search site as source) | |
| cpc | Paid Social | The source decides: a social network as source makes it Paid Social | |
| paid_social | Paid Social | Any medium starting with paid counts as paid | |
| display | adnetwork | Display | Banner ads (display, banner, cpm and similar) |
| newsletter | Newsletters and e-mail campaigns | ||
| social | Organic Social | Unpaid posts on social networks | |
| organic | Organic Search | Unpaid search results (Google sets this itself; rarely tagged by hand) | |
| affiliate | partner | Affiliates | Affiliate links |
| referral | partner | Referral | Links on other sites |
| sms | sms | SMS | Text-message campaigns |
| newsletter | newsletter | Unassigned | Not a recognised medium: use email instead |
| Organic Social | A platform name is a source, not a medium; GA4 still counts a social-network source as Organic Social |
How case and spaces are handled
| Setting | Written as | Why |
|---|---|---|
| Lowercase, spaces to _ (default) | spring_sale_2026 | One spelling for every report; matches the common snake_case style. |
| Lowercase, spaces to - | spring-sale-2026 | The same, with hyphens. Pick one style and keep it across the team. |
| Keep case, spaces to _ | Spring_Sale_2026 | Capitals stay, so “Spring_Sale” and “spring_sale” would be two rows in reports. |
| Keep case and spaces | Spring+Sale+2026 | Spaces are written as +, and capitals are kept. The riskiest combination. |
How values are encoded
| You type | In the URL | What happens |
|---|---|---|
| spring sale | spring+sale | A space becomes + (the form-encoding rule URLSearchParams uses). |
| a&b | a%26b | & would end the value, so it becomes %26. |
| x=y | x%3Dy | = is reserved inside a value, so it becomes %3D. |
| #1 | %231 | # would start the fragment, so it becomes %23. |
| 50% | 50%25 | A literal % becomes %25 (this is why pasting an already encoded value double-encodes it). |
| café | caf%C3%A9 | Non-ASCII letters are written as their UTF-8 bytes. |
| a/b | a%2Fb | / is encoded too, so the value never looks like a path. |
| x_y-z.1~ | x_y-z.1%7E | Letters, digits and _ - . * stay as they are; ~ becomes %7E. |
How to add UTM parameters to a URL
- Enter the page address. Paste the full URL of the page the link should open. A query string and a #fragment are fine; they are kept. A missing https:// is added for you.
- Fill in the three required tags. Source is where the link sits (newsletter, linkedin), medium is the kind of channel (email, cpc, social) and campaign is the promotion (spring_sale).
- Add the optional tags if you need them. utm_content tells apart links in the same campaign, utm_term holds a paid-search keyword, utm_id ties the link to uploaded campaign data and utm_source_platform names the buying platform.
- Read the warnings. The builder lowercases values and replaces spaces by default. Turn those off and it warns instead, and it warns when the medium will not match a GA4 default channel.
- Copy the tagged URL. Copy the result into your newsletter, ad or post. Switch to “Read a tagged URL” to check a link someone else made, or “Bulk” to tag a whole list.
Frequently asked questions
- Which UTM parameters are required?
- Google Analytics asks for three on every tagged link: utm_source, utm_medium and utm_campaign. utm_term, utm_content and utm_id are optional, as is utm_source_platform. The builder will not produce a URL until the first three are filled in.
- Do UTM values have to be lowercase?
- No, but it is the safe habit. Analytics reports list “Email”, “email” and “E-mail” as separate values, so one campaign ends up split across several rows. The builder lowercases by default; if you turn that off it warns about every value with capitals.
- How should I write spaces in a UTM value?
- Avoid them. A space is written as + (or %20 by other tools) and different tools show it differently. Use an underscore or a hyphen and use the same one everywhere: spring_sale, not “spring sale”.
- What happens to the query string and #fragment already in my link?
- They are kept. The other parameters stay exactly as written and the new utm_ parameters go after them, before the #fragment. If the link already has utm_ parameters, they are replaced, and the builder says which ones.
- Which utm_medium values does GA4 recognise?
- Its default channel group matches the medium (and for paid media the source) against a fixed list: for example email, cpc or paid* with a search or social source, social, display, affiliate, referral, organic, audio and sms. A paid medium with a source outside the search, social and video lists lands in Paid Other. A source that is a social network or a search engine can decide the channel by itself, whatever the medium. The table above shows what the builder expects. A medium outside the list, such as “newsletter”, typically ends up in Unassigned, and the builder warns you. Google can change its table, so check the Default channel group article for the current rules.
- Why is my encoded value different from what I typed?
- Characters that have a meaning in a URL, such as & = # and %, are percent-encoded, a space becomes +, and non-ASCII letters become UTF-8 bytes. Analytics decodes them back. If your value already contains %20 or %26, type the plain text instead, or it is encoded a second time (% becomes %25).
- Can I put UTM parameters after the # in a single-page app URL?
- Not usefully. Everything after # is the fragment, which is not part of the query string that analytics reads. Put the tags before the #. The “Read a tagged URL” mode warns if it finds utm_ after a #.
- Should I use UTM parameters on links inside my own site?
- No. A UTM-tagged internal link can overwrite the real source of the visit with your own tag, which hides where the visitor came from. Use them on links that bring people from outside: e-mail, ads, social posts, partner sites and QR codes.
- Is my URL or campaign data sent anywhere?
- No. The URL is only parsed as text in this page. It is not fetched, stored or uploaded, and the site records only that a button was used, never any URL or tag.
How it works
The address is parsed with the platform URL class (the WHATWG URL Standard). Every existing utm_ parameter is removed, the other query parameters are kept as written, and the new ones are added in the order source, medium, campaign, id, term, content, source platform. Each value is trimmed, its runs of whitespace are replaced (by _, by -, or kept as one space), and it is lowercased if that option is on; empty optional fields are left out. Values are written with URLSearchParams, so a space is + and reserved characters are percent-encoded. The fragment is kept after the query string. Only http and https addresses are accepted. The channel hint is a small model of Google’s Default channel group article: it checks the medium and the source in the order of Google’s table (for paid media, whether the source is a search, social or video site) and does not model Direct, Cross-network or the Shopping channels and is labelled “typical” because Google can change the table and the real result also depends on other signals. Bulk mode cleans the values once and tags each non-empty line on its own, up to 500 lines. Reading a tagged URL separates utm_ parameters from the rest and reports missing required tags, capitals, spaces, repeated tags and tags placed after the #.
Sources
More free tools
- URL Encode & DecodePercent-encode or decode URLs and query strings with correct UTF-8, split a URL into parts and parameters, and catch double-encoding. Runs in your browser.
- QR Code GeneratorTurn a link, text, Wi-Fi login, email or phone into a QR code. Set error correction, size and colors, then download PNG or SVG. Made on your device.
- URL Slug GeneratorTurn titles into clean URL slugs: hyphen or underscore, accents to ASCII, optional stop-word removal and a max length. Batch mode warns about duplicates.
- Meta Tag GeneratorGenerate a copy-ready head snippet: title, description, canonical, robots, Open Graph and X card tags, with length checks and search and social previews.
- Favicon GeneratorMake a favicon from an image, text or an emoji: PNGs from 16 to 512 px, favicon.ico, an SVG icon, the HTML link tags and a ZIP. Runs in your browser.
- Image to Base64 ConverterTurn an image into a Base64 data URI with ready HTML, CSS and Markdown snippets and exact sizes, or decode Base64 back to an image. Runs in your browser.
More: Web, URLs, images and networkAll developer toolsAll toolsHome & DIY calculators