UTM Links: Tracking Which Posts and Profiles Send Customers

A laptop with an abstract bar chart on a small shop counter beside a notebook and pen.

A UTM link is an ordinary web address with a few labels added to the end, and Google Analytics reads those labels to report where a visit came from. Without them, a click from a newsletter button, a social profile and a printed flyer can land in the same pile, filed as direct traffic or as a vague referral. Google’s help pages set out which labels exist, which are required and how they surface in reports, and what follows summarizes them.

Analytics Mania on UTM parameters in Google Analytics 4. Google’s own definitions are in the help pages listed under Sources.

What a UTM link is

A hand holding a smartphone with a photo grid next to a printed flyer on a shop counter.

The labels are query parameters whose names begin with utm_. Google’s help page on campaign URLs gives this example: https://www.example.com/?utm_source=summer-mailer&utm_medium=email&utm_campaign=summer-sale. The address before the question mark is the page being linked to. Everything after it tells Analytics how the visitor arrived.

Adding UTM labels by hand is called manual tagging. Google’s page on traffic-source dimensions separates it from auto-tagging, in which Analytics adds a GCLID or DCLID to destination URLs for supported platforms such as Google Ads, provided the account is connected. Either method fills the same dimensions, which appear in reports, explorations and the audience and segment builders. The page adds that combining both methods is needed only in specific cases, since auto-tagging is generally sufficient for advertisers. Links placed outside Google’s ad platforms, such as a newsletter or a social profile, rely on manual tagging.

The values then appear in the Acquisition, then Traffic acquisition, report under Session source / medium, Session medium, Session source and Session campaign. When the labels are missing, those columns show “(not set)”.

The three required parameters and the optional ones

Google’s page says to always use three: utm_source, utm_medium and utm_campaign. Each has a plain job.

  • utm_source names the referrer, such as a site, a newsletter or a billboard.
  • utm_medium names the marketing medium, such as cpc, banner or email.
  • utm_campaign names the product, slogan, promo code or campaign, such as spring_sale.

Three more are optional. The utm_id parameter carries a campaign ID, matching the IDs used when campaign data is uploaded. The utm_term parameter holds the paid keyword. And utm_content tells similar links apart; the page’s example is two call-to-action links in the same email, each given a different value so the report shows which one performed better. The page also recommends setting every relevant parameter, especially utm_id and utm_source_platform. Two others, utm_creative_format and utm_marketing_tactic, are not currently reported in Google Analytics properties.

In the page’s own summer sale example, utm_source=summer-mailer identifies the email campaign as the origin, utm_medium=email separates it from in-app traffic, and utm_campaign=summer-sale names the overall campaign.

Naming rules that keep reports from splitting

A printed spreadsheet with ruled columns, a highlighter and a pen on a tidy desk.

Values are case sensitive. According to the page, utm_source=google and utm_source=Google are treated as different sources, and SpringSale and Spring_Sale become different campaigns. Lowercase is the standard it recommends.

The best-practices section asks for one unique utm_source per platform, one unique utm_medium per channel, and a utm_campaign that matches the exact campaign name. Each deviation fragments a row. A shop that tags one Instagram link as instagram and another as Instagram ends up reading two lines for one platform.

A small business could apply the rules with a short sheet of agreed values. For a social profile link: utm_source=instagram, utm_medium=social, utm_campaign=bio-link. For a newsletter button: utm_source=newsletter, utm_medium=email, utm_campaign=november-issue. Those values are illustrations of the rules above, not values Google prescribes, and the same sheet can be reused for every later link.

The help page covers campaign links such as referral links and ads, and does not discuss a site’s internal links.

How channels get sorted

Analytics also groups sessions into channels, and the default channel group is a rule-based classification that can’t be edited. Traffic that matches no rule lands in Unassigned. The page says channel definitions themselves are not case sensitive.

A few of the rules, as the page states them:

  • Direct is a source of “(direct)” with a medium of “(not set)” or “(none)”.
  • Email is a source or medium of email, e-mail, e_mail or “e mail”.
  • Organic Social is a source on a list of social sites, or a medium of social, social-network, social-media, sm, social network or social media.
  • Referral is a medium of referral, app or link.
  • Paid Search and Paid Social need a listed source plus a paid-type medium, matched by the pattern ^(.*cp.*|ppc|retargeting|paid.*)$.

By that list, a newsletter link tagged with a medium of “newsletter” matches none of the medium values the page gives for Email. A label that looks sensible to a person can still miss every rule, which is the reason to copy the page’s own values instead of inventing synonyms.

When the default rules do not fit a business, custom channel groups offer another route. A group is built from the default one or an existing custom group, in Admin under Data display, then Channel groups. Each channel gets a name, a description and conditions, and conditions can use fields such as campaign name, medium, source and source platform, with exact-match and regex operators. Traffic goes into the first channel whose definition it matches, so the order of channels matters. A standard property can hold two custom groups in addition to the default, each with up to 50 channels, and creating or editing one takes the Editor role or above at the property level. The page says custom groups can be applied to reports retroactively, though a group set as the primary channel group applies its criteria to future data only, and deleting a group cannot be undone.

Where the results show up

A tablet showing an abstract email layout on a wooden counter beside paper bags and twine.

In Google Analytics, the path is Reports, then Acquisition, then Traffic acquisition. If the report is missing from the left menu, the page says it may have been removed or hidden, and editors and above can add it back. Its dimensions include Session default channel grouping, which is the default, along with Session campaign, Session medium, Session source, Session source / medium and Session source platform.

The report’s metrics include sessions, engaged sessions, engagement rate, average engagement time per session, key events and session key event rate. With key events listed beside sessions, a campaign can be judged by the actions set up as key events, not only by visits. The page describes adding a secondary dimension with the plus icon next to the dimension drop-down, and using the search bar above the table to isolate one source, such as “google / organic”.

Traffic acquisition and User acquisition answer different questions. The first covers where new and returning users come from; the second covers where new users come from.

One quirk is worth knowing before searching for a landing page. The UTM parameters are omitted from the Landing page + query string and Page path + query string dimensions, and they appear in the Page location dimension instead.

Problems that produce (not set) and direct traffic

A well-labeled link can still be reported badly if the tag on the site is set up wrong. Google’s tagging best practices page traces unassigned rows, “(not set)” values and an excess of direct traffic to broken session or user identity. Late or out-of-order tag calls and a customized cookie prefix are named among the causes of (not set), and late linker adoption or altered client or session IDs among the causes of direct traffic.

The fixes it lists are specific. The Google tag has to initialize before any event is called, with the config command placed as early as possible and before any events. Custom events should not fire before config. A site should use one consistent cookie prefix, and linker parameter values and client or session IDs should never be customized, since Analytics expects particular formats.

For a small site, that means UTM links belong after the basics are in place. Related guides on this site cover setting up Google Analytics 4 for a small business site, reading the reports and setting up Search Console. The places where tagged links usually live are covered in posts on choosing one social platform, scheduling social posts with free tools and writing a welcome email for new subscribers.

Sources