Back
 

Overview

Often when a first-time TMS user tags a site, they maintain the 1-to-1 mentality of tagging. Vendor documentation often also pushes this thinking by providing individual tags for each page type. In our earlier exercise – Training Exercise: Tealium Demo - Tagging lv 1 – we created 2 Criteo OneTag tags, and often it is more than just 2. If you look carefully, many times the only difference between each tag is a parameter to call out the site section, as is the case with our Criteo OneTag tags.

 

This exercise will walk you through some basic Extension Use Cases for TealiumDemo.com 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.

 

 


 

Lookup Tables – Consolidate Tags

https://community.tealiumiq.com/t5/Developers/Lookup-Table-Extension/m-p/2161

 

To combat this we can use Lookup Table Extensions to pass the Account, as well as the Event Name, fields to the tag dynamically, and then just use one tag across the entire profile. A Lookup Table extension looks at one Data Source for a Match, and then outputs the associated Value  to a Destination Data Source. For our exercise we’ll use the Domain and Pathname for simplicity, but in the Lv 2 module of this exercise we’ll use a cleaned-up page_type value.

 

Navigate to the Extensions tab, click the green Add Extension button, and then the Add button to the left of Lookup Table. Set the following values for each field:

 

  • Name – Criteo Account
  • Execution – Before Load Rules
  • Lookup Value In: domain
  • Destination – [ Click the + button and set: ]
  • Source – criteo_account
  • Description – Account name specific to domain
  • Alias – Criteo – Account
  • Match Table Values:

Lookup Match

Output

Note

www.tealiumdemo.com

tealiumdemo

Default Site

training.tealiumdemo.com

tealiumdemo-training

Training Site

yourprofile.tealiumdemo.com

tealiumdemo-yourInitials

Your Site

 

Be sure to change yourprofile, yourIntials, and Your Site, appropriately

 

 

Your extension should look as such:

 

image03.png

 

 

Now that we have a new Data Source (Criteo – Account) we need to map it to the Tag. Go back to the Tags tab, expand any Criteo tag, and hit the Edit button on Data Mapping section. From the Data Source drop-down select Criteo – Account, and then click Set Destination, and select Account ID (overrides account).

 

image04.png

image02.png

 

 

 Create another Lookup Table Extension. Set the following values for each field:

 

  • Name – Criteo Event Name
  • Execution – Before Load Rules
  • Lookup Value In: pathname
  • Destination – [ Click the + button and set: ]
  • Source – criteo_eventname
  • Description – Event name (tag type) specific to site section
  • Alias – Criteo – Event Name
  • Match Table Values:

Lookup Match

Output

Note

/product-category/

viewList

Category Page

/product/

viewItem

Product Page

/cart/

viewBasket

Cart Page

 

 

Your extension should look as such:

 

image00.png

 

 

Repeat the Data Mapping step, this time setting the Data Source to Criteo – Event Name to the Destination of Event(s) (overrides default).

 

image01.png

 

 

You can now safely delete the other Criteo OneTag tag, since we now have a single tag that runs across the site. Be sure to also Rename that remaining tag to remove – Category Pages.

 

 


 

Save and Publish

We’ve completed our first optimization and best practice. Let’s now Save and Publish to Dev/QA.