Manual, existing, built, hosted or managed: five customer data platform routes on common fields

Manual, existing, built, hosted or managed: the five customer data platform routes are compared here on one fictional England retail journey and one set of common evidence fields. Each route receives authorised events, handles uncertain identity links, preserves correction and suppression, and exports a bounded audience only after separate approval.

Named starting points keep the comparison concrete. Manual work runs on Shopify or EPOS CSV exports and Excel. Existing systems usually mean HubSpot or Salesforce Sales Cloud.

Buyer-built stacks pair Snowplow with dbt, and may add Hightouch or Census. Hosted routes include Twilio Segment, Adobe Real-Time CDP, Salesforce Data Cloud and Treasure Data. Managed delivery comes from integrators such as Accenture Song, Deloitte Digital or Merkle.

CRM, warehouse, consent management, analytics and activation stay separate functions even when one supplier packages them together. This desk comparison was prepared on 6 September 2026 for organisations operating in England. It names suppliers as market examples. No product was tested or ranked, and there is no winner. Supplier interviews and contract reviews were not performed either.

What to take away

The common case and units

Use the same fictional event set, input schema, eligible records, reporting period and Europe/London clock for every route. Record capacity in the charging unit the supplier actually uses, not a converted figure.

Compare each route on function, legal entity, data role and buyer work. Commercial unit, permission boundary, security evidence and accessibility follow. Export and exit complete the field set. The three criteria that separate the routes are the buyer job, the control arrangement and the evidence for exit.

Twilio Segment counts monthly tracked users. Adobe Real-Time CDP and BlueConic count profiles. Treasure Data bills on events or rows. Salesforce Data Cloud sells credits, and Microsoft Dynamics 365 Customer Insights charges per tenant per month.

The baseline is the buyer's current manual process. The other four routes are an existing approved system, a buyer-built service, a licensed hosted product and managed integration.

Exact current editions, legal entities and controlled-test evidence were not supplied. Every figure above is a labelled market range, not a quote.

For the manual baseline, UK contract rates as of 2026 run about £250 to £450 a day for an analyst and about £400 to £700 a day for a data engineer. Managed integration senior data staff typically run £700 to £1,200 a day.

Snowplow Community Edition is free to self-host. Hightouch and Census paid plans typically start at a few hundred pounds a month. Enterprise list prices typically run from five to six figures a year.

Which route fits which buyer

For a bounded decision, the manual baseline may be enough. Where no platform engineers are available, a licensed hosted service such as Twilio Segment suits self-serve setup. For an existing CRM estate, Salesforce Data Cloud or Adobe Real-Time CDP fit.

Buyer-built routes suit teams with platform engineers who can run code, infrastructure and controls. Managed integration services design or operate a defined data journey, sometimes with third-party technology from Adobe, Salesforce or Segment.

What exits with each route

Typical exportable and non-exportable items differ by route.

The manual baseline typically exports working extracts, joins and outputs for a successor operator. Local macros, undocumented exceptions and deleted working copies are not typically exportable.

A licensed hosted service typically exports configured settings, source mappings and exported records. Vendor proprietary transformation logic, historical raw events and workspace permissions are not.

A buyer-built route typically exports code, infrastructure definitions, lineage and logs held in buyer repositories. Managed services, proprietary connectors and prior runtime state that depend on vendor support are not.

A managed integration service typically exports mappings, documentation and reusable artefacts if handover is agreed. Bespoke transformations, embedded third-party licences and provider know-how are not.

Compare actual responsibility

A hosted route does not transfer the buyer's decisions to the supplier by default. A managed provider is not automatically a processor. The ICO's controllers and processors guidance ties roles to factual control over purposes and means. Write down who chooses sources, join rules, profile fields, destinations and retention for each route.

Twilio Segment and Adobe Real-Time CDP process personal data on the buyer's instructions under standard terms. Salesforce, Adobe and Microsoft publish data processing addenda and subprocessor lists. The buyer still owns the join rules and the retention decision.

Where a processor relationship exists, the ICO's contracts guidance identifies areas including instructions, security, subprocessors and assistance. Audit rights and end-of-contract treatment are covered there too.

That page is under review following the 2025 data legislation. Commercial matters still need separate legal and procurement analysis.

Run an identical behaviour test

Predeclare expected outputs and forbidden changes. Capture version, operator, log evidence and exception handling. A route that hides uncertainty or drops suppression on export fails the relevant gate, regardless of convenience elsewhere.

For security, use the NCSC's SaaS guidance to examine access removal, service identities, monitoring, incident planning and recovery. Apply the questions to the actual configuration; a supplier's general security material is not equivalent to observed buyer controls.

Keep hard gates outside the comparison score

Privacy and PECR, identity accuracy and rights, security: separate pass conditions, as are accessibility, contract authority and exit. Weights, performance thresholds, prices and service levels stay blank until buyer evidence supports them.

Select a route only when qualified reviewers accept their own gates and the common fixture passes. Otherwise the comparison shows HOLD and names the next missing record, never a numerical winner.

Before you act

Common questions

What is the baseline for comparing customer data platform routes?

The baseline is the buyer's current manual process, often Shopify exports worked in Excel. The other four routes are an existing approved system such as HubSpot, a buyer-built service such as Snowplow with dbt, a licensed hosted product such as Twilio Segment, and a managed service from an integrator.

Each route must expose the same evidence fields: function boundary, buyer work, external dependency, commercial unit and exit proof.

How should a buyer test identity handling and suppression across routes?

Feed each admitted route fictional records with a plausible false match, a supported duplicate and conflicting dates. Add a corrected attribute, an objection, suppression and a deletion state. Predeclare expected outputs and forbidden changes. A route that hides uncertainty or drops suppression on export fails the gate.

When should a route be selected according to the article?

Select a route only when qualified reviewers accept their own gates and the common fixture passes. Otherwise the comparison shows HOLD and identifies the next missing record rather than manufacturing a numerical winner. Privacy, security and exit remain separate pass conditions.