Why does your GA4 report keep showing fields you can’t make sense of?
You open your GA4 report, ready to present last month’s marketing results to your boss, and your heart sinks. The source / medium column says (not set) in big letters, or a pile of Unassigned appears in the channel group. At that moment you may start to wonder: was the tracking set up wrongly? Or is GA4 acting up again?
Seeing these “empty values” doesn’t mean your data is broken. They’re actually “optimisation signals” from the system.
In GA4, missing data values fall into four main types: (not set) means tag information is missing; Unassigned means traffic naming doesn’t match the rules; Unknown is mostly related to restricted privacy attributes; and (data not available) is caused by system thresholds.
This article explains the causes of each of these four labels in depth and offers practical fixes, to help you restore the real data in your reports so your analysis doesn’t get stuck.
1. What exactly is (not set)? Common setup mistakes and fixes
Put simply, (not set) is GA4 telling you: “I know an event happened here, but I can’t find the matching label information.”
💡 Imagine receiving a letter with a postmark but no sender’s name. In the system, that letter would be classed as (not set).
Common situations and fixes:
- Ad links missing parameters: if you run Google Ads without turning on auto-tagging, or your manually tagged UTMs leave out key information, GA4 will label the source (not set) because the information is incomplete.
- Session timeout: if a user opens a page and then doesn’t do anything for a long time (for example, they step away), the original source information may be lost when they come back and click, so their later behaviour becomes data with no owner.
✅ CloudAD’s practical advice: check straight away whether GCLID auto-tagging is turned on in Google Ads. If you use manual UTMs, make sure source, medium and campaign name are all complete.
👉 Find out more: Understanding (not set) in GA4: why data disappears and what marketers can do about it
2. Unassigned vs. Unknown: why has traffic become “Unassigned”?
The question marketers most often get confused about is: what’s the difference between Unassigned and (not set)?
- (not set) means “information is missing entirely” (no label at all).
- Unassigned means “information doesn’t match” (there is a label, but it doesn’t match any address).
1. Unassigned
This means GA4 received traffic information (for example, the source is My_Blog_Post), but that name isn’t in GA4’s default channel group rules. The system doesn’t know whether to class it as Organic Social or Referral, so it ends up as Unassigned.
✅ Troubleshooting tip: check whether your source and medium naming follows Google’s guidelines. For example, if you name Facebook traffic fb / ads instead of facebook / cpc, GA4 may not recognise it. You can use custom channel rules to reclassify this stray traffic.
2. Unknown
This mostly appears in reports on user characteristics such as gender or age. When GA4 can’t collect enough personal information from Google Signals or user settings, it labels these unidentifiable users as Unknown to keep the report’s structure intact.
3. (data not available): why does data suddenly disappear?
Apart from the label issues above, you may sometimes see a yellow exclamation mark at the top of a report, and a field that should have a number shows (data not available).
This usually doesn’t mean your tracking code is broken. It’s GA4 choosing “not to display” data in certain situations to ensure data quality or comply with privacy rules. Here are the three main causes:
Common situations:
- GA4 thresholding: this is the most common cause. To protect user privacy and prevent specific individuals from being identified from very small amounts of data, GA4 automatically hides data when too few users fall under a dimension.
- Processing lag: GA4 needs time to process data (usually 24–48 hours). Until the data has been fully processed, event-level details may temporarily show as unavailable. We suggest checking again later.
- Incorrect User-ID setup: if the User-ID integration logic has errors, several different events may be wrongly attributed to the same user, causing calculation conflicts so the data can’t be displayed properly.
✅ Quick fix: to check whether a privacy threshold is the cause, first see whether the report includes demographic data such as age and gender, or Search Console search queries. These are withheld when there are too few users. Google removed Google Signals from Reporting identity in February 2024, so switching to “Device-based” won’t necessarily bring the data back. Try a longer date range or fewer dimensions, or check against the raw event data in BigQuery.
Note: if the data doesn’t exist or is still being processed, adjusting the report won’t fill it in automatically.
4. Summary: GA4 data issue troubleshooting table
Next time you see something odd in a report, use the table below to pinpoint the problem quickly:
| Label | Core definition | Common causes | Recommended action |
|---|---|---|---|
|
(not set) |
Tag parameters missing |
Missing UTMs, auto-tagging not turned on |
Check ad links and whether parameters are complete |
|
Unassigned |
Channel classification failed |
Naming doesn’t match default channel group rules |
Standardise naming conventions or set custom channel rules |
|
Unknown |
Privacy attributes restricted |
Not enough sensitive data collected, such as gender and age |
Treat as the group that didn’t provide attributes, and check that Google Signals is enabled correctly in Admin. |
|
data not available |
Privacy threshold triggered |
Data volume too small, triggering threshold protection |
Wait 48 hours, or use a longer date range and fewer dimensions |
The first step in data analysis isn’t chasing perfection, but learning to live with imperfection. Open your GA4 account now and run through this list, so your next monthly report isn’t full of blanks.
If you get stuck while troubleshooting, CloudAD can help you find where the problem lies, so get in touch.
