I found this case for several days after integrating Google Analytics and Google Tag Manager.
For the first time, I think this problem will fix in the next day. But the problem still appears. The "Not set" value looks like:
Follow this way to fix the issue looks like.
Table of Content
- What the value (not set) means?
- The "Not-set" value impacts for Web Analysis
- Automated Check Issue
- Content Grouping Issue
- Behavior Reports Issue
- Hostname Issue
- Page Title Issue
- Source, Medium, Campaign and Ad Content Issue
- Organic Keyword Issue
- Paid Keywords Issue
- Browser and Browser Version Issue
- Geo Location Issue
- Reverse Goal Path Issue
Google Analytics hasn't received any information for the dimension you have selected.
As a marketing specialist, you have numbers but it’s not clear what visitor mean and how to use in data analysis.
When the "not-set" comes, the reporting and analysis can be a real pain.
The reason is, the (not set) label did not tell valuable stat for analysis or decision-making process. It hurts the usefulness of stats, right?
The (not set) label is a nightmare for Web ownership. Why?
Imagine you have the website with thousands of visitors per day and found this label.
It is a disaster!!
You can see, the web has a content grouping configuration. There are 9 group product category data. The"not-set" value is 45% of all data stats.
Set up content grouping on the website is so important. That's can:
- Being a holistic overview of content performance with success events (conversions) indicators.
- Being holistic navigational analysis and optimization.
- Overcoming technical hurdles with their content structure.
The result is, the higher the (not set) value makes data analysis becomes more difficult. The stats on Google Analytics is nothings. You can't know what the data says and means too.
Here are the details to fix the "not-set" first:
Needs a lot of time to manually checking (not set) data label. Even more, if you wanna monitoring the issue in every month or even more often.
You can track the not-set data using custom alerts with segmentation. Check this out:
This is the first alternative to set up an automated alert for each of the dimensions.
This setting will send the 3 notification about:
- Trigger an alert daily, weekly, monthly.
- The current base level of (not set).
- Ideal trigger needed. Increase of (not set) value with 10% or others.
Here's how to set up Custom Alert:
Open the Google Analytics Go to Segments
Click to Create new Segments Click +New Segment
Follow as well as the screenshot below:
Move to Custom Alerts.
Click +New Alert
Type the setting as well as the screenshot:
It can be an issue if the (not set) value is greater than 10% of total page views.
The problems appears because a
<title> tag in the header is an error or not created at all.
To know which pages cause the problem, use the additional page parameter. Maybe your GA tracking code is launching before the
<title> tag. In this case, switch the order.
If this issue still exists, try to use Paul guide:
You can find this issue on the Site Content (Landing Pages report)
This report shows the landing page which the visitors start a session. The landing page looks like an entry-point for the visitor.
You can use it to check the bounce rate.
The bounce rate is the percentage of visitors who leave without taking any actions on the page.
In short, you can’t define which the pages need improvement if the not-set label exists. It's happening because:
- The session ended at midnight or after 30 minutes of visitor standby. Google marks a new session after that.
- A session has no page or screen views. You set a filter deleting specific page views or screen and page tracking settings are wrong.
- There are two tracking codes at a time (analytics.js and gtag.js). Use one code only.
Web owner frequently ignorance this issue. It because the hostname dimension is "hidden".
Check your hostname dimension here:
The report should only contain relate to “hostnames”. Pay attention to the traffic coming from spam bots (in case of (not set) value).
Spambots leave fake data on Google Analytics account without actually visiting your website.
- Exclude all hits from known bots and spiders in view settings.
- Add an include filter on your hostname(s).
This issue looks like:
You can view the page title issue on Behaviour menu.
Fix the problem using 2 steps:
- An error with the
<title>tag in the head of your page or no
<title>tag at all. Pay attention in there and fix it accordingly.
- Adding the secondary dimension “Page” to the (not set) value on “Page Title”.
- The GA tag position was in above the
<title>tag of your pages. Move the GA code to under the
This is an urgent issue on SEO and site experience.
These labels are automatically recorded by Google or tagged with custom UTM parameters.
The (not set) will appear because these traffic sources did not have campaign or content information. Check your Source and Medium labels on:
View the Campaign and Ad Content labels with:
How to fix the issue?
- Make sure that all tagged links are formatted (and spelt) correctly.
- Use the URL builder from Google include source, medium and campaign.
Google is not showing for privacy reasons. That's why you see the not-set or not-provided label.
View the Organic Keyword using:
In short, the traffic coming from an odd search engine or you’ve manually tagged something as Organic and not supplied a keyword.
It makes the traffic coming without the keyword.
Fix the issue using the “utm_term” field from the URL builder.
Go to the Paid Keywords label issue on:
There are configured correctly in your Paid Search traffic such as:
- Improper integration of Google Ads and Google Analytics
- The automatic signature feature in Google Ads being turned off. When a visitor clicks on an ad message, the Google Click Identifier (GCI) value is added to the target URL. Google Analytics saves it as a new site cookies file on the website’s domain.
- Void clicks. Google Ads understands these as clicks made by bots or malware, or double or triple clicks with no use for the advertiser.
- Redirects. While redirecting from one URL to another, gclid might get lost. As a result, you’ll see (not set).
- Syntax and gclid problems such as the register changes in the URL, website cuts the gclid parameter because it has more than 100 symbols, the website settings forbid processing of the request.
Fix this issue with:
- Make sure the accounts are linked to your Google Analytics view.
- Make sure the auto-tagging is enabled. If you are using manual tagging, passing the keyword through the utm_term parameter.
Google Analytics will detect the user agent when the visitor comes. The user agent contains information about the device you are using as well as which browser and browser version.
Sometimes, Google can't identify user agents because:
- Deleted cookies
- Couldn’t detect the location based on IP or couldn’t detect the IP at all
- Variety of blockers (AdBlocker, etc.)
That's why (not set) show up.
How to fix?
- Exclude hits from known bots and spiders is checked in View Settings.
- Add the secondary dimension to know the providers and manually exclude with view filters.
Google Analytic identify the location of users from their IP address, but this information isn’t always available.
Hence the Google Analytic limit, sometimes you can see not-set label on Audience >> Geo >> Location.
The reason why this issue come is, The IP address or service provider may not be shared by the visitor. Google will identify as spam or bots and sometimes display the traffic as a (not set) label.
The network issue come from this issue too. As the behaviour of this group doesn’t deviate, you don't need to further investigate this.
How to fix?
Go to transactions/goal completions/pageviews to recheck this issue.
Find this issue on Conversions >> Goals >> Reverse Goal Path.
The reverse goal path report shows goal completion locations and the three previous pages viewed.
This issue based on your goal settings. If your goal needs less than 3 steps to complete, (not set) appears for sure and it's fine.
Remember, “not set” shows up when there is no data to show. If someone visits the site and completes a goal right away (#1 in the example below), previous steps 2 and 3 would be “not set.”
That's how to fix the not-set label. Sometimes you can avoid the not-set reports by:
- More thorough campaign tagging
- Event tracking and spam blocking
But other times, it is an inherent part of the reports, such as in the reverse goal path.