Integration guide

Customer data platform (CDP) integration guide

This customer data platform (CDP) integration guide helps data engineers plan warehouse, stream and activation connections. Choose one source and destination, obtain the supported contracts, and test identity, consent, retries and deletion before expanding.

Request an architecture review Review Enterprise TCO Model →

Start with one source and one destination

Write the intended business action and the evidence that would show it worked. Draw the path through ingestion, identity, profiles, permissions and the selected destination. Include the party that operates each step, support access and failure recovery. This public guide describes that planning process; it does not claim a fixed connector count, GraphQL support, an event tier or a production SLA.

Workflow categories

Contracts to verify before implementation

Request supported schemas, authentication and limits for the selected release. A category name does not establish that every vendor connector is available.

Warehouses and lakehouses

Identify the required tables or views, permitted fields, change detection, query ownership and freshness expectation. Confirm supported access for the chosen release and test the actual extraction path.

Streams and batch events

Define event IDs, source timestamps, schema versions, validation errors and replay ownership. Measure ordering, duplicate handling and recovery with a bounded synthetic workload.

Identity and consent systems

List identifiers, matching rules and conflict behavior. Test a changed identifier, merged record and withdrawn permission so identity updates cannot silently restore an unauthorized use.

Activation and reverse ETL

Agree the destination contract, allowed payload and suppression behavior. Inspect actual delivery and reconciliation; an accepted request is not proof of a final user-facing effect.

What is public and what needs a release contract

The API and MCP checklist describes contracts to request. Obtain the endpoint schema, authentication, rate and batch limits, error semantics and supported connector version before writing production code. Confirm document availability and any confidentiality terms in the review. The legacy integration page is superseded; no unsupported certification, uptime or dashboard-key claim has been carried forward.

What to prepare for an integration review

Bring a synthetic payload, identifier rules, consent states, measured workload assumptions and the owners of both endpoints. Describe a failed or delayed destination and how you expect retries to behave. Agree an acceptance test that checks the resulting profile, restriction and delivered payload, with retained evidence. Use the shared evaluation checklist for the wider architecture and cost review.

For an email activation workflow, read MailOps: authentication and delivery evidence. Verify provider acceptance, inbox placement and customer response as separate observations.

Discuss your deployment with engineers.

Bring your data flow, operating owners and evaluation questions.

Request an architecture review Review Enterprise TCO Model →Request permissioned references and release-specific evidence during evaluation.