This exercise will walk you through the basic Data Layer 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.


For a review of all the aspects in the Data Layer tab, see:



Common Data Sources

The first thing will want to do is use the common data sources which are pre-configured bundles of – as the title suggests: common data sources used on multiple sites. These make it very easy to start of the Data Layer specification with standards. We also have bundles for popular CMS and eCommerce platforms, which make deploying the Tealium code AND exposing/populating the Data Layer, a breeze. We’ll import the
Wordpress Bundle since that is what is built on. Click the drop-down arrow on the right side of the
Add Data Source button and select Add Common Data Sources.Import the Wordpressand Event Trackingbundles.




Bulk Import From CSV

This feature allows us to bring in additional custom data mappings in mass. For our sandbox site we’ll get this information from the Tealium Wordpress Plugin. We’ve cleaned the list up significantly for the purpose of these exercises, but you can see that it is pretty extensive out of the box. It will also include the WooCommerce data, which we include in our CSV. This is a good way for you as a Partner to build out common data schemas for various industries or engagement types, and reuse.

We’ll start by opening the CSV in a text editor (note you cannotcopy/paste from Excel since that converts it to Tabs), selecting all the contents, copying, and then using the Bulk Import dialog.




Manual Entry

The other method of adding a Data Source is to just click the Add Data Source button directly (ie, not the drop-down), and manually enter the information. The data points are the same as the bulk import csv we used:



  • Source​ – This is the exact variable name that you are referencing. This must match capitalization and complete paths
  • Type​ – This tells us where to look for the Source variable name. This
  • could be the UDO, Javascript, Meta Tags, Cookies, or Querystring Parameters
  • Description​ – Don’t forget this
  • Alias​ – A user-friendly name that will appear in the drop-down menus throughout IQ


Let’s setup some Google Campaign tracking data sources using the below settings. This will pull from
the appropriate querystring parameters on inbound campaign links. In a later exercise we’ll use this for Analytics as well as Affiliate tag firing control. It’s important to remember that these will
onlybe set on the entry page, and not persisted (that is the later exercise).









Querystring Parameter

Google Campaign Name from click-through URL. Expect: Campaign_1, Campaign_2, etc

Google Campaign – Name


Querystring Parameter

Google Campaign Source from click-through URL. Expect: Google, Yahoo, AOL, etc.

Google Campaign – Source


Querystring Parameter

Google Campaign Medium from click-through URL. Expect: Banner, Email, CPC

Google Campaign – Medium


Querystring Parameter

Google Search Campaign Term from click-through URL. Expect: Product 1, Company Name, etc.

Google Campaign – Name



You can change the examples to any other media parameters that you use, such as Yahoo or Bing, or any other. Make sure that you keep track of substitutions for that later exercises you work with the appropriate replacement data source.




Save / Publish

Always remember to save after completing each exercise, or any time you’ll need to walk away from the UI. Hit the Save/Publish button in the upper-right – which should be orange now. Chose Save As, give it a title (starts pre-populated with a timestamp), and notes, but for now do not choose an Publish locations. Hit the Save button in the lower-right of this dialog.



Next Lesson:

Training Exercise- Tealium Demo – Load Rules lv 1