Customer 360
Donor Identity Resolution

Understanding household and person relationships using entity resolution on Snowflake

How the Orthodox Union unified donor and household relationships across 40+ custom CRMs, running person-level and household-level matching on Snowflake with Zingg Enterprise.

"Even matches between 0.65–0.8 score are really clean. We can pull back anything under 0.6 only and the number of records to manually review are somewhere in the 1,000 range. It far exceeded our expectations."

Shelomo Dobkin, Director of Product Development
Orthodox Union

Customer image
40+ systems
websites, apps, and CRMs connected into a single identity graph
~1,000
records needing manual review — far fewer than the 10,000s expected
12h → 3h
initial matching runtime reduced (was 12 hours)
Background

The Orthodox Union (OU) is one of the largest Orthodox Jewish organizations in the US, founded in 1898. They run 40+ websites, 5 mobile apps, and multiple custom CRMs across departments, each generating separate donor and member records with no shared identifier across systems.

Challenge

Understanding donors and household relationships across 40+ custom CRMs was impossible without unified data. Person-level and household-level matching both needed to work across decoupled systems without disrupting existing architectures. Initial runtime for the full data load was 12 hours, far too slow for the planned multi-batch-per-day cadence.

Solution

The Orthodox Union put Zingg Enterprise at the center of their data architecture on Snowflake, with Airbyte bringing data in from Postgres and MongoDB, and dbt handling cleansing. They built both person-level and household-level matching models, and worked with the Zingg team to develop the Incremental Flow feature that made multi-batch-per-day processing possible.

  • Both person-level and household-level matching models built and running in production
  • Runtime reduced from 12 hours to 3 hours for initial load, now running incrementally 4–8 times per day
  • Family relationship trees constructed automatically from matched household data
"When we saw that you started offering an enterprise version on Snowflake, we took a step back and put Zingg first, you are the engine that’s powering building out our golden records."

Shelomo Dobkin, Director of Product Development
Orthodox Union

Results
  • Person and household matching models both live in production, with family relationship trees built automatically from matched data
  • Manual review reduced to ~1,000 records vs. the 10,000s expected, accuracy far exceeded initial projections
  • Incremental Flow running 4–8 times per day, changes processed in near real-time without full reprocessing
  • Golden records now feeding BI tools, reverse ETL into operational systems, and an enterprise-wide OpenSearch index
Platform
Snowflake
Edition
Enterprise
Customer
Orthodox Union
Full Transcript
Read the complete transcript
15 min read
→
FULL VIDEO
Watch the complete interview
→

See how Zingg runs natively on Snowflake — incremental matching, Zingg ID, household relationships.

See how it works →