43 Census Testimonials

"From the first demo, I was hooked. Especially the fact that it would plug in directly to our database, which is our source of truth, so I didn't have to go through Shopify anymore."

"As Marketing is coming up with campaigns and ideating on them, we don't have to deal with complex code, and we'll have more real-time insights into exactly when the data is syncing."

"Census’s warehouse logging enables healthy end-to-end data flows by helping us drill down to each record and ensure data quality. We can find bottlenecks in our ETL provider and our own transformations, not just reverse ETL pipelines."

"This is revolutionary. When we first implemented the data warehouse, we tried to be digital leaders in sport but could never get to a personalized experience. We had the warehouse but couldn’t activate it, because I didn’t want to build a monolithic system and the API. This makes me so happy."

"We've always had analytics data coming through to Customer.io through Segment, but there was previously no ability to transform that data. There was a clear gap for us around the way we handled ETL and our ETL layer."

"We estimated that it would take six months to implement a CDP fully, but with Census we were up and running in one day. There was no need to modify the code base. There was no UAT. We just plugged it into the data warehouse and were ready to go."

"One of the problems we were running into was actually our API usage. We were just absolutely blowing through our call limit with Salesforce. Syncing one sales opportunity could easily have used 10 API calls."

"Census allowed us to do things that, at other companies, had taken months to build with a data team."

"It’s transforming the way that we operate."

"Census makes it really easy to sync audiences into our Ad platforms. I build my audiences on top of models from my data team, click go, and it just works."

"Data teams get stretched thin. It’s so important that the operational people can just own the operations pieces."

“Census can tell me exactly what might be wrong. It could be a Salesforce trigger or not having permission to a certain field. With all that information and all those records, specific details are captured in Census, which means it's easier to go and troubleshoot that data. Even people who are not as close to the data can still go in and look at what might be wrong, because Census provides a good layer of transparency into how the data pipeline is feeding the data.”

“It was extremely minimal, Back in the day we used a tool that literally did one job load the account ID, and then everything was triggered based on that. But because of that, everything happened in a very suboptimal way.”

"We've been able to train folks who traditionally would write out a request form, send it to the BI team, and wait a few days to get their data. Now we've got analysts outside of the BI team, folks who aren't comfortable writing code or merging changes into our BI repo, that can set up their own connections to feed their operations tools out of our warehouse."

"Rapid iteration is hard to do when you don’t have data. You don’t have the ability to try different things. You run the same playbook, not optimizing, not growing. With access to this data, my team can turn their ideas into action faster than ever."