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
Industry · Publishers

Audience Data for Publishers

Every sales conversation starts with the same question: who is your audience — and why you rather than the title next door? Cookieless Audience gives publishers a documented, coded answer: a domain-level audience profile drawn from fixed v1.0 vocabularies aligned with IAB Audience Taxonomy 1.1, plus the same profile for every competitor title you get comped against. It powers pitch decks, seller-defined audience labels and direct-sales narratives — without cookies, panels or a data-science team.

102Mdomains profiled — yours and every comp set
1,667deterministic personas for inventory labels
285sub-interests (INT.* codes)
283purchase-intent segments (PI.* codes)
Aligned with IAB Audience Taxonomy 1.1 Fixed, versioned vocabularies (v1.0) Banded confidence: low / medium / high No PII anywhere in the pipeline Self-serve download, quarterly refresh
The publisher problem

“Who reads you?” deserves a better answer than a media kit adjective

Large publishers answer the audience question with first-party data teams and survey programmes. Everyone else answers it with panel numbers that thin out below the head of the market, or with media-kit language — “affluent, engaged, influential” — that buyers have learned to discount. And when an agency comps your title against three competitors, their data about you is usually better than yours.

Domain-level audience profiling changes the footing. Your properties — and your competitors’ — sit in the same 102M-domain database, described with the same coded fields: demographics, 285 sub-interests, 283 purchase-intent segments, B2B firmographics and a resolved persona, each with a banded confidence value. The profile is computed from the property itself, not from visitor cookies, so it covers the Safari, Firefox and iOS readership — roughly 40%+ of traffic — that cookie-derived audience counts systematically miss. Cookies remain on Chrome, but a premium editorial audience skews heavily to exactly the browsers that block them.

The result: a defensible, reproducible audience story you can put in front of a buyer, with codes a buyer’s own analysts can verify against the published taxonomy.

Where cookie-based audience counts undercount editorial readers

Chrome
cookies remain
Safari
blocked by default
iOS in-app
blocked by default
Firefox
blocked by default

A domain-level profile describes your whole readership with one method — because it never depended on the identifier in the first place.

Three sales motions

What publisher teams actually do with the data

The same domain file feeds three distinct revenue workflows — each with its own dedicated guide.

Pitch decks with coded evidence

Replace media-kit adjectives with vocabulary values: your readership’s age brackets, income bands, life stages, top INT.* and PI.* codes — and how each over-indexes against your named competitor set. See publisher pitch decks.

Seller-defined audience labels

SDA asks publishers to describe their own inventory in taxonomy terms. Because every attribute here is aligned with IAB Audience Taxonomy 1.1, the profile of each of your domains translates directly into SDA-style audience labels. See seller-defined audiences.

Direct-sales intelligence

Work out which advertiser categories your audience over-indexes for — purchase-intent codes are effectively a prospecting list — and arrive at the meeting knowing how you compare to every title on the buyer’s shortlist. See publisher sales intelligence.

Workflow

From domain list to sales narrative in five steps

No integration project. The dataset is a flat file you filter in a spreadsheet or warehouse — or query per-URL through the real-time API for section-level analysis of your own properties.

Pull your own profile

Look up your domains and read the coded audience attributes and resolved persona for each property or vertical site.

Pull the comp set

Look up the competitor titles you are sold against. Same fields, same vocabularies — a like-for-like comparison by construction.

Find your over-index

Identify the interests, intent segments and demographics where your audience concentrates more strongly than the comp set.

Package the story

Turn the differentiating codes into pitch-deck slides, SDA labels and direct-deal audience descriptions buyers can verify.

Refresh quarterly

Vocabularies are fixed at v1.0, so the same comparison re-runs cleanly against each quarterly data refresh.

Scale

Your title, your comps, the whole open web — one file

102Mdomains in the full corpus
$490top-100k file with full audience attributes, one-time
34purchase-intent groups — a category prospecting map
v1.0fixed vocabularies — comparisons stay stable over time
Worked example

