Product News

Monitor and optimize Match Rates across all your ad platforms in Census Audience Hub

Nick Carchedi
Nick Carchedi January 19, 2024

Match rates are the percentage of users from an audience that an advertising platform is able to recognize. Match rates have always been critical for advertising teams because they help them measure if ads are successfully reaching target audiences.

Advertising teams at companies like Canva and Crocs use Census to send first-party audiences from their cloud data warehouse to ad platforms like Google and Facebook. Leveraging the data warehouse for advertising boosts match rates by providing ad platforms with more and better quality data to match their users. Data warehouses provide:

  • The most complete Customer 360 profiles — A wealth of first-party and third-party identifiers gathered from multiple sources within and outside of the organization, that are normally difficult for advertisers to access.
  • The highest quality data — The warehouse contains cleaned, resolved, and modeled customer data, maintained by data teams, to ensure insights are trustworthy.

Two related metrics—matched audience size and match rate—help advertising teams understand the sizes of their addressable audiences, as well as the quality of the customer data they’re sending to ads platforms. The larger they are, the greater the reach.


See all match rates within Census Audience Hub

Audience Hub is a powerful suite of features designed to help marketers create, activate, and analyze their audiences, without needing to rely on engineering teams.

Census users can now view both matched audience size and match rate across every ad platform—all in one place. In the past, advertising teams had to visit each ad platform individually to get these numbers, which is tedious and time-consuming. 

Finally, all your match rates in one place!


Managing and measuring audiences in Census

Match rates help with the analysis stage of audience management—understanding the reach of an audience. Audience Hub enables direct access to the data warehouse throughout the entire audience lifecycle:

1. Create

Census customers can create an audience in two different ways:

  • Directly in Audience Hub—marketers build audiences using our no-code interface
  • Via Warehouse-Managed Audiences—data teams manage audiences programmatically in the warehouse

2. Activate

Regardless of how an audience is defined, it can be sent to ad platforms with a single click thanks to our new One-Click Audience feature. Alternatively, users can use the full sync creation experience to customize field mappings and sync behavior.

3. Analyze

As of today, match rates and matched audience size are conveniently displayed next to each connected ad platform. Also, Audience Hub offers multiple other tools for analyzing success, including audience and cohort performance monitoring, comparing audiences, and audience size over time.


How match rates work in Census

Let’s take a deeper look at how these numbers are calculated.

Matched audience size

This is the total size of an audience in the ad platform after accounting for invalid and unmatched records:

The original segment size is the total number of members in an audience as reported in Audience Hub:

Audience Hub displays the total size of an audience over time

Obviously, this number has a big impact on the final matched audience size, but volume isn’t everything—data quality matters too.

Records can be invalid in different ways. One of the most common is that data isn’t normalized and/or hashed properly. Each ad platform has different requirements for how data should be formatted before being sent. For example, TikTok requires you to remove all periods before the @ in an email address, whereas Facebook doesn’t.

Fortunately, Census handles this normalization automatically if you provide us with unhashed identifiers. (If you give us hashed data, we can’t tell whether it was normalized correctly prior to being hashed.)

Once the data is normalized, it’s often required to be hashed as well. If you haven’t given us hashed data for a field that requires hashing, we’ll do it automatically behind the scenes so you don’t have to worry about it.

If the ad platform still can’t match a properly normalized and hashed record to one of their users (using their black box methods) then that person will be omitted from the final audience, thus reducing the matched audience size. This might happen because the identifiers provided were either wrong or insufficient to uniquely identify someone, or because that person is actually not a user of that platform.

Subtracting both the invalid and unmatched records from the original segment size yields the matched audience size reported in Census. We get this number directly from the ad platforms.

Match rate

Once we have the matched audience size, computing the match rate is straightforward—it’s simply the matched audience size divided by the total number of audience members uploaded to the platform (i.e. the original segment size in Census):

Some ad platforms report their own match rate and it may differ from what you see in Census. If that’s the case, it’s probably because they’re computing it based on the number of records that were successfully uploaded to their platform, whereas Census counts all records in your original audience.

In this case, ignoring invalid records decreases the size of the denominator (i.e. original segment size) in the formula above, thus increasing the match rate. We think it’s better to include those invalid records in the calculation, because otherwise you may not know there’s a problem that’s directly impacting the size of your matched audience!

A final note—some platforms take 24-48 hours to process audience uploads, so these numbers may lag changes in your source data slightly.


Get started with match rates today

Audience Hub enables you to quickly create audiences and get them into your mission-critical advertising and marketing channels. Match rates provide an important feedback loop so you can feel confident about the audiences you’re sending to ad platforms.

Match rates are now available to all customers using Audience Hub. Start a free 14-day trial today, or request a personalized onboarding session.

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: