Graphed LogoGraphed
Graphed LogoGraphed
How It WorksAgentsIntegrationsPricing

What Does This Represent Inside of Google Analytics?

Cody Schneider••7 min read

Seeing "(not set)" in a Google Analytics report can be frustrating. It feels like your data has a hole in it, leaving you with questions instead of answers. Did something break? Is your tracking wrong? The good news is that "(not set)" isn't an error message - it's a signpost. This article explains what it means, the most common places you'll find it, and how to fix the underlying issues for cleaner, more reliable data.

GraphedGraphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Watch Graphed demo video

What Exactly Does '(not set)' Mean in Google Analytics?

In Google Analytics, "(not set)" is a placeholder value. GA uses it whenever it has collected data for a session or event but hasn't received any information for a specific dimension you're looking at. Think of it like a survey form where a person answered most questions but left one field blank. The survey was still submitted, but that specific piece of information is missing.

So, when you see "(not set)" in your Landing Page report, it means Google Analytics recorded sessions but, for some reason, couldn't associate them with a specific landing page. When you see it in your Campaign report, it means GA knows you got traffic, but it couldn't identify which marketing campaign sent it.

It’s important to remember that "(not set)" is a symptom, not the disease itself. Your job is to play detective, identify the root cause of the missing data, and patch the leak.

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Why '(not set)' Appears in Your Reports (and How to Fix It)

The reasons for "(not set)" values vary depending on the report you're viewing. Let's break down the most common dimensions where this placeholder pops up and what's likely causing it.

1. Landing Page Report

One of the most frequent places you'll encounter "(not set)" is in the Landing Page report. This can be particularly confusing - how can a session not have a landing page?

  • Common Causes: This usually happens with sessions that don't include a page_view event. In GA4, new sessions are triggered by the first event that comes in. If that first event is a custom event (like a purchase or a file download) sent via the Measurement Protocol or a server-side tag and it doesn't also contain page details, the session will lack a designated landing page. Other causes can include sessions that span across midnight or long sessions where inactivity periods (over 30 minutes by default) cause a new session to start without a fresh page load.
  • Relatable Example: Imagine a customer adds items to their cart on your retail site but gets distracted and leaves the tab open. An hour later, they return and complete the purchase. When they check out, GA starts a new session because the previous one timed out. The first event in this new session is the purchase event, not a page_view. As a result, GA logs the conversion but shows the landing page as "(not set)".
  • How to Fix It:

2. Traffic Acquisition Reports (e.g., Session Source / Medium, Campaign)

This is arguably the most critical area to clean up. When your traffic sources are "(not set)", you can't properly attribute conversions, calculate ROI, or understand which marketing channels are working.

  • Common Causes: The overwhelming cause here is improper or missing UTM parameters on your marketing links. If Google Analytics receives traffic but doesn't see UTM parameters (utm_source, utm_medium, utm_campaign, etc.) or an automatic identifier (like a gclid from Google Ads), it can't figure out where the user came from. This traffic is often miscategorized as Direct. However, if only some parameters are present (e.g., utm_source but not utm_campaign), the missing dimension will show as "(not set)".
  • Relatable Example: Your social media manager posts a link to your latest blog post on LinkedIn. The link is yourwebsite.com/blog/new-post?utm_source=linkedin. Because they forgot to include utm_medium and utm_campaign, anyone clicking that link will show up correctly in the Source report, but if you look at the Campaign or Medium reports, they’ll appear under "(not set)".
  • How to Fix It:
GraphedGraphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Watch Graphed demo video

3. Geographic Reports (e.g., Country, Region, City)

Seeing "(not set)" bubble up in your location reports can seem odd, but it's becoming more common in today's privacy-focused web.

  • Common Causes: Google Analytics determines location based on the user's IP address. If the IP address is hidden, masked, or otherwise unavailable, GA can't resolve it to a geographic location. This is frequently caused by users on a Virtual Private Network (VPN), corporate proxies, or using privacy features in browsers that obscure their IP.
  • How to Fix It: For the most part, you can't. This is a user-side privacy measure and generally out of your control. For "(not set)" city or region data, it just means GA could identify the country but couldn't get more specific. As long as the percentage of "(not set)" country data is low, you usually don't need to worry. This is simply a feature of the modern internet.

4. Page Title Report

Similar to the Landing Page issue, "(not set)" can appear in reports that use Page title as a primary dimension.

  • Common Causes: This usually traces back to events that are not intrinsically tied to a page view. If you trigger a custom event - for example, a video_progress or scroll_depth event - and that event fires independent of a page load (perhaps through a custom script), it may not carry a page_title parameter along with it.
  • How to Fix It:

A Simple Framework for Investigating '(not set)' Values

When you spot "(not set)", don't panic. Follow this simple process to diagnose what's happening:

  1. Identify the Report: Where are you seeing "(not set)"? The location of the issue provides the first major clue. Is it in the Landing Page report? The Campaign report? The City report?
  2. Assess the Impact: What percentage of the data is affected? Anything under 2% is likely just unavoidable statistical noise. If "(not set)" accounts for 10%, 20%, or more of your traffic for a critical dimension like Campaign or Landing Page, you have a problem worth solving.
  3. Cross-Reference with a Secondary Dimension: This is the single most powerful diagnostic tool. By adding a second dimension to your report, you can add valuable context.
  4. Form a Hypothesis and Investigate: Based on the data, form a hypothesis. "I believe the high volume of "(not set)" campaigns is caused by missing UTMs in my email provider because the secondary dimension shows a high correlation with my newsletter / email source/medium." Now, go look at the links in your last email newsletter to prove or disprove your theory.

One major pro tip: Never just filter out "(not set)". It can be tempting to create a report filter to exclude rows where the dimension equals "(not set)" to get a "cleaner" view. Don't do it! This is like hiding the check engine light instead of fixing the engine. You're not solving the problem, you're just ignoring a data quality issue and making decisions based on an incomplete picture.

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Final Thoughts

Finding "(not set)" in your Google Analytics reports isn't a sign of failure but an opportunity to improve your data hygiene. It serves as a valuable signal, pointing to gaps in your data collection. By systematically identifying where it appears, analyzing the potential causes, and then fixing the source, you can build a more accurate and trustworthy foundation for your analytics.

Tidying up data collection can feel like a time-consuming chore, especially when you’re manually digging through Google Analytics reports trying to identify the root cause of issues like "(not set)". At Graphed, we help you connect your data sources in seconds, allowing you to bypass the report wrangling. Instead of building complex reports with multiple dimensions, you can simply ask a question like, "Show me all sessions with a '(not set)' landing page and chart them by traffic source." We generate the visualization instantly, so you can spend less time hunting for problems and more time acting on clear insights.

Related Articles