Understanding GA4 Default Channel Groups: The Complete Guide

What Are GA4 Channel Groups?

Channel groups in Google Analytics 4 organize your traffic into meaningful categories like Organic Search, Paid Social, Email, and Direct. They answer a fundamental question: Where did this traffic come from?

Unlike Universal Analytics, which had a relatively forgiving channel classification system, GA4 uses strict, rule-based logic. If your UTM parameters don't match GA4's expected patterns, your traffic gets misclassified—or worse, marked as "Unassigned."

Understanding how GA4 channel groups work isn't just academic. It's the difference between:

• Knowing which campaigns actually drive conversions
• Making budget decisions based on accurate attribution
• Trusting your analytics data vs. constantly questioning it

This guide breaks down GA4's default channel groups, explains the classification rules, and shows you how to avoid common pitfalls.

---

The "Order of Operations" (Priority)

GA4 evaluates traffic against a specific top-to-bottom hierarchy. Traffic is "claimed" by the first rule it matches. For example, if a link matches the Paid Shopping rule, it is never evaluated for Paid Search, even if it uses utm_medium=cpc.

This priority system is critical to understand because it explains why certain source/medium combinations end up in unexpected channels.

---

GA4 Default Channel Groups Explained

GA4 includes 18 default channel groups out of the box. Here's a breakdown of each one and how traffic gets classified.

1. Direct

What it means: Traffic where GA4 has no referral information.

Classification rules:

• User types your URL directly
• Clicks a link from a non-web source (desktop app, document)
• Bookmarked link
• Source is (direct) and medium is (none) or (not set)

Common issue: Direct traffic can be inflated by:

• HTTPS → HTTP referral loss
• Links in apps or documents
• Redirects that strip referrers
• Email clients that don't pass referral data
• Consent Mode: When users deny cookies, return visits often default to Direct because GA4 cannot persist the client ID to link them to their original source

---

2. Organic Search

What it means: Unpaid clicks from search engines.

Classification rules:

• Medium = organic
• Source matches known search engines (Google, Bing, Yahoo, DuckDuckGo, etc.)

Example UTM:

utm_source=google
utm_medium=organic

