GA4 Traffic Acquisition Report Explained

GA4 Traffic Acquisition Report Explained

The GA4 traffic acquisition report answers the question every client asks: "where did these people actually come from?" It is also the report most likely to start an argument, because the channel names Google uses are not the words agencies and clients use in meetings.

This guide covers what the report measures, how the session default channel group decides which bucket a visit lands in, why user acquisition vs traffic acquisition trips people up, and how to explain it without running a training session.

We build ReportsMate around Google Analytics data every day. Across our platform, Google Analytics is the most connected platform of all, making up close to 40% of every client-to-platform connection our agencies have set up.

Last updated: August 2026

Key takeaways

• The GA4 traffic acquisition report groups sessions by where each session came from, using the session default channel group dimension.
• The user acquisition report groups people by where they first arrived, using first user default channel group. Same data, different question.
• Session default channel group is rules-based: GA4 reads each session's source and medium and matches them against fixed definitions like Organic Search and Paid Social.
• "Unassigned" is not a channel. It means the source and medium matched none of GA4's rules, almost always a tagging fault you can fix.
• Performance Max and Demand Gen traffic lands in Cross-network, not Paid Search, which is why Google Ads and GA4 channel totals look mismatched.

What this guide covers

1. What is the GA4 traffic acquisition report?
2. User acquisition vs traffic acquisition
3. What is the session default channel group?
4. Which metrics matter to clients?
5. Why does GA4 show Unassigned traffic?
6. GA4 channel reporting for clients
7. FAQs

What is the GA4 traffic acquisition report?

The GA4 traffic acquisition report shows how many sessions a website received in a date range, broken down by the source of each individual session. Find it in Google Analytics under Reports, then Life cycle, then Acquisition, then Traffic acquisition.

The important word is session. Every time somebody arrives and starts a visit, GA4 asks what brought that specific visit, then files it under a channel. One person who finds you on Google in March, clicks a Meta ad in April and types your URL in May produces three sessions in three different channels. That is why this is the right report for judging campaigns: it reflects the marketing that caused each visit, not the marketing that started the relationship.

By default the report groups by session default channel group, but the dropdown at the top of the first column switches to session source / medium, session campaign or session primary channel group. Source / medium is the raw truth. Channel group is the tidy version built on top.

One caution worth passing on: GA4 data can shift for a day or two after a date range closes, so pull the monthly report on the 3rd, not the 1st.

User acquisition vs traffic acquisition - what's the difference?

Traffic acquisition counts sessions by the source of each session. User acquisition counts users by the source that first brought them to the site. Both reports are correct. They answer different questions, and the dimension is the giveaway.

Here is the scenario that settles it. A first-time visitor arrives from an organic listing, then returns three days later through a Facebook ad. Traffic acquisition records two sessions, one Organic Search and one Paid Social. User acquisition records one user, filed permanently under Organic Search.

If your client asks whether the paid social worked this month, use traffic acquisition. If they ask which channel brings new people to the brand, use user acquisition. Then say which one you used, in writing. Most reporting arguments start with two people quoting two different reports.

For the wider metric vocabulary around these reports, our breakdown of GA4 metrics explained for clients pairs well with this one.

What is the session default channel group in GA4?

Session default channel group is a label GA4 applies automatically to every session by reading its source, medium and campaign, then matching them against Google's fixed channel definitions. You do not set it. GA4 derives it, session by session.

There are around 19 possible values. These are the ones agencies see in client accounts:

Two terms explain most of the confusion. Source is where the session came from (google, facebook.com). Medium is how it came (organic, cpc, referral, email). GA4's rules read both, and the medium usually decides the bucket. Google Analytics Help sets out every rule in its "Default channel group" article.

The other term is auto-tagging. When a Google Ads account is linked to a GA4 property with auto-tagging on, Google appends a gclid to each ad click and GA4 classifies it on its own. Meta, LinkedIn and TikTok have no equivalent, so those clicks only land in the right channel if you tag them manually with UTM parameters.

