Skip to content

Commit f34aa98

Browse files
authored
Note on audience edits
Adding note to state that it is not possible to change the computation type simply be editing audiences.
1 parent 87a7e43 commit f34aa98

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

src/engage/audiences/index.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -132,6 +132,10 @@ Engage then processes your realtime Audience or Trait edits. While the edit task
132132
> warning ""
133133
> If your audience includes historical data (Historical Backfill is enabled), editing an audience creates a new backfill task. The backfill task, and therefore the edit task, take longer to process if the audience is connected to a destination with rate limits. Rate-limited destinations dictate how fast Engage can backfill. View a list of [rate-limited destinations](/docs/engage/using-engage-data/#rate-limits-on-engage-event-destinations).
134134
135+
> warning ""
136+
> It is not possible to edit an audience to convert it from real-time to batch, or vice-versa. If the computation type needs to be changed, you will need to recreate the audience with the appropiate conditions.
137+
138+
135139
## Access your Audiences using the Profiles API
136140

137141
You can access your Audiences using the Profile API by querying the `/traits` endpoint. For example, you can query for `high_value_user` property with the following `GET` request:

0 commit comments

Comments
 (0)