Your CDP's Identity Resolution Posture Is a Strategic Choice, Not a Feature Checkbox

Angle

Identity resolution — stitching disparate identifiers into a unified customer profile — is the foundational prerequisite for any cross-session or cross-modality activation. The choice between a packaged platform's ID graph and a CDW-native build isn't just an engineering decision; it determines match rate, GDPR deletion propagation behavior, and resilience to cookie deprecation and Apple ATT. Most organizations inherit their identity resolution posture as a side effect of their CDP architecture choice, rather than choosing the identity posture explicitly. The article helps readers ask the right questions before that happens.

Key decision this helps with

What are the identity resolution implications of choosing packaged vs. composable CDP architecture, and how do those implications interact with cookie deprecation, mobile privacy changes, and right-to-erasure requirements?

Tradeoffs the article will map

• Packaged CDP ID graph (vendor-managed matching rules, turnkey GDPR deletion pipeline, but matching policies are vendor-constrained and opaque to the customer) vs. CDW-native identity build (full control over matching logic, but match rate depends on data engineering investment and starts below packaged baselines)
• Probabilistic identity matching (higher match rate, more privacy-risk surface) vs. deterministic-only matching (lower match rate, more appropriate for regulated industries)
• Centralized identity graph (simpler to govern, single point of failure) vs. distributed identity resolution across CDW and packaged CDP (more resilient, harder to keep consistent)

Open questions / uncertainties

• Third-party cookie deprecation timelines continue to shift — the article should frame guidance around architectural resilience patterns rather than any specific deadline
• Match rate baselines vary too widely by industry, data maturity, and channel mix to cite representative numbers — the article should frame match rate as a variable the reader must measure in their own environment, not a benchmark to compare against
• Apple ATT opt-in rates are platform-reported and subject to change with iOS updates; no authoritative third-party measurement of population-level opt-in rates exists

Knowledge-graph nodes this draws from

• vendor.adobe-experience-platform
• vendor.snowflake
• vendor.databricks
• concept.data-liquidity
• concept.modality-complexity