The marketer notices some strange behavior in emails that were going out and noticed a Profile that had multiple email identities. What would the marketer do next to identify the root cause?

Question

Options

• AUse the Identity API to get the details of the Identity Namespace definition
• BUse the Identity API to list the Identity Mappings for the email
• CUse Identity graph viewer to retrieve the list of data sources
• DUse the Identity graph viewer to retrieve the Identity Map linked to the profile

• A
  5% (1)
• B
  5% (1)
• C
  79% (15)
• D
  11% (2)

Explanation

Option C is correct because when a profile exhibits unexpected behavior due to multiple email identities, the root cause is almost always a data ingestion problem - meaning one or more data sources are incorrectly contributing duplicate or conflicting email identities. The Identity graph viewer's data source list reveals which systems are feeding identity data into the profile, giving the marketer a clear starting point for investigating where the bad data originates.

Why the others are wrong:

• A - The Identity Namespace definition describes the structure/configuration of a namespace (e.g., what "Email" means as a type), not why a specific profile accumulated multiple email values. This is too upstream to help diagnose the problem.
• B - The Identity API can list mappings programmatically, but it shows what is linked, not where it came from. You'd confirm the problem exists without identifying its cause.
• D - The Identity Map shows identities linked to a profile, which the marketer already knows (multiple emails). It confirms the symptom but doesn't expose the data sources responsible - so it doesn't advance root cause analysis.

Memory tip: The keyword is "root cause." Root cause = source of the problem = data sources. When diagnosing identity issues visually, the Identity graph viewer + data sources list answers "who sent this data?" - C is always the investigative first step.

No community discussion yet for this question.