Data Dictionary Overview: Fields, Joins, Delivery

Buyer-facing data dictionary overview for GSDSI feeds: field structure, join keys, refresh cadence, and delivery formats. Request a field-level dictionary pack.

Field-level documentation for enterprise evaluation

GSDSI data dictionary packs explain how feeds are structured before a matched-sample pilot lands in your warehouse. Buyers use them to confirm join keys, refresh cadence, partition conventions, and schema stability, the same artifacts procurement cites in RFP annexes.

What a dictionary pack includes

  • Field names, types, nullability, and sample value ranges.
  • Entity keys and recommended join paths (MAID, HEM, household, POI ID, ticker mapping).
  • Refresh cadence, change-delta expectations, and delivery manifests.
  • Format notes for Parquet partitioning, CSV delimiters, JSON Lines, Snowflake shares, and SFTP batches.

What to validate during a pilot

  • Join yield on your own seed segmented by geography and cohort.
  • Accuracy floors, dedupe rules, and sensitive-category exclusions.
  • Schema stability across at least two delivery cycles.
  • Alignment between dictionary fields and your activation or measurement stack.

Related feeds and hubs

Start from the product catalog, identity resolution buying guide, location intelligence hub, and sourcing methodology. Request a scoped pack via contact or the sales toolkit.

FAQ

What is included in a GSDSI data dictionary pack?
A dictionary pack documents field names, types, nullability, entity keys, recommended join paths, refresh cadence, partition conventions, and delivery manifests for the feeds in scope. Enterprise buyers use it to wire warehouse schemas and QA scripts before production.
Which join keys are most common across GSDSI feeds?
Identity feeds emphasize MAID, SHA-256 HEM, household or device cluster IDs, and CTV identifiers. Location feeds pair POI IDs with mobility device hashes at privacy-safe cohort grain. Finance-oriented feeds add ticker, brand, and geography mapping columns. The pack calls out the keys required for your pilot.
How do I request field-level documentation for a pilot?
Use /contact or the Request dictionary pack CTA on this page. Specify the product families (identity, POI, mobility, CTV/ACR, clickstream, property, B2B) and delivery path (S3, SFTP, Snowflake). The solutions team typically returns a scoped pack within 2 to 3 business days after scoping.
How often do schemas change?
Core identity and POI schemas are versioned with backward-compatible change logs. Breaking changes require notice per contract. Pilots should include a schema-stability checklist and a sample change-delta file when available.
Where does provenance documentation live?
Pair the dictionary pack with /sourcing-methodology for source categories and exclusions, and /trust/sub-processors for hosted processing. Executable permitted-use language remains in the signed order or data processing addendum.