(not set) in GA4

(not set) in GA4 is the placeholder value Google Analytics 4 shows when it received no information for a dimension. Google’s help center defines it as “a placeholder name that Analytics uses when it hasn’t received any information for a dimension.” It can appear in any report, and it usually points to a tagging, linking or consent setup problem you can fix.
What (not set) Means
(not set) is not a traffic source. It is an empty field. Every row in a GA4 report combines a metric with one or more dimensions, such as session source, landing page or campaign. When the event behind that row arrived without a value for the dimension, GA4 fills the gap with “(not set)”.
That makes the cause specific to the dimension. A (not set) landing page and a (not set) campaign have different causes and different fixes. Start by noting which report and which dimension show the value.
What Causes (not set) in GA4, by Dimension
Google’s documentation lists these causes:
| Dimension | Shows (not set) when | Fix |
|---|---|---|
| Session source / medium | The session has no session_start event, often because the Google tag does not fire on initialization |
Set the Google tag trigger to “Initialization – All Pages” |
| Session campaign | UTM parameters are missing or incomplete, or Google Ads is not linked | Tag every link with a full UTM set; link Google Ads |
| Google Ads campaign, keyword | The Ads account is not linked or auto-tagging is off | Link the accounts and enable auto-tagging |
| Landing page | The session has no page_view event |
Make sure the first hit of every session is a page view |
| Content group | The content_group value is empty, or it is paired with session_start or first_visit |
Send a value on every page; use page-level events |
| Custom dimensions | The parameter was registered less than 24 hours ago, or the event never sent it | Wait 24 hours, then check the event payload in DebugView |
Consent mode adds a cross-cutting cause. Google notes that using the consent default command for post-interaction changes, instead of update, can drop the session_start parameter. Sessions then lose their source.
(not set) vs Similar GA4 Values
Four placeholder values get confused with each other:
- (not set): GA4 never received a value. Usually fixable.
- (data not available): GA4 received a click ID or UTM value but has not finished processing it. Google says event-level data “can be updated up to 12 days later,” and it appears more in intraday tables than daily ones.
- (direct) / (none): GA4 received the session but found no referrer and no campaign tags. This is a real source assignment, not a missing value.
- (other): GA4 grouped low-volume rows together because the report exceeded its row limit. This is a cardinality issue, not a tagging issue.
“Unassigned” is a separate case again. It is a default channel grouping label for sessions whose source and medium match no channel rule. A (not set) medium usually lands there.
How to Find and Fix (not set) Traffic
- Isolate the dimension. Open the report showing (not set) and add a secondary dimension such as device category, browser or landing page.
- Check the date it started. A sudden spike usually lines up with a tag change, a consent banner update or a new campaign launch.
- Inspect live events in DebugView. Confirm that
session_startandpage_viewfire first, and that custom parameters carry values. - Audit campaign links. Missing
utm_mediumor a misspelled key such asutm_souresends a session to (not set). Running links through linkutm’s UTM checker catches these before launch. - Verify Google Ads linking. In GA4 Admin, open Product links, then Google Ads links, and confirm auto-tagging is on in Google Ads.
For a session source/medium problem specifically, the 7 causes of (not set) in GA4 source/medium walks through each fix in detail.
Fixes only apply going forward. GA4 does not reprocess historical (not set) rows.
Frequently Asked Questions
What does (not set) mean in Google Analytics?
(not set) means Google Analytics received no value for the dimension in that row. It is a placeholder, not a real source, page or campaign. The cause depends on the dimension: a missing session_start event for source/medium, a missing page_view for landing page, and missing UTM tags for campaign.
How much (not set) traffic is normal in GA4?
Google publishes no benchmark for an acceptable share. Some (not set) is expected from consent choices and edge cases such as sessions that start without a page view. A sudden increase matters more than the absolute level, because it usually marks a tagging or consent change. Compare the share week over week rather than against a fixed number.
Can you fix historical (not set) data in GA4?
No. GA4 does not reprocess past data after you fix a tag or link an account. The exception is (data not available), which Google can update for up to 12 days. Annotate the fix date so later reports are read correctly.
Why is my GA4 campaign showing (not set)?
Most campaign (not set) rows come from links with no UTM parameters or an incomplete set. Google Ads traffic shows (not set) when the Ads account is not linked or auto-tagging is off. Check one sample link from each channel to find the gap.
Is (not set) the same as direct traffic?
No. Direct traffic is a real assignment for sessions with no referrer and no campaign tags. (not set) means the value is missing entirely, often because a tag or event fired out of order.
To stop campaign traffic from landing in (not set), build every link with a complete parameter set using the free UTM builder at linkutm.