NumerSpace

Categories

Finance & InvestmentHealth & FitnessWork & CareerTime & DateMarketing & AnalyticsMath & ConvertersEducation & ProductivityHome & LivingClothing & SizingPetsVehicle & TravelFaithAstrologyTax & BillsUnit Converters
Blog
TR EN
Türkçe oku
Marketing & Analytics

GA4 Unassigned traffic: which utm_medium values map to which channel

Unassigned means no GA4 channel rule matched. Tables from Google's rules show where each utm_medium lands, given source and campaign.

Ali Yılmaz··10 min read
Campaign tags sorted into channel bins, with one tag left outside every bin

GA4 Unassigned traffic is traffic that GA4 could not place in any of its 19 default channels. Google's default channel group page defines Unassigned as the value Analytics uses when no other channel rule matches the event data. For hand-tagged traffic, the rules look at source, medium and sometimes campaign name together. A tagged link lands there when that combination fits no rule, such as a utm_medium of newsletter, mail or qr.

The first table below lists Google's manual-traffic rules channel by channel, with the exact values each one accepts. It follows the English help page as read on November 7, 2026, and Google says these definitions may evolve as the market changes. The second table shows which rules example tags fit and where they should land, including paid tags that end up in organic channels. Steps to find the values in your own report and to test a fix are in "How to fix Unassigned traffic in GA4."

When GA4 shows Unassigned

Split Unassigned traffic into two cases first, because each one has its own fix. In the first, the link is tagged and the report shows a readable source and medium, but the tag matches no channel rule. In the second, the session's source and medium were recorded as (not set). Google's page on the (not set) value says such traffic is shown as Unassigned in the default channel group.

A (not set) value can have more than one cause, and the report value alone does not tell you which. The same page says session source / medium reports (not set) when the automatically collected session_start event is missing. It names two likely causes: a Google tag in Google Tag Manager (GTM) without the Initialization trigger, and consent code sending default instead of update. Google's URL builders page adds that missing UTM (campaign tag) parameters produce (not set) values.

The rest of this post covers the first case, the campaign values you write by hand. Google's page gives separate rules for traffic whose source platform is Google Ads, where the channel comes from ad network type and campaign type. The tables below show the page's manual-traffic rules. How untagged links distort channel reports is covered in the tracking section of the marketing return on investment (ROI) and customer acquisition metrics guide.

Which utm_medium values go to which channel

Google lists 19 rules for manual traffic, and most of them check the source or campaign name as well as the medium. These values reach GA4 through UTM parameters on the link: utm_medium carries the medium, utm_source the source and utm_campaign the campaign name.

In the table, "paid pattern" means Google's regular expression ^(.*cp.*|ppc|retargeting|paid.*)$. It accepts any value containing cp, the exact values ppc and retargeting, and any value starting with paid. That is why cpc, the usual tag for cost per click (CPC) ads, counts as paid. In each row both the medium and the source or campaign column must hold, unless a cell starts with "or."

Channelutm_medium ruleSource or campaign conditionClose spelling that misses
Direct(not set) or (none)Source is exactly (direct)Source set, medium missing
Cross-networkNo medium conditionCampaign name contains cross-networkcrossnetwork
Paid ShoppingPaid patternShopping-site source or campaign name matching the shop patternremarketing
Paid SearchPaid patternSearch-engine source (google, bing, yandex)ads, sponsored
Paid SocialPaid patternSocial-site source (facebook, ig, linkedin)promoted
Paid VideoPaid patternVideo-site source (youtube, vimeo)video-ads
Displaydisplay, banner, expandable, interstitial, cpmNo source conditiondisplay-ads, banners
Paid OtherPaid patternNo source conditionNone
Organic ShoppingNo medium conditionShopping-site source or campaign name matching the shop patternCampaign named workshop-invite
Organic Socialsocial, social-network, social-media, sm, social network, social mediaor social-site sourcesocial_media, socialmedia
Organic VideoAny value containing videoor video-site sourceNone
Organic SearchExactly organicor search-engine sourceorganic_search, seo
AI AssistantExactly ai-assistantNo source conditionai, chatgpt
Referralreferral, app, linkNo source conditionpartner, qr
Emailemail, e-mail, e_mail, e mailor source is one of those fournewsletter, mail, email-newsletter
AffiliatesExactly affiliateNo source conditionaffiliates, influencer
AudioExactly audioNo source conditionpodcast
SMSExactly smsor source is exactly smstext
Mobile Push NotificationsEnds in push, or contains mobile or notificationor source is firebasealert