An outdoor-lifestyle publisher pitches a camping-gear brand

An independent outdoor publisher wants a direct deal with an equipment advertiser. Here is the audience evidence its domain profile provides — codes on the left, what the buyer reads on the right.

FieldProfile value (code)Reads asConfidence
age_bracket25_34, 35_4425–44 core readershiphigh
income_levelupper_middleUpper-middle incomehigh
urbanicitysuburban, small_townSuburban and small-town skewmedium
interestINT.travel.campingCampinghigh
interestINT.travel.adventure_travelAdventure travelhigh
purchase intentPI.sporting_goods.outdoor_recreation_equipmentOutdoor recreation equipmenthigh
purchase intentPI.travel.campingCamping trips & bookingsmedium
The pitch that follows: the publisher shows the buyer that its readership carries in-market intent for exactly the advertiser’s category (PI.sporting_goods.outdoor_recreation_equipment), then places the two generalist comp titles from the agency’s plan next to it — both indexing on broad news interests but neither on outdoor equipment intent. That is a differentiated, checkable argument for a direct deal or a premium PMP, not an adjective. Explore any domain’s profile in the audience demo dashboard.
Comparison

How publishers document their audience today

 Panel measurementFirst-party surveysCookie-derived segmentsDomain-level profiles (this dataset)
Covers mid-size & niche titlesThin below the head of the marketYes, but only your own titlesSparse where cookies are blockedYes — 102M domains, head to tail
Competitor comparisonOnly for panelled competitorsNo — no competitor dataInconsistent across vendorsSame fields for every domain, yours and theirs
Safari / iOS readershipModelledCovered for respondentsLargely invisibleCovered — profile is a property of the domain
Buyer verifiabilityPanel methodologySelf-reportedVendor black boxFixed v1.0 vocabularies, published taxonomy
Cost & effortSubscriptionOngoing programmeContract-dependentFrom $490 self-serve, quarterly refresh
Scope note: these approaches are complements, not substitutes. If you run a first-party survey programme, domain-level profiles add the competitor half of the story. And this dataset is a planning, packaging and sales instrument — it does not claim impression-level pre-bid classification in the bidstream.
FAQ

Publishers — common questions

My domain is already in the database — can I see its profile before buying?

Yes. The demo dashboard lets you look up individual domains and inspect their audience attributes interactively. For a full comp-set analysis you would buy a tier — the top-100k file is $490 one-time, the top-1M file is $1,990 with instant checkout — or a vertical slice ($190–$490) covering your market.

How does this support seller-defined audiences (SDA)?

SDA participation requires publishers to label their inventory using standard audience taxonomy terms. Every attribute in this dataset comes from fixed v1.0 vocabularies aligned with IAB Audience Taxonomy 1.1 — demographics, interests, purchase intent and personas — so a domain’s profile maps directly onto the taxonomy IDs SDA labels are built from. You still control which labels you declare; the dataset gives you the evidence base for declaring them.

What if I disagree with the profile of one of my properties?

Every attribute carries a banded confidence value (low / medium / high), and the vocabularies are published openly on the taxonomy page, so you can see exactly what each code claims. Publishers with first-party data can treat the profile as an external, third-party view — useful precisely because it is the same view a data-driven buyer would compute about you — and contact us about discrepancies.

Does this replace my first-party data or consented audience segments?

No. First-party data is your most valuable asset and stays yours. This dataset adds what first-party data cannot: a consistent, like-for-like profile of every competitor title, and coverage of the readership you cannot observe through cookies — Safari, Firefox and iOS users, roughly 40%+ of traffic. There is no PII anywhere in the pipeline, so nothing here touches your consent posture.

Related pages

Put a documented audience in your next pitch

Look up your own domains and your comp set in the demo, or download a database tier and build the comparison this week.

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.