The Tag Manager feature includes a Chrome™ browser extension that a user (Customer Service Manager, trafficker, or an agency/advertiser analytics expert) can use to analyze a web page for variables. This extension can identify the tag manager's advertiser and create variables for that advertiser. It can also recognize data layer variables according to the data layer defined in Sizmek Ad Suite (SAS).
To install the Chrome extension, see Installing the Chrome Extension.
Note: This extension works in the Chrome browser only.
If there is a tag manager on the web page, the extension can scan the page and add variables to the advertiser for which the tag manager is defined.
If there is no tag manager on the web page, the extension will create variables under an advertiser that is specified by the user (according to the advertisers to which the user has access). The extension scan tool tries to obtain variables from one of the following data layers:
dataLayer (Google data layer)
utag_data (Tealium data layer)
universal_variable (Ensighten data layer)
tm_param (Tagman data layer)
If there is more than one data layer on a page, the user must select one.
Navigate to a web page.
Click the Chrome extension icon and select Analyze the webpage for variables.
If there are no data layer variables from any of the aforementioned data layers, the Chrome extension prompts the user to supply the data layer name and will try to analyze the page with the given data layer name.
Select the variables to add to the tag manager or advertiser and click Create on SAS.
The selected variables are added in one of the following ways:
To the advertiser that was specified by the user
To the tag manager’s advertiser, if there is a tag manager on the page
The selected variables are added to the advertiser that was specified by the user (or to the tag manager's advertiser, if there is a tag manager on the page).
Note: The Exists on Server column includes variables that already exist in SAS for the tag manager.
Note: The Variables list collects the initial value found on the page and is not affected by updates done to the variable on page after using the OneTag API (e.g. versaTagObj.generateRequest() ). If you observe a value change in a network devtool, such as Fiddler), this behavior is correct; the new value should not be passed to our servers. You will not see the new value in the Variables list, since this behavior is not in the scope for this tool.