Open the traffic acquisition report in Google Analytics 4 and you may find a row called Unassigned, sometimes a large one. It is not a country, a campaign, or a bot. It is the place where visits go when Analytics cannot say which channel they belong to, and on many sites it holds traffic that was tagged by hand: newsletter links, partner links, and campaign posts.
This guide explains what Unassigned means, what puts a visit there, and how to stop it. It draws on four pages of Google's own Analytics Help: the default channel group, the campaign URL guide, the tagging best practices for unassigned and (not set) traffic, and custom channel groups, all linked at the end. It also uses what we learned building the UTM builder on this site, which shows the channel for each link before you send it.
The short answer: Unassigned is a rule result, not a fault. A visit lands there when its source and medium match none of Google's channel rules, or when the tag could not record where the session came from. Both can be fixed, but only for the visits that come after the fix.
What Unassigned means
Google's page on the default channel group gives the plain definition. Unassigned is the value that Analytics uses when there are no other channel rules that match the event data. Its page on tagging best practices says the same thing from another angle: the unassigned row appears when Analytics cannot categorize the source of traffic.
So the word is literal. Analytics tried every channel rule in turn, none of them fitted, and the visit was filed under the one name that is left. It does not mean that the visit was fake or that the data is lost. The visit is counted, and its sessions and events are all there. It is only the label that is missing.
How Analytics picks a channel
A channel is a rule-based group of traffic sources. The default channel group has a fixed list of channels, such as Direct, Organic Search, Paid Social, Email, Referral, and Display, and each one has a rule that reads the source and the medium of the visit, and for some channels the campaign name or the type of ad. Google says the default channel group cannot be edited and that the definitions are not case sensitive.
The rules look for particular words. Email matches when the source or the medium is email, e-mail, e_mail, or e mail. Referral matches when the medium is referral, app, or link. Organic Search matches when the medium is exactly organic. Organic Social matches the mediums social, social-network, social-media, sm, social network, and social media. A paid medium is one that contains cp anywhere, or is ppc or retargeting, or starts with paid. Display needs one of display, banner, expandable, interstitial, or cpm.
Several channels also use lists that Google keeps of search, social, video, and shopping sites. A visit whose source is on one of those lists can be put in a channel without a matching medium. If a visit matches no rule at all, it is Unassigned.
Cause one: a medium that no rule knows
This is the most common cause on sites that tag their own links. A team picks medium names that make sense to them, such as newsletter, social_media, fb, or partner, and uses them in every campaign. None of those words is in the rules above. If the source is a site on one of Google's lists, the visit goes to the organic channel for that kind of site. If it is not, the visit is Unassigned.
The mistake is easy to make because the link works. The visitor lands on the page, Analytics records the session, and the report shows a source and a medium in the source and medium view. Only the channel view shows the problem, because the channel is worked out afterwards by the rules.
The same thing happens with a good idea that is slightly wrong. A medium of social_paid is not paid, because the paid rule needs the word at the start, while paid_social is. A medium of e-newsletter is not email, because the email rule needs the whole value to be one of its four spellings. The rules are exact, and a near miss is a miss.
Cause two: missing or partial campaign tags
Google's campaign URL guide says that you should always use utm_source, utm_medium, and utm_campaign. It also says that if you set one UTM parameter, you should set all the relevant ones, especially utm_source, utm_medium, utm_campaign, utm_id, and utm_source_platform, because missing UTM parameters will result in (not set) values being present in reporting.
A link that has a source and a campaign but no medium is therefore a link with a (not set) medium. The rule for Direct needs the source to be exactly (direct) and the medium to be (not set) or (none), so a visit with a real source and an empty medium is not Direct either. It meets no rule that fits, and it can land in Unassigned.
This often happens with links that were built by hand, copied from an old campaign, or shortened by a tool that dropped part of the query. If a link has lost a parameter on the way, it is the report that shows it.
Cause three: the tag fires in the wrong order
The causes above are about links. This one is about your site. Google's tagging best practices page says that if the Google tag is not configured correctly, traffic sources may not be identified or categorized, and the result can be unassigned rows in the channel groups, (not set) values, and an unexpectedly large portion of traffic put in Direct. It adds that traffic can be (not set) because it is missing session or user identity information.
The page names the common mistakes. Calling a custom event before the config command, or loading the Google tag after other events on the page, can leave the page view unable to join the session that started earlier. Changing the cookie name with a custom prefix, or using different prefixes in different places, means that users cannot be tied across sessions and events cannot be included in sessions. A cross-domain linker that starts late changes the user identity part way through the page. Setting your own client ID or session ID breaks the assumptions that the tag and the processing make about how a session is built.
Google adds a warning about server-side tagging. You should not run both a server-side and a standalone client-side setup on the same page for the same Analytics property, because every measurement for the stream should pass through the server tag.
- Put the Google tag or the config command first on the page, before any event.
- Use one cookie prefix across the whole site, or none.
- Do not set client_id or session_id yourself. Use user_id if you need your own identity.
- Start the cross-domain linker early, with the rest of the settings.
- Send every event through the server tag when you use server-side tagging, and do not also send it from the page.
Cause four: a source that is not on Google's lists
Because some channels rely on Google's lists of search, social, video, and shopping sites, a source that is on none of the lists has no way into those channels. A new social network, a regional search engine, or a small shopping site may not end up in the channel that you expect, because its source is not on the list. Google says there may be no predefined rule to categorize traffic that comes from a user-defined source or medium.
Google says that you can ask it to add a site or change a listing, by writing to the address on the default channel group page, and that Google Analytics reviews these requests at least once a year and often more frequently. It also says that the inclusion is based on several factors, including whether a significant volume of traffic comes from the site. The page offers a spreadsheet of the default sources and categories, so you can check whether your source is on a list before you decide that the tag is wrong.
What does not cause Unassigned
Capital letters do not cause it. Google says that the channel definitions are not case sensitive, so a medium of Email is treated as email for the channel. The case still matters for another reason: Google says that parameter values are case sensitive, so utm_source=Google and utm_source=google are two rows in the source report. Capitals split your numbers but they do not push visits into Unassigned.
Two other labels look similar and mean something else. (not set) is the value of a dimension that has no data, and it can show up in a source or a medium column whether or not the channel is Unassigned. (other) is an aggregated row that Google uses because of cardinality limits. It is not a channel at all. It is worth knowing which of the three you are looking at before you start to fix anything.
The channel name also depends on which dimension you are reading. Google lists three: the default channel group, which is measured for the event, the session default channel group, which is measured for each session, and the first user default channel group, which is measured for the user. They are worked out at different levels, so check that you are looking at the one you meant to.
How to find which visits are Unassigned
Start from the data, not from a guess. Google lists Session source / medium, Session medium, Session source, and Session campaign as dimensions that you can view in the traffic acquisition report. Use the source and medium view next to the channel view, and look at the pairs that go with the Unassigned row.
Then compare each pair with the rules. If the medium is one that you made up, that is cause one. If the medium is (not set) next to a real source, that is cause two. If the source is a new site that sends a lot of visits, that is cause four. If (not set) shows up for the source and the medium together, and the user and session counts also look wrong, look at the tag order, which is cause three. Google lists incorrect user and session counts among the results of events that fire out of order.
Keep a list of the pairs and the cause of each. When the same few pairs account for most of the row, a few fixes will remove most of it.
How to fix it for future visits
For links, change the medium to one of the words that Google's rules know, such as email, social, cpc, referral, or a medium that starts with paid, and keep the source, the medium, and the campaign on every link. Use lowercase everywhere. A strict naming convention is the best protection, and Google recommends one that is case sensitive and lowercase.
For the tag, follow the ordering rules above, test on a copy of the page, and look at the reports a day later. For sources that are not on a list, write to Google if the volume is large, and meanwhile set up a custom channel group.
Remember that a fix changes only the visits that come after it. A link that is already in an email that went out last month will keep its old tags, and a visit that was recorded without a session identity will not be repaired. That is why the checking should happen before a campaign goes out.
Custom channel groups for the rest
If you want to keep a naming convention of your own, a custom channel group lets you define channels with your own rules. Google says that custom channel groups can be applied to reports retroactively, that traffic is placed in the first channel whose definition it matches in the current order of the group, and that a standard property can have two custom groups, each with up to 50 channels. So the order of the channels matters, and a broad rule placed too high takes visits from the ones below it.
You can also choose one custom group as the primary channel group, which Google describes as the editable default channel group of your property, and which uses the new criteria for reporting from that point on. A channel for a medium such as newsletter, with a rule that the medium exactly matches it, is a simple way to give your own names a channel without changing the links. Google's own example shows the same method for AI assistants: create a channel that matches a regex of their addresses, and place it above Referral.
The default rules change over time too. The default channel group page now lists an AI Assistant channel, for visits from sources such as ChatGPT, Gemini, Copilot, and Grok, and says that its definitions may evolve as the market changes. A report that you checked last year may group traffic differently today.
Check the link before you send it
The cheapest fix is to find out the channel before the campaign goes out. The channel rules are public, so for most links you can read the answer from them. The UTM builder on this site does this for you: it writes the parameters, leaves the rest of the address as it was, and shows the channel that the rules give for each link, and it says when the answer depends on Google's lists of sites, so it does not guess.
It was written from Google's help pages and tested on written examples. It was not tested against a live Analytics property, so treat the channel that it shows as what the rules say and not as a record of what your property did. After a campaign starts, look at the first real visits in your reports to confirm it.
Practical checklist
- Remember that Unassigned means no channel rule matched, not that the data is missing.
- Use mediums that Google's rules know: email, social, cpc, referral, organic, or one that starts with paid.
- Always set utm_source, utm_medium, and utm_campaign together, and add utm_id and utm_source_platform when you can.
- Write every value in lowercase, with one name for each source, medium, and campaign.
- Fire the Google tag or config command before any event, and keep one cookie prefix across the site.
- Do not set your own client or session IDs, and do not run server-side and client-side tagging for the same stream.
- Compare the pairs in the Unassigned row with the channel rules, and note the cause of each.
- Use a custom channel group for naming conventions of your own, and check its order.
- Check the channel of a link before the campaign goes out, and look at the first real visits after.
Research and references
This guide was prepared from the authoritative references below.



