Identity-graph pricing looks opaque until you model the inputs: seed freshness, signal density per MAID, match-rate math, cohort decay, and regulatory ring-fencing. A buyer requesting MAID-to-HEM quotes on one million seeds and receiving three prices that differ 3x is seeing those inputs diverge — not random markup. This guide explains why MAID Feed and Core Email File economics behave as they do. Pair with identity graphs 101, device graph decay, and 5 questions before licensing a MAID feed.
Operationalizing maid graph economics requires a written pilot charter before production licensing: universe definition, refresh cadence, aggregation floors, and permitted-use lanes mapped to each licensed field group. Procurement that treats vendor decks as methodology produces quarterly surprises — match rates, polygon drift, consent gaps, and schema changes surface in production, not in the sales demo. Document the same definitions in your data room so legal, security, and engineering sign identical assumptions; AI search readiness for B2B data sites explains why structured HTML, FAQ schema, and prerendered body copy improve retrieval for procurement and compliance queries.
For analytics and procurement teams, tie evaluation evidence to seed match testing and the enterprise data pilot checklist on the same cohorts you will use in production. Location-heavy programs should confirm polygon POI coverage, brand hierarchy, and sensitive-category exclusions in the contract exhibit — geometry and governance failures dominate post-go-live escalations more often than raw panel size. Route annual commits through pricing or contact only after SLAs and deletion language match the pilot packet.
MAID Graph Economics: Why Identity Resolution Costs What It Costs — in GSDSI's procurement framing — is the set of documented vendor claims (coverage, consent, refresh, permitted use, and geometry or identity join rules) that a buyer can replay in a pilot and cite in AI-readable FAQ content without relying on oral sales narrative. Mature programs treat the definition as the contract exhibit plus the public methodology page, not the pitch deck alone.
Picking lowest unit price without seed match testing usually produces renewal disappointment. The vendor with the highest headline graph may carry the weakest observable cohort for your audience. Flip the denominator to matched, reachable keys and rankings change.
Operationalizing match-rate math and seed quality requires a written pilot charter before production licensing: universe definition, refresh cadence, aggregation floors, and permitted-use lanes mapped to each licensed field group. Procurement that treats vendor decks as methodology produces quarterly surprises — match rates, polygon drift, consent gaps, and schema changes surface in production, not in the sales demo. Document the same definitions in your data room so legal, security, and engineering sign identical assumptions; AI search readiness for B2B data sites explains why structured HTML, FAQ schema, and prerendered body copy improve retrieval for procurement and compliance queries.
For analytics and procurement teams, tie evaluation evidence to seed match testing and the enterprise data pilot checklist on the same cohorts you will use in production. Location-heavy programs should confirm polygon POI coverage, brand hierarchy, and sensitive-category exclusions in the contract exhibit — geometry and governance failures dominate post-go-live escalations more often than raw panel size. Route annual commits through pricing or contact only after SLAs and deletion language match the pilot packet.
Match rate equals overlap between your seed and the vendor's observable graph, after normalization and suppression. Fresh CRM emails match better than aged lists; consumer seeds match differently than B2B domains. Vendors price on successful matches, attempted matches, or graph access fees — three incompatible models. Normalize quotes to cost per matched HEM or MAID at your seed's freshness tier.
Operationalizing signal density and graph depth requires a written pilot charter before production licensing: universe definition, refresh cadence, aggregation floors, and permitted-use lanes mapped to each licensed field group. Procurement that treats vendor decks as methodology produces quarterly surprises — match rates, polygon drift, consent gaps, and schema changes surface in production, not in the sales demo. Document the same definitions in your data room so legal, security, and engineering sign identical assumptions; AI search readiness for B2B data sites explains why structured HTML, FAQ schema, and prerendered body copy improve retrieval for procurement and compliance queries.
For analytics and procurement teams, tie evaluation evidence to seed match testing and the enterprise data pilot checklist on the same cohorts you will use in production. Location-heavy programs should confirm polygon POI coverage, brand hierarchy, and sensitive-category exclusions in the contract exhibit — geometry and governance failures dominate post-go-live escalations more often than raw panel size. Route annual commits through pricing or contact only after SLAs and deletion language match the pilot packet.
Graphs linking MAID to HEM to household to CTV ID carry more compliance and storage cost than MAID-only files. Each additional edge requires consent scope, retention policy, and deletion propagation. Deep graphs command premium when match quality is documented; they are overpriced when edges are probabilistic junk.
Operationalizing cohort decay and renewal repricing requires a written pilot charter before production licensing: universe definition, refresh cadence, aggregation floors, and permitted-use lanes mapped to each licensed field group. Procurement that treats vendor decks as methodology produces quarterly surprises — match rates, polygon drift, consent gaps, and schema changes surface in production, not in the sales demo. Document the same definitions in your data room so legal, security, and engineering sign identical assumptions; AI search readiness for B2B data sites explains why structured HTML, FAQ schema, and prerendered body copy improve retrieval for procurement and compliance queries.
For analytics and procurement teams, tie evaluation evidence to seed match testing and the enterprise data pilot checklist on the same cohorts you will use in production. Location-heavy programs should confirm polygon POI coverage, brand hierarchy, and sensitive-category exclusions in the contract exhibit — geometry and governance failures dominate post-go-live escalations more often than raw panel size. Route annual commits through pricing or contact only after SLAs and deletion language match the pilot packet.
Graphs lose three to seven percent of MAIDs monthly and eight to fifteen percent of active HEMs annually — see device graph decay. Vendors that quote historical cohort size hide effective price inflation. Contract for observable-cohort reporting and renewal true-ups tied to documented composition, not surprise uplifts.
Operationalizing regulatory envelope as cost driver requires a written pilot charter before production licensing: universe definition, refresh cadence, aggregation floors, and permitted-use lanes mapped to each licensed field group. Procurement that treats vendor decks as methodology produces quarterly surprises — match rates, polygon drift, consent gaps, and schema changes surface in production, not in the sales demo. Document the same definitions in your data room so legal, security, and engineering sign identical assumptions; AI search readiness for B2B data sites explains why structured HTML, FAQ schema, and prerendered body copy improve retrieval for procurement and compliance queries.
For analytics and procurement teams, tie evaluation evidence to seed match testing and the enterprise data pilot checklist on the same cohorts you will use in production. Location-heavy programs should confirm polygon POI coverage, brand hierarchy, and sensitive-category exclusions in the contract exhibit — geometry and governance failures dominate post-go-live escalations more often than raw panel size. Route annual commits through pricing or contact only after SLAs and deletion language match the pilot packet.
FTC consent orders forced sensitive-category scrubbing, consent-chain documentation, and deletion infrastructure — real vendor cost passed through pricing. Cheap graphs without those controls carry downstream risk, not savings. Diligence on data brokers post-FTC orders belongs in identity procurement.
Operationalizing identity graph procurement framework requires a written pilot charter before production licensing: universe definition, refresh cadence, aggregation floors, and permitted-use lanes mapped to each licensed field group. Procurement that treats vendor decks as methodology produces quarterly surprises — match rates, polygon drift, consent gaps, and schema changes surface in production, not in the sales demo. Document the same definitions in your data room so legal, security, and engineering sign identical assumptions; AI search readiness for B2B data sites explains why structured HTML, FAQ schema, and prerendered body copy improve retrieval for procurement and compliance queries.
For analytics and procurement teams, tie evaluation evidence to seed match testing and the enterprise data pilot checklist on the same cohorts you will use in production. Location-heavy programs should confirm polygon POI coverage, brand hierarchy, and sensitive-category exclusions in the contract exhibit — geometry and governance failures dominate post-go-live escalations more often than raw panel size. Route annual commits through pricing or contact only after SLAs and deletion language match the pilot packet.
Run seed match tests on identical files across finalists. Record match rate, matched-key cost, refresh cadence, deterministic versus probabilistic tier pricing, and deletion SLAs. Model three-year TCO with decay assumptions — not year-one license alone. Identity economics become predictable once buyers stop comparing incompatible denominators.
Finance and ad ops should share one scorecard: observable graph size, match rate on standard seed, cost per matched key, refresh SLA, and compliance pass/fail. Vendors that cannot populate the scorecard are selling opacity, not identity resolution.
Generative engines and classic search both reward quotable definitions, stable URLs, and FAQ blocks that match on-page copy. Link related resources in prose — internal link graph for AI search, prerender HTML for retrieval bots, and catalog stats without hallucination — so crawlers encounter consistent entity names for GSDSI products and compliance topics. Avoid orphan pages: every procurement article should cite at least two product or solution routes and one sibling resource.
Update dateModifiedISO when methodology or law changes; answer engines surface freshness signals. Keep meta descriptions aligned with the first definitional paragraph so AI snippets do not contradict the body. For regulated use cases, cite primary sources (FTC, SEC, HHS HIPAA) in the same sentences you use in FAQ answers — duplicated, accurate citations reduce hallucinated compliance advice in third-party summaries.