Why BDEX
Reported reach and real reach are not the same number.
Customer identity is fragmented across devices, channels and systems. Stale, recycled, fraudulent and synthetic identifiers fill that gap, inflating the audience count on the plan while quietly degrading the performance of everything built on it.
Identity resolution connects fragmented identifiers such as emails, mobile IDs, IP addresses and CTV IDs to the same person or household. BDEX continuously validates those connections and removes fraudulent, temporary and synthetic identifiers so marketers can work with real, addressable audiences rather than inflated counts.
The hidden cost
Media spent on nobody
Impressions delivered to identifiers with no reachable person behind them are paid for at the same rate as the rest of the buy.
The hidden cost
Match rates that flatter
A high match rate against a padded graph looks like coverage and behaves like waste. The number rises as the audience gets worse.
The hidden cost
Frequency you can’t control
When one person appears as several identities, capping fails and the same household absorbs a campaign meant for many.
The hidden cost
Measurement you can’t trust
Attribution inherits every identity error upstream of it, so the report explains a campaign that never quite happened.
Who we are
Fearless. Forward-thinking. Focused on your data.
Fearless. Forward-thinking. Focused on your data, and your business’s success. That’s BDEX.
The Story of BDEX
Founded in 2014, BDEX was the first-ever Data Exchange Platform (DXP). Its proprietary infrastructure powered human connectivity by deeply understanding consumer behaviors and intents. Today, BDEX has evolved into the US identity layer for brands, agencies and platforms.
Before creating BDEX, CEO David Finkelstein and CDO Michael Aronov founded one of the first Internet service providers in the country: National Internet Source, Inc. Six years later, the pair sold the company to U.S. Cable Corporation. They went on to found Contextuads, which served advertising networks and PPC search engines through more efficient ad targeting.
With a mountain of information at their fingertips, Finkelstein and Aronov knew what they had to do. Together, they created BDEX and revolutionized the identity data landscape.
The team
Meet the BDEX Team
We’re the thinkers, do-ers, and get-it-done-ers that power BDEX.
Driven to Succeed
Our team works together with one common goal: to bring our vision to life. No one individual can get us there alone. Only through team effort can we realize our ideas, and it’s that same team effort that will help us achieve greatness.
Team Members
We’re more than data experts, we’re veteran entrepreneurs, start-up fiends, artists, writers, and philanthropists. And we’re putting our combined experience to work for businesses and organizations throughout the country every day.
DF
David Finkelstein
Co-founder / Chief Executive Officer
David is a serial entrepreneur and founder of numerous Internet companies dating back to 1994. He founded National Internet Source, Inc. in 1994 and sold it to US Cable Corp in 2000. He also co-founded Contextuads, FreeAirMiles.com, Triplejack, and Dynaprice. David is responsible for all day-to-day operations at BDEX. He has a passion for all things data and enjoys tennis, kayaking, the beach, and spending time with his family. He was a member of Entrepreneurs’ Organization for over 10 years.
MA
Michael Aronov
Co-founder / Chief Data Officer
Mike has over 25 years of experience in the technology field and helped fellow Co-Founder David build one of the first Internet Service Providers in the country: National Internet Source, Inc. Mike is a co-founder and board member of BDEX and serves as Chief Data Officer. Mike is responsible for directing onboarding for new data sources and account management.
DW
David Welborn
Chief Technology Officer
David is a hands-on technology leader with over 25 years of experience in enterprise architecture delivery from concept to production. He got the startup bug in 2000, when he became a software development manager at Internet Billing Company, one of the first online credit card payment processors. He has been working at startups creating high performance technology teams ever since. In his free time, David can be found playing trumpet in salsa and jazz bands.
JL
Jessie Lizak
Chief Marketing Officer
Generating revenue, growing audiences and connecting people through data-driven marketing and sales is what Jessie has done for the last 10+ years. Jessie has senior management executive and c-suite experience with a solid track record of providing leadership and direction to drive revenue for technology companies. Marketing and communications including business text messaging, e-mail, social media, video and content creation and SEO/SEM have been a focus of Jessie’s experience.
HC
Hector Cen
Data Engineer
Hector has been involved in software development and engineering for over 20 years. He is an advocate of open-source software and initiatives. His current passion is working on data-centric projects. In his free time, he enjoys jogging, roller skating, and reading non-fiction.
ID Graph / Data & Tech
Four steps, running continuously.
Signals enter in real time, get validated against what the graph already knows, and either strengthen a link or decay out of it.
01
Ingest live signals
Two to three trillion raw data signals a month analyzed in real time every day from dozens of sources for scale and redundancy.
Why it matters: coverage that reflects this month, not last year’s file.
02
Filter what shouldn’t be there
Proprietary algorithms remove IDs linked to ad fraud along with temporary and synthetic identifiers before they can enter the graph.
Why it matters: budget goes to people, not to padding.
03
Validate to the household
Over 80 million households are mapped to IP address, then confirmed a second time against geoIP centroid and household location data.
Why it matters: household targeting and capping that hold up across channels.
04
Decay and refresh
An identity graph is not permanent. It is a living organism and constantly changing. As devices change, links lose weight and drop out, as the graph is constantly re-validating.
Why it matters: the audience you buy today is the audience you can still reach.
Two layers of validation
A household IP is only useful if it really is the household.
We validate IDs to the household level by mapping over 80 million households to IP address. We then use geoIP centroid and household location data to further validate that the IP belongs to that household.
Where the two layers agree, the link enters the graph with a confidence score. Where they disagree, it is withheld rather than shipped.
IN
Device signal arrives
A MAID, HEM, UID2 or CTV ID observed alongside an IP address.
1
Match to household-IP map
The IP is checked against 80M+ mapped US households to identify the household it belongs to.
2
Confirm with geospatial data
GeoIP centroid and household location data must corroborate the mapping independently.
✓
Link written with confidence score
Agreement writes the link and its score into the graph. Disagreement holds it back.
Inside the identity graph
All major identifiers, in one graph.
Match on what you already hold and receive back what you need to activate. Coverage figures are supplied on request against your own file.
| Identifier | What it resolves | Match in | Return |
|---|---|---|---|
| MAID | Mobile advertising ID on iOS and Android devices | Yes | Yes |
| HEM | Hashed email, the anchor for authenticated audiences | Yes | Yes |
| Household IP | IP address validated to one of 80M+ mapped US households | Yes | Yes |
| UID2 | Unified ID 2.0 token for open-web addressability | Yes | Yes |
| CTV device ID | Connected TV identifiers tied to the household | Yes | Yes |
| Postal address | Offline household record for direct mail and measurement | Yes | Yes |
Sample match response
{
"person_id": "BDX-7K42",
"household_id": "HH-3319",
"identifiers": {
"maid": "a41f…9c2",
"hem": "sha256:…",
"household_ip": "24.18.•.•",
"uid2": "token",
"ctv": ["device-1", "device-2"]
},
"household_validated": true,
"validation_layers": ["ip_map", "geo_centroid"],
"fraud_screen": "passed",
"confidence": 0.94,
"last_validated": "2026-09-01"
}
Illustrative structure. Field names and available attributes are documented in the API reference.
Fraud
A bigger graph is worse if the extra IDs aren’t real people.
Fraudulent, temporary and synthetic identifiers inflate every coverage number in this industry. BDEX uses proprietary methods to filter out IDs linked to ad fraud and IDs that are temporary or synthetic, so what you match against is population, not padding.
Before and after filtering
Example customer audience demonstrates volume of bad IDs in a typical audience without the BDEX identity graph
Removed
IDs linked to ad fraud
Identifiers associated with known fraudulent activity are screened out rather than counted as reach.
Removed
Temporary identifiers
Short-lived IDs that will never be reachable again are excluded instead of inflating segment counts.
Removed
Synthetic IDs
Machine-generated identifiers with no person behind them are identified and dropped at ingest.
What you get
A graph you can trust
Counts that survive scrutiny, and match rates that mean the same thing in a media plan as in a report.
Data Partners / Integrations
Meet Our Partners
Game-changers, bar-raisers, and industry leaders working together to change the way businesses use data.
Teaming Up with the Best
BDEX has joined forces with some of the best-known names in the world to create better, smarter, and harder-working data tools. These partners play an important role in our mission to put clients in control of their data, and we’re pleased to have them on board.
Data / strategic
Activation
Activation destinations & integration partners










Privacy & compliance
Compliance is a precondition, not a feature.
Sources are vetted before they enter the graph, consumer rights requests are honored across the graph, and sensitive categories are governed by policy rather than by a buyer’s discretion. Provenance and permitted use are documented for every source, and every published metric carries a definition, a scope and a review date.
Compliant with
- CCPA
- CPRA
- GDPR
- VDPOSA
- TDPSA
- OCPA
Source vetting
Every supplier is diligenced for provenance and consent before activation.
State privacy law support
Opt-out and deletion requests propagate through the graph, not just the delivery file.
Sensitive category policy
Restricted attributes are excluded at the graph level.
See the difference on your own data.
Bring a sample file and we’ll show you what resolves, what gets filtered out and what is actually addressable.