This exercise will walk you through the basic Tagging configuration for sandbox accounts. To complete this exercise you will need a sandbox provisioned for you by your Channel Enablement Manager, after which you’ll have access to Tealium IQ, as well as the URL to access the sandbox site.


Tags are the snippets of vendor code that collects data and/or provides site functionality. For a review of all the aspects in the Tags tab, see:


Google Analytics


We’ll create a Google Universal Analytics tag first, since analytics tags are on every site has an analytics tag. We’ll use the out-of-the-box configuration, and have it run across the entire site. Navigate to the Tags tab, click the green Add A Tag button. This will bring up the Tag Marketplace, where you can search for Google Universal Analytics, and hit the green Add button.





This brings us to the Tag Configuration Wizard. All tags follow the same 3 steps:

  1. Tag Configuration – The basic/account settings provided by the Vendor
  2. Load Rules – When and Where you want the tags to load
  3. Data Mapping – Map the Data Sources from our Data Layer to Vendor variables

For this first tag we’ll leverage the Extract From Code button, and supply it the code that the Google Analytics Admin Dashboard gives us. This is also available in the Supporting Document – Tagging lv 1 file.






This is a SUPER basic configuration, so all it essentially does is set the UA/Tracking ID, but if you had other settings like Cross-domain tracking enabled, then those would be picked-up as well.






We’ll keep it assigned to the default Load on All Pages Load Rule.





We’ll skip the Data Mappings tab for this exercise, but will revisit in Tagging Lv 2.




Criteo OneTag (Retargeting)


Let’s create a simple Retargeting tag that will be served only on pages with products, that being Category and Product Pages. Open the Tag Marketplace again, search for Criteo, and add the Criteo OneTag tag.





We’ll set the Name to Criteo OneTag – Category Page, the Account to TealiumDemo, and we’ll change the Event Name to viewList.





Next we’ll set the Load Rule so that the tag only fires on our Category Page condition.





And then we’ll make our first use of Data Mappings so that we can pass it a list of Product ID’s for products shown on the page:


First click on the Data Sources drop-down, search for product, and select product_ids, then hit Destination:





Here we’ll be presented with a UI that changes based on the options available for this specific tag. We’ll select Product ID’s.





You should now have a configured tag for the Category page that looks like this:





Hit the Finish button. Now we need to create a tag for Product pages. On the left side of this new tag, below the logo, is a Copy button that we can use to duplicate this configuration. Click this.


Click one of the Edit buttons on the newly created Criteo tag. Change the Tag Configuration to have a Name of Criteo OneTag – Product Pages, an Event Name of viewItem, and then change the Load Rule to the Product Page condition. We’ll keep the same Data Mapping since we want to still pass the Product ID’s to the tag, but in this case it will simply be a single value.






Save and Publish

At this point we have a simple analytics setup, and a retargeting strategy. We’ll create some other tags later, but for now Save and Publish to Dev/QA. We’ll expand on these configurations  in our next exercise: Extensions lv 1.