Skip to content

Commit 4a1af52

Browse files
authored
multiple audience entered events for the same user
1 parent ccad90a commit 4a1af52

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

src/engage/faqs.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -130,3 +130,10 @@ If your team would like to avoid receiving the notifications for transient failu
130130

131131
Each step of a Journey is an Engage audience under the hood. The conditions stack, so a user must be a member of the previous step (audience) and meet all conditions to be added to subsequent steps. However, if the user no longer meets entry conditions for a particular step, they'll exit and you'll see the user count reduced. For any subsequent steps a user is still a part of, they'll remain until they no longer meet entry conditions.
132132

133+
## Why were multiple audience-entered events triggered for the same user?
134+
135+
Multiple audience events can be triggered for the user if it falls under any one of the following conditions:
136+
1) A merge (there is a merge on this user)
137+
2) [New external_id’s](/docs/engage/using-engage-data/#new-external-identifiers-added-to-a-profile) added to the profile (a new external_id that was added can trigger this).
138+
3) The user has [multiple emails](/docs/engage/using-engage-data/#multiple-identifiers-of-the-same-type). Personas sends one event per email for each audience or computed trait event.
139+
4) Anonymous audience. This is expected behavior of Personas when the 'include anonymous users' option is selected in the audience. We will send an event per every anonymousId on the user profile, when there's multiple (not your case).

0 commit comments

Comments
 (0)