Merge pull request #4750 from segmentio/criteo

clarify how email is actually set

Author: forstisabella

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

@@ -379,7 +379,7 @@ window.criteo_q.push({ event: 'viewItem', item: 'PRODUCT-ID', sub_status: 'trial
 
 ### Setting Emails
 
-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
+If you make an [identify call](/docs/connections/spec/identify/) that has an `email` trait in the payload, this email is stored as a customer trait. We then include a hashed version of this email in subsequent [`track`](/docs/connections/spec/track/) calls by pushing the `setHashedEmail` event to Criteo along with your event. Segment takes care of hashing customer emails for you.
 
 ### Criteo Data Centers