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.
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).
When available, the Criteo salted user ID (GUM ID) is required.
This is retrieved by getting the value of the cookie
crto_mapped_user_id
and can be set using the Criteo - User Identification client-side template which is available in our library following these steps:INTEGRATION
➜ Sources
➜ Web Containers
.Settings | Description |
---|---|
Account Id | Required |
Caller Id | The Caller Id is used for identifying the user and it's provided by Criteo upon request. |
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 | viewList |
view_cart | viewBasket |
view_item | viewItem |
[1] If
page.type
ishome
thenviewHome
is also sent withviewPage
, otherwise, justviewPage
is forwarded.
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 andid.email.sha256_md5 [3] |
user.email_sha256 | id.email.sha256 |
[1] Automatically converted in the ISO 8601 format.
[2] If
app.name
is defined then this field is set withm
, otherwise,d
.
[3]id.email.sha256_md5
is automatically hashed.Last modified 4d ago