GA4 Default Channel Groups Explained for Clients

GA4 default channel groups explained for clients

Every agency has had this conversation. The monthly report goes out, and the client replies with one line: "Why is Direct our biggest channel? Nobody types our URL in."

It is a fair question, and the honest answer is that GA4 is not telling your client what they think it is. GA4 default channel grouping is a set of rules Google applies to every session, sorting it into a bucket like Organic Search, Paid Search or Direct based on the source, medium and campaign name attached to that visit. Those rules are rigid, they are applied at session level, and when a visit matches none of them it lands in a bucket most clients have never heard of: Unassigned.

If you report on GA4 for clients, you need to explain those buckets in one sentence each. This guide gives you the plain-English version of every default channel, the three issues that come up most in client reporting (organic vs direct traffic in GA4, Unassigned traffic, and when to build custom channel groups in GA4), and the wording we use to explain it without losing the room.

Last updated: August 2026

Key takeaways

• GA4 default channel grouping is rule-based, not editorial. GA4 reads the source, medium and campaign name on a session and matches them against fixed Google-defined rules.
• Direct is not "people who typed your URL". It is GA4's fallback for any session with no usable source, which includes untagged email links, PDFs, in-app browsers and expired attribution.
• Unassigned means "no rule matched", not "no value". It is almost always a tagging problem on your side, and fixing it does not repair historical data.
• Custom channel groups apply retroactively but cannot invent missing data. They reprocess most reports back to property creation, yet never rescue sessions that arrived untagged.
• Google Analytics 4 is the most-connected platform across the client accounts connected to ReportsMate: 30 of the 43 clients with any platform attached have GA4, or roughly 7 in 10.

What this guide covers

1. What is GA4 default channel grouping?
2. The full list of GA4 default channels in plain English
3. How does GA4 decide which channel a session belongs to?
4. Why does organic vs direct traffic in GA4 look wrong?
5. What is Unassigned traffic in GA4 and how do you fix it?
6. When should you build custom channel groups in GA4?
7. What we see across the GA4 properties we report on
8. How to explain channel groups to a client
9. FAQs

What is GA4 default channel grouping?

GA4 default channel grouping is Google's built-in classification system that sorts every session into one of roughly twenty named channels based on the source, medium and campaign name recorded for that session. It turns thousands of raw referrer values into a chart a client can read in five seconds.

The important word is default. You did not choose these buckets and you cannot edit them. Google defines the rules and every GA4 property uses the same set, which is what makes one agency's Organic Search number comparable to another's. The rules live in the Google Analytics Help centre and Google does revise them, so if a client challenges a definition, send them to the source rather than paraphrasing from memory.

Two pieces of insider vocabulary worth defining for clients, because both come up constantly here:

• Source and medium. Source is where the visit came from (google, facebook.com, newsletter). Medium is how (organic, cpc, email, referral). Channel groups are built almost entirely from these two fields.
• Session-scoped attribution. GA4 assigns the channel to the session using the last non-direct source it can find in the lookback window. That differs from the conversion-scoped attribution in the Advertising reports, which is why two GA4 reports can disagree about the same conversion. Our walkthrough of the GA4 traffic acquisition report covers where that split appears.

The full list of GA4 default channels in plain English

Keep this table where your account managers can find it. It ends most "what does that mean" emails.

Two notes worth passing on. Paid Other and Unassigned are different problems: Paid Other means GA4 knows the click was paid but not what kind, while Unassigned means it could not classify the session at all. And this list is deliberately generic, so it will never know that your client's biggest partner site is an affiliate rather than a referral. That is what custom groups are for.

How does GA4 decide which channel a session belongs to?

GA4 evaluates source, medium and campaign name against its rules in a fixed order, assigns the first channel that matches, and drops the session into Unassigned if nothing does. There is no fuzzy matching and no interpretation. Three consequences matter before you write report commentary.

The rules are literal. A medium of e-mail is not email. CPC with a trailing space is not cpc. Newsletter is not a recognised medium at all. GA4 corrects none of these, which is how good campaigns end up in Unassigned.

Auto-tagging beats manual tagging. With auto-tagging on in Google Ads, the gclid parameter carries campaign detail through and GA4 classifies it correctly without a single UTM. Hand-written UTMs on the same links can produce conflicting signals. Google Ads Help is the authority on auto-tagging behaviour, and it is worth checking that setting before blaming GA4.

Attribution expires. GA4 remembers a session's acquisition source for a limited window. Someone who arrived through an ad in January and returns unprompted in April is a new Direct session, not a delayed ad conversion. Explain that to any client convinced their Direct number is inflated. It partly is, and that is normal.

We built ReportsMate email-first because, after years around agency reporting, the dashboards clients were handed almost never got logged into. The report that lands in the inbox is the one that gets read, and if that report is the only place a client sees a channel chart, the labels had better be explained in the email itself. If the channel chart is going into a client email, the explanation belongs in that same email.

