Today we’re shipping a powerful new feature in Census: Built-in Data Validation.
We help our customers sync millions of records every day to the apps that communicate with customers. That’s an amazing power, but it also means that a bad join upstream can cause a data fail 🤦♂️ if the team isn’t careful. Ever received an automated email that opened with “Hello
We don’t want any of our customers to have that experience. We call these types of failures Implicit Data Breakages, and they’re a lot harder to catch than those easy explicit “Cannot Connect to DB” errors. To catch them, our users need even more advanced tools.
With today’s release of Data Validation, we take our very first step in helping our customers make sure no bad data slips out to the apps and especially customers.
Built into every sync, we now check every single data source (dbt model, census query, view or table) for two classic data errors:
- null values
- duplicate identifiers.
If any record has either of these two issues, it’s automatically skipped and reported inside the Census UI. And that’s already in addition to our report for data that is rejected by the destination tool for any of their reasons (Salesforce validation errors, I’m looking at you!).
As of this morning, every single Census sync automatically gains built-in Data Validation by default and this is just the beginning. Keep an eye out for email alerts and dbt test support coming soon!