Google Analytics 4 automatically groups traffic into categories such as:
- Organic Search.
- Paid Search.
- Referral.
- Email.
- Direct.
- Organic Social.
Those default channels work well for many websites.
But your business may have traffic that deserves a more useful reporting category.
For example:
AI Assistants
Strategic Partners
Newsletter Partners
Influencers
Google Analytics currently allows eligible users to create custom channel groups using rule-based traffic-source categories. Custom channel groups can be used in acquisition reports, other supported reports, Explorations, and audience conditions.
That can improve reporting.
But custom channels should answer a business question.
They should not simply make the report look different.
What Is a Custom Channel Group?
A channel group is a collection of rule-based categories.
Google provides the default channel group.
You can create additional groups that classify traffic differently.
For example:
Google’s default report may show:
Referral
Your custom group may separate:
AI Assistants
from:
Other Referral
Now the traffic can be analyzed more specifically.
Custom Groups Do Not Rewrite the Actual Source
Suppose traffic arrives from:
chatgpt.com
The source remains the source.
Your custom channel rule may classify it as:
AI Assistants
That is a reporting layer.
It does not change the underlying acquisition information.
This distinction is important.
Google Currently Supports Several Rule Fields
Google’s current documentation lists fields including:
- Campaign ID.
- Campaign name.
- Default channel group.
- Manual ad content.
- Medium.
- Source.
- Source platform.
These become the building blocks for custom channels.
Example: AI Assistant Traffic
Google now includes an explicit example showing how a business could create a custom:
AI assistants
channel.
The example uses a regular expression matching referral sources associated with services such as ChatGPT, Gemini, Microsoft Copilot, Claude, and Perplexity, and recommends placing the AI Assistant channel above Referral so matching traffic enters the new category first.
This is useful because AI referral traffic may otherwise appear inside broader referral categories.
Channel Order Matters
GA4 evaluates channels in order.
Google states that traffic is included in the first channel whose definition it matches.
That means rule order can change the result.
Example:
Channel 1
AI Assistants
Channel 2
Referral
If Referral appears first:
AI-assistant traffic may be captured before GA4 reaches the AI Assistants rule.
Order more specific rules before broader rules.
Start With a Business Question
Weak reason:
I want more custom channels.
Better:
I want to see whether AI-assistant referrals generate leads differently from ordinary referrals.
Now the custom group has a purpose.
Example: Partner Traffic
Suppose you receive traffic from five strategic partners.
Google may classify all of them as:
Referral
You could create:
Partner Traffic
using source conditions that match the partner domains.
Then compare:
- Sessions.
- Engagement.
- Leads.
- Revenue.
That is a useful business category.
Example: Newsletter Partners
Suppose external newsletters link to your content.
If they use consistent UTM tagging:
You might define:
Newsletter Partners
using:
medium = email
plus selected source rules.
This keeps your own email traffic separate from paid or partner newsletters.
Use Clean UTM Tags First
Custom channels should not become a substitute for bad tagging.
Your verified UTM Parameters in GA4 guide explains why consistent:
- Source.
- Medium.
- Campaign.
values matter.
If utm_medium contains random values:
Fix the tagging.
Do not create dozens of channels to accommodate inconsistent naming.
Custom Groups Can Be Applied Retroactively
Google currently says custom channel groups can be applied retroactively in supported reports.
That is useful.
You can create a new grouping and analyze historical traffic using the new rules.
This is different from changing GA4’s editable primary channel group, where future reporting behavior has additional implications.
Standard Properties Have a Limit
Google currently allows standard GA4 properties:
2 custom channel groups
in addition to the predefined group.
Analytics 360 currently allows:
5 custom groups.
Each group can contain up to:
50 channels.
That limit is another reason to create groups intentionally.
Do not waste them on minor categories.
You Can Make a Custom Group Primary
Google currently allows a custom channel group to become the property’s primary channel group.
The primary group acts as an editable default channel definition for future reporting when selected in Admin.
This is more consequential than merely creating a comparison dimension.
For most small websites:
Start by using the custom group as an additional reporting dimension.
Do not make it primary until you understand the effects.
Keep Google’s Default Group Available
Google’s default channel group remains a useful standard reference.
Even if your business uses:
AI Assistants
or:
Partners
you may still want to compare against:
Referral
under Google’s standard classification.
This gives you both:
Standard reporting
and:
Business-specific reporting.
Custom Channel Groups Work in Acquisition Reports
Google currently says custom channel groups can be used as a primary dimension in reports that support the default channel group, including:
- User Acquisition.
- Traffic Acquisition.
This is especially useful when evaluating a specialized acquisition strategy.
Remember User vs Session Scope
Your verified GA4 User Acquisition vs Traffic Acquisition guide remains important.
A custom channel group does not remove the difference between:
First-user channel
and:
Session channel.
If the question is:
Where was the user originally acquired?
use the user-scoped view.
If the question is:
How did this session begin?
use the session-scoped view.
Custom Channels Are Also Available in Explorations
Google currently allows custom channel groups in:
- Custom reports.
- Explorations.
- Audience conditions.
That makes them useful for deeper analysis.
Example:
Create an Exploration comparing:
AI Assistants
against:
Organic Search
for:
- Landing pages.
- Engagement.
- Key-event rate.
They Are Not Available Everywhere
Google currently notes that custom channel groups are not available in the Key events paths report and are not included in the BigQuery export schema as custom group dimensions.
Do not assume your custom category will appear in every GA4 surface.
Deleting a Group Has Consequences
Google states that deleting a custom channel group is irreversible and can affect reports, audiences, and other configurations using it.
Therefore:
Do not create and delete groups casually.
Document:
- Group name.
- Purpose.
- Rules.
Editing a Group Can Change Historical Reporting
Because custom group definitions can be applied to underlying data, changing the rule can change what you see when the group is reused in reports and Explorations. Google also documents special behavior for audiences and expanded datasets.
Record significant rule changes.
Otherwise:
Last month’s report may be difficult to reproduce.
Use a Change Log
When you change:
AI Assistants rule
record:
Date
Old Rule
New Rule
Reason
Your analytics documentation becomes much easier to maintain.
Example: AI Assistant Channel
Business question:
Do AI assistant referrals generate qualified traffic?
Possible custom channel:
AI Assistants
Rules:
Match selected assistant referral sources.
Then compare against:
- Referral.
- Organic Search.
- Direct.
Use:
- Sessions.
- Engagement.
- Leads.
Your verified AI Assistant Traffic in GA4 guide provides additional context for identifying this traffic.
Do Not Create a Channel From Tiny Traffic
Suppose AI Assistants produced:
4 sessions in 90 days.
You probably do not need an elaborate reporting architecture yet.
Use volume and business relevance.
A custom channel is most useful when:
- Traffic is meaningful.
- Business cares about the source.
- Repeated analysis is likely.
A Simple Custom Channel Worksheet
Record:
Business Question:
Group Name:
Channel Name:
Source Rules:
Medium Rules:
Campaign Rules:
Order:
Expected Traffic:
Report Used:
Metric Used:
Date Created:
Last Changed:
This prevents custom channels from becoming undocumented experiments.
Conclusion
GA4 custom channel groups let you create reporting categories that match your business more closely than Google’s default channel definitions alone.
They can be especially useful for:
- AI assistants.
- Strategic partners.
- Newsletter partners.
- Specialized campaigns.
But custom channels should not replace clean acquisition tracking.
Use:
Accurate Source/Medium Data → Clear Business Question → Specific Rules → Correct Order → Documented Reporting
Keep Google’s default channel group available as a standard reference.
Your Next Action
Open:
GA4 → Admin → Data Display → Channel Groups
Do not create a group immediately.
First write one question:
“What important traffic source am I repeatedly unable to isolate with the default channels?”
If you have a clear answer, create one custom channel for that source.
Document:
Channel Name | Rule | Why It Exists | Order
Then open:
Traffic Acquisition
and compare the custom channel with Google’s default grouping.
Use the custom category only if it gives you a genuinely better business answer—not simply a different-looking report.