You share a link in your newsletter, on Instagram, and in a Facebook ad. Traffic arrives — but which campaign actually brought the visitors who signed up or bought? UTM parameters answer that question.

UTM parameters are tags you add to the end of a URL. When someone clicks the link, analytics tools like Google Analytics 4 read the tags and associate collected visits with the campaign labels.
Example:
https://hostreta.com/speed-up-wordpress/?utm_source=newsletter&utm_medium=email&utm_campaign=oct_speed_week
Without UTMs, many clicks show up as “direct” or vague “referral” traffic — especially from email apps, messaging apps, and some social platforms.
| Parameter | Purpose | Example |
|---|---|---|
utm_source (required) |
Where the traffic comes from | newsletter, instagram, facebook, google |
utm_medium (required) |
The marketing channel/type | email, social, cpc, referral, paid_social |
utm_campaign (required) |
The specific campaign | oct_speed_week, black_friday_2026 |
utm_content (optional) |
Differentiates links/creatives | header_button, reel_1, carousel_v2 |
utm_term (optional) |
Paid search keywords or extra detail | wordpress_hosting |
GA4 also supports additional parameters like utm_id (campaign ID), and it uses source and medium values to group traffic into default channel groups (Email, Organic Social, Paid Social, etc.). Using standard medium values (like email, social, cpc) helps GA4 classify traffic correctly.
Tools:
Steps:
Important: don’t use UTMs on internal links within your own website (e.g., from your homepage to a blog post). Internal navigation should use event measurement rather than campaign acquisition tags; these tags can make attribution harder to interpret.
Consistency is everything. Facebook, facebook, and fb appear as three different sources in reports.
Rules:
Example convention:
| Parameter | Allowed values |
|---|---|
| source | newsletter, facebook, instagram, linkedin, x, youtube, whatsapp, partner_name |
| medium | email, social, paid_social, cpc, referral, affiliate, qr |
| campaign | yyyy_mm_theme e.g., 2026_10_security_week |
| content | post_type_variant e.g., reel_hook_a, carousel_1 |
Keep a UTM log spreadsheet: date, link, source, medium, campaign, content, and notes.
Questions to answer:
Use insights to plan future content — for example, repurposing formats that convert best — see Social Media Scheduling Tools and How to Track Affiliate Links.
Open the untagged page first. Confirm that it is public and that its main action works on a phone. UTM parameters cannot repair a missing landing page, an inaccessible form or an offer that has expired. Use the final public URL rather than a draft preview.
Use a question mark to begin the query and ampersands between parameters. If a destination already contains a query, append another parameter with an ampersand instead of adding a second question mark. Keep any fragment identifier after the query. An example such as https://example.com/guide/?lang=en&utm_source=linkedin&utm_medium=social&utm_campaign=2026_11_guides#checklist is illustrative, not a live campaign.
Assign one spelling to each source and medium. UTM parameters are case-sensitive in Google’s documentation, so review copied values before publishing. Keep a campaign name stable across channels when it represents the same initiative; use content to distinguish approved creative variants.
Do not put an email address, customer name, order identifier or other personal data in UTM parameters. URLs can be copied into logs, reports and shared messages. Describe the creative or campaign rather than identifying the recipient. This checklist is an operational precaution, not a legal compliance assessment.
Test the actual link from its intended context, including any redirect or shortener. Confirm that the landing URL retains the expected UTM parameters and that the page still works. A preview opening successfully does not prove that the final public link follows the same route.
Inspect an authorised test visit using your analytics debugging workflow. Consent choices, blocking and implementation differences can affect collection. In reports, use session dimensions for session questions; first-user acquisition answers a different question. Record the property, date range, time zone and report before interpreting a result.
A platform click count and a GA4 session count are different measurements. Several clicks may occur within a session, and a click may never produce a measured page visit. UTM parameters provide campaign labels; they do not guarantee complete measurement or prove that a visitor became a customer.
If a campaign is missing, first check the published URL and the final landing address. Then inspect the relevant date range and session dimension. Check collection before rewriting a naming scheme. Do not change unrelated analytics settings merely because a new campaign has not appeared immediately.
If results are fragmented, compare exact values in the link log. Separate a spelling error from an intentional creative variant. Fix future links and annotate the decision; changing the link now does not rewrite earlier collected records. Preserve a record of which UTM parameters were used and when.
For supported campaign fields and current reporting guidance, consult Google Analytics campaign URL documentation. The examples here are planning examples, not measured results from Hostreta.
Start with the decision you want the report to support. A small web agency might ask which distribution channel sends engaged readers to a migration guide. A store might ask which launch creative leads to completed purchases. These are different questions and may need different landing pages, event definitions and comparison periods.
Write the question beside the campaign record before building links. Define the audience, intended action and observation window. Treat UTM parameters as labels for that plan. A detailed naming scheme is useful only when the team can connect the resulting report to a real decision.
Keep the first implementation small. One campaign across two channels with clearly distinguished content variants is easier to validate than dozens of inconsistent links. Once collection and reporting are understood, extend the same dictionary to additional channels. Do not rename every campaign each week merely to make a spreadsheet look current.
Suppose a business publishes a public guide and prepares a LinkedIn post plus an email newsletter. Use one campaign value, such as 2026_11_site_maintenance, across both channels. Choose linkedin with social for the first source and medium, and newsletter with email for the second.
Distinguish creative placements with content values such as checklist_post and main_button. The examples describe intended links, not observed traffic. UTM parameters do not establish whether a person saw both messages or which message persuaded them; they supply campaign context to the measurements actually collected.
Before launch, record the untagged public destination, full tagged link, channel, content value, owner and planned date. After launch, add the actual post location and publication time. A log with working evidence is more useful than a list of links that nobody can match to live placements.
| Field | What to record | Why it helps |
|---|---|---|
| Destination | Current public page URL | Avoids distributing previews or retired pages |
| Source and medium | Approved dictionary values | Reduces accidental fragmentation |
| Campaign | Stable initiative name | Connects related placements |
| Content | Creative or placement variant | Separates assets within a channel |
| Owner and date | Responsible person and actual publication | Supports corrections and handovers |
| QA evidence | Final destination and collection check | Separates planned labels from verified behaviour |
Limit editing rights to the people who maintain the dictionary while keeping the approved values available to writers. Review a sample of UTM parameters before a large distribution batch. When a new channel needs a new value, document the reason rather than silently introducing an abbreviation.
Do not place private credentials, unpublished customer details or account recovery information in the register. Where a campaign concerns a sensitive audience, use an appropriately broad campaign name. A link can travel beyond the original audience through forwarding and sharing.
Begin a session-acquisition review with sessions rather than pageviews. A person can view several pages during one visit, and the same person can return on another day. Keep users, sessions, views and completed actions in separate columns. Define the event you count as a business outcome before presenting a conversion rate.
For example, a report with 120 sessions and 8 completed contact forms would have a different meaning from a report with 120 pageviews and 8 form starts. These are hypothetical values illustrating a denominator problem. They are not results from Hostreta, a benchmark or a prediction for another campaign.
Use UTM parameters with a consistent report scope. A first-user dimension describes initial acquisition of a user, while session dimensions support a session-focused review. Do not compare one campaign’s first-user totals against another campaign’s session totals and call the difference growth.
Record the date range and reporting time zone. Compare completed periods and allow for processing delays. A partially completed day can look weaker simply because fewer hours have elapsed. Keep launch-day monitoring separate from a considered performance comparison.
If the business targets the United States, Canada, the United Kingdom, Ireland, Australia and New Zealand, review each country separately before combining totals. A campaign can generate many sessions outside the intended audience. That is a distribution observation, not proof of fraudulent traffic.
Add the landing page to the review where the reporting tool supports the required dimensions. Confirm that visitors reached the intended guide rather than a homepage or redirect destination. UTM parameters alone do not prove that the landing content matched the promise in the social post.
Review engagement alongside business actions. A high volume of short or unengaged visits may suggest a mismatch worth investigating, but it does not identify the cause by itself. Examine the actual message, page experience and implementation before changing channel priorities.
A link may pass through a social wrapper, a shortener and a website redirect before reaching the page. Test the route used by real visitors. Do not assume every component preserves every query parameter merely because the destination loads.
Keep a known-good original link in the campaign register. If UTM parameters disappear, investigate one stage at a time with the responsible site or tool administrator. Do not disable security or privacy protections to force collection. Record a measurement limitation when the permitted journey cannot preserve the desired labels.
A forwarded newsletter can retain the newsletter source even when the recipient found it through somebody else. A copied social URL can similarly retain its original campaign values. Interpret labels as evidence about the distributed link, not a complete account of every person’s discovery journey.
Avoid quietly repurposing an old campaign link for a substantially different offer. Use a new documented campaign when the initiative changes, while preserving historical records. When the same evergreen guide is promoted again, distinguish the new distribution period without changing the article’s public permalink.
A scheduler, email platform or advertising system may add campaign labels automatically. Inspect the actual generated URL before enabling another tagging layer. Duplicate parameter names and conflicting conventions create avoidable ambiguity. Assign one owner for the final values used by each channel.
For advertising, review how manual tags interact with the platform’s supported automatic tagging and your analytics integration. Do not replace a working paid-media setup with a generic social-link template. Preserve the current configuration until the responsible specialist has verified the proposed change.
For organic distribution, keep UTM parameters descriptive and modest. A channel-specific source, an agreed medium and a campaign name usually provide a clearer start than an elaborate code that only one employee understands. Extend the scheme when a report requires the extra distinction.
Use this review to improve decisions, not to promise a ranking or traffic total. UTM parameters do not create demand, improve an article’s search position or make a referral link stronger. They help organise campaign evidence when the collection and reporting implementation works as intended.
Yes, a tagged link can point to an existing public article. Keep the underlying destination stable and test the resulting link. There is no need to create a duplicate article for each campaign.
They provide campaign labels within the collected analytics data. A defensible revenue conclusion also depends on the purchase implementation, attribution model and reporting scope. State those limitations rather than presenting a label as complete causal proof.
Preserve its record and explain what was learned. Removing a spreadsheet row does not remove the earlier collected data, and it makes later comparisons harder to audit. Correct future links without disguising the history.
No. Search Console search clicks and analytics sessions answer different questions. Keep organic search performance separate from manually tagged distribution, then compare the sources using their appropriate definitions and periods.
The public destination works, the approved UTM parameters are present, the intended route has been tested and the measurement check is recorded. Mark any unverified collection step explicitly instead of describing a link-opening test as complete attribution verification.
We may earn a commission on purchases made through these links, at no extra cost to you.
Don’t miss the chance to participate in the biggest giveaway of this year.