01 · About This Episode
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.
David explains how BDEX links offline consumer records to online identifiers, why the deterministic versus probabilistic debate misses the point, and how validation and disqualification layers keep fraudulent identifiers out of the graph. The conversation also covers the BDEX hybrid pixel, keyword based intent, activation across channels, the weekly graph rebuild, and the delivery paths available to customers.
BDEX is a SpringDB partner, and BDEX audiences are syndicated on the SpringDB Data Marketplace. If you are evaluating BDEX identity, audience, or intent data, or you want it blended with other consumer and business sources and hosted without runaway query costs, SpringDB can help you scope it and put it to work.
About BDEX
BDEX is a consumer identity company. The name originally stood for big data exchange, and the business began as a platform for helping data companies monetize their data. The team quickly found that the identity graph was the piece everything else depended on, and identity became the core of the company. 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 consumer and household level. Rather than describing the graph as deterministic or probabilistic, BDEX applies validation and disqualification layers across two to three trillion signals a month, then rebuilds the exportable graph each week. The platform also includes a hybrid pixel for identity resolution, audience building and modeling tools, keyword based intent, and an API for identity matches. Data is delivered in CSV or parquet through Amazon S3, Google Cloud, or SFTP, and coverage is currently United States only. BDEX audiences are syndicated on the SpringDB Data Marketplace.
02 · What You Will Learn
TAKEAWAY 01
Why an Identity Graph Is More Than a Match
Why BDEX maps online signals, devices, and touch points back to offline consumer records, and how linking email addresses, mobile IDs, connected TV IDs, and household IP addresses creates a usable view at the person and household level.
TAKEAWAY 02
How Ad Fraud Corrupts Identity Data
How bots and click farms steal real digital identifiers, mimic consumers, and attach false activity to legitimate profiles, and why that contamination damages far more than a single campaign.
TAKEAWAY 03
Why Deterministic Versus Probabilistic Is the Wrong Question
Why David argues that a bot can be linked deterministically just as easily as a real person, and why validation and disqualification layers matter more than the label attached to a graph.
TAKEAWAY 04
The Validation Work Behind Every Weekly Rebuild
How BDEX analyzes two to three trillion signals a month, decides which identifiers qualify, removes the ones that do not, and rebuilds the exportable graph at the end of each week.
TAKEAWAY 05
Identity Resolution With a Hybrid Pixel
How a pixel that combines cookie and non cookie identifiers can resolve consumers and households, and the range of use cases it supports, from retargeting and direct mail to attribution and fraud checks.
TAKEAWAY 06
Intent, Activation, and Delivery
Why BDEX uses a keyword based custom taxonomy rather than IAB categories, how quickly intent needs to be activated to stay useful, and the file formats and delivery paths used to move the data.
03 · Who Should Listen
Advertising and Marketing Platforms
Running cross device targeting and needing an identity graph that can be trusted at the point of match.
Agencies and Brands
Buying audiences and wanting to understand how much of a campaign is reaching real people rather than bots.
Data Providers
Holding data tied to a single identifier type and looking 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 a production pipeline.
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
Asking where a data set came from, how it is validated, and what happens to identifiers that fail those checks.
04 · Topics and Timestamps
