CRM glossary
Data contract
Also called: schema contract, producer contract
A data contract is an explicit agreement between whoever produces a dataset or event and whoever consumes it, covering field names, types, meaning, freshness and what counts as a breaking change. Lifecycle teams need them because a silent rename in a checkout event kills a triggered campaign without raising an error anywhere. To work, the contract has to be enforced in the producer's own pipeline, tested automatically and able to block a release. Otherwise it is documentation that everyone quietly drifts from.
Articles using this term · 7
- Snowflake, CDP and the experience layer: a conversation between Zeotap and Glassjaw · 28 September 2026
- Handing a CRM programme back to an in-house team · 22 September 2026
- A segmentation framework your team can actually maintain · 9 June 2026
- Briefing a CRM agency: what to hand over on day one · 18 April 2026
- Data contracts between marketing and engineering · 24 February 2026
- Migrating engagement platforms without a dark month · 13 January 2026
- Pruning the segments nobody uses · 20 January 2025