Audiences
An Audience is a user segment that you can notify. You can bring audiences into Knock programmatically with our API or a supported reverse-ETL source.
Once you start creating audiences in Knock, you can use them to:
- trigger workflows for lifecycle messaging (such as new user signups) and transactional messaging (such as payment method updates)
- orchestrate branch and conditional logic within your workflows using audience membership (e.g. if a user is in a
paid usersaudience, opt them out of the workflow)
Creating an audience
Navigate to the Audiences section on the Knock dashboard’s sidebar, then click “Create Audience” in the top right corner.
Using audiences across environments
When you create an audience, its key instantly exists across all environments. Any users added to an audience are scoped to a specific environment. Audiences do not follow Knock version control and do not need to be committed or promoted to environments. Learn more about environments.
Using audiences with workflows
Triggering workflows
Workflows can be configured to trigger for every new member added to an audience.
Create or open the workflow you’d like to trigger for your audience, then open the workflow editor. Click on the “Trigger” step, then click “Edit trigger type” in the top right corner. Click “Audience“ and then select the audience you’d like this workflow to trigger from.
Commit your workflow to development, and when you’re ready promote it to production. At this point, every time a user is added to the selected audience a workflow will be triggered with that user as a recipient.
Audience conditions
Audience membership can be checked in branch and step conditions. Create a condition, then select “Audience membership” as the type. When the condition is evaluated during workflow execution it will check if the recipient is a member of the selected audience.
Populating an audience
Before populating your audience ensure that your user data has been identified in Knock and that you’ve configured and promoted any workflows you want to trigger with the Audience.
Supported reverse ETL vendors
Audiences can easily be synced from Hightouch Models and Census Segments by configuring Knock as a sync destination. Please reach out to support@knock.app for beta access to our rETL integrations with Hightouch and Census.
Audiences API
The Knock API can be used to sync audiences from any data warehouse or reverse ETL system. Create the audience in the Knock dashboard, then use the add and remove API operations to power your sync.
The API is designed for batch processing and accepts payloads of up to 1,000 members at a time. For more information see the audiences API docs.
Using audiences with tenants
When adding users to an audience you can optionally include a tenant ID to power per-user, per-tenant workflows. A user can exist in an audience with multiple distinct tenants.
When a workflow triggers from an audience entry event, the tenant ID provided for the member will be passed along to the workflow trigger. If no tenant ID is provided in the API request, the workflow will run with no tenant data. If the same user is added with multiple distinct tenants, the workflow will trigger each time by default. To configure this behavior use trigger frequency controls.
Tenancy is also taken into account when checking audience membership. For a recipient to be considered a member of an audience during workflow execution, the tenant ID provided with the trigger data must match the user’s audience membership record. If no tenant ID was provided with the trigger, the user must have been added to the audience with no tenant ID.