Skip to content

Commit a24c56c

Browse files
author
Thomas Gilbert
committed
clarify how email is actually set
1 parent 99bc7bf commit a24c56c

File tree

1 file changed

+1
-1
lines changed
  • src/connections/destinations/catalog/criteo-app-web-events

1 file changed

+1
-1
lines changed

src/connections/destinations/catalog/criteo-app-web-events/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -379,7 +379,7 @@ window.criteo_q.push({ event: 'viewItem', item: 'PRODUCT-ID', sub_status: 'trial
379379

380380
### Setting Emails
381381

382-
It's easy to associate emails with a user, if there's an `email` property in a [`track`](/docs/connections/spec/track/) call, we'll include the `setHashedEmail` event to Criteo along with your event. We'll take care of hashing it for you
382+
Once an [identify call](/docs/connections/spec/identify/) has been made that has an `email` trait in the payload, this email will be stored as a trait on the client. We then include this email in subsequent [`track`](/docs/connections/spec/track/) calls, by pushing the `setHashedEmail` event to Criteo along with your event. We'll take care of hashing it for you.
383383

384384
### Criteo Data Centers
385385

0 commit comments

Comments
 (0)