GA4 Custom Channel Groups: Setup Rules, Examples, and Reporting Checks

Overview

A channel group is a set of rules that places traffic into labels such as Paid Search, Organic Search, Email, Affiliates, Organic Social, or Partnerships. GA4 includes a default channel group, but its categories may not match the way your organization buys media, names campaigns, or reports performance. A custom channel group lets you create a reporting view that reflects your measurement plan.

Keep three concepts separate during an audit:

• Source: the platform or referring origin, such as google, newsletter, or partner.example.
• Medium: the traffic type recorded in the URL or collection setup, such as cpc, organic, email, or referral.
• Channel: the reporting category created by rules that use source, medium, campaign, source platform, and other available dimensions.

Choose the scope before comparing results. Session channel dimensions describe the channel that drove a session, while first-user channel dimensions describe how a user was originally acquired. Mixing these in one report can make a campaign appear to have different results. For a broader measurement foundation, document the intended events and properties in a tracking plan before changing channel rules.

Channel-definition comparison

Treat this table as a starting taxonomy, not a universal definition. Your naming conventions should reflect how campaigns are tagged and how stakeholders make budget decisions.

Checklist by scenario

Before creating the group

1. List the business questions the group must answer. For example: “How does paid social compare with paid search?” is more useful than “Create more channels.”
2. Export or inspect recent source, medium, campaign, and source-platform values. Look for spelling variants, capitalization, spaces, and unexpected values.
3. Define the approved taxonomy. A practical template is Channel | Source rule | Medium rule | Campaign rule | Owner | Review date.
4. Decide whether the group is intended for session acquisition, user acquisition, or another reporting view.
5. Write the naming convention into your campaign documentation. The UTM naming guide can support this step.

For a new custom channel group

1. Open the relevant GA4 property and go to Admin. Under the property’s data display settings, open Channel groups. Interface labels can change, so use the property search if the menu differs.
2. Select the option to create a new channel group and give it a descriptive name, such as “Acquisition Reporting v2,” rather than a vague name such as “Test.”
3. Add channels one at a time. For each channel, choose the dimensions and operators that identify it. Prefer explicit conditions for high-value channels.
4. Order rules from specific to general. For example, classify paid social before a broader social rule, and named partners before a general referral rule.
5. Save the group, then use it in acquisition reports or Explorations where the custom channel-group dimension is available. Confirm the selected dimension is the custom group, not the default group.

Regex and rule examples

Use anchored patterns when you mean an exact family of values. Examples include ^(cpc|ppc|paid_search)$ for paid search media and ^(email|e-mail|newsletter)$ for email. A source pattern such as ^(facebook|instagram|linkedin|tiktok)$ can identify selected social platforms, but it should be paired with a paid or organic condition rather than used alone. Test regex behavior against real values; do not assume punctuation, spaces, or capitalization will be normalized for you.

Scenario checklist

• Paid campaigns: Confirm every ad platform uses a documented medium and that auto-tagging does not conflict with manual UTMs.
• Email: Require UTMs on links that leave the email platform, and exclude internal links from campaign tagging.
• Affiliate: Separate affiliate traffic from ordinary referrals with a stable medium or approved source list.
• Social: Maintain separate paid and organic rules where budget and conversion decisions require it.
• Partners: Keep a controlled list of partner domains and decide whether partner traffic should override a generic referral category.
• Cross-domain journeys: Verify that domains are configured consistently before diagnosing channel changes. See the cross-domain tracking guide.

What to double-check

Run a QA review before using the group for a budget or performance decision.

• Rule precedence: Confirm a broad rule is not capturing traffic intended for a narrower channel.
• Unassigned traffic: Inspect sessions with an unassigned channel. Common causes include missing or nonstandard campaign values, incomplete tagging, and traffic sources that do not meet any rule.
• Direct traffic: Do not automatically treat every direct session as a campaign failure. Check redirects, missing UTMs, consent behavior, landing-page links, and cross-domain configuration.
• Dimension scope: Compare session channel groups with first-user channel groups only when the difference is understood and intentional.
• Historical behavior: Check how the custom group appears across the selected date range. Avoid assuming that changing a rule will reconstruct every historical report exactly as expected.
• Conversions: Validate channel results against conversion events and revenue definitions. A channel report is only as reliable as the conversion tracking behind it; use the GA4 tracking audit checklist for a wider review.

Use a small comparison report with date, session channel, source, medium, campaign, sessions, engaged sessions, conversions, and revenue where applicable. Investigate large shifts by drilling from channel to source and medium instead of editing rules immediately.

Common mistakes

• Changing the default group instead of creating a custom one: Preserve the standard view when it is useful for comparison, and document why the custom taxonomy differs.
• Using source alone: The same platform can send paid, organic, referral, and email traffic. Combine source with medium, campaign, or source platform where needed.
• Making rules too broad: A rule containing “social” may capture values that are not social campaigns. Prefer approved values and explicit patterns.
• Ignoring capitalization and spelling: “Paid-Social,” “paid_social,” and “paidsocial” may not behave as one value. Standardize future tagging and account for existing variants during cleanup.
• Calling all referrals partnerships: Referral traffic includes many sources. Maintain a partner allowlist rather than assuming every referral is commercially managed.
• Reporting without annotations: Record the group version, rule changes, campaign launches, and tracking fixes so month-to-month shifts have context.

When to revisit

Review the channel group before seasonal planning cycles, whenever a new advertising or email platform launches, and whenever campaign naming conventions change. Also revisit it after a site migration, consent or tagging workflow change, cross-domain update, or unusual movement in unassigned, direct, or referral traffic.

Set a recurring lightweight check: sample recent source and medium values, compare channel totals with the previous period, inspect unassigned traffic, and confirm that important conversions still appear in the expected channels. Review the full taxonomy at least annually, or sooner if reporting needs change. When a problem appears, first identify the source value and collection path, then decide whether to fix the tagging implementation, update the rule, or document an intentional exception.

The practical goal is not to eliminate every irregular value. It is to make channel definitions explicit, repeatable, and stable enough that marketers, analysts, and developers interpret acquisition reports the same way.