This Tag has been deprecated from the Tag Marketplace. Any existing instances of this Tag in your profile are still supported.

 

Tag Specifications and Requirements

Specifications

Name: Criteo

Vendor: Criteo

Type: Display Ad

Required

Services: Criteo Account

Configurations:

  • Page Type
  • Partner ID1 (PID)
  • Partner ID2 (wiSE)
  • Partner ID3 (wiTR)
  • Location
  • Server Pool

Tag Configuration in Tealium iQ

1. Adding the Tag

Tealium iQ's Tag marketplace offers a wide variety of Tags. Click here to learn how to add a Tag to your profile.

2. Configuring the Tag

Criteo_Tag_Configs_Part_1_of_2.png

Criteo_Tag_Configs_Part_2_of_2.png

  1. Title (Required): Enter a descriptive title to identify the Tag instance.
  2. Page Type (Required): Select the page type from the drop-down list. This selection determines which Criteo tracker will load, which in turn determines which data is sent to Criteo. You can dynamically set this value through mapping. If you do plan to set this configuration through mapping, then leave the default 'home' option selected.

    Note: The page type is automatically set to confirmation whenever the E-Commerce extension's _corder variable has a value.

    • home - This notifies Criteo when a visitor has seen your homepage.
    • product - This notifies Criteo when a visitor has seen your product pages.
    • list - This notifies Criteo when a visitor has seen your pages that display a list of products.
    • basket (cart) - This notifies Criteo when a visitor has seen your cart pages.
    • confirmation - This notifies Criteo when a visitor has seen your order confirmation pages.
    • search - This notifies Criteo when a visitor has seen your search results page.
    • Multiple: product and search - Combines product and search.
    • Multiple: list and search - Combines list and search.
  3. Partner ID1 (PID) (Required): Enter the PID provided by Criteo. This is usually a 4-digit number.

    Note: Partner ID1, Partner ID2, and Partner ID3 reside in the code that was provided to you by Criteo. To find these values locate the CRITEO.load() method in the code provide by Criteo. The code will look like [PID,'','us',' 0 1 1 ',[[wiSE, wiTR]]]

  4. Partner ID2 (wiSE) (Required): Provided to you by Criteo. This is usually a 7-digit number.

    Note: The wiSE and wiTR values are often no more than 1 number apart. For example, the wiSE could be 7012345 and wiTR could be 7012346.

  5. Partner ID3 (wiTR) (Required): Provided to you by Criteo. This is usually a 7-digit number.
  6. Location (Required): Select the Location from the drop-down list.
    • For the US, Canada, Latin America, Australia, and New Zealand select 'us'.
    • For Asia, with the exception of Russia and Turkey, select 'as'.
    • For all other locations, select 'none'.
  7. Server Pool (Required): Select the Server Pool from the drop-down list.

    The items in the pools list are ranges in the alphabet with a 'p' appended. So the first selection, 'pac', indicates the range of letters from 'a' to 'c', 'pdf' indicates the range of letters from 'd' to 'f', and so on. The pool you should select depends on the first letter of your domain. For example, tealium.com would use 'psu' because 't' falls within the range of 's' to 'u'.

  8. Call Protocol (Required): Select the Call Protocol from the drop-down list. You have two options: 'Two calls (widget)' and 'One Call'.
    • 'Two Calls (widget)' loads the widget and display.js file.
    • 'One Call' skips the widget and display.js file and calls only the dis.aspx file.
3. Applying Load Rules

Load Rules determine when and where to load an instance of this Tag. The 'Load on All Pages' rule is the default Load Rule. To load this Tag on a specific page, create a new load rule with the relevant conditions.

Best Practices: The page type configuration is the most important determinant of which page to load the Criteo Tag on. For example, if the page type is set to home, create a load rule to only load the Tag on home pages. The same consideration applies to the other page types. If you're dynamically setting the page type configuration through mapping, then create a more complex load rule to load the Criteo Tag on all the page types you specified.

4. Setting up Mappings

Mapping is the simple process of sending data from a data source, in your Data Layer, to the matching destination variable of the vendor Tag.

Note: This Tag requires the E-Commerce extension. As long as the E-Commerce Extension is properly added and configured, the Tag automatically sends the following data, depending on which page type is selected:

  • list: The first three product IDs shown on the page.
  • product: The product ID.
  • basket (cart): The product ID, price, and quantity of each item in the cart.
  • confirmation: The order ID, product ID, price, and quantity of each item in the cart.
Standard Mappings
  • Page Type (overrides default)

    Map the data source that identifies the page type. This allows you to dynamically set the page type configuration.

  • Search Keyword (for list page type)

    Map the data source that contains the keywords used for a search.

  • Product IDs (overrides _cprod)

    Map the data source that contains the product IDs. This overrides the E-commerce extension's mapping.

  • Customer ID (ci)

    Map the data source that contains your site's internal customer ID.

  • Sales Attribution (dd)

    Map the data source that identifies whether the conversion is attributed to Criteo or not. A value of 1 means yes, a value of 0 means no.

  • New Customer (nc)

    Map the data source that identifies if this is the first time the visitor converts. A value of 1 means yes, and a value of 0 means no.

  • Site Type (site_type)

    Map the data source that identifies the site time. There are three values that correspond to the site types:

    • m - This identifies a mobile site
    • t - This identifies a site displayed on tablets
    • d - This identifies a site displayed on desktops
  • PID

    Map the data source that contains the partner ID1 value. This allows you to dynamically set the Partner ID1 configuration.

  • wiSE

    Map the data source that contains the partner ID2 value. This allows you to dynamically set the Partner ID2 configuration.

  • wiTR

    Map the data source that contains the partner ID3 value. This allows you to dynamically set the Partner ID3 configuration.

  • Segment (si)

    Map the data source that identifies the segment the visitor belongs to.

  • Channel (loc)

    Map the data source that identifies the channel.


 

Vendor Documentation

E-Commerce Extension

Version history
Revision #:
5 of 5
Last update:
‎09-28-2016 03:52 PM
Updated by: