Product News

Warehouse-Managed Audiences: Enabling data teams to manage audiences programmatically from the warehouse

Nick Carchedi
Nick Carchedi January 12, 2024

At Census, we’ve had the privilege of working with large and highly sophisticated customers like Canva who communicate daily to their 125 million monthly users. Businesses with higher data maturity often prefer to model audiences in their data warehouse rather than using a point-and-click interface for several reasons:

  • Data teams can maintain the warehouse as the source of truth for customer data, including critical audience definitions like exclusion lists.
  • Audiences are defined in version-controlled SQL, which allows for more rigor and observability, and can be managed within existing data team workflows.
  • Because audiences are defined in code, this technique scales much more easily to large userbases, high volume audiences, and very large numbers of audiences.
  • Data teams are able to ensure trustworthy and approved audiences for the benefit of marketers.

Last year, we released Census Audience Hub to cater specifically to marketers who want to use their warehouse to power customer engagement. Although it was a gamechanger to help non-technical users build complex audiences without SQL, it wasn’t designed for situations in which some (or all) audiences are already defined in the warehouse.

As a result, customers often ended up recreating their audiences in Audience Hub, rather than just mirroring the definitions directly from their warehouse.

Introducing Warehouse-Managed Audiences

Today, we’re excited to announce Warehouse-Managed Audiences. This feature allows data teams to manage audiences programmatically from their warehouse while taking full advantage of all the features that come with Audience Hub, including:

This approach makes it trivial to manage hundreds or thousands of audiences and still maintain the data warehouse as source of truth—a data team’s dream come true. We’re proud to be the first and only marketing platform to enable importing audiences directly from your data warehouse. 

How to use Warehouse-Managed Audiences

In order to support importing audiences directly from the warehouse, we’re introducing a data standard for defining audiences. This standard requires 3 distinct tables—a list of people, a list of audiences, and a join table that tells Census which people are in each audience.

3 tables that enable importing audiences from the warehouse

People 

Also known as contacts, customers, users, etc., this is a list of all people belonging to every audience you plan to model in your warehouse.

Audiences

This is a list of all audiences you plan to model in your warehouse. Each audience must have a unique ID (assigned by you) and a name, which will be reflected in Census.

Audience Membership

This is a join table that tells Census which people are in each audience. Each row must include a unique pair of person and audience identifiers.

Once these tables are defined in the warehouse, you simply create 3 datasets in Census and define the relationships between them using our entity layer.

Then, you can sit back and let Census work its magic. Audiences will be automatically mirrored from your warehouse into Census and kept fresh as your source data changes over time.

To maintain the warehouse as source of truth, Warehouse-Managed Audiences are “Census-managed”, meaning they can’t be modified in the UI but all other Audience Hub features are available.

For more information on setup, check out our product documentation.

Can marketers still create audiences in Census?

Yes! Marketers can use our no-code Audience Hub to build audiences in Census. Those audiences may be built on top of those that are imported from the warehouse, or could represent entirely new audiences.

Data teams manage audiences in the warehouse, marketers manage audiences in Audience Hub

Altogether, this allows data teams to maintain control over a core collection of high-quality, vetted audiences in the warehouse, while allowing marketers the freedom to rapidly experiment with new audiences without being blocked by the data team. When an experimental audience is working well for the marketing team, the data team can incorporate it into the warehouse.

Bottom line: if you have a set of audiences that your data and marketing teams have battle-tested and you want to govern them in code, we’ve got you covered. If you need a more experimental workflow, no problem.

Get started with Warehouse-Managed Audiences today

Beginning today, Warehouse-Managed Audiences are available in private preview to all customers on our Enterprise plan. If you’re interested in checking it out, please reach out to your account manager or send an email to support@getcensus.com.

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: