Foundations
Part of Customer data platforms foundations for buyers
Six gates a customer data platform service must pass before market entry
Use a gated CDP market-entry checklist for England covering evidence, data authority, identity quality, security, accessibility, contracts and exit.
This checklist is for a proposed customer data platform offer aimed at organisations operating in England. It was researched on 6 September 2026. Passing one gate cannot offset failure elsewhere, and a completed checklist is not proof of legal compliance or commercial demand.
What to take away
- Passing one gate cannot offset failure elsewhere, and a completed checklist is not proof of legal compliance or commercial demand.
- A single customer view is not enough; state the source records, proposed joins, output and decision instead.
- Broad enterprise totals do not establish CDP adoption, so a market total stays on hold without direct measurement.
- A suppressed record must not be silently rebuilt from another source, and rights must be traced through every recipient.
- Stop market entry if essential authority, provenance, suppression, security, accessibility or exit evidence is missing.
1. Define the buyer job
- Name a recent customer-data decision, its owner and the evidence currently missing.
- Separate CRM, storage, identity resolution, preferences, tag management, analytics, activation, clean-room work and managed integration.
- Describe the existing manual route and why a change is being considered.
- Set an expiry date for the problem statement.
Reject a proposal framed only as obtaining a single customer view. State the source records, proposed joins, output and decision instead.
Define the buyer job
- Name decision, owner, missing evidence
- Separate CRM, storage, identity, activation
- Describe manual route and change reason
- Set expiry date for problem statement
- Reject single-customer-view framing
2. Establish evidence of a reachable market
- Choose one market unit and one England geography rule.
- Record direct evidence such as permissioned briefs, funded projects or qualifying contracts separately from interest signals.
- Publish sampling coverage, non-response and uncertainty.
- Do not use broad enterprise totals as CDP adoption.
The ONS UK business activity, size and location methodology can inform a registered-business sampling frame. It does not establish purchases, so a market total remains on hold without direct measurement.
3. Map collection and identity authority
- Inventory each source, identifier, person or organisation represented and collection authority.
- Version every deterministic and probabilistic join rule.
- Preserve provenance and uncertainty in the resulting profile.
- Test false matches, splits, stale values and missing identifiers with synthetic fixtures.
The ICO's data-protection principles guidance is a UK-wide starting point for purpose limitation, minimisation, accuracy, storage limitation and security. A named privacy reviewer must apply it to the actual design rather than approve a generic platform category.
4. Trace choices and rights
- Keep research participation, data collection, device access and later marketing permission distinct.
- Trace correction, objection, suppression, restriction and deletion through every recipient and copy.
- Prevent a suppressed record from being silently rebuilt from another source.
- Log exceptions, authority and completion evidence.
The ICO's individual-rights guidance frames the rights questions. Where tags or similar technologies are involved, separately consult the ICO's storage and access technologies guidance.
5. Require security and accessibility evidence
- Define least-privilege roles, service accounts, logs and access review.
- Rehearse incident containment and recovery with authorised fixtures.
- Identify supplier and subprocessor access, including support routes.
- Test critical administration, review and export tasks for accessibility.
The NCSC's supplier assurance questions supports a structured evidence request but is not a supplier approval. Accessibility findings must relate to the configured tasks, not a badge or generic statement.
6. Fix the commercial and exit record
- Identify the legal entity, exact service, edition, scope and data roles.
- Record charging unit, currency, VAT status, term, overages and buyer labour.
- Define acceptance, change control, support, incident duties and liability review.
- Export and restore a usable sample before operational dependence.
- Require deletion evidence and continuity ownership at termination.
Stop market entry if essential authority, provenance, suppression, security, accessibility or exit evidence is missing. The appropriate next step is a reversible synthetic test against the manual baseline, with blank thresholds set by the buyer and independent reviewers before use.
Date every gate and name the person who can reopen it. A change in purpose, data source, identity rule, destination, supplier access or ownership invalidates the affected decision until fresh evidence is reviewed.
Before you act
- Name the buyer job and set an expiry date for the problem statement.
- Separate direct evidence from interest signals and publish sampling uncertainty.
- Version every join rule and preserve provenance and uncertainty in profiles.
- Trace correction, objection, suppression, restriction and deletion through every recipient.
- Rehearse incident containment and test critical tasks for accessibility.
- Export and restore a usable sample before operational dependence.
Common questions
What evidence does the article require before a market total can be stated?
It says to choose one market unit and one England geography rule, and to record direct evidence such as permissioned briefs, funded projects or qualifying contracts separately from interest signals. The ONS methodology can inform a registered-business sampling frame, but it does not establish purchases, so a market total remains on hold without direct measurement.
How should identity joins be handled under this checklist?
Inventory each source, identifier, person or organisation represented and collection authority. Version every deterministic and probabilistic join rule, and preserve provenance and uncertainty in the resulting profile. Test false matches, splits, stale values and missing identifiers with synthetic fixtures, and have a named privacy reviewer apply the ICO principles to the actual design.
What should happen if essential evidence is missing at market entry?
You should halt market entry. Without proof covering authority, provenance, suppression, security, accessibility or exit, the proposal cannot proceed.
