Profile Fields — see where each value came from

The Source column on a profile's Profile Fields tab now shows what actually set each value on that profile. Previously it listed every stream that could write the field, so a field like last_name named several streams that had supplied nothing next to the one that had.

What's new

• Trace any value to its origin: a specific identity fragment, a Cloud Connect data model, Scoring, or "Merged from N fragments" when the field combines several.
• Click a source to open Why this value?, which lists every fragment that wrote the field and marks the one that won. Use it to answer "why does this profile have that last name?" without reading raw data.
• Switch to By identity fragment to see a profile from its pieces: each fragment's values, and which of them survived on the merged profile.
• Profiles open faster. Fields show right away, and the Source column fills in a moment later.
• Identifiers are listed first and internal fields last, so the fields you care about are at the top.

How it works

Look up a profile under Building Profiles → Search and open the Profile Fields tab. The drawer names the winning fragment, not the individual stream or event within it, and which fragment wins is decided by the field's merge operator, not by identity-key rank.

See Identity Explorer for details.