Which traffic acquisition metrics actually matter to clients?

Sessions tells you volume, engagement rate tells you quality, and key events tells you whether the traffic did anything worth paying for. The rest is supporting detail.

Since 2024 the conversion column in GA4 is labelled key events, so the metric your client remembers as "conversions" now has a different name. Explain the rename once and it stops being a monthly question. The columns worth putting in front of a client:

• Sessions - raw visit volume per channel, the headline number.
• Engaged sessions - sessions over 10 seconds, or with a key event, or with two or more page views.
• Engagement rate - the honest quality signal per channel, and the one that exposes traffic that looks good and does nothing.
• Key events - filter to the one or two actions that matter.
• Session key event rate - the closest thing GA4 gives you to a channel-level conversion rate.

Sort by sessions, then read engagement rate across. A channel delivering 30% of sessions at half the site's average engagement rate is where next month's conversation starts.

One thing not to do: quote GA4 key events as if they equal Google Ads conversions. They are counted, attributed and windowed differently, which is why we wrote a full explainer on Google Ads vs GA4 conversions.

Why does GA4 show Unassigned traffic (and how do you fix it)?

Unassigned means GA4 received a session whose source and medium matched no default channel rule, so it had nowhere to file it. It is a data quality flag, not a traffic type, and in most accounts it is fixable in an afternoon.

The usual causes, roughly in order of frequency:

1. A utm_medium GA4 does not recognise. Tagging a link utm_medium=social-post or utm_medium=partner feels sensible but matches no rule. Use social, cpc, email, affiliate, referral or display instead.
2. Campaign links with no tagging at all. An email send or partner placement pushed out as a bare URL arrives as Direct or Referral.
3. A source with no medium, or the reverse. GA4's rules mostly need both. Half a tag is worse than no tag.
4. Consent or tracking gaps where events arrive without the session_start context that carries the traffic source.

The fix is unglamorous and permanent: standardise your UTM conventions, document them once, and build every campaign link from the same tool. Google Analytics Help lists the accepted medium values and Google Ads Help covers switching on auto-tagging. Between those two, most Unassigned traffic disappears.

Set a threshold with your team: if Unassigned passes a few percent of sessions it goes on the fix list before the next report goes out. A channel breakdown with 18% Unassigned teaches a client not to trust the report.

How should agencies run GA4 channel reporting for clients?

Good GA4 channel reporting for clients means fewer channels, consistent definitions, and the same comparison period every month. Clients do not need all 19 channel groups. They need the four or five that describe their marketing, plus a clear note on what changed.

What works across most accounts:

• Roll everything outside the client's active channels into "Other" rather than listing a long tail of two-session rows.
• Use the same date comparison every time (previous period and previous year) and never switch mid-engagement.
• Put one sentence of interpretation under the table. "Organic search sessions fell 12% while engagement rate held steady, which points to ranking or seasonality rather than a site problem" is worth more than the table above it.
• Reconcile paid channels against the ad platform before you send. Google Ads clicks will never equal GA4 Paid Search sessions.

That last point matters. Across ReportsMate accounts, about 70% of connected clients have a GA4 property attached and half of those also have Google Ads or Meta Ads connected. The channel breakdown is nearly always read next to a paid platform report, and if the two disagree with no explanation the client assumes one is broken.

Having built this product around agency reporting workflows for years, the pattern we keep seeing is that channel reports fail on inconsistency, not accuracy. Report the same six channels the same way for twelve months and you build trust. Reformat every quarter and you look like you are hiding something, even when the numbers are good. Our GA4 report template for agency clients lays out a structure section by section.

Then there is delivery. A dashboard link, a Looker Studio share, a portal invite: each asks the client to remember a password before reading something they did not request. Most never do. This is why we built ReportsMate email-first. The channel breakdown, the period-on-period change and an AI-written insight arrive as a branded email on your schedule, fully white-labelled (your logo, colours, sender name and sending domain) so it reads as your agency's work. AgencyAnalytics, DashThis, Whatagraph, Swydo, Supermetrics and Looker Studio are all capable tools and several offer email delivery too. The difference is that with us the email is the product, not an export of a dashboard.

