Cookieless Audiences
Home Database API Docs Pricing Live Demo Taxonomy
Use Cases
Media Planning by Persona Inventory Curation & Deal Packaging Seller-Defined Audiences CDP & Analytics Enrichment ABM Account Profiling
Industries
SSPs DSPs Publishers Agencies Curation Platforms
Company
Contact Login
Try Live Demo
Use case · Brand suitability & fit

Brand Suitability & Audience Fit

Safety tools tell you where a brand must never run. They say nothing about where it belongs. Fit analysis matches your target profile against each domain’s coded audience attributes across 102M domains, producing a transparent score from readable fields — not an opaque vendor rating.

Demographics, life stage & urbanicity 285 sub-interest codes 283 purchase-intent segments
102Mdomains with audience profiles to score
4fit components: demographics, interests, intent, confidence
1,667personas for fast first-pass matching
0black boxes — every score decomposes into fields
IAB Audience Taxonomy 1.1 aligned Fit scores decompose to inspectable attributes Banded confidence per attribute No PII in the pipeline Quarterly refresh
Beyond the blocklist

Safety, suitability, fit — three different questions

Most brand-protection budgets stop at the first rung of a three-rung ladder. Each rung asks a progressively more valuable question, and only the third requires audience data.

Rung 1 · Safety

“Where can we never run?”

Binary exclusion of illegal, hateful or dangerous content. Universal across brands, handled by blocklists. Necessary — and entirely negative: removes the worst without rating the rest.

Rung 2 · Suitability

“What content matches our standards?”

Brand-specific content judgments — an airline’s view of aviation-incident news differs from a newspaper’s. Content-category data from our API drives this rung. Still silent on who is reading.

Rung 3 · Audience fit

“Does the readership match our buyer?”

A domain can be safe, suitable — and read by entirely the wrong people. Fit compares your target profile with each domain’s coded audience, turning “acceptable inventory” into “right inventory.”

Fit components

What a fit score is made of

Simple arithmetic over coded fields — documented on the taxonomy page — so any score can be challenged, decomposed and reproduced by another analyst.

Demographic match

Field-by-field agreement on age brackets, gender skew, income band, life stage and urbanicity between the domain’s profile and your target.

Interest overlap

Shared INT.* codes between the brand’s interest set and the domain’s — weighted toward specific sub-interests over broad tier-1 groups.

Intent alignment

Shared PI.* segments — the strongest fit evidence, because purchase intent is the commercial behavior the brand is buying access to.

Confidence weighting

Each component is weighted by low / medium / high confidence bands. A strong match on weak evidence never outranks a moderate match on strong evidence.

Workflow

The fit-scoring workflow

Five steps from brand profile to a scored, tiered domain list — a spreadsheet exercise on the database file, or a scripted job via the API.

Encode the brand profile

Write the target audience in vocabulary codes: demographics, interests, intent segments — the same fixed values the database uses.

Assemble the candidate list

Start from the media plan, a curated package, or a database tier — every candidate already carries its full attribute set.

Score the components

Compute demographic match, INT.* overlap and PI.* alignment per domain, each weighted by confidence bands.

Tier the results

Bucket domains into strong fit, partial fit and mismatch. Components tell you exactly why each domain landed where it did.

Act on the tiers

Shift budget toward strong-fit domains, price partial fits accordingly, and cut mismatches that safety tools would have approved.

Coverage

Fit-score the whole plan, not just the head

102Mdomains scoreable, head to long tail
285sub-interests for overlap scoring
283purchase-intent segments for alignment
40%+of traffic is cookieless — fit works there too
Worked example

Scoring three domains for an outdoor-apparel brand

The brand’s encoded target profile, then three candidate domains scored against it:

Ages 25_3445_54, balanced gender, upper_middle income
Interests INT.travel.adventure_travel, INT.travel.camping, INT.healthy_living.fitness_and_exercise
Intent PI.sporting_goods.outdoor_recreation_equipment, PI.travel.camping
Candidate domain (archetype)DemographicsInterest overlapIntent alignmentFit verdict
Adventure-travel & trail blog
35–44, balanced, upper-middle, high confidence
Match on age, gender, income adventure_travel, camping, fitness_and_exercise all present outdoor_recreation_equipment + PI.travel.camping, high confidence Strong fit
Metro news site
Broad 25–64, mixed income, medium confidence
Partial — audience broader than target Weak — news & politics dominate; no camping or adventure codes None of the target PI.* segments Partial fit
Esports team-coverage site
18–24, male-strong, high confidence
Mismatch on age and gender skew INT.video_gaming.esports — no overlap with target set Gaming and electronics intent, not outdoor Audience mismatch
The point: all three domains pass every safety blocklist. Only fit scoring reveals the third buys the wrong audience entirely, and the first deserves a budget premium. Run the same comparison on real domains in the audience demo.
Comparison

What each layer of brand protection sees

 Safety blocklistSuitability categoriesAudience fit (this dataset)
Question answeredWhere can we never run?What content matches our standards?Does the readership match our buyer?
BasisContent exclusion listsContent categories per brand policyCoded audience attributes: demographics, INT.*, PI.*, personas
OutputBinary block / allowCategory-level allow / avoidGraded fit score with inspectable components
Budget effectRemoves the worstShapes the middleConcentrates spend on the best
RelationshipComplementary layers — fit analysis assumes safety and suitability screening remain in place and adds the audience dimension on top
Fit scoring is a planning exercise over domain-level data — not an impression-level pre-bid signal. For per-URL granularity when auditing specific placements, use the real-time page-level API.
FAQ

Brand suitability & audience fit — common questions

How is audience fit different from brand safety and suitability?

Safety excludes unacceptable content universally. Suitability applies brand-specific content judgment. Fit is an audience question — do the domain’s readers resemble the brand’s buyers? A domain can pass the first two completely yet fail on fit. The three layers are complementary, not interchangeable.

Is the fit score a field in the database?

No — deliberately. The database ships raw coded attributes (demographics, interests, intent, personas, confidence bands). You compute fit against your brand profile with transparent arithmetic. Scores stay decomposable, and different brands — or different campaigns — can score the same domain differently.

Does this work for the cookieless share of the plan?

Yes. The audience profile is a property of the domain, not of visitor identifiers. Domains whose traffic skews to Safari, Firefox or iOS — roughly 40%+ of traffic today — are scored exactly like everything else. Fit analysis never depended on cookies.

Do we need the API or just the database file?

For campaign-level fit scoring, the database file is enough — top-100k at $490 one-time, top-1M at $1,990 with instant download. Quarterly refreshes keep scores current. The real-time API adds page-level segmentation for auditing specific URLs rather than whole domains.

Related use cases

Find out where your brand actually belongs

Encode your target profile, score your current plan, and see which approved domains are quietly buying the wrong audience.

Open the audience demo See database pricing
Stay in the loop

You are on the list!

We will send you updates that matter — no spam.