What is a best practice for designing a Real-Time Customer Profile in Adobe RT-CDP?

Question

Options

• AAvoid creating identity namespaces for customer data.
• BCreate a unified schema to include all data types and relationships.
• CSegment data into multiple unrelated schemas.
• DAvoid enabling datasets for profile use.

• A
  3% (1)
• B
  83% (24)
• C
  10% (3)
• D
  3% (1)

Explanation

Creating a unified schema (B) is correct because RT-CDP's Real-Time Customer Profile is built by stitching together data from multiple sources into a single, coherent view of the customer - this requires a well-designed schema that captures all relevant data types and their relationships under the XDM (Experience Data Model) framework.

Why the distractors fail:

• A is the opposite of best practice - identity namespaces (e.g., email, ECID, CRM ID) are essential for identity resolution and merging records into a unified profile.
• C contradicts the core goal of RT-CDP; fragmented, unrelated schemas prevent the platform from joining customer data into a single profile view.
• D is self-defeating - datasets must be enabled for Profile ingestion, otherwise their data never contributes to the Real-Time Customer Profile at all.

Memory tip: Think "U for Unified = U for User (customer)" - the entire point of RT-CDP is one unified profile per customer, so every design decision should support unification, not fragment it.

No community discussion yet for this question.