The main takeaway is that a medium only satisfies a channel rule when it matches one of these lists. Channel definitions are not case sensitive, so a link tagged Email still matches the Email rule. A value that means the right thing but is not listed, such as newsletter or mail, does not count. It falls into Unassigned unless the source sits on one of Google's lists.

The campaign condition in both Shopping rules is Google's pattern ^(.*(([^a-df-z]|^)shop|shopping).*)$. It accepts shop at the start, after a non-letter or after an e, so black-friday-shop and eshop match while workshop does not. Paid Shopping needs that condition or a shopping-site source, plus the paid pattern. Google lists the conditions as OR then AND, and the table reads them in that grouping.

The Email rule lists its four values with an equals sign. Google's regular expressions page adds that Analytics regex is full-match by default. Read together, the two pages mean a value like email-newsletter misses the Email rule even though it contains email.

Which rule wins when a value fits two?

When a tag fits two rules, their order decides the channel, but the default channel group page does not state that order. The custom channel groups page says traffic goes into the first channel it matches in the group's order. The same page says a new group starts as a copy of the default group. Treating the table order as the evaluation order is an inference from those two statements.

Even a plain paid tag fits several rules: facebook / paid_social matches Paid Social, Paid Other and Organic Social. If the order inference holds, paid rules come before organic ones and the source lists come before medium-only rules such as Email. A session from a listed social site with medium email would then go to Organic Social. An email campaign whose name matches the shop pattern would go to Organic Shopping.

A tag that fits one rule does not depend on order. Test any tag that fits several in your own report.

Why paid traffic shows up in an organic channel

Paid traffic lands in an organic channel when the source is on a list but the medium misses the paid pattern. The tag then fits no paid rule and matches only Organic Search, Organic Social or Organic Video, depending on the source. The table below shows every rule each example tag fits and the channel to expect. The source list is the file Google links from its default channel group page, with a server date of February 9, 2023.

Tag (source / medium)Rules it fitsExpected channelWhat the result rests on
newsletter / newsletterNoneUnassignedSource not on the 2023 list
email / newsletterEmailEmailOne rule
newsletter / mailNoneUnassignedSource not on the 2023 list
newsletter / no mediumNoneUnassignedMedium (not set), source not on the 2023 list
partner-site / social_mediaNoneUnassignedSource not on the 2023 list
bing / adsOrganic SearchOrganic SearchOne rule, source on the 2023 list
facebook / remarketingOrganic SocialOrganic SocialOne rule, source on the 2023 list
youtube / video-adsOrganic VideoOrganic VideoOne rule
facebook / emailOrganic Social, EmailOrganic SocialRule order (inference)
bing / cpmPaid Search, Display, Paid Other, Organic SearchPaid SearchRule order (inference)
publisher-site / cpmDisplay, Paid OtherDisplayRule order (inference)
publisher-site / mobile-bannerMobile Push NotificationsMobile Push NotificationsOne rule
newsletter / email, campaign spring-shopOrganic Shopping, EmailOrganic ShoppingRule order (inference)

The Bing, Facebook remarketing and YouTube video ads in the table each fit a single organic rule, so their result does not depend on order. In reports built on the GA4 channel group, their sessions and conversions count as organic, and the paid channels come up short. If you calculate return on ad spend (ROAS) or customer acquisition cost (CAC) by channel from those reports, the result shifts. Which way each channel's conversion rate moves depends on the two groups' own rates.

The table models the published rules, not GA4 output, so confirm results with the test step below.

Why cpm and mobile values land in unexpected channels

The cpm value fits several rules, so rule order decides its channel. Display lists it by name for ads bought on cost per mille (CPM), but cpm also contains cp, so it matches the paid pattern. If the order inference holds, a listed search-engine source gives Paid Search and an unlisted source gives Display. Because the order is not documented, both results are predictions to test.

The Mobile Push Notifications rule catches any medium containing mobile or notification. A value like mobile-banner misses Display, because that rule wants exactly banner. It fits only the push rule, so its result does not depend on order and it lands in Mobile Push Notifications.

Do Google's own UTM examples match its rules?

Google's URL builders page gives paid_social and organic_search as medium examples in its UTM best-practice table. The value paid_social fits the paid pattern, and with a listed social source the order inference points to Paid Social. The value organic_search is not the exact organic that the Organic Search rule wants. It fits Organic Search when google or another listed engine is the source, and fits no rule with an unlisted source such as newsletter.

