Skip to content

Commit 458f651

Browse files
committed
edits
1 parent 11aeda2 commit 458f651

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

src/engage/faqs.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -132,8 +132,8 @@ Each step of a Journey is an Engage audience under the hood. The conditions stac
132132

133133
## Why were multiple audience-entered events triggered for the same user?
134134

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 identifiers of the same type](/docs/engage/using-engage-data/#multiple-identifiers-of-the-same-type). Personas sends one event per identifier 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).
135+
Multiple audience events can trigger for a user if any of the following conditions occur:
136+
1) There is a merge on the user.
137+
2) An [`external_id`](/docs/engage/using-engage-data/#new-external-identifiers-added-to-a-profile) was added to the profile.
138+
3) The user has [multiple identifiers of the same type](/docs/engage/using-engage-data/#multiple-identifiers-of-the-same-type). Segment sends one event per identifier for each audience or computed trait event.
139+
4) The `include anonymous users` option is selected for an audience. Segment sends an event for every `anonymousId` on the user profile.

0 commit comments

Comments
 (0)