Strategy
Part of Planning a customer data platform decision around the data journey, not the product class
Eight customer data platforms strategy mistakes to avoid
Avoid eight observable customer data platforms strategy mistakes, from the single-view slogan to exit, with regulator-backed corrections and evidence limits.
These eight customer data platforms strategy mistakes are observable defects in a planning record, not claims about how often organisations make them.
Method: review of current UK regulator and cyber guidance against a customer-data journey. Research date: 6 September 2026. Scope: strategy for organisations operating in England; cited legal and regulator material is UK-wide. Inclusions: defects with an observable correction. Exclusions: vendor rankings, adoption claims, market forecasts and unsupported anecdotes. Ranking: non-ranked. Conflicts: no supplier funding, access or product test.
What to take away
- Start with a specific buyer decision, not a single-view slogan, and separate distinct data functions.
- Treat matching as uncertainkeep provenance, rule version, and a route to correct false matches.
- Capability does not equal permission; obtain separate privacy and PECR review for each use.
- Keep privacy, accuracy, security, accessibility, and exit as separate pass or hold gates.
- Test exit before dependence grows and record format, meaning, completeness, and deletion evidence.
1. Starting with a single-view slogan
The record names a CDP but not the buyer decision, sources, joins or output. Correction: define one recent decision and separate CRM, warehouse, identity, preference, tag, analytics, activation and managed-service functions. The ICO's data-protection principles guidance supports purpose limitation and minimisation, not indiscriminate consolidation.
2. Treating matching as truth
An inferred link becomes an unquestioned profile fact. Correction: retain provenance, rule version, uncertainty and a route for false-match correction. Test conflicting and missing identifiers with fictional records. Accuracy review cannot be replaced by a supplier confidence label.
3. Reading capability as permission
A plan assumes that because a service can ingest a tag identifier or activate an audience, the use is permitted. Correction: inventory the purpose and operation, then obtain a separate qualified privacy review and a PECR (Privacy and Electronic Communications Regulations 2003) review. The ICO's storage and access technologies guidance covers more than cookies and requires attention to the actual technology.
4. Assigning roles by contract heading
The diagram calls every supplier a processor without recording who decides purposes and essential means. Correction: map each activity and decision. The ICO's controllers and processors guidance makes the factual arrangement central.
5. Averaging away a failed gate
A low cost or polished interface offsets missing suppression, accessibility or security evidence in a combined score. Correction: keep privacy and PECR, accuracy and rights, security, accessibility and exit as separate pass or hold decisions. WCAG 2.2 is the benchmark for the accessibility gate and the Equality Act 2010 duty applies; public sector bodies also work to the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018. NCSC supplier assurance questions can structure requests about incidents, audit and data return but do not score a supplier.
6. Leaving exit until renewal
The plan assumes configuration, provenance and history will be portable. Correction: export and restore authorised fixtures before dependence grows, including the UK GDPR Article 20 export route for personal data the individual provided where processing rests on consent or contract. Record format, meaning, completeness, deletion evidence and continuity owner. Stop if essential evidence is trapped or the buyer cannot reproduce its decisions.
7. Mixing unlike commercial units
The plan compares a profile-based subscription with internal storage rows or a managed project fee as though they were the same price. Correction: state currency, VAT basis, unit, period, term, limits, implementation, operating labour, support and exit for every route. Leave the amount blank where the applicable record is missing. A low visible charge says nothing about whole-life cost.
8. Publishing claims ahead of evidence
The strategy promises a more accurate view, improved return or better outcomes before the buyer defines the population and test.
Correction: write the precise objective claim and the evidence it would require, including conditions and limitations. The ASA's substantiation guidance states objective claims capable of substantiation should be supported before publication. A technical demonstration cannot substantiate a live commercial result.
Review each correction against a dated journey version. A changed purpose, source, join, destination or subprocessor should reopen the relevant gate. The absence of a defect in the document does not prove lawful or successful operation; it only makes the next test more accountable.
Before you act
- Define one recent buyer decision and separate data functions.
- Retain provenance, rule version, and uncertainty for matches.
- Inventory purpose and operation, then obtain privacy and PECR review.
- Map each activity and decision to controller or processor roles.
- Keep privacy, accuracy, security, accessibility, and exit as separate gates.
- Export and restore authorised fixtures before dependence grows.
- State currency, VAT basis, unit, period and exit for every commercial route.
- Write each objective claim and the evidence it would need before publication.
Common questions
Why is starting with a single-view slogan a mistake?
The record names a CDP but not the buyer decision, sources, joins or output. The correction is to define one recent decision and separate the data functions. The ICO's data-protection principles guidance supports purpose limitation and minimisation, not indiscriminate consolidation.
How should matching be treated in a CDP plan?
An inferred link becomes an unquestioned profile fact. The correction is to retain provenance, rule version, uncertainty and a route for false-match correction. Test conflicting and missing identifiers with fictional records. Accuracy review cannot be replaced by a supplier confidence label.
Why is leaving exit until renewal a problem?
The plan assumes configuration, provenance and history will be portable. The correction is to export and restore authorised fixtures before dependence grows. Record format, meaning, completeness, deletion evidence and continuity owner. Stop if essential evidence is trapped or the buyer cannot reproduce its decisions.
