Can You See Demographics for a Specific URL in GA4?

Can You See Demographics for a Specific URL in GA4?

You have one page that matters. A pricing page, a landing page behind a paid campaign, a blog post that suddenly started converting. You want to know who is reading it: how old they are, where they live, what they are interested in.

So you open the Demographic details report, look for somewhere to type a URL, and find nothing. There is no page filter. There is no page column. The report simply does not work that way.

This is not a bug, and it is not a permissions problem. It is a consequence of how Google Analytics 4 models people versus pages, and once you understand that distinction the workaround is obvious.

The harder problem is the one almost nobody warns you about: even when you build the report correctly, Google may refuse to show you the numbers.

Can You See Demographics for a Specific URL in GA4?

Not in the Demographic details report, which has no page dimension at all. You can get close in an Exploration by pairing a page dimension with age, gender or interests. Whether you actually see data depends on data thresholds, which Google applies automatically and which you cannot turn off.

The Short Answer

Three things are true at once, and they pull in different directions.

The pre-made report cannot do it. Google's Demographic details report is reached from the left menu by selecting Reports, then clicking User Attributes and Demographic details.

Google describes it as a report covering the language, interests, location, age and gender of the people who use a site or app. Every dimension it offers describes a person. None of them describes a page.

An Exploration can do it. Explorations let you combine dimensions freely, so you can put a page dimension and a demographic dimension in the same table. This is the route that works.

Thresholding may stop you anyway. Google withholds rows whenever a report or exploration includes demographic data and the underlying user count is too small. Filtering to a single URL is the fastest way to make a user count small. The better your targeting, the more likely you are to see blanks.

Knowing who reads a page is only half the job. The other half is getting them there. A free SEO audit from SEO Stuff shows you which pages are losing search traffic and why. Get your free audit.

Why the Demographic Details Report Cannot Do It

The limitation is structural, not cosmetic. It is worth understanding, because it also tells you what to expect from the workaround.

What the Report Actually Offers

The dimensions available in the Demographic details report are Age, City, Country, Gender, Interests, Language and Region. That is the full set.

Age arrives in brackets rather than exact values. Google's brackets are 18-24, 25-34, 35-44, 45-54, 55-64 and 65+.

Editors and Administrators can add or remove dimensions in the report. Google does not publish which dimensions are available to add, so treat that as something to test in your own property rather than something to plan around.

If the report is missing entirely, Google notes it may have been removed from your property or may not be in your default view. Report navigation in GA4 is editable, so a colleague may simply have hidden it.

Why Age and Gender Are User Facts, Not Page Facts

GA4 separates what it knows about a person from what it knows about an action. Events record what someone did, such as opening a page. Event parameters add detail to those actions. User properties describe the person instead: things like age or location.

Age, gender, interests and language all sit on the user side of that line. A page path sits on the event side. The Demographic details report is built entirely from the user side, which is why it has no slot for a URL.

That framing matters for a second reason. A person can read six pages in one visit, so attributing one 35-44 year-old to six URLs teaches you one thing six times rather than six things once. Any page-level demographic figure is an approximation, and is worth presenting as one.

One Prerequisite People Miss

Demographics in GA4 are not collected from your site. They come from Google Signals.

Google says plainly that Analytics will not process demographic data if Google Signals is turned off for your property or region, and that geographic dimensions such as Country are unaffected by this. If your Demographic details report is empty across the board, check that setting before you blame your tagging.

Google Signals is turned on in Admin, under Data collection and modification, by opening Data Collection and enabling Google signals data collection. You need Editor access or above at property level. Google also notes that signed-in data expires after 26 months by default.

Only aggregated data from users who consent to sharing demographics is included. On mobile apps there is a further condition: Google states that without the Device Advertising ID present, Analytics cannot derive demographics and interest data, and that iOS apps must collect IDFA for Age, Gender and Interests to be derived automatically.

How to Get Demographics for One URL, Step by Step

This is the Exploration route, using Google's own interface labels.

Step 1: open Explorations. Click Explore in the left navigation.

Step 2: start a blank exploration. Google's instruction is to click the create icon for a blank exploration, or to use a template. A blank exploration opens as a free form table by default, which is what you want. The other techniques Google lists are Cohort exploration, Funnel exploration, Segment overlap, User exploration, Path exploration and User lifetime.

Step 3: import your dimensions. In the Variables column on the left, click the add-new-item icon to the right of the DIMENSIONS section, select a page dimension and a demographic dimension such as Age or Gender, then click IMPORT. Do the same for the METRICS section and import a user metric. Google caps each exploration at 20 dimensions and 20 metrics.

