Product News

Census Enrichment: Third-party data enrichment, now in your warehouse | Census

Katy Yuan
Katy Yuan February 15, 2023

Katy is a Product Marketing Manager at Census who loves diving into startups, SaaS technology, and modern data platforms. When she's not working, you can find her playing pickleball or Ultimate Frisbee.

Today we’re excited to announce Census Enrichment inside our data activation platform, with our launch partners Clearbit and Apollo.io. 🎉

We’re enabling marketers and data teams to build Customer 360 profiles that combine first- and third-party data in one source of truth – the data warehouse. Just enrich once and use everywhere.

The data enrichment challenge - where to enrich?

Marketers need to build complete Customer 360 profiles to target customers with the most personalized messaging. However, even a simple request like a list of “all users that work for companies with over 1000 employees” can be difficult to fulfill, because company size isn’t often data you already have, and not something customers would often provide.

That’s where data providers like Clearbit and Apollo fill in the blanks. They enrich your existing database with third-party data like employee count, job title, or company industry – as opposed to first-party data which is data that comes from you, your apps, and your customers.

The challenge has been – where do you do this enrichment across many fragmented systems?

Until today, it wasn’t easy to have that data available in the warehouse. Companies usually enrich Salesforce, Marketo, or HubSpot with third-party data through native integrations. Then they ETL ingest that data into the warehouse, to then stitch it back into the customer model. This fragmented integration flow results in increased costs and wasted credits (running enrich jobs in 2+ tools) as well as maintenance pains for custom scripts that hook up enrichment APIs.

⚡ TL;DR: Multiple GTM systems get enriched data in different ways, which makes the job of building complete Customer 360 profiles extremely complicated. Census Enrichment solves that problem by integrating enriched data into the warehouse.

Access 400 million+ records from Clearbit and Apollo.io with just a few clicks

Introducing Census Enrichment on your warehouse

With Census Enrichment, users can automatically add enrichment to Entities in their data warehouse from our partner enrichment services Clearbit and Apollo (with more to come soon) with just a few clicks.

Underneath the covers, Census takes care of building the corresponding enrichment data set in your data warehouse. This data is stored separately from your own first party data but can be referenced by any of your services. Census transparently takes care of joining that data with your first party data as necessary to power Census Segments and Syncs.

Like every Census product, Enrichment is built to be a natural addition to your data warehouse and to work at scale. The enrichment data is stored on your infrastructure and used to avoid making duplicate enrichment calls. You can also control how frequently data is refreshed, if at all.

For more information, read the product docs →

The benefits of enriching in the warehouse

Enriching the Customer 360 in the warehouse with Clearbit or Apollo makes your data even more comprehensive and actionable. By combining both first- and third-party data, you can build a more complete picture of your customers and prospects.

Because Census is the activation layer between your warehouse and SaaS apps, we already provide you with the tools to put that data to work.

Now, you can immediately use this unified customer data to:

  • Sync to automation tools like Marketo, Braze, and Iterable using Reverse ETL.
  • Segment customer lists based on third-party data attributes like company size.
  • Power any BI tool, ETL process, or SQL integration connected to the warehouse.

Unify and activate all your customer data – whether it’s first-party or third-party – in your warehouse.

Build audience segments using enriched third-party attributes, like company size

The benefits of combining first-party and third-party data in your warehouse with Census Enrichment:

  1. Better Personalization: Third-party data sources can help fill in the gaps and improve the accuracy of first-party data. A more complete and accurate Customer 360 enables marketers to deliver more personalized experiences and messaging, leading to higher customer engagement and satisfaction.
  2. Simplified Enrichment Workflow: Instead of enriching contacts and companies in multiple places then stitching data together, just enrich once and use it everywhere. No more wasted credits or duplicate enrichments. Maintain the enriched Customer 360 in the warehouse and sync it to all your marketing tools with Data Activation.
  3. Enhanced Insights: Combining first-party data with third-party data increases your customer understanding and helps you uncover new insights and patterns that may not be visible from a single data source. With deep understanding of individual customers, as well as wider context about those users and companies, you can make more informed decisions for sales, marketing, and product development.

Watch this video walkthrough for a step-by-step demo 👉

Get started today

Overall, combining first-party and third-party data provides more comprehensive and accurate Customer 360 profiles. Marketers can then activate those profiles across all their marketing and advertising tools with ease.

With Census, that’s just a couple of clicks away. Start a free trial or get a demo today 🙌

Related articles

Customer Stories
Built With Census Embedded: Labelbox Becomes Data Warehouse-Native
Built With Census Embedded: Labelbox Becomes Data Warehouse-Native

