Not Set Google Analytics? 9 Causes and How to Fix Each One
“Not set” means GA4 couldn’t attribute data to a dimension. Maybe a source, page title, or country. It’s a missing tracking element, not a broken report. The top cause: an incomplete tracking code. Missing UTM parameters come second.
Below are the 9 causes of GA4’s “not set” value. Each has an exact fix. Check the table first to find your case. Then jump to the matching section.
Not Set Google Analytics (TOC):
What is ‘Not Set Google Analytics’?
The not set Google Analytics label means GA can’t attribute data to a dimension. Take a traffic sources report as an example. “Not set” means GA couldn’t find that traffic’s source.
This lack of data can be due to various factors, including:
- Missing or incorrect tracking code: If your tracking code isn’t properly installed on all pages or is incorrectly configured, Google Analytics won’t be able to track data accurately.
- Redirection issues: Sometimes, when a user is redirected to your site, the referral data can be lost, leading to ‘not set’ entries.
- Filters and custom settings: Overly restrictive filters or custom settings in your Google Analytics account can also result in data being categorized as ‘not set’.
Why is ‘GA4 Not Set’ an Issue?
Left unresolved, not set in GA4 skews your data’s accuracy. It can lead to misguided marketing decisions. Fixing it improves data quality. It also sharpens your tracking of behavior and campaigns.
| Report Where You See It | Most Likely Cause | Quick Fix |
|---|---|---|
| Traffic Acquisition / Source-Medium | Incomplete tracking code or missing UTM | Check tag status, reinstall with Analytify, or add UTM parameters |
| Keyword report | Encrypted organic search (signed-in Google users) | Not fixable; expected for privacy reasons |
| Landing Page report | Session not captured, or a redirect issue | Switch JavaScript redirects to server-side 301s |
| Ecommerce reports | Custom dimension not configured | Register the dimension under Admin and Custom Definitions |
| Demographic / geo reports | Anonymized IP, VPN, or proxy | Not fixable; a visitor privacy choice |
| Pages and Screens (titles) | Missing page title tag | Add a title tag to every page |
Not Set in Google Analytics: 9 Causes and Fixes
| Cause | Where It Shows Up | Fix |
|---|---|---|
| Incomplete tracking code | Source/medium and most reports | Confirm the tag fires on every page via Admin → Data Streams → Tag status, or reinstall it with Analytify. |
| Missing UTM parameters | Campaign reports | Add utm_source, utm_medium, and utm_campaign to every marketing link before publishing it. |
| Redirection issues | Traffic source and referrer data | Use server-side 301 redirects instead of JavaScript redirects, which can drop referrer and UTM data. |
| Filters and custom configurations | Varies by report | Check Admin → Data Settings → Data Filters for exclusions that may be catching more traffic than intended. |
| Ad blockers and browser settings | Source/medium and device data | This is largely outside your control for individual visitors. Server-side tagging may help reduce the impact. |
| Incomplete GA4 migration | Custom events and conversions | Rebuild events and conversions directly in GA4. They do not automatically carry over from Universal Analytics. |
| Anonymized IPs and proxies | Country and city data | This is expected with privacy-conscious traffic. It is not fully fixable and does not necessarily indicate broken tracking. |
| Misconfigured custom dimensions | Ecommerce data and item names | Check Admin → Custom Definitions. The parameter name in your code must exactly match the registered custom dimension. |
| Undefined page titles | Page title dimension | Check Reports → Engagement → Pages and Screens for blank titles, then add missing <title> tags. |
What are the Reasons Behind not set Google Analytics?
“Not set” values signal a data or configuration problem. Left alone, they distort your read on performance and behavior. Here are the key reasons, and the fix for each.
1. Improper Tracking Code Implementation
The top reason for not set in Google Analytics is a broken tracking code. Maybe it’s missing from a page. Maybe it has an error. This is common right after a GA4 migration. The new setup often isn’t fully integrated yet.
How to Fix Improper Tracking Code
Go to GA4 Admin >> Data Streams >> your stream. Check the tag status. If it’s not connected, or missing on some pages, reinstall with Analytify. That’s simpler than editing template code by hand.
2. Missing Campaign Parameters
Campaign tracking shows how your marketing performs. Missing or misconfigured UTM parameters cause this. They show up as ‘not set’ values in campaign reports. Tag every marketing link with UTM parameters to prevent it.
How to Fix Missing Campaign Parameters
Add utm_source, utm_medium, and utm_campaign to every link you share. That includes emails, social posts, and paid ads. Google’s Campaign URL Builder generates these for you. Nothing gets typed inconsistently across campaigns.
3. Redirection Issues
When users are redirected to your site, referral data can drop. This is common with third-party services that redirect visitors in. The result: ‘Google Analytics not set’ entries for traffic sources.
How to Fix It
Check whether your redirects are server-side 301s or JavaScript-based. JavaScript redirects often drop referrer and UTM data mid-redirect. Switching to server-side 301s preserves it.
4. Filters and Custom Configurations
Custom filters in Google Analytics are powerful. Misused, they report data as ‘not set’. An overly restrictive filter can exclude data. So can one wrong setting.
How to Fix
Go to Admin >> Data Settings >> Data Filters. Review what’s active. An internal-traffic exclusion set too broadly is the most common culprit. Narrow the filter, or create a separate unfiltered view to compare.
5. Ad Blockers and Browser Settings
Ad blockers and privacy settings are a growing cause of not set in Google Analytics. They stop Google Analytics from capturing full visit data. That shows up as ‘not set’ values.
How to Fix It
You can’t fix a visitor’s ad blocker. But you can reduce how often it matters. Server-side tagging routes GA4 through your own server instead of the browser. It’s the standard mitigation.
6. Issues with GA4 Migration
Moving to GA4 often triggers the GA4 not set issue. GA4 tracks and reports data differently than Universal Analytics did. A correctly configured setup avoids most ‘not set’ values.
7. Countries(Geographical dimensions not set)
Anonymized IP addresses, privacy restrictions, and proxies are common causes. They show up as “not set” in your demographic data.
How to Fix It
This one usually isn’t fixable, and that’s fine. Anonymized IPs, VPNs, and proxies are a privacy choice on the visitor’s end. A small, steady percentage of “not set” here is normal. It’s not a tracking bug.
8. GA4 Custom Dimensions Issues
‘Not set’ in GA4 is often tied to issues with custom dimensions. Take an ecommerce report as an example. “Not set” where you expect an item name means the dimension isn’t set up correctly.
How to Fix GA4 GA4 Custom Dimensions Issues
Go to Admin >> Custom Definitions. Confirm the dimension is registered with the exact parameter name your tracking code sends. A mismatch here, even a casing difference, is the most common cause.
9. Undefined Page Titles in GA4
Undefined page titles are a less obvious cause of “not set” in GA4. They usually show up on a poorly maintained site. To find them, go to Reports >> Engagement >> Pages and Screens. “Not set” under page titles means those pages lack proper title tags.
How to Fix Undefined Page Titles to Fix Not Set Issue in GA4
Go to Reports >> Engagement >> Pages and Screens. Sort for blank titles. Add a proper <title> tag to each page you find. Rank Math flags missing titles in the SEO analysis on each post.
| Cause | Fixable? |
|---|---|
| 1. Improper tracking code | Yes |
| 2. Missing campaign parameters | Yes |
| 3. Redirection issues | Yes |
| 4. Filters and custom configurations | Yes |
| 5. Ad blockers and browser settings | Partially (mitigate, can’t force) |
| 6. GA4 migration issues | Yes |
| 7. Anonymized IP / geo data | No, privacy choice |
| 8. GA4 custom dimensions issues | Yes |
| 9. Undefined page titles | Yes |
How To Fix Not Set in Google Analytics 4 for WordPress users?
Now that you know the causes, here are the exact fixes. Fixing “not set” in GA4 makes your data more accurate and useful.
Each fix below is numbered to match its cause above.
Analytify: Your Ultimate Solution to Remove GA4 Not Set Values
Analytify connects Google Analytics to your WordPress site without code. See: Read A Complete Guide to Install Analytify Pro. ‘Not set’ means data GA couldn’t determine, or that wasn’t set up right. You’ll see it in reports like keywords or landing pages.
Seeing “not set” in your data means some information is missing. Here’s how Analytify helps address it:
- Easy Integration: By seamlessly integrating Google Analytics with WordPress, Analytify ensures that tracking code is placed correctly on every page of your website, reducing the chances of discrepancies in data collection.
You can use Analytify to smoothly integrate your website with Google Analytics. Read more How to Integrate Google Analytics 4 with Analytify.
- Ensure Correct Tracking: Sometimes, GA4 not set errors occur due to improper tracking code setup or conflicts with other plugins/themes. Analytify’s setup process helps to mitigate these issues.
- Custom Dimensions: Analytify lets you set custom dimensions for better data representation. For instance, if not set is appearing in your author reports, you can set up custom dimensions for authors to correctly capture this data. Learn How To Get Started With The Custom Dimensions Add-On.
You may also like to read How To Get Started With The Authors Tracking Add-On?
- Monitor Events and E-commerce Tracking: If not set appears in your event or e-commerce reports, it might be due to issues with event tracking codes or e-commerce setup. Analytify provides specific setups for these types of tracking, ensuring that data is captured correctly. Read our guide to Enable Google Analytics Ecommerce Tracking.
- Support and Documentation: Analytify not only presents the data but also supports users on what certain metrics or issues (like not set) mean, helping them to troubleshoot and understand their data better.
Analytify also explains what metrics like “not set” mean. That helps you troubleshoot and understand your data faster.
Frequently Asked Questions
What does not set mean in Google Analytics?
‘Not set’ is GA’s placeholder when a dimension has no data. It shows up across reports. It means the data is missing or unavailable.
Why am I seeing not set in my keyword report?
‘Not set’ in your keyword report usually means an organic visitor. Google just couldn’t determine their search term. This often happens when a visitor is signed into Google. Being signed in encrypts their search.
Why are my eCommerce Reports Showing ‘Not Set’ in GA4?
‘Not set’ in ecommerce reports usually means a custom dimension problem. Check that product names and categories are configured correctly in GA4.
Is it a problem if a large portion of my data shows not set?
A high percentage of ‘not set’ data usually points to tracking issues or misconfiguration. Some ‘not set’ is normal. A sudden spike or a large share means you should investigate.
Why am I seeing not set in my landing page report?
This happens when a visit has no specific landing page. Or session data wasn’t captured correctly. It can also come from tracking issues or specific GA settings.
Does not set affect the accuracy of my data?
‘Not set’ entries don’t mean your data is wrong, just incomplete. A large volume of them skews your read on user behavior and performance.
Can “not set” data be recovered?
No. Once GA records data as ‘not set’, it can’t be changed retroactively. But finding the root cause helps you reduce future ‘not set’ instances.
Conclusion
Most “not set” values trace to one of three causes. A bad tracking code. Missing UTM parameters. Or a filter that’s too broad. Start with the table above. Find your case, then follow its fix.
WordPress sites running Analytify have tracking code and campaign data handled from setup. Most causes never come up.
You may also like to read Traffic Acquisition Report GA4: A Complete Guide (2024).
Now, we turn to you. Have you encountered ‘not set’ issues in your GA4 experience, and how have you addressed them? Share your experiences and insights in the comments.
