A financial services firm uses Adobe RT-CDP to unify customer data from multiple sources, including credit card activity, email interactions, and website visits. What combination of features is critic

Question

Options

• AProbabilistic identity resolution and edge profiles.
• BDeterministic identity resolution and the Identity Graph.
• CStatic schemas and batch ingestion workflows.
• DReal-time activation without identity stitching.

• A
  3% (2)
• B
  84% (56)
• C
  9% (6)
• D
  4% (3)

Explanation

Deterministic identity resolution uses definitive identifiers - email addresses, loyalty IDs, login credentials - to confidently link records from credit card activity, email interactions, and website visits to a single person, while the Identity Graph maintains and connects all those identifiers so that every new event correctly collapses into the right unified profile. Probabilistic resolution (A) relies on statistical inference rather than confirmed identifiers, introducing ambiguity that's unacceptable in regulated financial services where profile accuracy directly affects compliance and personalization. Static schemas and batch ingestion (C) can't support real-time profile updates - financial event data like a card transaction must merge into the profile immediately, not hours later. Real-time activation without identity stitching (D) is self-defeating: you'd be activating on fragmented, siloed records rather than a complete customer view, undermining the entire purpose of a CDP.

Memory tip: Think "DIG" - Deterministic + Identity Graph. Just as a financial firm needs certainty (not guesses) about who a customer is before making decisions, deterministic resolution gives you certainty, and the Identity Graph is where that certainty lives.

No community discussion yet for this question.