The same table suggests fb for Facebook and insta for Instagram as source values. Google's source list contains fb and ig, but not insta. The list file dates from 2023, and the help page calls the social list a regex list, so live processing may differ. By the list, an insta / paid_social tag fits only Paid Other, while the listed instagram or ig removes the doubt.

How to fix Unassigned traffic in GA4

You fix Unassigned traffic in GA4 by finding which source / medium pairs land in that row. Google's URL builders page says session source / medium and session campaign appear in the Acquisition > Traffic acquisition report. Count sessions: the Unassigned total for a chosen date range, its share of all sessions and its split by source / medium pair. Compare before and after a fix with two periods of the same length made of complete days.

  1. In that report, set the primary dimension to Session default channel group and note the Unassigned session count and share.
  2. Show Session source / medium next to the channel group and read only the Unassigned rows.
  3. If you see a readable source with an unrecognized medium, change the value on the campaign link using the first table. If the source is set but the medium is (not set), check whether the link carries a utm_medium.
  4. If both source and medium are (not set), review the setup before you change any tags: the session_start event, the GTM trigger and the consent commands.
  5. Test the fix: give the link a utm_campaign value used only for this test, open it in a new session and check that the utm_ parameters are still in the landing page address. Once the data reaches the report, read that campaign's session source / medium and Session default channel group.

The test needs a new session because, per Google's page, Session default channel group shows the channel through which users started new sessions. A lower Unassigned share between two periods does not prove the fix on its own, since traffic in other channels changes too. The proof is the test campaign landing in the expected channel.

A UTM fix does not relabel past sessions, and the default channel group cannot be edited, so old sessions stay in Unassigned. Custom channel groups can be applied to reports retroactively, but they only regroup the source, medium and campaign values that were recorded. They can show sessions recorded with the newsletter medium under Email, but they cannot restore a source recorded as (not set). Changing the primary channel group, according to Google's page, only affects data from that point forward.

A short utm_medium glossary for your team

A team glossary turns the first table into a handful of source / medium pairs everyone uses. Each utm_medium value below matches its own channel rule. When the source is on a search or social list, or the campaign name matches the shop pattern, the result depends on rule order:

  • Email newsletters: medium email, source the newsletter or sending tool name, and a campaign name that does not match the shop pattern (such as november-newsletter).
  • Organic social posts: medium social, source the platform as spelled on the list (instagram, linkedin).
  • Paid social ads: medium paid_social or cpc, source the listed platform name.
  • Search ads outside Google Ads: medium cpc, source bing or yandex.
  • Display and banner ads: medium display.
  • Linking sites and press: medium referral. Google has no channel for quick-response (QR) code flyers, so filing them under referral is a reporting choice.
  • Commission-based affiliates: medium affiliate. Use sms for text messages and push for app notifications.

Use lowercase and one spelling per value in every campaign. The channel rules ignore case, but parameter values are case sensitive according to the URL builders page, so Email and email become two rows. Building every link with the UTM builder keeps that difference out from the start. Influencers, QR codes and messaging apps have no default channel of their own, so tracking them separately takes a tested custom channel group.

Related Tools

UTM Builder
Create UTM-tagged URLs for campaign tracking
Illustrated Google Ads invoice with ad cost, the 4.5% surcharge and VAT on separate lines
Marketing & Analytics

Google Ads regulatory operating cost in Turkey: what you are billed

Google adds a Regulatory Operating Cost to ads served in Turkey: 4.5% until the end of 2026, 2.5% from January 1, 2027. VAT and billed CPC examples.

Rising bar chart made of gold coins with an upward arrow and a megaphone
Marketing & Analytics

What Is ROAS? How to Calculate Return on Ad Spend

Calculate ROAS with the right formula, learn what counts as a good ratio by industry, and see the steps that turn ad spend into profit.

Paper-cut marketing funnel with a rising orange bar chart and arrow at its narrow end
Marketing & Analytics

Marketing ROI and Customer Acquisition Metrics Guide

Learn to read CAC, LTV, ROAS, and profit margin as one system instead of isolated numbers, and see which ratio signals sustainable growth versus risk.

Ali Yılmaz: Ali Yılmaz is NumerSpace's editorial identity, writing about finance, health, units of measurement, time and everyday calculations. Every article's figures and sources are verified before publication.