You open your GA4 acquisition report and the same Facebook campaign is scattered across five rows: facebook, fb, m.facebook.com, l.facebook.com, Meta-facebook. Each variant slices your sessions, conversions, and CPA into separate, uncomparable lines. On June 11, 2026, Google shipped a native answer to that problem: GA4 Source Group, a dimension that automatically consolidates those variants into a single clean value. This guide explains what it fixes, how to access it, when to use it instead of Source / Medium, and where its limits really are.
The problem: one Facebook split into five rows
Fragmented social sources aren’t a bug, they’re a side effect of how traffic arrives. A single Facebook post can produce different referrers depending on whether the user clicks from the mobile app, the website, a shortened link, or a Meta integration. GA4 faithfully records each raw string, and you end up with as many rows as there are variants.
Every analyst knows the consequence: to read Facebook’s true performance, you had to sum five rows by hand, redo the math on every export, and accept that any new referrer would break the total. The same mechanic hits Instagram, TikTok, and YouTube. Fragmented social attribution quietly distorts your channel ranking, and therefore your budget decisions.
What GA4 Source Group is and what it fixes
Source Group is a traffic-source dimension that gives a single, consistent name to traffic from a given platform, even when the raw referral string varies. In practice, the five variants facebook, fb, m.facebook.com and the rest now read under one value: Facebook.
Three properties make it genuinely useful:
It is auto-populated. No tag, UTM, or GTM container change is required. As soon as the dimension shows up in your account, it works.
It is retroactive. Source Group also applies to your history: your past Facebook traffic, once split five ways, consolidates backward into a single value. Year-over-year analysis therefore has no date break at June 11; the dimension reads consistently before and after.
It covers the major platforms. As of today, Source Group recognizes Facebook, Instagram, TikTok, Pinterest, Amazon, YouTube, Google Search, Google Maps, plus ChatGPT and Perplexity. That last point matters if you already track assistant traffic: Source Group gives a clean reporting view of those sources. To go deeper on that channel, see our guide on how to track ChatGPT, Gemini and Claude traffic in GA4.
How to access the Source Group dimension in GA4
Access requires no setup and runs through the dimension picker:
In an exploration (Explore), create or open a report, then in the Variables panel click the + next to Dimensions and search for “Source Group.” Drag it into rows to replace Source / Medium with a grouped view.
In standard reports, open the Traffic acquisition report, then change the primary dimension via the dropdown at the top of the table and select Source Group.
One important note: the rollout is incremental. If you don’t see the dimension in the picker yet, it isn’t a configuration error, it just means the rollout hasn’t reached your property. Check directly in your own property before stating a procedure to your team.
Source Group vs Source / Medium vs Channel Group: when to use what
These three dimensions answer different questions, and Source Group doesn’t replace the other two.
Source / Medium stays the most granular data point: m.facebook.com / referral tells you exactly where the session came from. It’s essential for debugging tagging, spotting a spam referrer, or auditing your UTMs. Keep it when you need the raw detail.
Source Group sits one level above: it answers “how much is Facebook bringing in, all variants combined?” with no manual math. It’s the dimension to set as default whenever you compare performance across platforms.
The Default Channel Group (Organic Social, Paid Search, Direct, and so on) stays the most aggregated level, by channel type. Source Group slots between the raw source and the channel: more readable than Source / Medium, more precise than the Channel Group.
| You want to know | Dimension to use |
|---|---|
| Exactly where this session came from (debug, UTM audit) | Source / Medium |
| How much each platform brings in, variants grouped | Source Group |
| Which channel category performs (social, search, direct) | Default Channel Group |
Limits and best practices
Source Group cleans up reporting, not tagging. That’s the nuance to keep in mind. The dimension groups what GA4 receives, but it doesn’t fix a source that was mistagged at the origin: if your UTMs are inconsistent, you gain readability without gaining accuracy. Clean UTM hygiene remains the foundation, and that’s often where the real data errors hide. If your reports are already polluted upstream, start by auditing your collection with our guide on the 7 data layer mistakes that wreck your GA4 data.
A few guardrails:
The list of grouped platforms will evolve. Check in your own property which sources are actually consolidated before relying on the dimension for a specific channel.
Availability in the BigQuery export and the Data API isn’t guaranteed on the same cadence as the interface. Source Group appears natively in standard reports and explorations, but if you build dashboards outside the interface, test for its presence in your export before building on it. To then turn that grouped data into a dashboard, see how to automate your reporting with Looker Studio and BigQuery.
Uncovered cases (niche sources, very rare variants) will keep falling into their raw value. Source Group sharply reduces fragmentation; it doesn’t remove it entirely.
Checklist: audit your social sources in 5 minutes
- Open the Traffic acquisition report and switch the primary dimension to Source Group. If it isn’t there, the rollout hasn’t reached your property yet.
- Compare the grouped Facebook total against the manual sum of your old rows (
facebook,fb,m.facebook.com, and so on) to validate the consolidation. - Check how your platforms re-rank: once the fragments reassemble, the relative ranking of your channels can shift.
- Switch back to Source / Medium on the remaining variants to spot tagging worth fixing upstream.
- Document the switchover date for your team and set Source Group as the default in your social performance explorations.
In summary
GA4 Source Group answers an old, universal pain: fragmented social attribution. It is auto-populated, retroactive, free of year-over-year date breaks, and it covers the major platforms, ChatGPT and Perplexity included. It replaces neither Source / Medium for debugging nor clean UTM hygiene upstream, but it saves real time when reading your channels. Confirm its availability in your property, validate the consolidation on Facebook, then adopt it as the default dimension for comparing your social platforms.