Census segments let you build dynamic lists of users using attributes from your models, without touching SQL. It makes it easy to create marketing segments or audiences, and then sync them to ad platforms, marketing automation, and more. Your segments are defined once, on your data warehouse, and can be shared with any of your Census destinations.
See how Census Segments works in 2 mins
Here are just a few examples of Census segments you can build:
  • Users who haven’t engaged with the product in the last 30 days
  • Trial users who haven’t used the product in the past week.
  • Recommend a new product to customers who have purchased a similar product
Census Visual Segment Builder

Some destination apps allow you to create segments from a full list of items (users, accounts, etc.). So, how do you know whether to set up segments in Census or in a destination app?
Census segments have one primary benefit: they stay in sync between destinations. Let’s look at an example.
An eCommerce company creates segments based on customers’ past purchases. The company has a multi-channel marketing campaign for a new product but only wants to target customers who bought Product A in the last six months. Since their multi-channel campaign will use a variety of tools (an email tool and Facebook Ads, for example), they’ll need to align the segment in each system. That’s where Census comes in. When the customer segments are set up in Census, those segments can sync to each destination app.
Using Census segments has another common benefit: it allows you to move from one tool to another without needing to recreate segment conditions. If, for example, your company moves to a new email marketing platform, there’s no need to worry about losing your segment data. The segment conditions continue to exist in Census and segments simply sync to the new destination.
Interested in learning more on how you can use Census Segments with your data, read on!
Copy link