What UTM parameters do and when to use them
Urchin Tracking Module (UTM) parameters are query-string tags appended to destination web addresses. When visitors click a link containing these tags, web analytics platforms such as Google Analytics 4, Matomo, and Plausible read the key-value pairs to attribute the session to the precise marketing channel and campaign that generated the traffic.
Without UTM parameters, analytics platforms rely solely on the browser HTTP referer header. Referer headers frequently drop when visitors move from secure applications to web browsers, or when clicking links inside native mobile apps like Instagram, Slack, SMS messengers, and desktop email clients. In those common scenarios, analytics platforms record the session under Direct or as a generic domain referral. Applying structured UTM parameters ensures that every marketing channel, affiliate partner, and email newsletter campaign receives accurate revenue attribution and clear performance tracking in acquisition reports.
The six UTM parameters and their definitions
Google Analytics 4 recognizes six standardized UTM parameters. Each serves a distinct analytical purpose in distinguishing between traffic sources, delivery mechanisms, and creative assets:
| Parameter | Required | Analytical Role | Standard Example |
|---|---|---|---|
| utm_source | Yes | Identifies the platform, publisher, or partner sending the visit | google, facebook, newsletter |
| utm_medium | Yes | Identifies the top-level delivery mechanism or marketing channel | cpc, paid_social, email, referral |
| utm_campaign | Recommended | Names the specific marketing initiative or promotional launch | devkit_launch_2026, spring_sale |
| utm_id | Optional | The campaign identifier used to import cost data into GA4 | dk26, q4_ad_789 |
| utm_term | Optional | Records the paid search keyword or audience segment targeted | developer+tools, machine_learning |
| utm_content | Optional | Differentiates distinct creative variations, buttons, or placements | top_banner_button, video_card_v2 |
The utm_source parameter represents the foundation of campaign tracking: GA4 ignores secondary UTM parameters if utm_source is omitted. The utm_medium parameter is equally crucial because GA4 relies on it to assign sessions to high-level default channel groups. The optional utm_id parameter connects external campaign activity with manual cost-data imports in Google Analytics, allowing teams to view return on ad spend across non-Google networks directly alongside organic metrics.
How GA4 default channel grouping works
Google Analytics 4 organizes incoming traffic into Default Channel Groups using predefined rule hierarchies. When your source and medium match recognized definitions, GA4 files the session into clean categories such as Paid Search, Paid Social, or Email. If your tags use unexpected terminology, GA4 fails to match any rule and dumps the traffic into Unassigned, creating reporting blind spots.
Our builder checks your inputs against standard GA4 channel criteria:
| Source / Medium Combination | GA4 Channel Classification | Rule Trigger Criteria |
|---|---|---|
| google / cpc | Paid Search | Recognized search engine combined with cpc, ppc, or paid medium |
| facebook / paid_social | Paid Social | Recognized social platform combined with paid_social or paid medium |
| youtube / video | Organic Video | Recognized video host combined with video or organic medium |
| newsletter / email | Either source or medium explicitly equals email | |
| partner / affiliate | Affiliates | Medium explicitly set to affiliate |
| partner / banner | Display | Medium set to display, banner, cpm, or interstitial |
| linkedin / social | Organic Social | Social domain combined with standard social medium |
| promo / blast | Unassigned | Custom medium fails all predefined GA4 classification rules |
Notice that custom words like blast, promo, or sponsored_post fail standard rule matching. Keeping your medium tags strictly aligned with recognized standards prevents messy channel reclassifications later.
Worked example: multi-channel campaign tagging
Consider an engineering software company launching a new development toolkit. The growth team coordinates promotion across three channels: an announcement email, a targeted LinkedIn sponsor post, and a Microsoft Bing search campaign.
To track each channel accurately while aggregating company-wide performance under a single umbrella campaign, the team constructs the following parameter sets:
First, the email newsletter announcement:
- Base destination: https://example.com/products/devkit
- utm_source: newsletter
- utm_medium: email
- utm_campaign: devkit_launch_2026
- utm_content: top_banner_button
- utm_id: dk26
- Generated URL: https://example.com/products/devkit?utm_source=newsletter&utm_medium=email&utm_campaign=devkit_launch_2026&utm_content=top_banner_button&utm_id=dk26
- Predicted GA4 Channel: Email
Second, the LinkedIn sponsored ad:
- Base destination: https://example.com/products/devkit
- utm_source: linkedin
- utm_medium: paid_social
- utm_campaign: devkit_launch_2026
- utm_content: carousel_specs
- utm_id: dk26
- Generated URL: https://example.com/products/devkit?utm_source=linkedin&utm_medium=paid_social&utm_campaign=devkit_launch_2026&utm_content=carousel_specs&utm_id=dk26
- Predicted GA4 Channel: Paid Social
Third, a Bing paid search ad targeting an existing promotion page with an anchor fragment:
- Base destination: https://example.com/products/devkit?pricing=annual#calculator
- utm_source: bing
- utm_medium: cpc
- utm_campaign: search_developer_tools
- utm_term: developer+toolkit+ide
- utm_content: ad_copy_v1
- utm_id: sdt01
- Generated URL: https://example.com/products/devkit?pricing=annual&utm_source=bing&utm_medium=cpc&utm_campaign=search_developer_tools&utm_term=developer%2Btoolkit%2Bide&utm_content=ad_copy_v1&utm_id=sdt01#calculator
- Predicted GA4 Channel: Paid Search
In the Bing example, the builder preserves the existing query parameter pricing=annual, URL-encodes the search keyword term, and positions all UTM parameters before the anchor hash fragment #calculator so browser navigation remains functional.
Bulk URL tagging for catalogs and schedules
Marketing workflows often require tagging dozens of web pages simultaneously, such as launching a site-wide discount across multiple category pages or scheduling social media calendars. Manually copying query strings into spreadsheets introduces typing mistakes, inconsistent casings, and broken delimiters.
The Many URLs mode allows you to paste a batch of web addresses, one per line. The tool validates every line individually, preserves existing queries and anchor fragments, strips duplicate UTM parameters, and generates ready-to-use tagged links for every destination. If an invalid or malformed URL is entered, the builder flags that specific line without disrupting the rest of the batch.
Best practices and common mistakes
- Enforce strict lowercase conventions across all fields. GA4 treats Facebook, facebook, and FaceBook as three separate sources, fragmenting metrics across multiple report rows.
- Replace spaces with underscores or hyphens. Raw spaces become percent-twenty sequences in web addresses and report tables.
- Establish a company-wide taxonomy guide. When multiple team members produce marketing links, standardizing medium choices prevents accidental channel splitting.
- Never place UTM tags on internal website navigation links. Clicking an internal link with UTM parameters terminates the visitor original session and starts a new artificial session, destroying historical attribution.
- Avoid placing UTM parameters after a hash symbol (#fragment?utm_source=google). Browsers treat everything after a hash as a client-side anchor and never transmit it to the server, preventing analytics scripts from reading the campaign parameters.
- Never store sensitive personal information such as customer names or email addresses in UTM parameters, which would violate privacy standards.
Related tools and guides
Explore our companion utilities to format, validate, and optimize your web campaigns:
- URL Encoder/Decoder to inspect and convert complex percent-encoded web addresses.
- Schema Markup Generator to produce rich structured data for articles and FAQs.
- Word Counter to optimize character counts for ad headlines and meta descriptions.
- Meta Tag Generator to build social preview cards and open-graph tags.