Introducing Audiences
Today we’re excited to announce a new way to power your notification workflows: Knock Audiences. Audiences bring the concept of user segmentation into Knock.
An audience represents a list of users you define who all share a common set of characteristics. You can build any number of segments of users that you'd like, bring those audiences into Knock, and then use them to power notification behavior.
With this release, you can bring audiences into Knock programmatically through our new Audiences API and direct integrations with reverse ETL tools like Hightouch and Census. Your audiences are then available to view and manage through the Knock dashboard.
Once you start creating audiences in Knock, you can use them to:
- Trigger workflows when new users are added to an audience. This is great for powering lifecycle messaging (such as new user signups) and transactional messaging (such as payment method updates) use cases
- Orchestrate branch and conditional logic within your workflows (e.g. if a user is in
paid-usersaudience, opt them out of the workflow)
With today's release, we’re excited to expand the messaging use cases you can power with Knock and help our customers power a unified messaging motion across their product and lifecycle marketing.
Audiences are currently in beta. If you want to try them out, you can contact our team to request access. To learn more about what's possible with audiences, check out our documentation.
There's a lot more to come with Audiences in the future. They will form a pivotal building block for new features we're working on over the coming months, and we can't wait to share more with you soon.
Fixes and improvements
- 🐛 We fixed an issue with translations where archiving a namespaced translation would cause other translations for that locale to stop working when previewing and sending
- 🐛 We fixed an issue where using liquid in a JSON editor would sometimes cause the validation to fail