network, edp, plug, patch cord, data cable, rj45, ethernet, copper, lan, switch, router, hardware, data, dsl, internet, web, connection, connected, network, network, network, ethernet, ethernet, lan, lan, switch, switch, router, router, router, router, router, hardware, data
Photo by Bru-nO on Pixabay

Tools and providers

Assessing customer data platform tools and suppliers with dossiers, fixtures and exit gates

Assess CDP tools and supplier routes for one England data journey using verified dossiers, controlled fictional-data tests and firm exit gates.

Editorial Desk · · 10 min read

What to take away

  • Define one buyer-owned data journey and prove an exact service can support it before choosing a customer data platform.
  • A category label, demonstration, certification badge or contract heading does not establish that a service can do the job.
  • Test the exact legal entity, edition and configuration against the buyer's privacy, security, accessibility, commercial and exit constraints.
  • Non-compensating gates such as rights routes, accessibility and export sit outside any weighted score.
  • A controlled fictional-data test shows only that configuration's behaviour with that fixture, not legality or production scale.
  • Named routes such as Salesforce Data Cloud, Adobe Real-Time CDP, Twilio Segment, Tealium AudienceStream and Treasure Data still need edition-level dossiers.

Name the job before the product class

A CDP procurement can drift because several unlike functions appear under similar marketing labels. Record which functions are actually required:

CDP functions versus marketing labels

Function

CRM
Operational relationship records
Warehouse or lake
Stores and transforms broader data
Identity resolution
Proposes or applies record links
Consent management
Records choices and evidence
Tag management
Controls code or data collection
Activation
Sends audience or instruction onward

What it actually does

CRM
Warehouse or lake
Identity resolution
Consent management
Tag management
Activation

Name the job

  • CRM holds operational relationship records and staff activity;
  • a warehouse or lake stores and transforms broader data under buyer-defined architecture;
  • identity resolution proposes or applies links between records;
  • consent or preference management records choices and related evidence;
  • tag management controls code or data collection on digital properties;
  • analytics describes events and outcomes;
  • activation sends an audience or instruction to another service;
  • a clean room supports bounded analysis between participants; and
  • managed integration supplies people and operating work as well as technology.

A service may cover several functions, but the supplier must evidence each for the exact edition. A preference flag is not proof of a valid choice, and an identity score is not a verified identity.

Public CDP tools and suppliers include Salesforce Data Cloud, Adobe Real-Time CDP, Twilio Segment, Tealium AudienceStream and Treasure Data. Other named routes include BlueConic, Amperity, Ometria and Hightouch.

Salesforce Data Cloud is part of Salesforce Customer 360. Adobe Real-Time CDP is part of Adobe Experience Platform. Twilio Segment publishes a free tier and paid plans priced by monthly tracked users. Tealium AudienceStream sits within Tealium's tag management and event data platform. Treasure Data sells an enterprise CDP and has a London office.

BlueConic is a standalone CDP for marketing profiles and segments. Amperity targets retail and consumer brands. Ometria is a London-based retail marketing platform with CDP features. Hightouch is a composable CDP that syncs warehouse data to destinations. mParticle covers mobile and web event collection.

ICO guidance on data protection by design and default makes the buyer's processing decisions part of the assessment throughout the lifecycle. It does not confer approval on a product.

Write a journey card

One-page journey card fields

  • England operating entity and decision owner
  • Affected population and business purpose
  • Permitted sources and expected events
  • Identifiers, proposed joins and profile fields
  • Inferences, destinations and deletion point
  • Provenance and accountable owner per field

For the fictional retail case, an input might be an authorised account reference or a synthetic transaction event. A matching test can include deliberate ambiguity, duplicates and contradictory dates. The expected output is not a universal customer view. It is a versioned result that exposes the rule used, its uncertainty and any record withheld from joining.

A Salesforce Data Cloud dossier should name the exact Data Cloud edition and the identity resolution ruleset. An Adobe Real-Time CDP dossier should name the profile store, dataset and destination configuration. A Twilio Segment dossier should name the workspace, source and destination settings.

Map technology that stores information on or accesses a user's device separately. The ICO's final storage and access technologies guidance was updated on 29 April 2026 following changes to PECR. A tag or connector being available does not establish that its configured use is permitted.

Build the admission dossier

Procurement should request evidence for one legal supplier and one service or edition, dated and scoped to UK availability. A general corporate page cannot fill edition-level gaps. The dossier needs:

  • input types, collection mechanism and buyer authority assumptions;
  • identifier format, matching logic, confidence handling and manual correction route;
  • treatment of derived profiles, inferred fields and conflicts;
  • actual controller, processor or joint decision-making activities;
  • subprocessors, access locations and restricted-transfer information;
  • role permissions, authentication, activity logs, incident support and recovery;
  • accessibility evidence for administrator tasks, reports and exports;
  • service scope, commercial unit, support, change process and acceptance terms; and
  • export format, deletion process, transition help and failure continuity.