Why does organic vs direct traffic in GA4 look wrong?

Organic vs direct traffic in GA4 usually looks wrong because Direct is a catch-all bucket, not a behaviour. When a client says "our Direct is too high", they are nearly always looking at a tagging gap rather than a surge of people typing the URL.

Traffic that lands in Direct despite having a real source includes:

• Links clicked in desktop email clients such as Outlook, where no referrer is passed
• Links in PDFs, documents and slide decks
• Links opened from messaging apps and in-app browsers
• HTTPS to HTTP journeys, where the referrer is stripped
• Returning visitors whose original attribution window has expired
• Redirect chains that dropped the query parameters

The organic side has its own quirk. GA4 counts sessions on your site; Google Search Console counts clicks in the search results. They measure different events at different points, so they will never match, and neither is broken. We covered that specific mismatch in Search Console vs GA4 organic traffic, because it is the second most common client question after Direct.

The practical move is to stop treating Direct as a channel to optimise and start treating it as a diagnostic. If Direct exceeds roughly a third of sessions on a site with meaningful marketing spend, audit the tagging on email, offline campaigns and partner links before drawing a single conclusion from the chart.

What is Unassigned traffic in GA4 and how do you fix it?

Unassigned traffic in GA4 is any session whose source, medium and campaign combination matched none of Google's channel rules. It is not mystery traffic and it is not bot traffic. It is a labelling failure, and it is nearly always fixable on your side.

The usual culprits, in the order we find them:

1. Non-standard mediums. newsletter, partner, qr, Email, Social - none map to a default channel. GA4 recognises a specific set of values, and anything outside it falls through.
2. Partial UTMs. A link with utm_source and utm_campaign but no utm_medium gives GA4 nothing to classify.
3. Consent and modelling gaps. Where consent is declined, some sessions arrive without a full parameter set.
4. Broken redirects. A shortener or redirect that strips query strings wipes the tags before GA4 sees them.
5. New or renamed platforms. GA4 has to recognise a source before it can classify it, and newer ad networks sometimes take time to appear.

The fix is boring and it works: standardise your UTM conventions, write them down, and make everyone who builds a link use the same builder. We keep a free UTM builder for exactly this reason. Agree medium values across the whole client roster, use lowercase everywhere, and never invent a medium when an existing one fits.

Be clear with clients about one thing: fixing tagging today does not retroactively fix last quarter's Unassigned. Those sessions arrived unlabelled and stay that way. Set that expectation early rather than promising a clean historical chart you cannot deliver.

When should you build custom channel groups in GA4?

Build custom channel groups in GA4 when the default set genuinely misrepresents how a client acquires customers, and not before. Every custom group is a definition your agency now owns and has to maintain.

Good reasons to build one:

• A partner or affiliate programme that GA4 files as generic Referral
• Branded and non-branded paid search needing separate reporting, which the defaults never do
• Several ad platforms rolling up into one "Paid Media" line the client understands
• Offline or print campaigns using a vanity URL scheme that deserves its own bucket
• Marketplace or retail-media traffic that should be split out from Referral

Reasons that are not good enough: you dislike the word "Unassigned", or a channel name sounds unimpressive. Renaming a problem does not fix it.

Two mechanics before you commit. Custom channel groups apply to most standard reports and Explorations back to when the property was created, so the historical view does change. But they cannot invent data that was never collected, and they add a definition your successor will have to decode. If you manage a large roster, keep custom groups identical across clients so a single explanation covers every report you send.

What we see across the GA4 properties we report on

We can only speak to our own data, so here is what it says. Across the client accounts connected to ReportsMate, Google Analytics 4 is the most-connected platform: of the 43 clients with at least one platform connected, 30 have GA4 attached, roughly 7 in 10. Nothing else is close.

Two things follow. GA4 is the shared language of agency reporting, so whatever else a client has connected, the channel chart is usually the one page everyone looks at. And connections average under two platforms per client, with only about a third of connected clients attaching more than one. Half of our GA4 clients (15 of 30) also have Google Ads or Meta Ads connected, which means the other half are reading Paid Search numbers with nothing to cross-check them against.

A smaller observation, labelled honestly because it is not a benchmark: of the 16 GA4 properties we currently hold cached report data for, 15 showed at least some Unassigned sessions in the period. Small sample and directional only, but it matches what we see in support conversations. Unassigned is the normal state of a GA4 property, not an alarm. The Google Analytics integration page covers what pulls through into a report.

How to explain channel groups to a client

The best client explanation of channel groups is three sentences long and lives inside the report, not in a separate document nobody opens. Here is wording you can adapt:

"Channels are how Google sorts your visitors by where they came from. Direct means Google could not see a source, which usually points to email or offline links rather than people typing your address. Unassigned means a link was not tagged properly, and we are cleaning those up."

No attribution theory, no acronyms. Three sentences that pre-empt the two questions you would otherwise field by email.

Delivery matters as much as wording. A channel chart behind a dashboard login gets seen when the client remembers to log in, which for most accounts is somewhere between rarely and never. The same chart, with the same three sentences under it, arriving as a branded email on a set schedule, gets read. That is the thesis behind our email-first model. See how ReportsMate works for the mechanics.

One last term to hand your clients: reporting cadence, the fixed rhythm at which reports arrive. A chart that shows up monthly with commentary teaches a client to read it. The same chart shown once a quarter in a crisis meeting never will.

FAQs

Q: What is the difference between default channel grouping and source/medium in GA4?

A: Source and medium are the raw fields recorded on a session; default channel grouping is Google's rule set for turning them into readable buckets. Source is where the visit came from, medium is how it arrived, and the channel is the label GA4 assigns after matching both. For client reporting, always show the channel. For diagnosing a problem, drop back to source and medium, because that is where you will spot the misspelled e-mail medium or the missing utm_medium that pushed traffic into Unassigned. Show the channel to the client and keep source and medium for your own diagnosis.

Q: Can I edit GA4's default channel grouping?

A: No. The default channel grouping is defined by Google and cannot be edited in any GA4 property. You can create a custom channel group alongside it, which appears as a separate dimension while the default stays untouched. This is deliberate: the default set is what keeps definitions consistent across every property, so anyone comparing accounts is comparing the same thing. If a default channel is genuinely wrong for a client, the fix is better tagging or a custom group, never an edit to the default.

Q: Why is Direct traffic in GA4 so high?

A: Direct is GA4's fallback bucket, so it collects every session where no source could be determined, not just people typing the URL. Email clients that strip referrers, PDF links, messaging apps, in-app browsers, redirect chains that drop parameters, and returning visitors whose attribution window expired all land there. If Direct exceeds about a third of sessions on a site with real marketing activity, treat it as a trigger for a tagging audit rather than a genuine finding. Start with email links and any offline or partner campaigns, because that is where the untagged traffic usually hides.

Q: Does Unassigned traffic mean something is broken?

A: Usually yes, but it is a tagging problem rather than a GA4 fault. Unassigned means the session's source, medium and campaign combination matched none of Google's rules, which most often traces to a non-standard medium value, a UTM missing utm_medium, or a redirect that stripped parameters. A small amount is normal in almost every property. A large or growing share is a signal to audit link tagging, standardise UTM conventions, and check any recently launched campaign or new ad platform.

Q: Will creating a custom channel group change my historical reports?

A: Yes, for most reports. GA4 applies custom channel groups to standard reports and Explorations retroactively, back to the property's creation, so the historical view shifts once the group exists. What it cannot do is classify sessions that arrived without usable data. If a visit had no medium recorded, no custom rule can invent one and it stays Unassigned. Tell clients this before you build the group, so the change in their historical chart is expected rather than alarming.

Q: Why don't GA4 channels match my Google Ads or Meta Ads numbers?

A: They measure different things with different rules, so they will never match exactly. GA4 counts sessions using session-scoped, last-non-direct logic in your reporting time zone; the ad platforms count clicks and conversions using their own models and windows, crediting conversions back to the click date. Add Performance Max and Demand Gen landing in Cross-network rather than Paid Search and the gap widens. Report both, explain that the difference is expected, and pick one as the source of truth for decisions. Our piece on Google Ads vs GA4 conversions covers the arithmetic.

Q: What is Cross-network in GA4?

A: Cross-network is the channel GA4 assigns to Google campaigns running across multiple networks at once, most commonly Performance Max and Demand Gen. Because those campaigns can serve on Search, Display, YouTube, Discover, Gmail and Maps within one campaign, Google does not split them into Paid Search or Paid Video and files them under Cross-network instead. If a client's Paid Search number dropped sharply the month they moved budget into Performance Max, this is almost certainly why. Nothing was lost, it moved buckets.

Final tips

Get four things right and GA4 default channel grouping stops being a monthly argument.

Standardise tagging before you touch reporting. Agree UTM medium values across the entire client roster, keep everything lowercase, and route every link through one builder. Most channel reporting problems are tagging problems in disguise.

Explain Direct once, in writing, inside the report. It is the question you will otherwise answer every month for every client.

Treat Unassigned as a to-do, not a defect. Audit it, fix the tags going forward, and be honest that history will not clean itself up.

Use custom channel groups sparingly. Every custom definition is one your agency has to remember and explain. If the default set is close enough, leave it alone.

The reporting itself should not be the bottleneck. If your team still assembles GA4 channel charts by hand each month, that is time not spent on the analysis clients pay for. Automated, white-labelled reports that pull GA4, Google Ads, Meta Ads, Search Console and Google Business Profile into one branded email fix the mechanics so you can spend your time on interpretation. Compare current plans and what each includes when you are ready.

Stop losing your Sundays to client reports. Start your free 14-day trial - no credit card, no setup, cancel anytime. Your clients get branded reports in their inbox automatically, with the channel labels already explained.