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.
