Computed Traits are always sent to Event Destinations destinations through the identify call as a user trait, or additionally as a group call for account-level computed traits. With Audiences, we can send the audience either as a boolean user property to Event Destinations, or as a user list to List Destinations. Note that for account-level audiences syncing to list destinations, we will send the list of all users within an account that satisfies your audience criteria.
For event destinations, you can send an audience as an identify call and/or track call to the destination for each user being added and removed. For identify calls, the trait name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property
order_completed_last_30days: true, and when this user no longer satisfies we will set that value to
false. For track calls, we will send two events,
Audience Entered and
Audience Exited, with the event property
order_completed_last_30days equal to true and false, respectively.
When the audience is first created an identify or track call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.
The following event destinations below are supported. Note that some destinations do not support flexible schemas and require you to create the
audience_name field before Personas can update those values. Check the specific destination’s docs for more details.
- Google Analytics
- Help Scout
- Keen IO
- Salesforce Marketing Cloud
- Amazon S3
- All Aboard
- Amazon Kinesis
- Amazon Kinesis Firehose
- Google Cloud PubSub
- Marketo V2
- Optimizely X
- Stitch Data
- Salesforce DMP
- IBM Db2 Warehouse
- Azure SQL Data Warehouse
When syncing to a list destination Personas will upload lists of users directly to the destination. When an audience is first created the entire list of audience users will be uploaded to the destination. Subsequent syncs will only upload the users added or removed since the last sync.
Note that different user-list destinations have limits on how often we can sync. For example, AdWords recommends only updating user lists once every 6 hours. An AdWords audience would be updated every 6 hours if the sync rate was once an hour and every 8 hours if the sync rate was every 4 hours. Facebook supports syncing audiences every hour.
We support the following user-list destinations:
You can also access your computed traits and audiences programmatically via the Profile API. Consult the Profile API documentation for full details.
If you have any questions, or see anywhere we can improve our documentation, please let us know!