For Salesforce Data Cloud, ask for the edition, Data Cloud credits, region and identity resolution rules. For Adobe Real-Time CDP, ask for the Experience Platform sandbox, dataset and destination design. For Treasure Data, ask for the UK entity, processing region and usage unit. For BlueConic, ask for the hosting region, profile unit and export format.

The ICO explains that controller and processor status follows actual decisions about purposes and means. Procurement should therefore test the service description and configuration, rather than accepting a label in a data processing addendum.

For overseas access, trace actual recipient entities and processing locations. The ICO's international transfers material is the appropriate UK regulator starting point. A region selector, hosting statement or UK sales address does not by itself answer that assessment.

Compare routes, not slogans: manual process, hosted CDP tools and managed integration

At least five routes may deserve consideration: retain the current manual process, configure existing approved systems, build a buyer-controlled service, license a hosted product, or appoint a managed integrator. Compare them against the same journey, input volume unit, operating period and evidence date. Leave costs blank where the commercial unit, currency, VAT status, term or usage assumption is missing.

The manual route matters: it may expose slow or fragile work, yet it shows which staff decisions, corrections and exception paths automation must preserve.

A hosted product may reduce build work while adding supplier change and exit dependencies. A buyer-built route can increase control but transfers maintenance and security work to the buyer. Managed integration can combine these dependencies rather than remove them.

Hosted CDP tools include Salesforce Data Cloud, Adobe Real-Time CDP, Twilio Segment, Tealium AudienceStream and Treasure Data. BlueConic and Amperity also offer hosted CDP routes.

Salesforce Data Cloud is sold through Customer 360 editions and credits. Adobe Real-Time CDP is quote-based and usually priced by profiles or volume. Twilio Segment lists a free tier and paid plans by monthly tracked users. Tealium AudienceStream and Treasure Data are quote-based. BlueConic and Amperity do not publish list prices.

Hightouch and mParticle offer composable or event-based routes. Hightouch syncs warehouse data to destinations and publishes a free tier. mParticle collects mobile and web events. A managed integrator may assemble these tools, but the buyer still needs the same dossier and exit evidence.

Non-compensating gates sit outside any weighted score. A high functional score cannot cancel an unacceptable rights route, inaccessible task, uncontrolled privileged access or unusable export. The UK National Cyber Security Centre's SaaS security guidance covers onboarding and offboarding, privileged access, monitoring, incident preparation and recovery. Those are buyer configuration duties as well as supplier questions.

Run one controlled fictional-data test

Use no live customer records. Prepare a versioned fixture with fictional identities and authorised system events. Include:

Controlled fictional-data test

  • two records that look similar but must remain separate;
  • a confirmed duplicate with evidence for the intended merge;
  • a stale address and a newer correction;
  • conflicting attributes with no safe automatic winner;
  • an objection and a suppression state;
  • a deletion request routed across connected stores;
  • refused tracking or device access;
  • a user whose privileged access is removed;
  • a suspicious configuration event for log inspection; and
  • an export followed by a restore into an isolated environment.

Declare the expected state for each item before running it. Capture configuration version, operator and timestamps. Record logs, observed output, unresolved difference and rollback evidence. Passing demonstrates only that configuration's behaviour with that fixture. It says nothing about legality, production scale, accuracy for other populations or supplier performance.

A Salesforce Data Cloud fixture should test its identity resolution ruleset and profile merge. An Adobe Real-Time CDP fixture should test dataset joins and destination exports. A Twilio Segment fixture should test source payloads and destination filters. A Tealium AudienceStream fixture should test event rules and audience connectors. A Treasure Data fixture should test identity resolution and export jobs.

The ICO's guide to individual rights is marked under review following the Data (Use and Access) Act. It identifies rectification, erasure, restriction, portability and objection as distinct rights. Publication-day review is needed before converting the fictional test into an operational rights procedure.

Test security and accessibility as work

Ask a security reviewer to inspect administrative separation, service identities and authentication. The review should cover permission changes, protected logs, incident contacts and recovery evidence. The NCSC's supplier assurance questions provide prompts about supplier networks, privileged access and cloud dependencies. They are questions, not a certification scheme.

Accessibility evidence must cover the configured buyer tasks. Ask users of relevant assistive technology, or suitably qualified testers, to complete correction review, audience exclusion and approval, then cover export and error recovery.

Public-sector buyers have extra statutory requirements in the government's accessibility requirements guidance, which refers to WCAG 2.2 AA and procurement. Other organisations need fact-specific equality and accessibility review. Treat a supplier accessibility statement as evidence to examine, not a blanket verdict.

