Product Updates

To create objects, you’ll define their type—like companies, accounts, and so on. Then you’ll create them—this process is a bit like identifying people. You’ll identify an object, set its attributesA key-value pair that you associate with a person—like their name, the date they were created in your workspace, etc. Use attributes to target people and personalize messages., and then add relationships to people. Then you can create segments of people based on their relationships to objects.

In the past, if you wanted to manage your audience’s subscription preferences, you would have had to set up attributes representing people’s preferences and apply preferences to messages with complicated segments or campaign filters. It was a confusing, error-prone process. The new subscription center feature lets you set topics for your campaigns, broadcasts, and newsletters, and automates preference logic. When people click the Unsubscribe link in your messages, our default unsubscribe page now lets people pick their subscription preferences—providing an easy way for people to update their preferences and creating a way to retain subscribers who might not like all of your messages.

This helps you maintain a better understanding of your audience’s devices, so you know which devices are relevant and can get a real device count—without having to clean up old devices yourself.

With our original Track API, you’re limited to a single request per person, and a host of different endpoints. Today we’re releasing our v2 track API, which lets you send groups of requests for different people, and different kinds of actions, to our /v2/batch/ endpoint. Now you don’t have to maintain different calls for different actions; you can just modify your payload to fit different request cases and send requests in batches.

We’re committed to releasing, maintaining, and supporting Flutter. Try out our new SDK and let us know what you think. Your feedback helps us understand your needs, so that we build our SDK(s) and associated features to fit your needs.

We’ve made page rules for in-app messages easier to use! Before this update, you needed to set up a complicated workaround to limit an in-app message to to your website or mobile app. Now, when you select your web, iOS, and/or Android channels, we’ll automatically limit messages to the platforms you select. If you don’t select any platforms, your message will appear on whichever platform the person visits first.

In the past, we had a complicated recipe to perform holdout tests, but it involved sending real messages to a black hole address, which wasn’t ideal. Now you can set up holdout tests with a simple checkbox!

In the past, you needed to hunt down the ID of a transactional message before you could use it and actually send messages to your audience. Now you can set a friendly, case-insensitive Trigger Name, and use it to send messages. The Trigger Name makes it easier to find the message you want to send. It can also make your integration more human-readable if you use triggers that represent the kinds of messages you send—like password reset or order confirmation

Now, we attempt to perform sync operations on your exact interval without regard to the time it takes to complete an import operation; if we’re still importing from your database on a sync interval, we’ll skip it (showing a skipped status in our UI), and try again at the next interval. This adds predictability to your database sync integrations, so you’ll always know when you can expect to see your data in Customer.

See our Amplitude and Mixpanel pages for more information about these integrations.

Our Create Event workflow action used to be limited to Data Campaigns. Now you can create an event in any campaign, regardless of campaign trigger, providing a handy way to trigger parallel campaigns and add people to segments. You can create an event for the person in your current campaign, or another related person: anybody whose ID or email that you can access from the trigger event or the current person’s attributes.This release also makes it easier to add properties to your events, letting you click to select the values that you want your event to include so you don’t have to write liquid.Go to the docs