Your reporting cadence is the rhythm you commit to. Across the schedules switched on in ReportsMate, weekly and monthly are evenly split, with daily a distant third, which fits what most agencies find: GA4 channel data is too noisy day to day for a daily email.

Connecting a property takes about a minute through the Google Analytics integration, alongside Google Ads, Meta Ads, Search Console and Google Business Profile. To see the full flow first, see how it works.

GA4 traffic acquisition report FAQs

Q: What is the difference between the traffic acquisition and user acquisition reports in GA4?

A: Traffic acquisition counts sessions and attributes each one to the source that drove that visit, using session default channel group. User acquisition counts users and attributes each one to the source that first brought them to the site, using first user default channel group. Use traffic acquisition when a client asks whether a campaign worked this month, and user acquisition when they ask which channel introduces new people to the brand. The totals will never match, because one counts visits and the other counts people. Name the report you used so nobody compares two different numbers across two months.

Q: What is the session default channel group in GA4?

A: Session default channel group is the label GA4 assigns automatically to every session by reading its source, medium and campaign name and matching them against Google's fixed channel definitions. There are around 19 possible values, including Direct, Organic Search, Paid Search, Paid Social, Organic Social, Referral, Email and Cross-network. You cannot edit the default rules, although GA4 allows custom channel groups at property level. Because the classification is driven by your UTM parameters, the accuracy of the report depends on how consistently your team tags campaign links.

Q: Why is my Google Ads traffic not showing under Paid Search in GA4?

A: The most common reason is that the campaign is Performance Max or Demand Gen, and GA4 files that traffic under Cross-network rather than Paid Search by design. The second is that auto-tagging is switched off in the Google Ads account, or the two properties are not linked, so the gclid never reaches Analytics. Check the account link and auto-tagging first, then look in Cross-network before assuming data loss. Google Ads Help documents both the auto-tagging setting and the GA4 linking process.

Q: How do I fix Unassigned traffic in GA4?

A: Unassigned appears when a session's source and medium match none of GA4's channel rules, which almost always means a tagging fault rather than a tracking failure. Audit your campaign links and replace invented medium values like "social-post" or "partner" with ones GA4 recognises: cpc, social, email, affiliate, referral or display. Every tagged link needs both a source and a medium, never one alone. Standardise on a single link builder such as our free UTM builder, then re-check the channel report after a fortnight of clean data.

Q: How often should GA4 channel reports go to clients?

A: Weekly or monthly for almost every account. GA4 channel data is noisy day to day, so a daily email mostly reports weather rather than trend and trains clients to react to single bad days. Monthly suits SEO, content and brand work. Weekly suits paid media, where a wasted week of spend is worth catching early. Whichever you choose, send it on the same day every period with the same comparison window, because consistency is what makes a client trust a number they cannot verify themselves.

Final tips for reporting GA4 acquisition data

The GA4 traffic acquisition report is not hard once you accept that it answers a session-level question with a rules-based label. Get the tagging right and it is close to self-explanatory. Get it wrong and no commentary will rescue it.

Three things worth doing this week:

1. Check the Unassigned row in every client property. Anything above a few percent is a tagging job, not a data mystery.
2. Write down the four to six channels each client actually markets in, and lock the report to those.
3. Decide whether you are a sessions agency or a users agency, and stop switching mid-engagement.

Then take the manual work out of it. Pulling the GA4 traffic acquisition report, formatting it and rewriting the same commentary every month quietly eats an afternoon per client, and it is the first job worth automating once you are past a handful of accounts. Compare plans on the pricing page to find the tier that fits your client count.

Stop losing your Sundays to client reports. Start your free 14-day trial - no credit card, no setup, cancel anytime. Your clients get branded GA4 channel reports in their inbox automatically.