Every business’s best source of truth is in their cloud data warehouse. If you’re a SaaS provider, your customer’s best data is in their cloud data warehouse, too.

Best Practices
Keeping Data Private with the Composable CDP
Keeping Data Private with the Composable CDP

One of the benefits of composing your Customer Data Platform on your data warehouse is enforcing and maintaining strong controls over how, where, and to whom your data is exposed.

Product News
Sync data 100x faster on Snowflake with Census Live Syncs
Sync data 100x faster on Snowflake with Census Live Syncs

For years, working with high-quality data in real time was an elusive goal for data teams. Two hurdles blocked real-time data activation on Snowflake from becoming a reality: Lack of low-latency data flows and transformation pipelines The compute cost of running queries at high frequency in order to provide real-time insights Today, we’re solving both of those challenges by partnering with Snowflake to support our real-time Live Syncs, which can be 100 times faster and 100 times cheaper to operate than traditional Reverse ETL. You can create a Live Sync using any Snowflake table (including Dynamic Tables) as a source, and sync data to over 200 business tools within seconds. We’re proud to offer the fastest Reverse ETL platform on the planet, and the only one capable of real-time activation with Snowflake. 👉 Luke Ambrosetti discusses Live Sync architecture in-depth on Snowflake’s Medium blog here. Real-Time Composable CDP with Snowflake Developed alongside Snowflake’s product team, we’re excited to enable the fastest-ever data activation on Snowflake. Today marks a massive paradigm shift in how quickly companies can leverage their first-party data to stay ahead of their competition. In the past, businesses had to implement their real-time use cases outside their Data Cloud by building a separate fast path, through hosted custom infrastructure and event buses, or piles of if-this-then-that no-code hacks — all with painful limitations such as lack of scalability, data silos, and low adaptability. Census Live Syncs were born to tear down the latency barrier that previously prevented companies from centralizing these integrations with all of their others. Census Live Syncs and Snowflake now combine to offer real-time CDP capabilities without having to abandon the Data Cloud. This Composable CDP approach transforms the Data Cloud infrastructure that companies already have into an engine that drives business growth and revenue, delivering huge cost savings and data-driven decisions without complex engineering. Together we’re enabling marketing and business teams to interact with customers at the moment of intent, deliver the most personalized recommendations, and update AI models with the freshest insights. Doing the Math: 100x Faster and 100x Cheaper There are two primary ways to use Census Live Syncs — through Snowflake Dynamic Tables, or directly through Snowflake Streams. Near real time: Dynamic Tables have a target lag of minimum 1 minute (as of March 2024). Real time: Live Syncs can operate off a Snowflake Stream directly to achieve true real-time activation in single-digit seconds. Using a real-world example, one of our customers was looking for real-time activation to personalize in-app content immediately. They replaced their previous hourly process with Census Live Syncs, achieving an end-to-end latency of <1 minute. They observed that Live Syncs are 144 times cheaper and 150 times faster than their previous Reverse ETL process. It’s rare to offer customers multiple orders of magnitude of improvement as part of a product release, but we did the math. Continuous Syncs (traditional Reverse ETL) Census Live Syncs Improvement Cost 24 hours = 24 Snowflake credits. 24 * $2 * 30 = $1440/month ⅙ of a credit per day. ⅙ * $2 * 30 = $10/month 144x Speed Transformation hourly job + 15 minutes for ETL = 75 minutes on average 30 seconds on average 150x Cost The previous method of lowest latency Reverse ETL, called Continuous Syncs, required a Snowflake compute platform to be live 24/7 in order to continuously detect changes. This was expensive and also wasteful for datasets that don’t change often. Assuming that one Snowflake credit is on average $2, traditional Reverse ETL costs 24 credits * $2 * 30 days = $1440 per month. Using Snowflake’s Streams to detect changes offers a huge saving in credits to detect changes, just 1/6th of a single credit in equivalent cost, lowering the cost to $10 per month. Speed Real-time activation also requires ETL and transformation workflows to be low latency. In this example, our customer needed real-time activation of an event that occurs 10 times per day. First, we reduced their ETL processing time to 1 second with our HTTP Request source. On the activation side, Live Syncs activate data with subsecond latency. 1 second HTTP Live Sync + 1 minute Dynamic Table refresh + 1 second Census Snowflake Live Sync = 1 minute end-to-end latency. This process can be even faster when using Live Syncs with a Snowflake Stream. For this customer, using Census Live Syncs on Snowflake was 144x cheaper and 150x faster than their previous Reverse ETL process How Live Syncs work It’s easy to set up a real-time workflow with Snowflake as a source in three steps: