Analytics and Tracking

Custom Channel Group

Also called custom channel grouping

Your own set of rules for sorting GA4 sessions into channels, replacing the standard classification.

Quick facts: Custom Channel Group

Category
Analytics and Tracking
Also called
custom channel grouping
Level
Intermediate
Affects
Channel reports, budget decisions, campaign comparison
Where to see it
GA4 (Admin, Data display, Channel groups), Looker Studio
In this article4
  1. How a custom channel group works
  2. Why a custom channel group matters
  3. Common mistakes with custom channel groups
  4. How to act on it

How a custom channel group works

GA4 files every session under a channel by reading the source and medium it recorded when the visit began, then matching that pair against a list of rules Google maintains. A custom channel group swaps those rules for yours. You build it in the property’s admin settings, describe each channel as a condition on source, medium, campaign name or platform, and decide the order the conditions are tested in.

Order decides everything. A session falls into the first channel whose condition it satisfies and is never tested again, so a broad rule sitting near the top will swallow traffic meant for a narrower one below it. Anything matching nothing at all lands in that group’s Unassigned bucket. The default grouping stays in place alongside yours, so a rule you regret is a mistake you can undo rather than damage you have done to the data.

Why a custom channel group matters

The default rules were written for a generic advertiser, and anything they do not recognise is pushed into referral or direct. That is tolerable until a real business looks at its own mix. Messaging is the clearest example: for many Nepali businesses WhatsApp and Viber carry a serious share of enquiries, and a QR code printed on a shopfront or a delivery box is a genuine acquisition channel. Neither has a default rule waiting for it.

A custom group lets the report match the way you actually spend money and attention. If you brief a partner site, a print campaign and a messaging list separately, you should be able to read them separately too. Reporting shaped around your own decisions is far easier to act on than reporting shaped around a tool’s generic categories.

Common mistakes with custom channel groups

The usual fault is a rule that is too generous. A condition such as medium contains social will happily collect a paid campaign you tagged as paid-social, quietly merging advertising spend with unpaid posting. Match exactly wherever you can, and save loose matching for values you genuinely cannot control at the source.

The second is expecting classification to repair tagging. A group can only sort what was recorded; it cannot invent a source for a link that arrived with no campaign medium attached. Where links were never tagged, fix the links first and write the rules second, or you will spend months maintaining conditions that describe a mess instead of removing it.

How to act on it

Start by listing the channels you actually make decisions about, not the ones a tool offers. Write each as the narrowest condition that captures it, place narrow rules above broad ones, and name every channel in words a client would recognise. Then read the Unassigned bucket: that is your list of tagging faults, and it should shrink after every fix.

Keep one written definition of the group somewhere outside the tool, so whoever builds links knows which medium values are expected. If the property itself is not yet recording sources cleanly, a proper GA4 implementation has to come before any of this is worth the effort.

Do and do not

Do

  • Order rules from most specific down to broadest
  • Tag every campaign link before writing any rule
  • Check the Unassigned bucket after each change

Do not

  • Use loose contains matches that catch unrelated traffic
  • Rename channels instead of fixing the underlying tagging
  • Assume a custom group repairs badly tagged historic visits

Questions people ask about this

Does a custom channel group change my historic data?

No. Channel rules are applied when a report is built, not when the visit is collected, so the source and medium values already recorded stay exactly as they were. The default grouping remains available beside yours, and you can delete or rewrite a custom group at any time without losing anything underneath it.

Should I build a custom channel group or fix my campaign tagging?

Fix the tagging first. Channel rules can only sort the source and medium values your links actually carry, so consistent tagging solves problems no rule can reach. Once tagging is reliable, a custom group is worth building for the channels the default rules never anticipated, such as messaging apps, printed QR codes or partner referrals.

Why is traffic still showing as Unassigned after I built my group?

Because those sessions matched none of your conditions. Every custom group carries its own Unassigned bucket, and it fills with visits whose source and medium fall outside every rule you wrote. Treat it as a task list rather than an error: inspect the values sitting in it, then either add a rule that covers them or correct the links producing them.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.