GA4 (not set) in Source/Medium: Causes and Fixes
GA4 (not set) in Source/Medium: Causes and Fixes

When GA4 shows (not set) in source/medium, it means Analytics did not receive a value for that dimension on those sessions. The cause depends on which report you are looking at. For Google Ads traffic it is usually account linking, auto-tagging or sloppy UTMs. For Session source / medium it is usually a Google tag that fires too late or not at all.
I’m Jesse, a senior paid media specialist at Senior Ad Managers. We see this in Australian Google Ads and Meta Ads accounts every week. Below is how I work out the cause, in the order I check it, and what to change.
TL;DR
- (not set) is a placeholder. Google Analytics uses it when it has not received information for a dimension, so the fix depends on the dimension.
- For Google Ads rows, check three things first: the Ads account is linked to the GA4 property, auto-tagging is on, and any manual UTMs are complete and correct.
- For Session source / medium, look for a missing session_start event and set the Google tag to fire on Initialization - All pages.
- Unassigned is a different thing. It is a channel grouping result, and Session source / medium (not set) ends up there in the default channel group.
- Fix the cause, then recheck after new traffic comes in. Old rows will not change.
Table of Contents
- What (not set) actually means in GA4
- (not set), unassigned and (data not available)
- Step one: find which dimension is showing (not set)
- Fixing (not set) on Google Ads traffic
- Fixing (not set) in Session source / medium
- Fixing (not set) in landing page
- Perspective: why we treat (not set) as a spend question
- How to confirm the fix worked
- When (not set) points to a bigger tracking problem
- Get help with your Google Ads account
- FAQ
- Next step
- Sources
What (not set) actually means in GA4
Google’s own help page describes (not set) as a placeholder that Analytics shows when it has not received information for a dimension. It is not an error message and it is not a channel. It is a blank that GA4 labels so the row still appears in your report.
That matters because the same two words show up in very different places. You can see (not set) in landing page, in Google Ads campaign fields, in city and in session source / medium. Each one has its own cause. If you apply a landing page fix to a source/medium problem, nothing changes and you lose an afternoon.
The business cost is easy to underestimate. If 15% of your paid sessions land in (not set), then those visits cannot be tied to a campaign, and the conversions they produce cannot be credited to the ads that paid for them. You end up judging campaigns on partial data, and the gap is where wasted spend hides.

(not set), unassigned and (data not available)
These three labels get mixed up constantly, including in the reports agencies send to business owners.
| Label | What it means | Can you reduce it? |
|---|---|---|
| (not set) | Analytics did not receive information for that dimension | Generally yes |
| Unassigned | Analytics could not match the source or medium to a channel rule | Yes, by fixing tags, UTMs or channel rules |
| (data not available) | Information was not received or processed, often because of processing delays | Users typically cannot reduce it |
The distinctions come straight from Google. Unassigned is a channel-group result: Analytics could not categorise the traffic under the channel rules, which includes cases where a custom source or medium has no matching predefined rule. Google also notes that Session source / medium of (not set) is shown as Unassigned in the default channel group. So if you see a big Unassigned bucket in your channel report, open source/medium to see whether (not set) is behind it.
Google separates (not set) from (data not available) too. It says action is generally possible to reduce (not set), whereas users typically cannot reduce (data not available). The latter often reflects processing delays, so check yesterday’s and today’s numbers before you panic.
Step one: find which dimension is showing (not set)
Before touching any settings, answer this: which exact dimension is blank?
- Open Reports, then Acquisition, then Traffic acquisition.
- Change the primary dimension to Session source / medium.
- Add a secondary dimension such as Landing page or Session Google Ads campaign.
- Set the date range to exclude today, and ideally yesterday, so processing delays do not skew what you see.
- Note whether (not set) sits on rows with Google Ads campaigns, or on ordinary sessions with no campaign data.
The pattern tells you which route to take. If the problem is in Google Ads dimensions, go to the linking and tagging checks. If it is in Session source / medium, go to the tag timing checks. If it is in landing page, jump to the landing page section further down.
The Google Ads dimension and the session dimension are separate fields. Fixing one does not fix the other, and plenty of properties have both problems at once.
Fixing (not set) on Google Ads traffic
Google lists the common causes for Google Ads dimensions: an unlinked Google Ads account, disabled auto-tagging, traffic coming from another Ads account that is not linked, and incomplete or incorrect manual UTM parameters. Work through them in this order.

Link every Google Ads account to the property
In GA4, go to Admin, then Product links, then Google Ads links, and confirm each account that sends you traffic is listed. Google recommends linking the account to the Analytics property for exactly this reason.
In Australian businesses I often find two accounts: the one the owner created years ago and the one an agency set up later. Only one is linked. Clicks from the other arrive in GA4 with a click ID that GA4 cannot resolve to a campaign.
This is also where an eCommerce store running paid search and on-site search needs the whole picture joined up. If you run a Shopify store, search analytics for Shopify stores shows what shoppers look for once they arrive, which only means something if you know which campaign sent them. Linking the accounts is what makes that attribution possible.
Turn auto-tagging on
Auto-tagging adds a GCLID to your ad URLs so Analytics can pull in campaign, ad group and keyword details. In Google Ads, open Admin, then Account settings, then Auto-tagging, and tick the box to tag ad URLs. Google lists disabled auto-tagging among the causes of (not set) and says to enable it.
If you also use a tracking template or final URL suffix, check that it does not strip or overwrite the GCLID. A template that rebuilds the URL badly is a quiet way to break a working setup.
Investigate unlinked accounts holding GCLIDs
Google’s guidance includes investigating unlinked accounts that retain GCLIDs. If you see (not set) on Ads campaign rows and your own accounts are linked, ask who else could be sending traffic to your site. A previous agency, a franchise partner or a separate business unit may run an account you do not manage. Ask them to link it or confirm what they run.
Correct manual UTM parameters
If you tag URLs by hand, Google points to incomplete or incorrect UTM parameters as a cause, and recommends using Analytics URL builders. The common mistakes I see:
- utm_source filled in but utm_medium left off, or the other way around
- Different spellings of the same medium, such as cpc, CPC and paid-search
- A custom medium that matches no channel rule, which pushes traffic to Unassigned
- UTMs added to Google Ads URLs when auto-tagging already handles them
Pick one naming convention, write it down, and have everyone who builds links use the same URL builder. For Meta Ads, the same discipline applies. Facebook and Instagram links should carry consistent source and medium values so those sessions land in Paid Social rather than Unassigned.
Fixing (not set) in Session source / medium
If (not set) appears on ordinary sessions, the Google documents a different primary cause. For Session source / medium, Google says the key documented cause is a missing session_start event, which can result from an incorrectly triggered Google tag.
The fix Google gives is to change the Google tag trigger to Initialization - All pages. In Google Tag Manager that means:
- Open your Google tag (the GA4 configuration tag).
- Under Triggering, remove the current trigger, such as All Pages.
- Add the Initialization - All Pages trigger.
- Preview the container, load a page and confirm the tag fires first.
- Publish, then watch new data over the following days.
Why timing matters
Google explains that tags firing at unexpected times can affect user or session identity. If the Google tag or config command fires after other page events, reporting can show (not set), incorrect counts and users or sessions that are not measured properly. Google also says incorrect tag configuration can lead to unassigned rows, (not set) values and unexpectedly high direct traffic.
In practice, this happens when a developer adds a custom event that fires on page load before the base tag has loaded, or when a consent banner delays the config tag but not the events. The events arrive without a session context, and GA4 has nothing to attribute them to.
If your site uses a cookie consent tool, check the order in Tag Manager’s preview mode on a fresh browser session. Reading the sequence of tags in order tells you more than any report will.
Fixing (not set) in landing page
This one catches people because it looks similar but has a separate cause. Google says landing page is (not set) when a session has no page_view event. Session source / medium, by contrast, ties to a missing session_start.
So if your landing page report is full of (not set) but source/medium looks fine, the page_view event is failing to fire on the first page of the session. Check that the tag fires on the first page load, that redirects are not stripping the tag, and that single page apps send a page_view on route changes. The same Initialization timing fix often helps here as well.
Perspective: why we treat (not set) as a spend question
Most business owners first meet (not set) in a report and assume it is a cosmetic problem. We don’t see it that way. Every row of (not set) in a paid report is traffic you paid for that nobody can connect to a campaign.
When we take over a Google Ads or Meta Ads account, we check the basics first: account linking, auto-tagging and when the tag fires. A campaign can look fine in the Ads platform while GA4 loses a share of its sessions. If you judge budgets on a report with holes in it, you will move money to the wrong place.
Our rule is simple. Each lead should be counted once and tied to the campaign that earned it. That is why we pair tidy tagging with weekly search term reviews on exact and phrase match keywords, and why we check results against sales in the client’s CRM. Clean source/medium data makes every one of those decisions easier.
If you are spending on ads and cannot say where your customers came from, fix the data first. Then you can decide what to cut and what to scale.
Jesse Lees
How to confirm the fix worked
GA4 does not rewrite history. A fix applies to new data from the day it goes live, so old (not set) rows stay as they are. Use this routine:
- Note the share of (not set) in Session source / medium over the last 28 days, before the change.
- Make one change at a time, such as linking an account, enabling auto-tagging or moving the tag trigger.
- Wait a few days, then compare only post-change dates, leaving out today and yesterday.
- Check in DebugView with a test visit that session_start and page_view appear in the right order.
- Compare GA4 sessions from Google Ads against clicks in the Ads account. They will not match exactly, but the gap should be modest and steady.
A small amount of (not set) may always remain. What you want is a share low enough that it does not change a budget decision.
If your numbers still look off after these checks, our GA4 audit checklist walks through the wider setup, and our guide to GA4 conversion tracking covers which key events to count.
When (not set) points to a bigger tracking problem
Sometimes (not set) is a symptom. If conversions in GA4 disagree with Google Ads, or the platform reports leads that your sales team never saw, the cause may sit upstream in how conversions are recorded. That is a measurement job rather than a report tweak, and our page on how to fix Google Ads conversion tracking explains what we look at. For service businesses that take phone calls as leads, our call tracking guide for Australian businesses covers that gap.
Get help with your Google Ads account
If you have worked through the checks above and the numbers still do not add up, an outside look at the account is the quickest way forward. We manage Google Ads for Australian businesses from $1,725 AUD a month, with no setup fee, no percentage of ad spend and a 3 month minimum. Senior specialists run every account, and we check results against sales in your CRM.
Most owners start with our $99 AUD Google Ads audit. We review linking, auto-tagging, tracking and search terms, and tell you where spend is going. We do not promise results, but you will know what is worth fixing first.
FAQ
Is (not set) in GA4 a bug?
No. Google defines it as a placeholder shown when Analytics has not received information for a dimension. It usually points to a setup issue such as an unlinked Google Ads account, disabled auto-tagging, bad UTMs or a Google tag that fires late. Most of these are fixable.
What is the difference between (not set) and unassigned?
Unassigned is a channel grouping result. It means GA4 could not match the source and medium to a channel rule. (not set) means GA4 did not receive a value at all, and Session source / medium (not set) is shown as Unassigned in the default channel group.
Why does Google Ads traffic show (not set) in source/medium?
Google lists four common causes: the Ads account is not linked to the property, auto-tagging is off, the traffic comes from a different unlinked Ads account, or manual UTMs are incomplete or wrong. Check them in that order, because linking and auto-tagging take minutes.
Will fixing it clean up my old data?
No. The changes apply to data collected after you make them, so compare dates from the change onward. Recent days can also show (data not available) while Analytics processes information, so leave out today and yesterday when you check.
What should I change in Tag Manager?
Set your Google tag to fire on the Initialization - All pages trigger, and make sure it fires before other events. Google says a late tag can cause (not set) values, wrong counts and sessions that are not measured properly.
Next step
If you want a second pair of eyes on your tracking and spend, book the $99 AUD Google Ads audit and we will show you what the account is really doing.
Sources
- What the value (not set) means in your reports, Google Analytics Help
- Tagging best practices to avoid unassigned, (not set) and unexpected direct traffic, Google Analytics Help
- Strengthen your marketing strategy with high quality data, Google Analytics Help
Recommended
Keep reading
How we can help
Next step
Find out where your ad spend is going.
Get a $99 AUD Google Ads audit. We'll show you where money is being wasted and which leads you're missing out on.
Show me my current ad mistakes →