Tealium Learning Center

Overview URLs (Uniform Resource Locators) are something that we all see and deal with all the time, but the terminology that relates to the component parts of the URL are often misunderstood. This post attempts to explain them. A URL usually consists of the following components: Protocol, domain, path (or pathname), hash and query string. Protocol is the technology that will be used to transfer the data, usually http or https Domain is the the domain name, tealium.com for example. Path relates to the section and page on the site Hash relates to a section within the page Query string contains data that is being passed to the page So if we look at a URL, you can see how it gets broken up: http://tealium.com/solutions/?example=test&example2=test2#section3 In the data layer In terms of the data layer, this would appear as dom.domain: "tealium.com" dom.pathname: "/solutions/" dom.query_string: "example=test&example2=test2" dom.hash: "section3" dom.url: "http://tealium.com/solutions/?example=test&example2=test2#section3" Load rule example This is typically useful for load rules, where you want tags to fire for specific sections or pages of the site. Lets say you have a site which consists of several domains, and you want a load rule so that tags fire for any page on domain1.com - you could create a simple load rule like this: Now how about if you only wanted to fire a certain tag on the homepage, and only on domain1.com Or if you wanted a load rule for any page in a support section, on any of your domains Or, you wanted section2 hash of any support page, or if there was a query string which contains support=true Hopefully these examples show how you can build a load rule based on the data layer URL components.   ... View more

If you have many Floodlight tags, all with a slightly different configuration, but based on the same load criteria, for example, different paths in the URL, rather than setting up several similar instances of the Floodlight tag, each with different load rules and configuration values, you can combine them into one instance of the Floodlight tag using some additional configuration. Google recommends migrating to the Google global site tag by implementing the Floodlight (gtag.js) tag. Floodlight was previously marketed as "DoubleClick Floodlight". In this article: Table of Contents Placeholder How It Works This multi-tag solution uses data mappings to set the Floodlight parameters dynamically and a lookup table to set the Floodlight values based on a data layer variable. The lookup table creates a delimited string containing multiple values per entry which can then be separated into individual Floodlight parameters using a JavaScript Code extension. New Data Layer Variables You will need the following variables for the data mappings in the Floodlight tag and for the lookup table extension.  The "dc_" prefix is a best practice to remind you that these variables are used for the Floodlight configuration. Create the following: dc_advertiserId (mapping) dc_type (mapping) dc_category (mapping) dc_counterType (mapping) dc_settings (lookup table extension) Data Mapping In this multi-tag solution the Floodlight parameters will be set dynamically based on the output of the lookup table extension, so the values must be set in the tag configuration using data mappings. Set the following data mappings: dc_advertiserId  set to  src dc_counterType  set to   countertype dc_type  set to   type dc_category  set to   cat Once completed the mappings will look like this: Extensions This solutions uses three extensions to construct all of the Floodlight tags we intend to fire. The following extensions will be added and must be ordered as they appear here: Lookup Table This sets a delimited string based on the selection criteria (in this case we will be using the URL pathname). Set Data Values This converts the delimited string from the lookup table into the separate Floodlight variables. JavaScript Code This verifies that a value exists for the tag to fire, otherwise it suppresses the tag.  Lookup Table Extension This extension will be used to set a delimited string based on a criteria variable. In this example, the criteria variable is the  pathname  variable and the delimited string is the  dc_settings  variable set in the following format: ADVERTISER ID|TYPE|CATEGORY|COUNTERTYPE To add this extension: Add a Lookup Table extension. Set the Title e.g. "DC Settings". Set Scope to the Floodlight tag you just added. Set Lookup Value In:  pathname Set Destination:  dc_settings   Set Variable Type: String Set Match Type: Contains  Each lookup table entry will contain a URL pathname and a delimited string value. This example uses the following entries: Pathname Output /test1/test 321123|Testing|Test001|standard /test2/test/something.htm 321123|Testing|Test002|standard /test1/docs 321123|Docs|Test003|standard  The Lookup Table extension should appear as follows: Use the Import from CSV... option to manage long lists. Set Data Layer Extension This extension will separate the delimited string into separate Floodlight variables. To add this extension: Add a Set Data Values extension. Set the Title e.g. "Floodlight Parameters". Set Scope to the Floodlight tag you just added. Set a variable for each of the Floodlight parameters: Set Variable Value Type Value dc_advertiserId JS Code   b['dc_settings'].split("|")[0]  dc_type JS Code   b['dc_settings'].split("|")[1]  dc_category JS Code   b['dc_settings'].split("|")[2]  dc_counterType JS Code   b['dc_settings'].split("|")[3]  The extension should appear as follows: Use the Add Condition to test that  dc_settings  is populated to ensure this will only run when there is a value. JavaScript Code This extension will suppress the Floodlight tag if the lookup table extension did not output a value (i.e. there is no tag to fire). This means that you can keep the "All Pages" load rule set on the Floodlight tag and it will not fire if there is no configuration for the current page. To add this extension: Add a JavaScript Code extension. Set the Title e.g. "Check Value". Set Scope to the Floodlight tag you just added. Enter this code: if(b['dc_settings']===''){     return false; } Publish your changes for testing. ... View more