For Salesforce Data Cloud, ask for the trust and compliance package and the edition's accessibility conformance report. For Adobe Real-Time CDP, ask for the Experience Platform security documentation and VPAT. For Twilio Segment, ask for the workspace roles, audit logs and subprocessor list. For BlueConic, ask for hosting region, roles and export controls.

Contract around operation and exit

Confirm the contracting entity and exact schedule covering the selected service. Record the pricing unit without guessing. Profiles, events and storage may be counted differently. Destinations, users, environments and support may also be counted differently. Capture currency, VAT treatment and period separately. Record renewal, overage, change rights and buyer labour.

Salesforce Data Cloud uses credits and editions. Adobe Real-Time CDP pricing is quote-based by profiles or volume. Twilio Segment lists a free tier and paid plans by monthly tracked users. Treasure Data and Tealium AudienceStream are quote-based. Ask for the UK contracting entity, VAT treatment and exit format for each.

Where the arrangement is controller to processor, ICO contract guidance describes required topics. These include instructions, confidentiality, security and subprocessors. They also cover rights assistance, audits and end-of-contract provisions. The page is under review after the 2025 Act, and it is not a guide to commercial negotiation.

Exit evidence should be practical. Export the fictional fixture, its identifiers, suppression states, provenance and relevant logs in the proposed format. Restore them away from the supplier. Then obtain a deletion record for the service and known copies, subject to correctly reviewed retention obligations. If the buyer cannot rebuild a usable state, portability remains unproved.

For Salesforce Data Cloud, test Data Cloud export and deletion. For Adobe Real-Time CDP, test dataset and profile export from Experience Platform. For Twilio Segment, test destination replay and source deletion. For BlueConic, test profile export and deletion. For Treasure Data, test job export and account deletion.

Make the decision traceable

The decision paper should identify admitted routes, rejected routes and open questions. For each gate, record evidence, owner, review date, expiry and authority to stop. Keep the legal, privacy and PECR review separate from security, accessibility, commercial and data-governance judgements.

A conditional selection needs a dossier complete enough for qualified reviewers and a controlled test meeting its predeclared results. Otherwise, retain the current route, narrow the journey or request missing evidence.

Before any production activation, refresh supplier documents and regulator guidance, approve the real data map, repeat the test in the final configuration and prove rollback. This article cannot make that release decision.

Before you act

  • Name the job before the product class.
  • Write a one-page journey card with provenance and owners.
  • Build an admission dossier for one legal supplier and edition.
  • Compare routes against the same journey and evidence date.
  • Run one controlled test using fictional data only.
  • Test security and accessibility as buyer work.

Common questions

Which CDP tools and suppliers does this cover?

It names Salesforce Data Cloud, Adobe Real-Time CDP, Twilio Segment, Tealium AudienceStream, Treasure Data, BlueConic, Amperity, Ometria and Hightouch. The same dossier, fixture and exit gate tests apply to each. Public facts only.

What should a journey card record?

It should name the England operating entity, decision owner and affected population. It should also cover business purpose, permitted sources and expected events. Identifiers, proposed joins, profile fields, inferences, destinations and deletion point belong there too. Every field should link to provenance and an accountable owner, and it should fit on one controlled page.

Why does the manual route matter in a comparison?

The manual route may expose slow or fragile work, but it also shows which staff decisions, corrections and exception paths automation must preserve. It is one of at least five routes to compare against the same journey, input volume unit, operating period and evidence date.

What does a passing fictional-data test prove?

Passing demonstrates only that configuration's behaviour with that fixture. It says nothing about legality, production scale, accuracy for other populations or supplier performance. Capture configuration version, operator, timestamps, logs and observed output, plus any unresolved difference and rollback evidence. Declare expected states before running each item.

In this guide

  1. Selecting customer data platform software on an edition-specific dossier and one fixtureSelect CDP software for one England data journey through an exact-edition evidence dossier, independent gates and a predeclared fictional-record test.
  2. Manual, existing, built, hosted or managed: five customer data platform routes on common fieldsCompare manual, existing, buyer-built, hosted and managed CDP routes for one England journey using common evidence fields, units and tested exit evidence.
  3. Customer data platform vendor due diligence as an evidence dossier, not a scorecardBuild a CDP supplier evidence dossier covering identity, data roles, security, accessibility, commercial scope and tested exit without using scores.
  4. Running a reversible customer data platform implementation as a logged sequenceRun a customer data platform implementation as a logged reversible sequence: freeze the journey, set expected states, test correction, revoke access, roll back.
Filed undercustomer data platforms tools and providers

More in Tools and providers