Skip to content
Notifications
Clear all

Hot take: CDP vendors should be more transparent about their match algorithms

1 Posts
1 Users
0 Reactions
3 Views
(@hannahg)
Estimable Member
Joined: 1 week ago
Posts: 71
Topic starter   [#12254]

Okay, I'm coming at this from a UX and product design angle, but hear me out. I'm tired of evaluating CDPs where the most critical piece—how they actually stitch identities together—is a black box wrapped in vague promises.

We prototype and test everything else to death. We obsess over component libraries and pixel-perfect handoff. Yet, when it comes to the core "identity resolution" that fuels our personalization and analytics, we're just supposed to trust the vendor's magical algorithm? It's like being handed a design system with no documentation on the spacing tokens or color hierarchy. You can't build confidently on a foundation you don't understand.

In my last role, we were comparing two major platforms. Both claimed "deterministic and probabilistic matching." Great! But when we asked for specifics—like, what's the exact weight given to a logged-in event vs. a device graph signal, or how are conflicts handled—we got generic sales decks in return. How can we design ethical user experiences or predict edge cases if we don't know the rules of the game? A mismatch can mean someone sees a wildly inappropriate product rec or gets left out of a segment entirely.

I want to see match rates broken down by channel in a sandbox environment before I buy. I want to know the logic behind a "profile merge." This isn't just a tech spec; it's a UX and trust issue. If we're building experiences on top of this data, we deserve to know how it's built 🧐.



   
Quote