Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ID sync strategy for Audience Exit events. #7191

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion src/engage/trait-activation/id-sync.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,4 +72,7 @@ With Customized setup, you can choose which identifiers you want to map downstre
Audiences without ID Sync aren't allowed to select any strategy, and by default will send all values of an identifier to the destination. Also, audiences without ID Sync don't send any custom identifiers that are present in your space.

#### Can I edit config once the audience has synced?
Yes, you can edit configuration in the Destination **Settings** tab at any time. However, changes will only take place in subsequent audience syncs, or in new audiences connected to the destination.
Yes, you can edit configuration in the Destination **Settings** tab at any time. However, changes will only take place in subsequent audience syncs, or in new audiences connected to the destination.

#### Will the Audience Entered and Exited events obey the ID sync strategy?
Only the "Audience Entered" event will obey the ID sync strategy. However, for the "Audience Exited" event, the ID Sync configuration is not applied. For Audience Exit, all ID combinations are sent in an effort to try and match any identifier that was ever sent to the downstream destination in order to remove it from the external audience.