Procurement stalls when legal, engineering, and finance use the same words to mean different things. A match rate in one deck is a deterministic join yield; in another it is a modeled propensity score. This guide aligns vocabulary for teams licensing MAID feeds, POI geofencing, and CTV/ACR. The canonical live index is the site data glossary; attach it to RFPs so definitions stay linked to product pages and survive security review. Procurement and marketing teams should keep public product claims aligned with tested specs — see AI search readiness for B2B data sites for crawl and schema discipline.
Match rate in procurement is the share of a defined seed (numerator: matched IDs above confidence threshold; denominator: seed after legal suppressions) measured on a frozen refresh week — not a vendor headline statistic without a seed.
Misaligned vocabulary costs weeks in every enterprise deal. Legal reviews permitted use against field names engineering already mapped; finance models unit economics against metrics that data science never defined. A procurement glossary is not academic — it is the contract appendix that keeps MAID, POI, ACR, match rate, and refresh cadence from diverging across teams. Link every term to a product or solution page so definitions stay tethered to what you actually license.
A MAID (mobile advertising ID) is a device-level key subject to platform reset and opt-out. A HEM (hashed email) is a privacy-preserving join key to CRM files — specify SHA-256 versus proprietary encoding. Buyers should ask for match rate by cohort (consumer versus B2B, U.S. versus international) and document refresh and decay. See identity resolution, identity graph overview, and MAID diligence. IAB Tech Lab transparency frameworks are the external reference many legal teams cite. Without cohort splits, a headline 70% match can hide 40% on the segment you actually activate.
Document confidence tiers if the vendor supplies them: deterministic versus probabilistic links should not be blended in one match-rate number. Activation teams need to know which tier they are buying so legal permitted use and technical joins stay aligned.
POI (point of interest) data should ship with polygon footprints and brand hierarchy when foot-traffic or geofencing is in scope. Mobility feeds add device paths; buyers must confirm sensitive-location exclusions align with post-FTC consent-order diligence. The location intelligence hub routes to global mobility specs and compliance checklists.
ACR (automatic content recognition) logs what played on a smart TV. Measurement teams need stable CTV IDs, dedupe rules, and a written householding assumption before tying exposures to outcomes. Pair definitions with the CTV/ACR hub and clean room joins when outcomes live in a partner environment. Reach counts households or devices with at least one exposure; frequency counts exposures — conflating them breaks pacing analysis.
Refresh cadence is how often identifiers or places are updated — a performance spec, not a footnote. Drift is meaningful change in schema, coverage, or taxonomy after go-live; monitor per drift guide. A clean room is a governed environment for hashed joins — procurement uses it for seed matches; measurement uses it for exposure→outcome studies under aggregation floors.
Attach the glossary link as an appendix and require vendors to map their field dictionary to these terms. That single step reduces rework in legal review and speeds pilot acceptance. For bake-offs, add the vendor comparison checklist and the relevant GSDSI comparisons page for your category. Finance should see TCO defined to include integration and monitoring — not license fee alone. Require vendors to flag deprecated fields six months before removal — vocabulary stability is an operational SLA.
Need a scoped sample with field definitions? Use contact and reference the glossary appendix in your thread. Include a worked example join diagram in the RFP — exposure table, identity bridge, POI outcome — so respondents cannot hide weak links behind jargon.
Engineering should not translate vendor field names ad hoc during ingest. A shared dictionary prevents silent mismatches — for example when one vendor's device_id is another's maid with different normalization. Legal can then map each field to permitted use without re-opening the schema weekly. When programs span cross-channel measurement, add exposure and outcome terms to the same appendix so CTV and store-visit stakeholders argue from one vocabulary.
Update the glossary appendix when vendors ship taxonomy changes; tie updates to drift monitoring tickets so procurement knows which contract change-notice clause applies.
Train new hires on the glossary before they join vendor calls. Misheard terms during negotiations become permanent contract definitions — especially match rate, household, and refresh cadence. A 30-minute onboarding on MAID Feed and CTV/ACR field names prevents expensive rework during ingest.
When vendors propose new fields, require a glossary diff: what changed, whether it is personal data, and which permitted use applies. Cross-channel measurement stakeholders should approve exposure and outcome field names before engineers map them to warehouse tables. Circulate glossary updates to ad ops as well as analytics — trafficking mistakes are often vocabulary mistakes.
Seasoned procurement leads keep a term dispute log: phrases that caused rework, with the resolved definition and date. That log becomes appendix B on the next RFP and shortens legal review. Link disputes to product pages — MAID Feed versus generic device ID is a recurring example. Dispute logs are especially valuable when vendors rename fields without changing semantics — the log prevents your warehouse from silently diverging from contract language. Share the log with vendor success managers so responses stay aligned during renewals. Review the log quarterly even when no active RFP is open.
Circulate glossary updates to ad ops and analytics when vendors rename fields — trafficking mistakes are often vocabulary mistakes.
Attach the live glossary and this resource hub to every identity or location RFP; AI search readiness for B2B data sites explains why consistent field names reduce both warehouse bugs and mis-citations in AI-generated diligence summaries.