What is the primary consideration when designing identity relationships for modeling in Adobe RT- CDP?

Question

Options

• AUse one-to-one relationships exclusively.
• BEnsure all identities are linked to a primary namespace.
• CAvoid using secondary identity relationships.
• DDisable deterministic identity resolution.

• A
  8% (1)
• B
  69% (9)
• C
  15% (2)
• D
  8% (1)

Explanation

In Adobe RT-CDP, identity graphs function by anchoring all collected identifiers (email, ECID, loyalty IDs, etc.) to a primary namespace, which acts as the unifying hub that links disparate identities into a single customer profile - without this anchor, the system cannot reliably stitch records together across channels.

• A is wrong because real-world identity graphs require many-to-one and many-to-many relationships; a customer may have multiple emails, devices, and cookies that all need to converge.
• C is wrong because secondary identity relationships are essential - they are precisely what feeds additional signals into the graph and enriches the unified profile.
• D is wrong because deterministic resolution (matching on exact, known identifiers like hashed email) is a core strength of RT-CDP and should never be disabled; disabling it would undermine profile accuracy.

Memory tip: Think of the primary namespace as the "spine" of a book - all pages (secondary identities) must be bound to it, or the book falls apart. If identities aren't linked to a primary namespace, there's no unified story to tell.

No community discussion yet for this question.