Entity Resolution On Google Cloud
Run Zingg on Spark in Google Cloud and read from and write to BigQuery directly. Your data stays in your project, and resolved entities with a persistent ZINGG_ID land back in BigQuery for analytics, AI and activation.
Your Sources
- Web and mobile events
- CRM and ERP
- Application databases
- SaaS tools
- Third-party and advertising data
Your Google Cloud Project
Spark with the BigQuery connector
Results are written back to BigQuery.Your Applications
- Reporting and BI
- CRM and marketing automation
- KYC and AML systems
- RAG, chatbots and AI agents
- Reverse ETL to operations
From BigQuery, Back To BigQuery
BigQuery In And Out
Zingg reads source tables from BigQuery and writes resolved entities back, through the Spark BigQuery connector.
Your Project, Your Rules
Zingg authenticates with your service account and runs in your own Google Cloud project.
Scales With Spark
Blocking learned from your labels keeps comparisons low as your data grows. How Zingg scales
From Open Source To Enterprise
Zingg Community
A set of notebooks on the Zingg Python API that take you from setup to labeling training pairs, model documentation, and training and matching on Spark, with BigQuery as source and sink through the Spark BigQuery connector.
Zingg notebooksZingg Enterprise
Incremental flow, persistent ZINGG_IDs, explainability and model diff, plus support from the builders of Zingg.
Talk to usMore Than Matching
ZINGG_ID
A persistent, global identifier for every resolved entity, so every team and agent joins on the same key.
Learn moreIncremental Flow
Match only new, updated and deleted records against the clusters already resolved. IDs persist between runs.
Learn moreExplainability
See the evidence behind every match, so you can explain results to business users.
Learn moreModel Diff
Confidently add new signals, update configuration and deploy models in production.
Learn moreZingg On Google Cloud Questions
Does Zingg work with BigQuery?
Yes. Zingg reads from and writes to BigQuery through the Spark BigQuery connector. Writing uses a temporary Cloud Storage bucket.
Does my data leave Google Cloud?
No. Zingg runs on Spark in your own project and writes results back to BigQuery.
How does Zingg authenticate to BigQuery?
With a Google Cloud service account key that you point Zingg to.
What does Zingg Enterprise add on Google Cloud?
The incremental flow, persistent ZINGG_IDs, explainability, model diff and enterprise support.
Resolve Entities On Google Cloud
Run Zingg on your own Google Cloud project, with BigQuery in and out.