Step 4: place them in Tab Settings. Drag each variable from Variables into the Tab Settings panel, or double-click it, or click a landing spot in Tab Settings and pick it from the list. Dimensions go in the Breakdown area and metrics go in the Values area. Double-clicking a dimension applies it to the ROWS section of a free form exploration.

Step 5: narrow to your page. Add a filter in Tab Settings on your page dimension so the table covers only the URL you care about.

Step 6: read the data-quality icon before you read the numbers. This step is the one people skip, and it is covered in the next section.

The same discipline applies to search. Request a free SEO audit and see which pages are underperforming against their potential.

What Thresholding Does to a Single-URL View

Google applies data thresholds to stop anyone inferring the identity or sensitive information of individual users from demographics, interests or other signals in the data. The thresholds are system defined, and Google is explicit that you cannot adjust them.

The trigger conditions matter here. Google says data may be withheld when a report, exploration or API call includes demographic data, or audiences defined using demographic data. It also says data may be withheld over a narrow date range when user or event counts in that range are low.

Read those two conditions together and the problem with a single-URL demographic view becomes obvious. You have deliberately included demographic data, and you have deliberately shrunk your population to the visitors of one page. Both triggers are armed.

Google's own illustration of the mechanism is a gender example: if a report contains fewer than a certain number of instances of a given gender value, the data for that value may be withheld.

Applied to one page over one week, that is not an edge case. It is the normal outcome for most pages on most sites.

GA4 does tell you when it has happened. Explorations carry a data-quality icon that changes from green to yellow, with a tooltip explaining the state of the data, and reports show a thresholding notice.

A blank cell is therefore not a zero. Treat an unexplained gap as suppression until you have checked the icon.

Sampling is a separate ceiling worth knowing. Google says an exploration may be based on sampled data when more than 10 million events fall inside a particular exploration query.

When This Analysis Is Worth Running

Given the caveats, it is worth being honest about when the effort pays off.

It works well on high-traffic pages. A page with tens of thousands of monthly users will usually clear the thresholds comfortably and give you a stable read.

It works well on page groups. Filtering to a directory rather than a single URL, such as every page under a pricing or product path, keeps the user count high while still answering the question you actually have.

It works well over long windows. Ninety days beats seven. Google names narrow date ranges as a thresholding trigger, so widening the window is the cheapest fix available.

It works badly as a conversion diagnostic. If your real question is why one page converts and another does not, demographics are rarely the answer, and the thresholds will be at their most aggressive exactly where your sample is most interesting.

Limitations Worth Knowing First

A few constraints are worth internalising before you promise anyone a report.

Demographics are modelled, not declared. They come from Google Signals rather than from your visitors telling you anything, and they cover only consenting signed-in users. The percentages you see describe a subset of your traffic, not all of it.

Thresholds cannot be configured away. There is no setting, no workaround and no sampling control that turns them off.

Compatibility is not documented. GA4 shows an incompatible-request icon when an exploration contains a combination of dimensions and metrics it cannot serve, and asks you to update the request.

Google does not publish a list of which combinations are incompatible, and the help page gives no error text. You find out by building it.

One user is not one pageview. A user-scoped attribute spread across a browsing session will inflate any per-page count you build from it.

The Alternatives

If the Exploration route does not survive your thresholds, three options are genuinely useful.

Widen the scope. Page groups and longer date ranges are the first and best move, and they answer most real business questions better than a single URL does.

Use comparisons instead of filters. Applying a demographic comparison to a standard pages report asks the same question from the other direction, though the same thresholding rules still apply.

Collect it yourself. A survey, an onboarding question or a logged-in profile field gives you declared data about the people on a specific page, with no thresholding and no Google Signals dependency. It is more work and it is also more trustworthy.

Audience data is only useful if the audience arrives. Book a free SEO audit and find the fixes that move rankings.

Final Thoughts

The question looks like a feature request and it is really a modelling question. GA4 knows things about people and things about pages, and the Demographic details report lives entirely on the people side, which is why no amount of searching will produce a URL filter inside it.

Explorations bridge the two, and the procedure is short enough to build in five minutes. The part that deserves your attention is not the build, it is the reading. Check the data-quality icon, widen the window, group pages instead of isolating them, and never report a blank cell as a zero.

If your Demographic details report is empty everywhere rather than just on one page, the cause is almost certainly Google Signals rather than anything page-specific. Our guide to how to check website visitors in Google Analytics walks through the user-count reports and the retention settings that quietly limit what Explorations can reach.

Want the same clarity about your search performance? Get a free SEO audit from SEO Stuff and start with what is costing you the most.