Most identity graphs cannot explain where a single linkage came from. That is exactly how bots end up inside them. In this episode of the SpringDB Data Exchange, John Kosturos sits down with David Finkelstein, Chief Executive Officer of BDEX, to talk about what separates an identity graph you can trust from one you simply inherited. BDEX started life as a big data exchange, built to help data companies monetize what they had. The team quickly ran into a problem that changed the company: every supplier anchored identity differently, and without a reliable way to connect those records, nothing downstream worked. Identity stopped being plumbing and became the product. David explains how BDEX maps online signals, devices, and touch points back to offline consumer records, linking email addresses, mobile IDs, connected TV IDs, and household IP addresses at the person and household level. He also makes a case that should change how you evaluate any graph: the deterministic versus probabilistic question misses the point, because a bot using a stolen identifier can create a link that is perfectly deterministic and completely false. What matters is validation, disqualification, and knowing the origin of every record. The conversation covers ad fraud and why advertisers stopped treating it as a cost of doing business, the volume of signals behind every identity decision, state privacy regulation, the BDEX hybrid pixel, keyword based intent and why it beats fixed category taxonomies, activation across channels, the weekly graph rebuild, and how the data is delivered. BDEX is a SpringDB partner, and BDEX audiences are syndicated on the SpringDB Data Marketplace. If you want to evaluate BDEX identity, audience, or intent data, blend it with other consumer and business sources, or host it somewhere that does not punish you for running long lookbacks, SpringDB can help you scope it and put it to work. WHO SHOULD LISTEN Advertising and marketing platforms running cross device targeting, who need an identity graph that holds up at the point of match. Agencies and brands buying audiences, who want to understand how much of a campaign is reaching real people rather than bots. Data providers holding data tied to a single identifier type, who want to link it to other IDs so it can be activated more widely. Data and platform engineers evaluating file formats, delivery paths, and refresh cadence before wiring a graph into production. Go to market and revenue teams connecting consumer identity to business records, so buyers can be reached beyond a single work email address. Data buyers and procurement teams who want to ask better questions about where a data set came from, how it is validated, and what happens to identifiers that fail those checks. Guest: David Finkelstein, Chief Executive Officer, BDEX Host: John Kosturos, SpringDB
