A campaign link can open the right page and still give you messy reporting. Changing newsletter to Newsletter is enough to split values in Google Analytics, even though both links look fine when you click them. That's why my answer to how to create UTM campaign URLs starts before you paste a link into a builder. I choose the names first, build the URL, then check the whole click path and the analytics report. I'll walk you through that process.
What does a UTM campaign URL actually track?
I think of a UTM campaign URL as a normal destination link with a label attached. The destination says where you're sending someone. The UTM parameters describe the campaign context, such as an email newsletter or a social post. An analytics tool can use those values to help explain where a visit came from.
For example, my sample destination is https://example.com/demo. A tagged version is https://example.com/demo?utm_source=newsletter&utm_medium=email&utm_campaign=spring_launch. The page address is still the demo page. The extra values describe the link I shared, rather than changing the offer on that page.
What I don't expect the tags to do
I don't treat a generated URL as proof that tracking works. UTM parameters don't install analytics, record a purchase by themselves, or prove that a campaign caused a sale. I still need working analytics and conversion tracking. And the labels describe campaign context, not an individual person.
I also keep platform differences in mind. Google Analytics has its own reporting rules and dimensions. Another analytics product may interpret some fields differently. My examples below focus on website links and GA4, rather than Android app advertising, for which Google points people to its Play Campaign URL Builder.
What should I put in each UTM parameter?
I begin with source, medium, and campaign together. Google's wording matters here: it recommends that combination. I wouldn't describe all three as a universal technical requirement for a URL to open. A working link and a useful campaign report are different checks.
| Parameter | What it describes | My example value |
|---|---|---|
| utm_source | The source or referrer | newsletter |
| utm_medium | The marketing medium | |
| utm_campaign | The promotion or campaign name | spring_launch |
| utm_content | The link placement or creative variation | header_button |
| utm_term | The paid-search keyword | campaign_software |
| utm_id | The campaign identifier | spring_launch_main |
| utm_source_platform | The platform associated with the source | A consistent platform label |
How I separate source from medium
My source answers where I placed the link, such as linkedin or newsletter. My medium answers what kind of marketing it is, such as social or email. My campaign connects related work under one name. So I can keep spring_launch stable while changing the source and medium for each distribution channel.
I add fields because I need them, not because an empty box looks unfinished. Google's campaign URL documentation covers these fields and recommends relevant additions such as utm_id and utm_source_platform. It also says utm_creative_format isn't currently reported in Analytics properties, so I wouldn't build a reporting plan around it.
How do I choose consistent UTM names?
I settle the naming rules before generating links. Otherwise, it's easy to create email in one place and e-mail in another, then spend reporting time explaining why they differ. My preference is lowercase values with underscores between words. That's a convention I choose for consistency, not a special requirement imposed by UTM syntax.
- I keep a short approved naming sheet.
- Source names describe the publisher, platform, or distribution source.
- Medium names describe the marketing channel.
- Campaign names stay the same across links belonging to the same promotion.
- I use content values to distinguish placements, such as header_button and footer_link.
- I record the destination, finished URL, campaign owner, and intended placement together.
- I review a proposed new label before adding another spelling of an existing one.
Why I care about capital letters
Google Analytics treats UTM values as case-sensitive. google and Google are distinct values. I don't expect GA4 to tidy them into a single source automatically. Missing campaign parameters can also produce (not set) values, so I check completeness as well as spelling.
Tip from me: I copy an approved campaign name instead of retyping it for each channel. A plain shared sheet is enough if everyone actually uses the same version.
How do I create a UTM URL with UTM Builder?
I built UTM Builder and tried this workflow with it. I test my tools on a budget Android phone and a laptop. My aim here is simple: you should be able to build the link, inspect its values, and check the destination without guessing what the finished URL means.
- I open the destination first. For this example, I use https://example.com/demo as a sample address, not a live campaign destination.
- I open UTM Builder and enter my actual destination URL in the URL field.
- I enter newsletter for the source and email for the medium.
- I enter spring_launch for the campaign name, keeping it identical to my naming sheet.
- If I need to compare placements, I add header_button as the content value.
- I copy the generated URL, read it back against my planned values, and test it before using it in the campaign.
For those example values, I expect a link containing https://example.com/demo?utm_source=newsletter&utm_medium=email&utm_campaign=spring_launch&utm_content=header_button. The parameter order doesn't matter. What matters is that each name has the intended value and that the destination remains correct.
I wouldn't stop after copying. A builder helps assemble the URL, but it can't decide whether newsletter is the right source for your campaign or whether your landing page preserves query parameters. Those decisions and checks remain part of my workflow.
Which UTM values work for email, social, and partners?
I find examples easier to reuse when they share one campaign name. In this table, spring_launch is my sample campaign across several channels. These are proposed naming choices, not promises about how every analytics platform will group the traffic.
| Placement | utm_source | utm_medium | utm_content |
|---|---|---|---|
| Email header button | newsletter | header_button | |
| Email footer link | newsletter | footer_link | |
| Organic LinkedIn post | social | organic_post | |
| Paid social creative | paid_social | video_a | |
| Partner blog link | partner_blog | referral | article_link |
| Printed event flyer | flyer | offline | event_print |
For email, I'd use the same source, medium, and campaign for the header and footer links. I'd change only utm_content. That gives me a clear placement comparison without making the footer look like a separate marketing campaign.
For a printed flyer, I would build and test the tagged destination first, then use that address in QR Code Generator. I would scan the finished code too. Testing a typed URL doesn't check whether I put the correct address into the printed code.
I don't force every partner link into affiliate. I'd choose the label that describes the arrangement and keep it consistent. And I handle Google Ads separately, because Google's auto-tagging guidance is more specific than a generic source-and-medium example.
How do I add UTMs to a URL with a question mark?
I check the existing address before appending anything. The first query parameter follows a question mark. Each parameter name connects to its value with an equals sign, and later pairs use ampersands. If the URL already has a query string, I continue that query rather than adding another question mark.
How I preserve an existing query and fragment
My sample starting URL is https://example.com/demo?plan=team#pricing. With campaign tags, I want https://example.com/demo?plan=team&utm_source=newsletter&utm_medium=email&utm_campaign=spring_launch#pricing. I preserve plan=team, add the campaign values with ampersands, and keep the fragment #pricing after the query.
- I don't add a second question mark to start the UTM fields.
- I don't put campaign query parameters after the fragment.
- I check for existing UTM fields rather than appending conflicting copies.
- I preserve unrelated query values that the destination needs.
If the address is hard to read, I use URL Parser to inspect its parts. I may use URL Decoder to understand encoded text, but I don't replace a working campaign URL with a decoded display version without checking it. Reading a value and preparing a safe link are different jobs.
How can I tell if my UTM link is working?
I test the link from the place where someone will actually click it. That might be a test email, a social preview, or a QR code. Opening the original destination alone misses the redirect or shortening step that could drop the campaign information.
- I compare the finished URL with my approved source, medium, campaign, and content values.
- I click through the intended publishing route and check that the correct landing page opens.
- I inspect the landing URL and redirect path to see whether the campaign parameters reach the page.
- I include any consent flow in my test rather than assuming it leaves the URL handling unchanged.
- I check the resulting campaign data in analytics, because a correct-looking address isn't proof that a visit was recorded.
Google warns that redirects can strip UTM parameters and that some shorteners can lose referral details. I use Redirect Checker to help inspect the route, then still test the actual click. Google's explanation of direct traffic is useful when the expected campaign context is missing.
Tip from me: I save the exact published URL beside the original tagged destination. If a short link fails later, I can compare both addresses instead of trying to remember what I entered.
Where do I see UTM campaign results in GA4?
In GA4, I go to Acquisition, then Traffic acquisition. I use session campaign, source, and medium dimensions to inspect the campaign visits. I make sure the reporting date range includes my test or launch before deciding that a link failed.
How I read the result without overclaiming
I start by looking for the exact campaign name I used. Then I compare its sources and mediums. If I expected newsletter and email but find mixed spellings, I go back to the published links. If I find (not set), I check for missing campaign parameters instead of immediately blaming the builder.
For results beyond visits, I check whether the action I care about is actually measured. A campaign row can help me compare traffic, but it doesn't by itself establish sales, leads, or campaign profit. I need the relevant conversion tracking before using those outcomes to make spending decisions.
I also separate two questions: did the campaign labels arrive correctly, and did the campaign perform well? A correctly tagged link can lead to disappointing results. A popular link can still be poorly labelled. I fix the tracking question first so that the performance comparison has a sound starting point.
Which UTM mistakes should I avoid, including Google Ads?
My biggest caution is to avoid treating every link as an inbound campaign. I don't put UTMs on ordinary links between pages of my own website. That can confuse acquisition attribution rather than tell me which internal button worked.
For Google Ads, I check auto-tagging and the linked-account setup first. Google recommends auto-tagging, which adds a GCLID parameter. Manual tagging supplies a more limited set of Google Ads data, so I don't present it as an equal replacement.
When both methods are used, GA4 prioritizes auto-tagged values for source, medium, and other traffic-classification dimensions. Manual utm_content and utm_term still serve their respective manual dimensions. I refer to Google's auto-tagging guidance before interpreting an apparent mismatch.
- I keep personal and sensitive information out of UTM values because URLs can be shared or logged.
- I don't assume shortening a URL preserves every parameter.
- I don't mix case or rename an active campaign casually.
- I don't call the job finished until I've checked the published route and analytics.
Questions people ask
How do I create a UTM campaign URL?
I start with the destination URL and add utm_source, utm_medium, and utm_campaign using UTM Builder. I add utm_content if I need to distinguish placements. Then I copy the result, check the values against my naming sheet, and test the published click path and analytics report.
Which UTM parameters are required?
I use source, medium, and campaign together because Google recommends that combination for manually tagged campaign URLs. I distinguish that recommendation from a technical requirement for a page to open. Other relevant fields can add detail, while missing campaign information can leave reporting values such as (not set).
How do I add UTM parameters if my URL already has a question mark?
I append the UTM pairs with ampersands instead of adding another question mark. I preserve existing query parameters that the page needs. If there's a fragment, I keep it after the query. Then I inspect the finished URL to catch duplicate fields or an accidentally changed destination.
Are UTM parameters case-sensitive?
Google Analytics treats UTM parameter values as case-sensitive, so google and Google are distinct values. I use lowercase consistently and copy approved names rather than retyping them. My rule also covers campaign and content values, because inconsistent labels make a straightforward comparison harder to read.
Where can I see UTM campaign results in GA4?
I open Acquisition, then Traffic acquisition, and inspect session campaign, source, and medium dimensions. I check the date range and look for my exact campaign value. For business outcomes, I also check the relevant conversion tracking, since UTM labels alone don't establish whether a visit became a lead or purchase.
Can redirects or URL shorteners remove UTM parameters?
Yes. Google warns that redirects can strip campaign parameters and that some shorteners can lose referral details. I test the complete route, including the published short link and any consent flow. I check whether the tags reach the landing page, then confirm the campaign information in analytics.
What to do next
I would start with one campaign and one destination, not a huge naming system. Write down your source, medium, and campaign values, then open UTM Builder and create the link. Add content only if you need a placement comparison. Next, click through the route your reader will use, check the landing page and parameters, and look for the campaign in GA4 Traffic acquisition. Save the approved values beside the published URL. Once that small workflow works, reuse it across email, social, and partner links. Consistent names and a real test are what make the finished URL useful.