In this article:
The Tealium Tag Marketplace currently offers over 900 tags. A tag loaded through iQ Tag Management runs identically to the same tag that you would hard-code into your web pages. A tag in iQ Tag Management has the following components:
Before you add your first tag, let's review how it works:
This example uses the Google Analytics tag, but you can use any tag. If you are adding your own tag, it will be helpful to have the vendor's code snippet or implementation guide for reference.
Use the following steps to add a tag:
Google Analytics(or another vendor name), select a tag, and click +Add.
UA-12345678-1(or your own tracking ID if you have a Google Analytics account).
Now that you have a basic data layer and your first tag, you're ready to set up a load rule to determine when the tag will be triggered.
A load rule determines when a tag is loaded on your site and when the tag fires. A rule is made up of one or more logical conditions based on values in the data layer. When a load rule is assigned to a tag, the tag is only loaded when the condition evaluates to true.
page_type variable is often used in load rules because its value represents the types of pages of your site, such as
order, which makes it ideal for creating rules to load tags on specific pages of your site.
The Universal Data Object (UDO) also contains built-in variables that collect basic information about the page where it's loaded. These variables include cookies created by utag.js, standard DOM variables from the page, and Tealium-specific variables about the loaded configuration.
The built-in variable named
domain will be used to demonstrate how data layer variables are used with load rules.
You can configure load rules directly from the tag configuration window or from the Load Rules screen. The default load rule is named
All Pages, which loads the tag on every page of your site where the Universal Tag (
utag.js ) is installed. To only load a tag on specific pages, create a load rule with the necessary condition.
Conditions are formed using the following parts:
greater than, or
is not populated.
This example load rule uses the
page_type variable to identify the shopping cart page.
equals (ignore case) cart
equals (ignore case)
The next step is to create a rule that identifies your live production website so that you can ensure that your tag is never loaded on your QA site. The rule checks that the built-in variable
domain does not contain
qa, which would indicate that it's the production site. If the domain is
stage.yourdomain.com, the rule evaluates to false and the tag is not loaded.
Use the following steps to add this load rule:
Great! Now you have a tag that only loads on the production site (only domains that do not contain
qa ). You're ready to apply a data mapping to send data to your tag.
A data mapping connects a value from the data layer to the corresponding variable in the vendor tag. For example, a vendor might collect page name information in a variable named
pName, but your data layer has this value in the variable named
page_name. To send the value of
pName, use a data mapping. After the data mapping is configured, the value from the data layer variable is always passed to the vendor variable when that tag is triggered.
To add a data mapping:
That's it! The Google Analytics tag is now configured to pass the value of
page_name from your data layer to the
Great job, you are well on your way! Now that you have successfully configured your new marketplace tag, you are ready to learn about extensions and how to use them.