Demographic Targeting vs Topics Targeting: Person or Page
In short: Both narrow where a Display or video budget goes, but they cut along different axes. Demographic targeting filters the person - it prunes age, gender, parental status, and income brackets from whoever your other targeting reaches. Topics targeting selects the content - it makes your ads eligible on pages and channels Google files under a subject, regardless of who is reading. In practice demographics is a subtractive layer and topics is a primary inventory pick. If your waste comes from the wrong people, cut demographics; if it comes from the wrong pages, start with topics.
By the AdFlint research team · Fact-checked against current Google and Meta platform behavior · Last reviewed July 2026
Demographic Targeting
Restricts or adjusts delivery by age, gender, parental status, and household income, using the profile data Google has declared or inferred for signed-in users.
You set demographics at the ad group or campaign level, either excluding brackets outright or layering bid adjustments on top of them. It earns its keep as a subtractive control, cutting bands you cannot legally or profitably serve. Two traps: a meaningful share of impressions carry unknown demographics and get excluded alongside the rest, and housing, employment, and credit categories block these controls entirely.
Full definitionTopics Targeting
Places Display or video ads on pages and channels about a chosen subject, targeting the content being consumed rather than the person consuming it.
You pick from Google's topic tree and your ads become eligible on any inventory Google classifies under that topic, at whatever depth you select. It is a fast way to get broad contextual coverage across the Display Network or YouTube. Because topics are wide by design, they pull in far more inventory than expected, so placement exclusions and a capped budget keep the waste visible.
Full definitionSide by side.
The differences that actually change what happens in your account.
| Demographic Targeting | Topics Targeting | |
|---|---|---|
| What Google evaluates | The profile attributes attached to the signed-in user seeing the ad. | The subject matter of the page, app, or channel serving the ad. |
| Role in the ad group | A restriction layered on top of whatever other targeting is selecting inventory. | A targeting method that selects inventory by itself, no other layer required. |
| The blind spot | The Unknown bucket - users Google cannot classify, often a large share of impressions. | Misclassified or thin pages that Google files under your topic anyway. |
| Housing, employment, credit campaigns | Lose most of these audience controls under Google's restricted-targeting policy. | Unaffected - content targeting stays available when audience controls are restricted. |
| Where it reports | Demographic tables split by age, gender, parental status, and income. | Content reporting showing the topics and the individual placements that served. |
| What it costs you when wrong | Excluding Unknown silently removes reach that may have converted fine. | A broad topic buys junk inventory until you add placement exclusions. |
| How you tighten it | Exclude more brackets or bid down on the weak ones. | Pick a deeper subtopic and exclude the placements dragging it down. |
What actually separates them.
Demographics never adds inventory - it only removes people from what other targeting delivers - while a topic on its own makes an ad group eligible across everything Google files under it.
Topics targeting works identically on every impression because it reads the page, while demographic targeting shunts users Google cannot classify into an Unknown bucket you must decide to keep or cut.
In housing, employment, and credit campaigns Google disables age, gender, and related controls, so topics keeps working exactly where demographics is off the table.
A wrong topic shows up as bad placements you can name and exclude, while a wrong demographic exclusion is invisible - the impressions simply never happen.
Stacking the two intersects them - the ad must sit on a matching page and in front of a matching person - so each added layer multiplies the reach cut instead of adding to it.
Which one should you use?
Use Demographic Targeting when
- Your product is legally or practically limited to an age bracket, like retirement planning or student banking.
- Household income is a real qualifier and impressions below a bracket are money burned.
- You already have solid audience or content targeting and want to prune brackets that never convert.
- Creative and landing pages are built for one gender or life stage and bounce everyone else.
Use Topics Targeting when
- You have no first-party data and need reach among people consuming content about your category.
- You are in a restricted vertical where demographic controls are disabled and content is the main lever left.
- Context is the qualifier - your offer makes sense to anyone reading about the subject, whoever they are.
- You want fast, broad coverage for awareness and are prepared to police the placement report weekly.
Common questions.
Can I use demographic and topics targeting in the same ad group?
Yes, and they intersect: the ad serves only on pages under your topic and only to users in your included brackets. Every layer cuts reach multiplicatively, so check delivery after launch to confirm the combination can still spend. If volume collapses, loosen the layer with the weaker performance case first.
Why does so much of my traffic show as Unknown in the demographics report?
Google can only bracket users it can identify, and a meaningful share of Display impressions come from people it cannot classify. Those land in Unknown. Excluding it makes the report look cleaner but silently removes reach that often performs close to your targeted brackets, so judge Unknown on its own conversion numbers before cutting it.
Why are my age and gender controls missing on my housing campaign?
Campaigns in housing, employment, and credit fall under Google's personalized advertising restrictions, which remove age, gender, parental status, and related targeting. That is policy, not a bug. Content-based methods like topics remain available, which is why restricted advertisers lean on contextual targeting.
Does topics targeting know anything about who is viewing the ad?
No. It classifies the page or channel, not the person, so the same user is in scope on one article and out of scope on the next. If you need the person filtered as well, layer demographics or an audience segment on top and accept the smaller reach.
Or stop choosing between them.
AdFlint picks the setting, writes the ads, and keeps optimizing inside the Google and Meta accounts you already own.
Related comparisons
- Affinity Audiences vs In-Market Audiences
- Custom Segments vs In-Market Audiences
- Customer Match vs In-Market Audiences
- In-Market Audiences vs Remarketing Lists
- In-Market Audiences vs Similar Segments
- Demographic Targeting vs In-Market Audiences
- In-Market Audiences vs Life Events Targeting
- In-Market Audiences vs Optimized Targeting