Criteo
Criteo is a global technology company that powers the world's marketers and media owners with trusted and impactful advertising through our world-leading Commerce Media Platform, a suite of products that activates the world's largest set of commerce data to drive better commerce outcomes.
Official webpage: The Commerce Media Platform for the Open Internet | Criteo
Documentation of Server-to-Server integration: Criteo OneTag S2S
JENTIS - Criteo - Global Constants
Criteo JS SDK HTTP Reference* | The full HTTP URL locator of the Criteo JS library to be used with your website (source is fetched from this location as third party content). |
Criteo Account ID | Your Criteo Account ID, ie. “15432”. |
JENTIS - Criteo - Tag Types
(Connection type prefix: S2S: Server to Server, C2S: Client to Server, HYB: Hybrid, compiled server side, executed client side)
S2S: Visit event
Description | JENTIS Data Layer - Default Dependencies |
---|---|
Tracks an event of page type viewPage in Criteo One Tag. This will assure you have no blind spots in your tracking if no other event applies (ie. Product Detail Page, Homepage, etc). Please fire this event on all pages where no other event is being triggered. This tag must only be executed if no other (and more specific) Criteo tag is executed (ie. Product Detail Page, Homepage, etc). | The following default _jts push track calls are required for the default JENTIS Criteo implementation to work out of the box: _jts.push track:
Code example (do not execute or copy paste; for reference only).
JS
JavaScript Copy |
Recommended Trigger (default): Pageview Except Ecommerce
C2S: Homepage / S2S: Homepage Event
Description | JENTIS Data Layer - Default Dependencies |
---|---|
Tracks an event of page type viewHome in Criteo One Tag which translates to “Homepage“. A generic tracking with universal parameters (ie. Email, Customer Id, Account Id, etc.) but no specific parameters (ie. Product Name, etc). This tag should fire on the homepage or main landing page of your site to tag users and add them to the target audience. Fire this event on the homepage or main landing page of your site. | The following default _jts push track calls are required for the default JENTIS Criteo implementation to work out of the box: _jts.push track:
Code example (do not execute or copy paste; for reference only).
JS
JavaScript Copy |
Recommended Trigger (default): Home
C2S: Category Browse Listing Page / S2S: Listing event
Description | JENTIS Data Layer - Default Dependencies |
---|---|
Tracks an event of page type viewCategory in Criteo One Tag which translates to “Category Browse listing pages”. A specific tracking for taxonomy browse and category web pages displaying products or items. | The following default _jts push track calls are required for the default JENTIS Criteo implementation to work out of the box: _jts.push track:
Code example (do not execute or copy paste; for reference only).
JS
JavaScript Copy |
Recommended Trigger (default): Productlist
C2S: Product Detail Page / S2S: Product Event
Description | JENTIS Data Layer - Default Dependencies |
---|---|
Tracks an event of page type viewItem in Criteo One Tag which translates to "Product Detail pages". A “Product Detail page” contains details of a specific product or item. As this tag gives Criteo’s engine a clear flag for the product a user is looking at, please fire this event on any product details page. Installing the OneTag on product detail pages is key to the tracking process. Additionally, the tag […] provides functionality to update both price and availability in near real time anytime the page is visited in between feed processing runs.
| The following default _jts push track calls are required for the default JENTIS Criteo implementation to work out of the box: _jts.push track:
Code example (do not execute or copy paste; for reference only).
JS
JavaScript Copy |
Recommended Trigger (default): Productview
C2S: Add to Basket / S2S: Add To Cart Event
Description | JENTIS Data Layer - Default Dependencies |
---|---|
Tracks an event of page type addToCart in Criteo One Tag. This event contains details on an item that was put into the basket on ecommerce shops. | The following default _jts push track calls are required for the default JENTIS Criteo implementation to work out of the box: _jts.push track:
Code example (do not execute or copy paste; for reference only).
JS
JavaScript Copy |
Recommended Trigger (default): Add-to-Cart
C2S: Shopping Basket Page / S2S: Basket event
Description | JENTIS Data Layer - Default Dependencies |
---|---|
Tracks an event of page type viewBasket in Criteo One Tag which translates to “Shopping Basket pages“. An event to be executed when a basket of products or items selected for checkout is displayed to the user. Which consists of products or item objects. | The following default _jts push track calls are required for the default JENTIS Criteo implementation to work out of the box: _jts.push track:
Code example (do not execute or copy paste; for reference only).
JS
JavaScript Copy |
Recommended Trigger (default): Cartview
S2S: Begin Checkout event
Description | JENTIS Data Layer - Default Dependencies |
---|---|
Tracks an event of page type beginCheckout in Criteo One Tag which translates to “Begin Checkout Event“. An event to be executed on the 1st page of checkout process. | The following default _jts push track calls are required for the default JENTIS Criteo implementation to work out of the box: _jts.push track:
Code example (do not execute or copy paste; for reference only).
JS
JavaScript Copy |
Recommended Trigger (default): Inititatecheckout
S2S: Add Payment Info Event
Description | JENTIS Data Layer - Default Dependencies |
---|---|
Tracks an event of page type addPaymentInfo in Criteo One Tag which translates to “Add Payment Info Event“. An event to be executed on the 2nd page of checkout process by default. If your payment-information checkout page is a different step, please adjust accordingly your tags configuration. | The following default _jts push track calls are required for the default JENTIS Criteo implementation to work out of the box: _jts.push track:
Code example (do not execute or copy paste; for reference only).
JS
JavaScript Copy |
Recommended Trigger (default): Addpaymentinfo
C2S: Order Confirmation Page / S2S: Sale event
Description | JENTIS Data Layer - Default Dependencies |
---|---|
Tracks an event of page type trackTransaction in Criteo One Tag which translates to “Order Confirmation pages“. This event is to be used when the user a confirmation of a purchase is displayed, containing the order summary of products and order information (transaction id, etc). | The following default _jts push track calls are required for the default JENTIS Criteo implementation to work out of the box: _jts.push track:
Code example (do not execute or copy paste; for reference only).
JS
JavaScript Copy |
Recommended Trigger (default): Order
S2S: Login event
Description | JENTIS Data Layer - Default Dependencies |
---|---|
Tracks an event of page type login in Criteo One Tag which translates to “Login Event“.An event to be executed when a user logs into the web page. | JENTIS do not use default tracking command associated with this event. To use this event you have push your own tracking command, you name it. Furthermore a trigger associated with this tracking command.
JS
JavaScript Copy |
Recommended Trigger (default): none
Criteo JS SDK HTTP Reference*
The full HTTP URL locator of the Criteo JS library to be used with your website (source is fetched from this location as third party content).
Criteo Account ID
Your Criteo Account ID, ie. “15432”.
Description
JENTIS Data Layer - Default Dependencies
Tracks an event of page type viewPage in Criteo One Tag.
This will assure you have no blind spots in your tracking if no other event applies (ie. Product Detail Page, Homepage, etc).
Please fire this event on all pages where no other event is being triggered.
This tag must only be executed if no other (and more specific) Criteo tag is executed (ie. Product Detail Page, Homepage, etc).
The following default _jts push track calls are required for the default JENTIS Criteo implementation to work out of the box:
_jts.push track:
pageview
submit
Code example (do not execute or copy paste; for reference only).
function pageview() {
_jts.push({
"track" : "pageview"
});
_jts.push({
"track" : "submit"
});
}
JavaScript
Copy
Description
JENTIS Data Layer - Default Dependencies
Tracks an event of page type viewHome in Criteo One Tag which translates to “Homepage“.
A generic tracking with universal parameters (ie. Email, Customer Id, Account Id, etc.) but no specific parameters (ie. Product Name, etc).
This tag should fire on the homepage or main landing page of your site to tag users and add them to the target audience.
Fire this event on the homepage or main landing page of your site.
The following default _jts push track calls are required for the default JENTIS Criteo implementation to work out of the box:
_jts.push track:
pageview
submit
Code example (do not execute or copy paste; for reference only).
function pageview() {
_jts.push({
"track" : "pageview"
});
_jts.push({
"track" : "submit"
});
}
JavaScript
Copy
Description
JENTIS Data Layer - Default Dependencies
Tracks an event of page type viewCategory in Criteo One Tag which translates to “Category Browse listing pages”.
A specific tracking for taxonomy browse and category web pages displaying products or items.
The following default _jts push track calls are required for the default JENTIS Criteo implementation to work out of the box:
_jts.push track:
pageview
product
type
id
productlist
submit
Code example (do not execute or copy paste; for reference only).
function productlist() {
_jts.push({
"track" : "pageview"
});
//---------------------------
_jts.push({
"track" : "product",
"type" : "productlist",
"id" : "1111111"
});
_jts.push({
"track" : "product",
"type" : "productlist",
"id" : "2222222"
});
_jts.push({
"track" : "product",
"type" : "productlist",
"id" : "3333333"
});
//---------------------------
_jts.push({
"track" : "productlist",
"name" : "PRODUCTLISTNAME"
});
_jts.push({
"track" : "submit"
});
}
JavaScript
Copy
Description
JENTIS Data Layer - Default Dependencies
Tracks an event of page type viewItem in Criteo One Tag which translates to "Product Detail pages".
A “Product Detail page” contains details of a specific product or item.
As this tag gives Criteo’s engine a clear flag for the product a user is looking at, please fire this event on any product details page.
Installing the OneTag on product detail pages is key to the tracking process. Additionally, the tag […] provides functionality to update both price and availability in near real time anytime the page is visited in between feed processing runs.
Criteo One Tag Documentation
The following default _jts push track calls are required for the default JENTIS Criteo implementation to work out of the box:
_jts.push track:
pageview
product
type
id
brutto
productview
submit
Code example (do not execute or copy paste; for reference only).
function productview() {
_jts.push({
"track" : "pageview"
});
//---------------------------
_jts.push({
"track" : "product",
"type" : "productview",
"id" : "1111111",
"brutto" : 100.00
});
//---------------------------
_jts.push({
"track" : "productview"
});
_jts.push({
"track" : "submit"
});
}
JavaScript
Copy
Description
JENTIS Data Layer - Default Dependencies
Tracks an event of page type addToCart in Criteo One Tag. This event contains details on an item that was put into the basket on ecommerce shops.
The following default _jts push track calls are required for the default JENTIS Criteo implementation to work out of the box:
_jts.push track:
pageview
product
id
type
quantity
brutto
addtocart
submit
Code example (do not execute or copy paste; for reference only).
function addtocart() {
_jts.push({
"track" : "product",
"type" : "addtocart",
"id" : "1111111",
"brutto" : 100.00,
"quantity" : 1
});
//---------------------------
_jts.push({
"track" : "addtocart"
},true); //Automatic submit without "track":"submit" push
/* OR
_jts.push({
"track" : "addtocart"
});
_jts.push({
"track" : "submit"
});
*/
}
JavaScript
Copy
Description
JENTIS Data Layer - Default Dependencies
Tracks an event of page type viewBasket in Criteo One Tag which translates to “Shopping Basket pages“.
An event to be executed when a basket of products or items selected for checkout is displayed to the user. Which consists of products or item objects.
The following default _jts push track calls are required for the default JENTIS Criteo implementation to work out of the box:
_jts.push track:
pageview
product
type
id
name
quantity
brutto
cartview
submit
Code example (do not execute or copy paste; for reference only).
function cartview() {
_jts.push({
"track" : "pageview"
});
//---------------------------
_jts.push({
"track" : "product",
"type" : "cartview",
"id" : "1111111",
"name" : "Product 1",
"brutto" : 100.00,
"quantity" : 3
});
_jts.push({
"track" : "product",
"type" : "cartview",
"id" : "2222222",
"name" : "Product 2",
"brutto" : 150.00,
"quantity" : 1
});
//---------------------------
_jts.push({
"track" : "cartview"
});
_jts.push({
"track" : "submit"
});
}
JavaScript
Copy
Description
JENTIS Data Layer - Default Dependencies
Tracks an event of page type beginCheckout in Criteo One Tag which translates to “Begin Checkout Event“. An event to be executed on the 1st page of checkout process.
The following default _jts push track calls are required for the default JENTIS Criteo implementation to work out of the box:
_jts.push track:
pageview
product
id
type
brutto
quantity
checkout
step
submit
Code example (do not execute or copy paste; for reference only).
function checkout() {
_jts.push({
"track" : "pageview"
});
//---------------------------
_jts.push({
"track" : "product",
"type" : "checkout",
"id" : "1111111",
"brutto" : 100.00,
"quantity" : 3
});
_jts.push({
"track" : "product",
"type" : "checkout",
"id" : "2222222",
"brutto" : 150.00,
"quantity" : 1
});
//---------------------------
_jts.push({
"track" : "checkout",
"step" : 1
});
_jts.push({
"track" : "submit"
});
}
JavaScript
Copy
Description
JENTIS Data Layer - Default Dependencies
Tracks an event of page type addPaymentInfo in Criteo One Tag which translates to “Add Payment Info Event“. An event to be executed on the 2nd page of checkout process by default. If your payment-information checkout page is a different step, please adjust accordingly your tags configuration.
The following default _jts push track calls are required for the default JENTIS Criteo implementation to work out of the box:
_jts.push track:
pageview
checkout
step
submit
Code example (do not execute or copy paste; for reference only).
function checkout() {
_jts.push({
"track" : "pageview"
});
//---------------------------
_jts.push({
"track" : "checkout",
"step" : 2
});
_jts.push({
"track" : "submit"
});
}
JavaScript
Copy
Description
JENTIS Data Layer - Default Dependencies
Tracks an event of page type trackTransaction in Criteo One Tag which translates to “Order Confirmation pages“. This event is to be used when the user a confirmation of a purchase is displayed, containing the order summary of products and order information (transaction id, etc).
The following default _jts push track calls are required for the default JENTIS Criteo implementation to work out of the box:
_jts.push track:
pageview
product
id
type
quantity
order
orderid
submit
Code example (do not execute or copy paste; for reference only).
function order() {
_jts.push({
"track" : "pageview"
});
//---------------------------
_jts.push({
"track" : "product",
"type" : "order",
"id" : "1111111",
"brutto" : 100.00,
"quantity" : 3
});
_jts.push({
"track" : "product",
"type" : "order",
"id" : "2222222",
"brutto" : 150.00,
"quantity" : 1
});
//---------------------------
_jts.push({
"track" : "order",
"orderid" : "abcdef123456"
});
_jts.push({
"track" : "submit"
});
}
JavaScript
Copy
Description
JENTIS Data Layer - Default Dependencies
Tracks an event of page type login in Criteo One Tag which translates to “Login Event“.An event to be executed when a user logs into the web page.
JENTIS do not use default tracking command associated with this event. To use this event you have push your own tracking command, you name it. Furthermore a trigger associated with this tracking command.
function login() {
_jts.push({
"track" : "login"
});
_jts.push({
"track" : "submit"
});
}
JavaScript
Copy