Intro to the Criteo OneTag | Commerce Growth Help Center

The "Criteo Conversion/Sales Tag"

This tag records conversions that happened on site. This tag should fire for ALL conversion events regardless of attribution.

Please fire this event on the "thank you" page after a user has successfully completed their purchase.

FIELD	OVERVIEW	EXAMPLE	SYNTAX	REQUIRED
Email Address	Contains either: SHA256 hashed email (in line with industry standards) MD5 hashed email Plain text (if allowed by the law in your country)	79054025255fb1a26e4bc422aef54eb4...	String (trimmed and lowercased, encoded in UTF-8)	Yes
Hash Method	The hashing method used for the email. Doesn't need to be included for plain text emails For sha265 hashed emails: "sha256" For md5 hashed emails: "md5"	sha256	String	Yes
Phone number	Phone number in SHA256 hashed format or in plain text.	fda66831d0cb0eb4bffb21bc795308d69921c211c57be0ae15702071e3b9e989	Plain text phone numbers SHA256 hashed phone numbers	Recommended
Customer Id	A non PII value that can identify a unique user in a client's CRM. Examples: CRM id, user's login. The result that is passed to the tag must not be sent in plain value, it needs to be encrypted (MD5 or SHA256)	49f68a5c8493ec2c0bf489821c21fc3b	String	Recommended
Visitor Id	A unique Id that is consistent across multiple sessions for an unauthenticated user. Example: First party cookie id	53e20ea700424f7bbdd793b02abcb5d7	String	No
Zip Code	Zip code of the shipping address. Value is hashed before storing in our database. We do not store any PII and are compliant with all local regulations.	12345	String	Recommended
Transaction ID	An ID (uniquely) identifying the transaction on the advertiser's systems. Confirmation or Order #.	7654322	String	Yes
Deduplication	Indicates if the client attributed the sale to Criteo. Even if you put a 1, we will only attribute the sale if it matches our normal attribution model. Set to 1 if yes, else 0	1	Boolean	No
New Customer	Indicates if it is the first time that the user has bought a product on your site. Set to 1 if yes, else 0.	1	Boolean	No
Product Id	Unique id of the product	a123	String	Yes
Price	Unit price of the product.	20	Double	Recommended
Quantity	The number of a specific item that the consumer has in their cart.	2	Integer	Recommended
Currency	The currency of the price.	USD	String	No
Partner Id	Partner Id is a unique ID that can be found in your Commerce Growth Url.	https://marketing.criteo.com/technical-setup/assets-tags/implementation?advertiserId=93844&partnerId=101269	String	Yes

STRUCTURE

Dynamically replace fields surrounded by ## and ## with values, ensuring that all # symbols are also removed. See the table above for more info on the fields.

You need to send at least one of the setEmail events. If user emails are not collected by your website, you can remove these 3 lines. You should aim to prioritize sharing SHA256 HEM. Criteo is migrating from hashing our emails via MD5/SHA256MD5 to SHA256. If possible, in order to maximize match rates between your data and our identity graph, please share the MD5 format, alongside the SHA256 format. If a plain text value is shared, we will hash it on our side.

If you decide to share a phone number, depending on the choice of the format, you should use the appropriate event. ‘setSha256HashedPhoneNumber’ if sharing a hashed phone number or ‘setPhoneNumber’ if sharing a plain text phone number. You can find more information here.

For full information on how to manage your website policy, click here.

Please add the code snippets on the left to the <head> section of the Thank you page.

Pass user emails into Criteo’s tags

If the law permits it in your Country, you may pass the user’s email address in plain text format using the { event: "setEmail", email: "##Email Address of User##" } event. This piece of information will be converted by Criteo automatically into a SHA256 hashing ID before it is used/stored and will activate Cross-device functionality on your account, enabling Criteo to increase users' addressability, therefore enhancing both targeting and campaign delivery efficiencies.

Alternatively, you may pass this piece of information already hashed, in which case please pass both MD5 and SHA256 versions using the other two setEmail events instead.

Please ensure the user's email is added to the code whenever it becomes available to your website (ie when the user converts and when they are logged onto the site (if applicable).

Please refer to our Help Centre for more information on how to implement to enable Cross Device functionality. Additional help is available to assist with the implementation of hashing functions.