Skip to content

Add note on payload location for email id #5091

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.

Sign up for GitHub

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

Merged
merged 5 commits into from
Nov 17, 2023
Merged

Add note on payload location for email id #5091

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
a972255
Add note on payload location for email id
bobbyatsegment Jul 28, 2023
1772e9e
Move added note to previous section
bobbyatsegment Aug 11, 2023
41d81de
note > info
rchinn1 Nov 17, 2023
67a706c
Edits
rchinn1 Nov 17, 2023
eb69c1e
Merge branch 'develop' into bobbyatsegment-patch-1
rchinn1 Nov 17, 2023
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
7 changes: 4 additions & 3 deletions src/engage/using-engage-data.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -207,17 +207,18 @@ _See [this doc](https://segment.com/docs/engage/journeys/send-data/#what-do-i-se
}
```


## Additional identifiers

Engage has a flexible identity resolution layer that allows you to build user profiles based on multiple identifiers like `user_id`, `email`, or `mobile advertisingId`. However, different destinations may require different keys, so they can do their own matching and identification. For example, Zendesk requires that you include the `name` property.
Engage includes logic to automatically enrich payloads going to these destinations with the required keys.

If you send events to a destination that requires specific enrichment Segment doesn't already include, [contact Segment](https://segment.com/help/contact/){:target="_blank"}, and we‘ll do our best to address it.

> note ""
> **Note**: Profiles with multiple identifiers (for example, `user_id` and `email`) will trigger one API call per identifier when the audience or computed trait is first synced to a destination.
> info ""
> Profiles with multiple identifiers (for example, `user_id` and `email`) will trigger one API call per identifier when the audience or computed trait is first synced to a destination.

> success ""
> Email as an identifier is set in `traits.email` for Identify calls, and `context.traits.email` for Track calls.

## Multiple identifiers of the same type

Expand Down