Your product already handles domains: competitor sites in an SEO report, sender and referrer domains in an analytics view, publisher domains in a planning tool, company websites in an enrichment flow. A data licensing agreement puts a 102M-domain audience database behind those surfaces — demographics, interests, purchase intent, B2B firmographics and 1,667 personas per domain, every value an enumerated code from fixed vocabularies aligned with the IAB Audience Taxonomy 1.1. Your customers see a new audience panel in your product; you ship it without building a classification pipeline, and without touching personal data.
Anywhere your product renders a domain, it can render the audience behind that domain. These are the embedding patterns we see most.
Add an "audience profile" tab to domain overview reports: who a competitor's traffic actually is, not just how much of it there is. The analytical pattern is competitor audience benchmarking, productized.
Enrich referrer and source dimensions so acquisition reports break down by audience — the in-product version of referral-traffic audience analysis, and it works on the ~40%+ of traffic where cookies are blocked.
Resolve the domain behind each contact's work email to firmographics and audience type, powering segmentation and send-time content decisions without any third-party identifier.
Let planners filter and rank domains by persona, interest codes or income band — media planning by persona as a feature of your planning UI rather than a spreadsheet exercise.
Attach audience character to domain listings and portfolios; audience quality is a pricing input, as covered in audience-based domain valuation.
Use the referring domain's audience attributes as cold-start context: route a visitor from a developer tutorial site into a technical track before any first-party history exists.
Enumerated codes, not free text — so your dropdowns, filters and legends can be generated from the vocabulary files and stay stable across refreshes. The complete code lists are published on the taxonomy page.
| Field group | Fields | Vocabulary |
|---|---|---|
| Join key | domain | Normalized registrable domain (eTLD+1) — exact-match joins against any domain column your product holds. |
| Demographics | age_bracket, gender_skew, income_level, education_level | 8 age brackets, 5-point gender skew, 6 income bands, 7 education levels. |
| Lifestyle | life_stage, household_composition, employment_status, home_ownership, urbanicity | 14 life stages plus household, employment, ownership and urbanicity enums. |
| Interests | interests | INT.* codes — 29 groups, 285 sub-interests, IAB Audience Taxonomy 1.1-aligned. |
| Purchase intent | purchase_intent | PI.* codes — 34 groups, 283 segments. |
| B2B firmographics | audience_type, b2b_company_size_employees, b2b_seniority, b2b_job_function | b2c / b2b / mixed plus LinkedIn-standard bands. |
| Personas | personas | 1,667 deterministic personas — human-readable labels ready for UI. |
| Quality | confidence, vocab_version | Banded confidence (low / medium / high) your UI can badge; explicit vocabulary versioning for release management. |
confidence band alongside the attributes — a small badge, a filter, a tooltip — is the difference between a feature customers trust and one they argue with. It also gives your support team a clean answer when a customer questions a specific domain's profile.No SDK, no tags, no rev-share plumbing — a licensed reference dataset your backend serves like any other.
Buy the Top 100k ($490) or Top 1M ($1,990, instant download) file and measure coverage against the domains your product actually renders.
Corpus size (5M up to the full 102M), refresh cadence, and the product surfaces where the data appears — quoted individually, custom licensing from $15,000/year.
Load quarterly feed files into your warehouse or key-value store, keyed by eTLD+1. Generate UI enums from the vocabulary files rather than hard-coding labels.
Route long-tail and per-URL lookups to the real-time API (audience segmentation + IAB categorization; Pro at $99/month for 10,000 credits). Same codes, so cached rows and live responses merge cleanly.
A customer of an SEO suite opens a domain overview for a personal-finance publisher they compete with. The vendor's licensed dataset renders this panel next to the traffic charts:
budget-guides.example
domain overview · audience tab · vocab v1.0
25_3435_44female_leanmiddleundergraduateyoung_familyINT.personal_financeINT.personal_finance.frugal_livingPI.finance_insuranceb2cThe suite's customer now sees not just that this competitor ranks for "budget planner", but that its audience skews young-family, middle-income, female-leaning — and can judge whether that audience is worth contesting. The vendor shipped the panel by joining one licensed table on a domain key it already displayed.
The line is simple: if your customers see the data, it's a licensing conversation.
| Model | Who sees the data | Scope | Commercials |
|---|---|---|---|
| Self-serve database tiers | Your own team | Top 100k or Top 1M domains, full attributes; vertical/country slices $190–$490 | $490 / $1,990 one-time with quarterly refresh at $190 / $590 — Top 1M is an instant card-checkout download. See pricing. |
| Data licensing (embedded) | Your customers, inside your product | 5M up to the full 102M corpus; custom enrichment and feed cadences; raw-export or syndication rights scoped explicitly | Quoted individually; custom licensing from $15,000/year. Contact us with your product surface and volumes. |
| Real-time API | Either — per your plan's terms | Audience segmentation + IAB categorization per domain or URL (planning/analysis granularity, not bid-time) | Standard API tiers, e.g. Pro $99/month for 10,000 credits. See API documentation. |
One boundary worth stating plainly: this is planning- and analysis-grade data. It powers reports, filters, scores and enrichment columns. It is not an impression-level pre-bid classification service, and licensing it does not turn your product into one — if your roadmap needs bidstream claims, this is the wrong dataset and we will say so.
The deepest embedding case: domain enrichment as a native CDP source, with trait-builder mechanics and workspace-level joins.
Firmographic and audience layers on account domains — ICP scoring and prospecting filters built on the same reference table.
The practitioner workflow behind the audience panel in the worked example — useful as a feature spec for competitive-intel products.
A data licensing agreement lets you host the audience dataset inside your own product and expose it to your customers — as an audience panel on a domain report, a filter in a prospecting tool, an enrichment column in an export. Licenses are quoted individually based on corpus size (5M domains up to the full 102M), refresh cadence and how the data surfaces in your product; custom licensing starts from $15,000/year. Self-serve tiers (Top 100k at $490, Top 1M at $1,990) are for internal use and evaluation — see the pricing page.
As flat files keyed by normalized registrable domain (eTLD+1), loadable into any warehouse or served from your own key-value store. Licensed feeds refresh quarterly by default, with custom cadences available under an agreement. Every row carries a vocab_version field, so the enumerated codes your product UI renders keep the same meaning across refreshes. The real-time API serves the same vocabularies for long-tail domains and per-URL lookups.
Embedding is the normal pattern: the data appears as a feature of your product, under your product's name, with attribution handled in the license terms. What a license does not permit by default is redistributing the raw dataset as a standalone database product. If your roadmap includes raw-data exports or downstream syndication, say so in the licensing conversation — those rights are scoped and priced explicitly.
The dataset contains no PII anywhere in the pipeline. Every attribute describes the audience a website reaches, inferred from the site's content — a property of the domain, not of any person. Your product is therefore shipping reference data about websites, not personal data: no consent surface, no identifiers, no individual-level claims. Most vendors find this materially simplifies both their own DPIA and their customers' procurement reviews.
Query real domains in the demo dashboard, prototype with a self-serve tier, then bring your product surface and volumes to a licensing conversation.