Common issue: If you manually tag organic search links (don't), you'll override GA4's automatic classification.

---

3. Paid Search

What it means: Paid clicks from search engine ads.

Classification rules:

• Medium matches: cpc, ppc, paidsearch, paid-search, or matches regex ^(.*cp.*|ppc|paid.*)$
• Source matches known search engines (Google, Bing, Yahoo, etc.)

Example UTMs:

utm_source=google
utm_medium=cpc
utm_campaign=brand-keywords-q1

Common issue: Using non-standard medium values like:

• ✗ paid search (two words with space)
• ✗ paid-search (may not match depending on implementation)
• ✗ ppc_ads

Best practice: Stick with cpc, ppc, or paidsearch (no spaces, no hyphens).

---

4. Organic Social

What it means: Unpaid clicks from social media platforms.

Classification rules:

• Medium = social, social-network, social-media, sm, social network, or social media
• Source matches known social platforms (Facebook, Twitter, LinkedIn, Instagram, etc.)

Example UTMs:

utm_source=linkedin
utm_medium=social
utm_campaign=thought-leadership-2026

Common issue: Forgetting to tag organic social links. Without UTMs, they often appear as Referral instead (e.g., linkedin.com / referral).

---

5. Paid Social

What it means: Paid clicks from social media ads.

Classification rules:

• Source matches known social platforms (Facebook, Instagram, LinkedIn, Twitter, TikTok, Pinterest, Reddit)
• Medium matches: paid_social, paidsocial, paid-social, paid social, OR contains cpc, ppc, or paid

Example UTMs:

utm_source=facebook
utm_medium=paid_social
utm_campaign=product-launch-jan
utm_content=video-ad-a

Critical note: In earlier versions of GA4, using utm_medium=cpc with social sources would misclassify traffic as Paid Search. Google has since updated the logic so that social sources with cpc now correctly map to Paid Social. However, for clarity and best practice, use paid_social or paidsocial for all social advertising.

---

6. Email

What it means: Clicks from email campaigns.

Classification rules:

• Medium strictly matches the regex: ^(email|e-mail|e_mail|e mail)$

Example UTMs:

utm_source=weekly-newsletter
utm_medium=email
utm_campaign=spring-sale-2026
utm_content=header-cta

Common issue: Using creative variations like:

• ✗ email-blast
• ✗ email-marketing
• ✗ newsletter

These lead to Unassigned or Referral classification.

Technical Tip: While GA4 attempts to catch variations like e-mail and e_mail, using the single word email is the only 100% "bulletproof" method to ensure classification.

---

7. Affiliates

What it means: Traffic from affiliate partners.

Classification rules:

• Medium = affiliate or affiliates

Example UTMs:

utm_source=partner-name
utm_medium=affiliate
utm_campaign=affiliate-program-2026

Common issue: Rare to see implementation issues here since affiliate tracking is usually standardized.

---

8. Referral

What it means: Traffic from links on other websites.

Classification rules:

• Medium = referral, app, or link
• OR traffic arrives with a referrer but no UTM parameters

What gets classified as Referral:

• Blog posts linking to your site
• News articles
• Partner sites
• Forum posts
• Any external link without UTM parameters

Common issue: Organic social posts without UTMs appear as Referral (e.g., t.co / referral from Twitter, or linkedin.com / referral from LinkedIn).

---

9. Display

What it means: Display and banner advertising.

Classification rules:

• Medium matches: display, banner, expandable, interstitial, cpm

Example UTMs:

utm_source=ad-network-name
utm_medium=display
utm_campaign=retargeting-q1-2026

Common issue: Using non-standard values like:

• ✗ display-ad
• ✗ banner-ad
• ✗ display_banner

---

10. Paid Shopping

What it means: Paid product listing ads (Google Shopping, etc.).

Classification rules:

• Campaign name contains shop or shopping
• Medium matches ^(.*cp.*|ppc|paid.*)$
• Source matches shopping platforms

Example (auto-tagged): Google Shopping ads automatically use gclid tracking.

Common issue: Manual tagging Shopping campaigns incorrectly. Let auto-tagging handle this.

---

11. Organic Shopping

What it means: Unpaid product listings (Google Shopping free listings, etc.).

Classification rules:

• Source matches shopping platforms
• Medium = organic with shopping campaign indicators
• Campaign name may contain shopping-related keywords

Common issue: Rare. Most shopping traffic is paid or comes through organic search.

---

12. Organic Video

What it means: Unpaid traffic from video platforms.

Classification rules:

• Medium = video or organic_video
• Source matches video platforms (YouTube, Vimeo, etc.)

Example UTMs:

utm_source=youtube
utm_medium=video
utm_campaign=tutorial-series-2026

Common issue: YouTube links without UTMs usually appear as Referral, not Organic Video.

---

13. Paid Video

What it means: Paid video advertising.

Classification rules:

• Medium = paid_video, video_paid, or variations
• Source matches video ad platforms (YouTube, Vimeo, etc.)

Example UTMs:

utm_source=youtube
utm_medium=paid_video
utm_campaign=video-ads-q1-2026

Common issue: Using cpc as medium for YouTube ads. This can misclassify as Paid Search unless the source is recognized as a video platform.

---

14. Audio

What it means: Traffic from audio platforms and podcast ads.

Classification rules:

• Medium = audio
• Source matches audio platforms (Spotify, podcast apps, etc.)

Example UTMs:

utm_source=spotify
utm_medium=audio
utm_campaign=podcast-sponsorship-q1

Common issue: Forgetting to tag podcast links, causing them to appear as Referral.

---

15. SMS

What it means: Traffic from SMS/text message campaigns.

Classification rules:

• Medium strictly matches the regex: ^sms$

Example UTMs:

utm_source=sms-campaign
utm_medium=sms
utm_campaign=flash-sale-alert

Common issue: Using variations like text or sms-message won't work. Must be exactly sms.

---

16. Mobile Push Notifications

What it means: Traffic from mobile push notifications.

Classification rules:

• Medium ends with push OR
• Medium contains mobile or notification

Example UTMs:

utm_source=mobile-app
utm_medium=push
utm_campaign=abandoned-cart-reminder

Common issue: Not tagging deep links from push notifications, making attribution impossible.

---

17. Cross-network

What it means: Traffic from campaigns that span multiple networks (e.g., Performance Max in Google Ads).

Classification rules:

• Campaign name contains cross-network
• This is automatically applied by Google Ads for Performance Max and similar multi-network campaigns

Why it matters: Modern Google Ads campaigns often run across Search, Display, YouTube, Discover, Gmail, and Maps simultaneously. This channel helps you identify and measure cross-platform campaign performance.

Common issue: Rarely a problem since Google Ads handles this automatically. Manual campaigns won't trigger this unless you specifically include "cross-network" in the campaign name.

---

18. Paid Other

What it means: Catch-all for paid traffic that doesn't fit other paid channels.

Classification rules:

• Medium matches paid-related patterns (^(.*cp.*|ppc|paid.*)$)
• Does NOT match specific paid channels (Paid Search, Paid Social, Paid Shopping, Paid Video)

What gets classified here:

• Native advertising
• Sponsored content
• Paid partnerships that don't fit traditional categories

Example UTMs:

utm_source=taboola
utm_medium=paid
utm_campaign=native-content-2026

Common issue: This can become a dumping ground for misconfigured campaigns. If you see significant traffic here, audit your UTM tagging.

---

How GA4 Evaluates Channel Classification

When a session starts, GA4 follows this process:

1. Extract tracking parameters
   If present, GA4 uses utm_source and utm_medium as primary signals.

2. Apply channel group rules
   GA4 compares the source/medium combination against its rule set.

3. Evaluate in priority order
   Some channels take precedence (e.g., Paid Shopping is evaluated before Paid Search).

4. Assign to first match
   Once a rule matches, classification stops. Traffic goes to that channel.

5. Default to Unassigned
   If nothing matches, the session is marked Unassigned.

---

Common Channel Classification Mistakes

Mistake 1: Using Medium = CPC for Social Ads (Historical Issue)

The problem:

utm_source=facebook
utm_medium=cpc
utm_campaign=product-launch

What GA4 used to do: Classify as Paid Search (not Paid Social).

Why: The medium cpc triggered the Paid Search rule, regardless of source.

Current status: Google has updated GA4's logic so that if the source is a known social platform, utm_medium=cpc now correctly maps to Paid Social.

Best practice: Despite the fix, for clarity and consistency, always use utm_medium=paid_social or paidsocial for social advertising.

---

Mistake 2: Not Tagging Organic Social Posts

The problem: Sharing blog posts on LinkedIn without UTM parameters.

What GA4 does: Classifies as Referral (source = linkedin.com, medium = referral).

Why: Without UTM parameters, GA4 sees it as a standard referral link.

The fix:

utm_source=linkedin
utm_medium=social
utm_campaign=blog-promotion-2026

---

Mistake 3: Creative Medium Names

The problem:

utm_source=newsletter
utm_medium=email-blast
utm_campaign=spring-sale

What GA4 does: Classifies as Unassigned or Referral.

Why: email-blast doesn't match GA4's expected medium values. GA4 expects exactly email, e-mail, e_mail, or e mail.

The fix:

utm_source=newsletter
utm_medium=email
utm_campaign=spring-sale

Use utm_content or utm_term for additional detail like "blast" or "promotional".

---

Mistake 4: Inconsistent Casing

The problem:

• Link 1: utm_medium=Email
• Link 2: utm_medium=email
• Link 3: utm_medium=EMAIL

What GA4 does: Treats these as three separate mediums. Only email (lowercase) maps to the Email channel. Email and EMAIL will be Unassigned.

Why: GA4 is case-sensitive for all UTM parameters.

The fix: Always use lowercase. Document this in your UTM best practices.

---

Mistake 5: The "Unassigned" Session Start

The problem: Traffic shows as Unassigned even with proper UTMs.

The reason: This often happens when the session_start event is missing the page_location parameter. Without the URL (and its UTMs), GA4 has no idea where the session came from.

What causes this:

• Server-side events without proper parameters
• Measurement Protocol implementations
• Single-page applications (SPAs) with routing issues
• Cookie consent rejections that prevent client ID persistence

---

How to Check Channel Classification in GA4

Method 1: Traffic Acquisition Report

Navigate to: Reports → Acquisition → Traffic acquisition

This shows all traffic broken down by Default Channel Group.

What to look for:

• High Unassigned traffic = UTM quality issues
• Unexpected channel volumes = potential misclassification
• Referral traffic from platforms you tagged = missing or wrong UTMs

---

Method 2: Source/Medium Exploration

Create an exploration: Explore → Free form

Setup:

• Dimension: Session source/medium
• Dimension: Default channel grouping
• Metric: Sessions
• Metric: Conversions

What this reveals: Exactly how each source/medium combination is classified.

Example findings:

• facebook / cpc → Paid Social (correct in updated GA4)
• newsletter / email-blast → Unassigned (should be Email)
• linkedin.com / referral → Referral (should be Organic Social with proper UTMs)

---

Method 3: Real-Time Report

For immediate validation: Reports → Realtime

After publishing a link:

1. Click it from the channel (email, social, etc.)
2. Check Realtime report
3. Verify it appears in the expected channel group

This is the fastest way to catch classification issues before they affect your historical data.

---

Default vs. Custom Channel Groups

Default Channel Groups

• Built-in: Available to everyone automatically
• Consistent: Same rules across all GA4 properties
• Non-editable: You can't modify the rules
• Recommended: Use these as your primary classification

Custom Channel Groups

• Flexible: You define the rules
• Property-specific: Only affect your property
• Useful for: Edge cases or industry-specific channels
• Risk: Can mask poor UTM quality

When to use custom channel groups:

• You have legitimate traffic that doesn't fit default groups
• Industry-specific channels (e.g., "Marketplace" for e-commerce)
• Internal traffic segmentation
• Tracking AI/LLM traffic sources (ChatGPT, Perplexity, etc.)

When NOT to use custom channel groups:

• To "fix" Unassigned traffic (fix the UTMs instead)
• To compensate for inconsistent naming (standardize instead)
• As a substitute for proper UTM hygiene

---

How to Audit Your Channel Classification

Step 1: Export Traffic Acquisition Data

Go to: Reports → Acquisition → Traffic acquisition

1. Set date range to last 90 days
2. Add secondary dimension: Session source/medium
3. Export to Google Sheets

---

Step 2: Look for Red Flags

High Unassigned volume: Indicates UTM quality issues or missing parameters.

Social platforms in Referral: Should be Organic Social or Paid Social.

• Example: linkedin.com / referral

Paid channels in wrong groups:

• facebook / cpc should be Paid Social (now correctly classified in updated GA4)
• google / display-ad should be Display, not Unassigned

Email sources outside Email channel:

• newsletter / link is non-standard and will likely be Unassigned or Referral

---

Step 3: Create a Fix List

For each misclassified source/medium:

1. Document the current classification
2. Identify the root cause (wrong medium, missing UTMs, casing issue, etc.)
3. Note where the links are published (email tool, social scheduler, etc.)
4. Plan the fix (update UTM template, retag future posts, etc.)

---

Step 4: Prevent Future Issues

• Update UTM templates in email tools, social schedulers, etc.
• Document your standard values in a shared taxonomy
• Validate URLs before publishing with tools like UTM Guard
• Train your team on proper UTM tagging and the importance of consistency

---

Channel Group Rules Reference

Here's a quick reference for the most commonly used channels:

Channel	Required Medium	Example Source	Notes
Organic Search	organic	google, bing	Auto-detected for known search engines
Paid Search	cpc, ppc, paidsearch	google, bing	Must be from known search engines
Organic Social	social	facebook, linkedin, twitter	Requires manual UTM tagging
Paid Social	paid_social, paidsocial	facebook, linkedin, instagram	cpc now works for social sources
Email	email, e-mail	newsletter, campaign-name	Stick with email for best results
Display	display, banner, cpm	doubleclick, network-name	Avoid variations like display-ad
Affiliates	affiliate	partner-name	Usually standardized
Referral	referral, link	Any external domain	Default for untagged links
Video	video (organic), paid_video (paid)	youtube, vimeo	Requires manual tagging
Audio	audio	spotify, podcast-app	New channel for podcast tracking
SMS	sms	sms-campaign	Must be exactly sms
Cross-network	auto-tagged	Google Ads	For Performance Max campaigns

---

FAQ

Can I change the default channel group rules?

No, GA4's default channel groups are fixed. However, you can create custom channel groups with your own rules. You can also set a custom channel group as your "Primary" channel group, which makes it the default view in reports.

Why is my social traffic showing as Referral?

You're likely not using UTM parameters on social posts. Without UTMs, GA4 sees social platform links as standard referrals (e.g., linkedin.com / referral).

What's the difference between Default Channel Grouping and Custom Channel Grouping?

Default channel groups are GA4's built-in classification system with fixed rules. Custom channel groups are rules you create for property-specific needs. You can have up to 2 custom channel groups in the free version of GA4, or up to 5 in GA4 360.

How often does GA4 update channel classifications?

Channel classification happens in real-time as data is collected. Historical data doesn't change if you fix UTMs going forward. However, custom channel groups apply retroactively, which means you can reclassify historical data by creating new channel rules.

Should I rely on custom channel groups or fix my UTMs?

Always fix your UTMs first. Custom channel groups are useful for edge cases and specific business needs, but shouldn't be a crutch for poor data quality. If your Unassigned traffic is high, the problem is your UTM implementation, not your channel groups.

Can I see how individual URLs are classified?

Yes. Go to Explore → Free form and add "Page path and query string" plus "Default channel grouping" to see URL-level classification. This is helpful for debugging specific links.

What happened to the CPC + social issue?

Earlier versions of GA4 would misclassify social traffic with utm_medium=cpc as Paid Search. Google has since updated the channel grouping logic so that social sources (Facebook, Instagram, LinkedIn, etc.) with cpc medium now correctly map to Paid Social. However, best practice is still to use paid_social or paidsocial for clarity.

---

Final Thoughts

GA4 channel groups aren't magic. They're rule-based classification that depends entirely on the quality of your UTM parameters.

When your traffic gets misclassified, GA4 isn't broken—it's doing exactly what it's designed to do: following strict rules and refusing to guess.

The solution is straightforward:

1. Understand the rules (now you do)
2. Use standard medium values (stick to GA4's expected patterns)
3. Tag consistently (document your taxonomy)
4. Validate before launch (catch mistakes early)

Get those fundamentals right, and your channel classification becomes reliable, predictable, and actionable.

---

Next Steps

• Validate your campaign URLs to ensure proper channel classification
• Review UTM best practices for consistent tagging
• Fix Unassigned traffic caused by channel classification issues

Stop wondering why your traffic is misclassified. Use UTM Guard to validate channel mapping before you publish.