Criteo - Events

Using the Criteo Server-side API you can track web events you are used to report via Criteo OneTag client-side JS (pixel). This is normally required for technical and legal reasons.

Key features

The Criteo (events) destination provides the following key features:

• Events structure: our Events reference suits Criteo's events, meaning that your data is properly bridged to the expected fields in an optimized way.

• Prebuilt mappings: data mapping for event-based destinations happens automatically, which simplifies user inputs.

• Refined data: you can freely push additional information based on your specific needs (E.g. adding custom events, custom event and user properties).

• Support for multi-item data: information included in the item array is brought to Criteo.

Destination setup

The Criteo salted user ID (GUM ID) is required: this value must be passed to this destination by including the cookie crto_mapped_user_id. The easiest way to manage this cookie is to use this client-side tags in our tag library : Criteo - User Identification in your web container.

Configuration

Settings	Description
Account Id	Required The retailer’s Criteo Account Id can be found in the Management Center.
Caller Id	The Caller Id is used for identifying the user and it's provided by Criteo upon request.

Quick reference

Commanders Act Events	Criteo Events
add_payment_info	addPaymentInfo
add_to_cart	addToCart
begin_checkout	beginCheckout
login	login
page_view	viewHome and/or viewPage [1]
purchase	trackTransaction
search view_item_list	viewList
view_cart	viewBasket
view_item	viewItem

[1] If page.type is home then viewHome is also sent with viewPage, otherwise, just viewPage is forwarded.

Field mappings

Commanders Act Properties	Criteo Properties
event_timestamp	timestamp [1]
Account Id	account
device.ip	ip
page.location.href	full_url
page.referrer	previous_url
(app.name)	site_type [2]
device.user_agent	useragent
user.id	retailer_visitor_id
Caller Id	id.mapping_key
user.email	id.email.raw
user.email_md5	id.email.md5 and id.email.sha256_md5 [3]
user.email_sha256	id.email.sha256

[1] Automatically converted in the ISO 8601 format. [2] This is either m or d, depending if app.name is defined or not. [3] id.email.sha256_md5 is automatically hashed.