Tealium Learning Center

This article describes how user permissions work in Tealium iQ Tag Management and describes the steps required to add and edit permissions for single or multiple users. For server-side permissions, see Managing Server-Side User Permissions. In this article: How it Works There are two categories of user permissions, account-level and profile-level, as described in the following sections. Existing users can view their permission settings and other information from User Settings. Account-Level Permissions Account-level permissions pertain to the management of the account, site scans, and profiles. The following table describes the available account-level permissions: Permission Description Manage Account Enables the user to assign account-level permissions for other users. Manage Profiles Enables the user to create, manage, and rename profiles for this account. Manage Site Scans Enables the user to run and delete site scans. All users can view site scans. Manage JavaScript Code Extensions Enables the user to edit JavaScript code extensions set up in the account. This permission only applies to legacy JavaScript code extensions.  Profile-Level Permissions Profile-level permissions are assigned using one of the following three methods: All Current and Future Profiles Use this option for Admin users or any user that requires access to all profiles for the account, including those that will be created in the future. Select from Currently Assigned Profile(s) Use this option to filter the available profiles to only those that the user is currently assigned. Select the profiles assigned from the Profile List. Select Profile(s) Use this option to edit permissions for the selected profiles in the Profile List. The following table describes the available profile-level permissions: Permission Description Manage Users Add, edit, and remove users and their permissions for this profile. Manage Tag Templates Edit and delete all tag templates for this profile Manage Resource Locks Apply and manage resource locks (labels) for variables, tags, load rules, and extensions. Save Existing Versions Perform a Save for this profile, which overwrites the existing configuration of the version with the new configurations. Ensure that users with this permissions understand the difference between performing a Save and a Save As. Apply labels to variables, tags, load rules, and extensions. Save As New Versions Perform a Save As for this profile. JavaScript Draft Promotion Promote drafts in the JavaScript Code extension to be published to Dev, QA, or Prod. Publish to Dev Environment Publish to the Dev environment and any custom environments added to this profile. Required to publish to custom publish environments. Publish to QA Environment Publish to the QA environment. Publish to Prod Environment Publish to the Prod environment. Adding a New User To add a new user, you must have Manage Account and Manage User permissions. Use the following steps to add a new user and assign permissions: On the user admin menu, select Manage Users. In the User Manager dialog, click + Add User. In the Create New User dialog, enter the user's email address in the New User Email field, then click Next. Select the account permissions for this user, then click Next. Select Select Profile(s). The list of profiles that you have access to is displayed in the Profile List. If you select multiple profiles, you can set permissions for each profile separately, or apply the same permissions to all the selected profiles. In the Profile List, select the profiles for which you want to assign permissions for the user, then click Next. Select one or more profile permissions to assign to the user, or select Select All Permissions. If you selected multiple profiles, you can click each profile to set permissions. To set the same permissions for all selected profiles, set permissions for one profile, then click Apply Permissions to Selected Profiles. When you finish selecting profile permissions, click Next. Review and confirm that the selected permissions and publish environments are correct, then click Finish. An activation email is sent to the user's email address. Click Close. Removing a User Use the following steps to remove a user's client-side access: On the User Menu, select Manage Users. In the User Manager dialog, select the user you want to remove. Click More and select Remove User. In the Remove User dialog, confirm the user to be removed, then click Remove User. The user no longer has access to the client-side profile. Changing User Permissions To modify a user, you must have Manage Account and Manage User permissions. Editing permissions for users is a separate process from adding or removing permissions. The following sections describe the methods used to edit user permissions: Edit permissions (add and remove) for a single user Add permissions for multiple users Remove permissions from multiple users Edit Profile-Level Permissions for a Single User Use the following steps to edit profile-level permissions for a single user: On the user admin menu, select Manage Users. In the User Manager dialog, select the user whose profile-level permissions you want to change. Click Edit/View User Permissions. Click Select Profiles(s). In the Profile List, select the profiles for which permissions need to be changed, then click Next. Edit the profile-level permissions for the user, then click Next. Permissions that are not selected are removed for the selected user.. Review and confirm that the updated profile-level permissions are correct, then click Finish. Click Close. Adding Profile-Level Permissions for Multiple Users Use the following steps to profile-level permissions for multiple users: On the user admin menu, select Manage Users. In the User Manager dialog, select the user accounts to which you want to add account-level permissions. In Bulk User Options, click Add Profile Permissions. Under Profile Options, select either All Current and Future Profiles or Select Profile. If you selected Select Profile, select one or more profiles in the Profile List. Click Next. Select the permissions to add to the user accounts or select Select All Permissions, then click Next. Leaving a permission checkbox blank or deselecting a permissions does not remove that permission from any selected user. Review and confirm that the selected permissions are correct, then click Finish. Click Close. Removing Profile-Level Permissions for Multiple Users Use the following steps to remove profile-level permissions for multiple users: On the user admin menu, select Manage Users. In the User Manager dialog, select the user accounts from which you want to remove permissions. Click More and select Remove Profile Permissions. This step does not remove the All Current and Future Profiles permission. Clicking Remove from Profile removes the users from this profile only. Select Select Profile. Select All Profiles to remove users permissions for all profiles to which you have access. If the users have the All Current and Future Profiles permission, selecting this option removes permissions from all current and future profiles. Select the profile-level permissions to remove from the user accounts, then click Next. The permissions selected to remove are highlighted in red. Leaving a permission unselected or deselecting permissions does not remove the permission from the user accounts. Review and confirm that the selected permissions should be removed, then click Finish. Click Close. ... View more

This article describes how to set up the Criteo OneTag tag in your Tealium iQ Tag Management account. In this article: Tag Tips Use mapping to: Override the value for Account ID Set values for required and optional parameters Trigger events and set values for event parameters Supported E-Commerce extension parameters: Order ID ( _corder ) List of Product IDs ( _cprod ) List of Quantities ( _cquan ) List of Prices ( _cprice ) Tag Configuration First, go to the tag marketplace and add the Criteo OneTag tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Account ID: Required For multiple accounts, use a comma-separated list. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Tag destination Description Account ID Criteo account number. Overrides account . email String Customer email address. retailer_visitor_id String Retailer Visitor ID A unique unauthenticated ID that is consistent over multiple sessions on the the same device. customer_id String Customer ID An identifier for an authenticated user that is consistent for all logged in sessions. Criteo requires that this ID not contain personally identifiable information such as names, email addresses, unencrypted phone numbers, etc. Leave empty if the customer is unknown or your site does not have unique IDs. This variable is not related to e-commerce extension _ccustid variable. site_type Site type. Version of the site. The value can be one of the following: m - The mobile version of your site t - The tablet version of your site d (default) - The classic version of your site. This is often the site that browsers access. hashed_email Hashed email. String Customer hashed email address. zip_code String Customer zip code. E-Commerce Tag Destination Description order_id Order ID Unique transaction identifier. Overrides _corder . Product IDs Array Products ID Unique identifier of each product in the product array. Overrides _cprod . Product Prices Array Unit price of each product in the product array. Overrides _cprice . Product Quantities Array Quantity of each product in the product array. Overrides _cquan . Events To trigger Criteo events on a page, map variables to these destinations. The event triggers when the supplied value is found in the data layer. Select an event from the Events drop-down list. In the Trigger field, enter the value of the variable being mapped. Click + Add. To map more events, repeat steps 1, 2, and 3. Event Name Description viewHome Home page viewed. viewCategory Product category viewed. viewSearchResult Search results viewed. viewItem Product viewed. viewBasket Cart viewed. viewList List of products viewed. addToCart Product added to cart. trackTransaction Transaction page activity. Load Rules Load Rules determine when and where to load an instance of Criteo OneTag on your site. Create custom Load Rules to load the tag on any page where you want trigger Criteo Events. For example, if you are tracking conversion events, load this tag on the checkout page or the confirmation page. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see Data Mappings. The destination variables for Criteo OneTag are built into the Data Mappings tab. The available destination variables are described in the following sections. Passing Parameters with Events To pass additional data with the Event destinations you mapped earlier, map variables to the corresponding parameters. If a user has filtered a product list, the filters can be included as parameters. To pass a parameter with a mapped Criteo event: Select an event from the Events drop-down list. Select a parameter from the Parameters drop-down list. Click + Add. The available parameters and filters vary depending on the selected event, as shown in the following table: Event Parameters Filters viewHome Page ID Custom None viewCategory viewSearchResult Item Keyword Category Page Number Page ID Custom Name Operator Value viewItem Item Price Availability Custom None viewBasket addToCart Page ID Custom ID Price Quantity viewList Item Custom None trackTransaction Transaction ID Custom ID Price Quantity Vendor Documentation Intro to the Criteo OneTag Criteo OneTag for Sponsored Products Criteo Support Center (login required)   ... View more

This article describes how to manage profile libraries in iQ Tag Management (TiQ). In this article: How it Works Libraries are used to manage configurations that are shared across multiple profiles. Consider the following points before you begin working with libraries: A profile can load one or more libraries, but libraries cannot load profiles or other libraries. A library is almost identical to a profile with the exception that a library can be imported into another profile. After an element from a library is imported into a profile, it cannot be edited. You can modify the tag configuration of an imported tag, as changes to tag configuration take precedence over library settings. After saving and publishing a profile with imported libraries, the resulting version and utag.js file  represent the entire profile configuration. Creating a Library Though all users in an account can see all libraries, only users with the Manage Profiles permission can create a profile library. Use the following steps to create a new library: In the user admin menu click Manage Profiles. The Manage Profiles window displays with all libraries and profiles for your account on the left. Next to Libraries, click Add. The Create Library dialog displays. In the Name field, enter the name for your library. As a best practice, devise a naming convention to differentiate your libraries from your profiles. For example, adding "lib-" in front of your library names makes it easy to determine if you are working with a library or a profile. Profiles and libraries cannot share names. Library names have the same limitations as profile names: no spaces, lowercase letters, numbers, periods, and dashes only. Select one of the following checkboxes to determine if the library is optional or required: Require All profiles to include library All profiles include this library automatically. Optionally include this library in other profiles You specify which profiles include this library. In Copy Elements From, check one or more boxes to select the specific elements you want to include from the profile or library you selected. The elements you select are copied from the profile/library that you are currently logged into. If you select none, you will create a blank library. Variables Extensions Consent Manager Load Rules Publish Settings Tags Users Click Create Library. Wait for the library to publish and display a success message. Click Apply. You must log into the library by selecting it from the account/profile menu and clicking Load Version. Editing a Library Use the following steps to edit a library: In the user admin menu click Manage Profiles. The Manage Profiles window displays with all libraries and profiles for your account on the left. Click the library you want to view and select the correct profile from the Profiles drop-down list and then click Edit. Select Require All profiles to include library or Optionally include this library in other profiles and click OK. When editing a library, the changes go into effect immediately. Although changing a required library to an optional library does not affect the profiles that are linked to it, changing an optional library to a required library automatically links the library to each profile. Click Apply to exit the window. Saving a Library Consider the following before saving your library: You may only perform a Save as action with a library. As a best practice develop a naming convention to keep track of your library versions.  Changes to a library do not automatically propagate to all the profiles that load it. You must re-publish each profile to include the changes to the library. Use the following steps to save a library: Click Save/Publish. Only the Save As option displays. Enter a title using your naming conventions. Enter descriptive notes about this version. Click which environments to publish to. Click Publish. Next, load the profiles that are linked to the library to import the latest changes and save the profile. Linking a Library to a Profile You may link a library to profile, or a profile to a library. After you create a link between a library and a profile, the next time you load the profile, the contents of the library will be imported. To link a library to a profile: In the user admin menu click Manage Profiles. The Manage Profiles window displays with all libraries and profiles for your account on the left. Select the profile to which you want to link a library from the profiles list on the left. You can optionally select a library to which you want to link a profile. Select the library from the drop-down list at the top of the window. Click + Link to Library. The library selected displays. Select the publish environment (Dev, QA, Prod) of the library you want to link to the profile. To remove a link, click Remove Link. You cannot remove a link to required libraries. Click Apply. Publishing Linked Profiles Regardless of whether the library is optional or required, additions of new libraries or changes to existing libraries require that you publish a new version of the linked profiles to import the latest library configurations. You must publish each profile individually. Use the following steps to determine which profiles are linked to a library: In the user admin menu click Manage Profiles. The Manage Profiles dialog displays. Under the Libraries section, click the library to inspect. The profiles to which this library is linked display in the main window on the right. The Library Version column displays which publish environment of this library the profile is linked to. Click Cancel to close the window. Identifying Library Elements in a Profile Consider the following when identifying library elements in a profile: Elements added from a library receive a label that indicates which library each element belong to. Tags added to a profile through a library receive a unique ID for that profile. This unique ID may be different than the ID that a tag receives when added to the library. Any tag, load rule, or extension added in a library will display as 'ON' in the profile that loads the library. You cannot turn off a library-loaded element from a profile that loads the library. You cannot remove data layer variables imported from a library. Deleting a Library Deleting a library is an irreversible action. Tealium recommends that you phase out the use of a library across all affected profiles prior to deleting. To delete a library, contact your account manager. ... View more

Omnichannel is a legacy feature that has been replaced by the File Import Data Source. Omnichannel is a feature for importing offline data into AudienceStream where it can enrich visitor profiles and trigger real-time connector actions. Before you begin: Preparing a CSV File for Import This guide has the following sections: How It Works  Learn about the process: from the basic components and import process to the final results within the Customer Data Hub. Using Omnichannel  Step by step instructions on configuring your omnichannel imports. Here's a quick overview of the omnichannel feature:  This guide covers the following topics: Table of Contents Placeholder How It Works The primary goal of an omnichannel import is to supplement online visitor profile data with valuable offline data. This is accomplished using two types of attributes: visitor and omnichannel. Visitor attributes define your visitor profiles and represent the unified view of your customer. Imported omnichannel attributes help complete this view of the customer via attribute enrichments. An omnichannel attribute must be used in an enrichment of a visitor attribute in order for its data to be imported. There are two components used in setting up an omnichannel file import: a file transfer service and a file definition. File Transfer Service The file transfer service is a secure location where you upload your files for Tealium to retrieve them. Tealium supports the following file transfer services: Amazon S3 (Tealium bucket or your own bucket) Microsoft Azure File/Blob Storage FTP/SFTP If using your own file transfer service, be sure to have the connection details ready before proceeding. File Definition A file definition is a detailed description of the CSV files to import. This includes the names of the files and the name of each CSV column (corresponds to a Customer Data Hub attribute). Each file definition must also specify a visitor identifier in each row of the file. This identifier links the imported data to visitor profiles in AudienceStream. Visitor Enrichment When a file is processed, the omnichannel attributes are used to create and update visitor attributes via enrichments. For this reason, it's important that your visitor attributes are configured to use the new omnichannel attributes in their enrichments. For example, if you are importing offline purchase data and want to update a visitor lifetime order value, create an enrichment in the visitor attribute to leverage the omnichannel attribute. Omnichannel Attribute: order_total_amount Visitor Attribute: Lifetime Order Value Resulting enrichment: Import Process After you have configured a file transfer service with a file definition, upload a file to the service. The omnichannel system then follows this order of operations: Check for New Files The system checks the file transfer service for new files every 10 minutes. When multiple files are uploaded at the same time using SFTP or S3, the files are processed in the order of the upload timestamp. Copy New Files When a new file is detected, it is copied from the file transfer location and processed in the Customer Data Hub. Match Filename Prefix to File Definition The prefix of the filename is used to identify which file definition to use when importing the data in the file. The file definition is used to identify which visitor ID attribute to use and which data attributes to import. Process Files The header line is read to identify the attributes being ingested. From there, the following processing is performed: Visitor Lookup: The visitor ID is used for a lookup of the visitor record in AudienceStream. If an existing visitor record is not found, a new one is created. Grouping rows with the same visitor ID increases the speed of the import. Attribute Enrichment: The visitor record is enriched according to the attributes imported and the existing enrichments in your account. EventStream/DataAccess Processing: If configured to do so, the imported data is made available to EventStream connectors and stored in DataAccess. Using Omnichannel Setting up an omnichannel enrichment requires you to configure a file transfer service and a file definition. To begin setting up an omnichannel enrichment, go to Sources > Omnichannel and click + Add Enrichment. The omnichannel dialog appears with a two-step process to configure a file transfer service and create a file definition. Adding a File Transfer Service To configure your file transfer service: Select a Service. The remaining fields change depending on the service selected. Enter a Title to identify this enrichment, preferably by its channel. For example, "In-Store Transactions". Enter the credentials necessary to access the service you selected. If you selected Tealium S3 Bucket, then the necessary credentials are generated for you automatically. (Optional) Enter notes to describe the enrichment. Click Next to proceed to file definitions. Adding a File Definition A file definition identifies the names of the columns in the CSV file. These column names automatically generate omnichannel attributes with the same names. In the next section, these attributes are used to enrich visitor attributes. Use these steps to set up a file definition and define omnichannel attributes: Click + Add File Definition. The file definition form appears. Send to DataAccess and EventStream Connectors - Check this box if the imported data should be made available to EventStream connectors and DataAccess storage. Unique File Prefix - Enter a prefix to identify these files. This prefix identifies which files on the file transfer service to retrieve. Visitor ID - Select a Visitor ID attribute from the Map drop-down. In the From text field, enter the name of the corresponding column from the CSV file. Omnichannel Attributes (CSV Column Names) - Enter the name of each column to import from the file. Each column creates a new omnichannel attribute with the same name, which is made available for use in rules, enrichments, and streams. Column names are case sensitive and may not contain "#", "^", or whitespace characters. Date Format - Columns with date/time values must have a matching date format setting. Click the calendar icon and select a data format. For example, "yyyy-MM-dd". Restricted Data - Check this box to mark a column as having restricted data and to exclude it from other Tealium services (for more information, see What is Restricted Data?). Click Save. Download/Copy Sample CSV  To see an example of what your CSV file should look like based on the file definition, click Download CSV or Copy CSV. The resulting file contains two rows of data, the header line with the column names and one row of placeholder data. Example sample CSV: "Email","OrderID","OrderDate","OrderTotal","TotalProductSpend","TotalShippingCharges" "example@email.com","yyyyMMdd","value_1","value_2","value_3","value_4" Using Omnichannel Attributes The next step is to configure your visitor attributes with enrichments based on the omnichannel attributes. Omnichannel attributes appear in the attribute drop-down menus for rules, enrichments, and streams. Use these steps to view the list of existing omnichannel attributes: Navigate to EventStream > Attributes. In the side bar, select the Omnichannel scope. Use these steps to enrich a visitor attribute with an omnichannel attribute: Navigate to AudienceStream > Attributes. In the side panel, under Scope, select Visitor. Select a visitor attribute to enrich. Add an enrichment. The omnichannel attributes are available from the attribute drop-down menus for use within the enrichment. F Uploading Omnichannel Files The final step is to upload your CSV files. You need a third-party application to initiate the upload. We recommend Cyberduck because it’s free and supports FTP and Amazon S3, but you may use any client for this purpose. To upload a file via FTP or Amazon S3 using Cyberduck: Install (or launch) Cyberduck. Create a new connection and give it a title. From the first drop-down list, select the file transfer service used in your omnichannel configuration. Enter the credentials (username and password) for your service. My FTP Connection and My SFTP Connection Tealium S3 Bucket - The credentials are pre-populated as Access Key (username) and Secret Key (password). Provide other details, such as the server, path, port, etc, required by your service. Read more about accessing third-party S3 buckets using Cyberduck. Save the connection. If you try to access an S3 bucket that is empty, the message "Listing directory / failed." may be displayed.  The workaround is to add ".s3.amazonaws.com" to the end of the information in the Path field and then cut and paste everything from the Path field into the Server field instead (leaving the Path field empty).  This is an issue only when the bucket is empty; after that the normal set-up works. You are now ready to upload files by dragging and dropping your CSV files into Cyberduck. When using S/FTP, the file must be located in the root folder. Omnichannel cannot locate files in the sub-folders of an S/FTP connection. Additional Resources Tealium Tool: Omnichannel Status Checker Omnichannel File Status API Verifying Omnichannel Imports Frequently Asked Questions What if the file transfer service fails? If AudienceStream fails to copy a file via the file transfer service, it waits 10 minutes and tries again. What if a file failed to be processed? When a process failure occurs, the file is ignored and no further attempts are made to process it. Submit a Support Desk request to get assistance diagnosing a problem with a failed import. File processing can fail for one of the following reasons: The CSV file is improperly formatted and is not a valid CSV file. The CSV file is not in UTF-8 format with no BOM encoding. The column names used in the File Definition do not exist in the file. Can files be encrypted with PGP/GPG? Omnichannel does not support PGP or GPG key encryption. FIles must be unencrypted before import. Can files be compressed? Compressed files can be imported. ... View more

SiteCatalyst is Adobe’s software as a service application offering Web Analytics to tracking how visitors interact with your site.   Tag Specifications and Requirements Specifications Name: SiteCatalyst Vendor: Adobe Type: Analytics Required Services: SiteCatalyst Account Configurations: S-Code Version Report Suite Server Server Secure Namespace Internal Link Filters Tag Configuration in Tealium iQ 1. Adding the Tag Tealium iQ's Tag marketplace offers a wide variety of Tags. Click here to learn how to add a Tag to your profile. 2. Configuring the Tag Here's a list of configurations for the SiteCatalyst Tag. You can find the values for the configurations in the s_code file provided to you by SiteCatalyst. Title: (Required) Enter a descriptive title to identify the Tag. S-Code Version: (Required) Select the version of SiteCatalyst you want to use. Versions H20 through H27 are supported. Report Suite: (Required) Enter the name of your SiteCatalyst report suite. You can find this value as s.account in your s_code.js file. Server: (Required) Enter the data collection server information. You can find this value as s.trackingServer in your s_code.js. file. Server Secure: (Required) Enter the secure (https) data collection server information. You can find this values as s.trackingServerSecure in your s_code.js file. Namespace: (Required) You can find this value as s.namespace in your s_code.js file. Auto Link Tracking: (Optional) The default selection is "Yes" and is the recommended selection. If you set this to "No", you will have to duplicate all the automatic link tracking with Tealium's link tracking extensions. You may still use Tealium's link tracking extensions for custom tracking even if you select "Yes". Download Types: (Optional) In this field list the types of file extensions that, when downloaded, you want to track as download links. For example, you could enter zip,exe,wav,mp3,mov,mpg,avi,wmv,pdf,doc,docx,xls,xlsx,ppt,pptx Internal Link Filters: (Optional) You must enter a value here, otherwise all link clicks will be reported as exit links in your SiteCatalyst report. In order to properly track link clicks that trigger a JavaScript activity such as a modal popping up you need to make certain you include "javascript" in the field. You can find these values as s.linkInternalFilters in your s_code.js file. Currency Code: (Optional) Enter the three-letter currency code of the currency you want your revenue data in. The default value is 'USD'. This is the default currency that SiteCatalyst will understand revenue data in your report suite. If a transaction occurs in another currency on your site, SiteCatalyst can do the currency conversion for you. You can find this value in the s.currencyCode in your s_code.js file. Use Dynamic Account: (Optional) Set to 'Yes' when you want to send data to different report suites based on the domain. Dynamic Acct List: (Optional) Enter the list of report suites and their corresponding domains to dynamically set the report suite based on domain. For example: testreportsuite=testing.example.com,qa.example.com;prodreportsuite=www.example.com S-Object Name: (Required) Keep this set at the default 's' unless you plan to run this tag alongside a completely separate implementation. Clear Vars: (Optional) Set this to 'Yes' to clears props, eVars, and events set in the global s object after each tracking request. Partner: (Optional) Enter your partner ID here. This is only required to use Adobe AudienceManager, so leave it blank if you do not use Adobe AudienceManager. You can find the partner ID value in the DIL.create call. Tip: Place this Tag near the top of the list in the Tags tab to ensure that it loads as soon as possible. The sooner the Tag loads, the sooner it captures visitors' activity. 3. Applying Load Rules Load Rules determine when and where to load an instance of this Tag. The 'Display on All Pages' rule is the default Load Rule. To load this Tag on a specific page, create a new load rule with the relevant conditions. Note: Since SiteCatalyst is an analytics Tag you will want it to load across your entire site, so we recommend leaving the default "Load on all Pages" selection as is. 4. Setting up Mappings Mapping is the process of sending data from a data source, in your Data Layer, to the matching destination variable of the vendor Tag. In order to properly format the Products String and send revenue data to your SiteCatalyst report suite, you must add and configure the E-Commerce Extension in your Tealium iQ profile. Note: As of the latest template update, linkTrackVars and linkTrackEvents are set automatically. You may have to update your template to the latest and greatest to take advantage of this. Standard Mappings pageName channel server hier1 through hier3 VisitorID s_account Map to this destination in order to dynamically set the account configuration. Events You can use mapping to trigger the following events events: prodView scOpen scAdd scRemove scView scCheckout purchase event1 through event100 For more information on Event tracking in SiteCatalyst via Tealium iQ, click here. Product-level Events Mapping here will add these events to the Products String. PRODUCTS_event1 through PRODUCTS_event100 Props Map data sources to these destinations to send them to SiteCatalyst as props. prop1 through prop75 eVars Map data sources to these destinations to send them to SiteCatalyst as eVars. eVar1 through eVar75 Merchandising eVars Map data sources to these destination to send them to SiteCatalyst as merchandising eVars. PRODUCTS_eVar1 through PRODUCTS_eVAr75 Commerce Map data sources to these destinations to send commerce data to SiteCatalyst. Much of this data is sent automatically via the E-Commerce Extension. purchaseID transactionID state zip Product IDs (PRDOCUTS_id) {Array} Product Categories (PRODUCTS_category) {Array} Product Quantities (PRODUCTS_quantity) {Array} Product Prices (PRODUCTS_price) {Array} Other Map data sources to the destinations below to send list data and the doneAction parameter. Link Tracking - doneAction param (H25 only) list1 through list3 Vendor Documentation General website Support site ... View more

This article explains how cookies from the Universal Tag (utag.js) work and how to work with your own cookies within Tealium iQ Tag Management. Additional reading: How Tealium Uses Cookies In this article: How It Works The Tealium Universal Tag (utag.js) creates and maintains several first-party cookies. The utag.js script creates and maintains a single cookie called utag_main . Within that cookie are several built-in values that keep track of the visitor session. These variables can be easily added to your data layer using the Tealium Built-In Data Bundle. The expiration time of the  utag_main cookie is set to one year. Built-In Cookies The built-in cookie variables are: Cookie Variable Description ses_id The Unix/Epoch timestamp of the session start, in milliseconds. _st The Unix/Epoch timestamp of the session timeout, in milliseconds - updated on new events. v_id A unique, partially random identifier. _ss A Boolean that indicates if the page viewed is the first in a session. A value of 1 means yes and 0 means no. _pn The number of pages viewed during the current session. _sn The number of sessions for this visitor. You can add custom values to the utag_main cookie by creating a new variable of type First Party Cookie with the prefix  utag_main_  for example: utag_main_mycookie . This keeps cookies associated with your Tealium installation separated from the global cookie namespace, which helps to avoid name collisions reduces the overall number of cookies used for your site. Cookies from Extensions The Persist Data Value, Split Segmentation, and Privacy Manager extensions create and leverage cookies when used. Persist Data Value (Cookie) The Persist Data Value extension allows you to create a cookie in which you can persist the value of a variable. To persist the value for a variable, you can create a new cookie or use an existing cookie. You may persist the value for a variable in the utag_main cookie by prefixing utag_main_ to the name of the cookie variable, for example: utag_main_mycookievar . Split Segmentation The purpose of the Split Segmentation extension is to divide visitors into segments you specify. The extension stores the segment data in the cookie variable you create. If this extension is scoped to Preloader, you must use a cookie other than utag_main . Privacy Manager The Privacy Manager extension uses a cookie named OPTOUTMULTI to save the privacy settings for a visitor for the next time they visit your site. The settings you select in Privacy Manager are saved as parameters in the cookie. Consent Manager The Consent Manager uses a cookie named CONSENTMGR to save the consent settings of a visitor.  Learn more about consent management. To change the name of the  CONSENTMGR cookie, first verify that you are using version 2.0.1 or higher of the cmGeneral template (using the Template Status Checker), then use a Javascript Code extension scoped to All Tags - Before Load Rules with the following code: utag.gdpr.cookieNS = 'NEW_COOKIE_NAME'; To change the retention period of the consent cookie, use the configuration override setting for utag.js. Cookies from Web Companion Web Companion uses a cookie to remember which publish environment (Prod, QA, Dev, or Custom) you were viewing when you last visited your site. Viewing the default publish environment for your site does not set a cookie. The last viewed publish environment is saved in the following cookie, where {account} and {profile} are replaced with your account and profile: utag_env_{account}_{profile} If you clear your browser's cookies, Web Companion does not remember which publish environment you were viewing, requiring you to re-select the environment to view. ... View more

This article describes how the Workflow Management feature works and how to use it. In this article: Table of Contents Placeholder How It Works The Workflow Management feature activates a workflow process where all publishes to the Prod require approval. Users without permission to publish to Prod can submit a publish request to Prod for approval by users with permission to publish to Prod. If approved, the changes will go to Prod, otherwise no publish occurs. While a version is pending approval, only approvers will be able to save changes to it. For this reason it is important for submitters to always perform a Save as when publishing to Prod. Familiarize yourself with the following terms and how they apply to Workflow Management when using this feature: Disabled When Workflow Management is disabled (default setting), the Prod publish target is only available to users with permission to use it. Enabled When Workflow Management is enabled, the Prod publish target becomes available to any user with either the Publish to Dev or Publish to QA permission. Submitter Users that submit requests to publish to Prod are called submitters. When a submitter submits a version to publish to Prod, it is sent to a queue of pending publishes where it must be reviewed before it will actually publish. Approver Users with the Publish to Prod permission are notified of the pending request and can approve or decline the submitted version. These users are called approvers. Workflow The workflow from submitter to approver is as follows: A submitter performs a Save as and selects Publish To: Prod. The saved changes are not actually published to Prod, but instead are sent to a queue to await review. An email is sent to all approvers notifying them of the pending publish to Prod request. Any approver can log into the account/profile to review the pending publish and take one of two actions: Approve – the changes are approved and the version is published to Prod. Decline – the changes are denied and no publish occurs. Setting Up Workflow Management The following sections describe how to enable Workflow Management from the Publish Settings screen and then adjust User Permissions by updating user permissions for your submitters and approvers. Enable Workflow Management Use the following steps to enable Workflow Management for your profile: Click Save/Publish. Click Configure Publish Settings in the upper right corner. The Publish Configuration dialog displays. (Learn More) In Version Workflow section, scroll down to Workflow Management and click On. Click Save. The Save/Publish dialog displays. Click Save As. It is important for the approver that the submitter uses Save As versus Save. If the submitter selects Save, the current version becomes locked for all submitters. Enter a new title and descriptive notes. Click one or more publish environments. Click Publish. Adjust User Permissions The workflow process is dependent on two types of users: submitters and approvers. The following sections describe how to adjust user permissions for each type of user. Submitter Permissions Submitters are users that cannot publish directly to Prod. Their changes must be approved through the workflow process. Submitters must have the Publish to Prod Environment permission removed. The Publish to QA Environment and Publish to Dev/Custom Environment settings should remain checked. Use the following steps to adjust user permissions for a submitter: Expand the user drop-down list in the upper right corner, and click Manage Users. The User Manager dialog displays. (Learn more). Click a checkbox to select an existing user or add a user and click Edit/View User Permissions. A new dialog displays. Click the Select Profiles radio button and leave the default value of the current profile in the profile list. Click Next. Ensure that Publish to Dev/Custom Environment and Publish to QA Environment remain checked. Uncheck Publish to Prod Environment and then click Next. Click Finish. Click Close to close the Edit/View User Permissions dialog. Save and Publish your changes. Approver Permissions Approvers are users that can publish directly to Prod and are responsible for reviewing pending publishes to Prod. Approvers must have the Publish to Prod Environment permission enabled. Due to the fact that all approvers receive email notifications each time a request for publish is submitted, it is best to limit the number of approvers in your profile. Use the following steps to adjust user permissions for an approver: Expand the user drop-down list in the upper right corner, and click Manage Users. The User Manager dialog displays. (Learn more). Click a checkbox to select an existing user or add a user and click Edit/View User Permissions. Click the Select Profiles radio button and leave the default value of the current profile in the profile list. Click Next. Check Publish to Prod Environment and then click Next. Click Finish. Click Close to close the Edit/View User Permissions dialog. Save and Publish your changes. Workflow Example Once you have enabled Workflow Management and set the publish permissions for your users, you are ready to see it in action. The following example shows the workflow process when Workflow Management is enabled. Submitting a Publish Request When a submitter makes changes, they save and publish to the Dev and QA environments freely and then an approver approves the change and published to Prod. A submitter uses the following steps to submit a request to publish to Prod: When changes are complete, click Save/Publish. Click Save As. Enter version notes. From the Publish Locations, select Prod - Approval Required Click Publish. A red box displays next to the Save/Publish button indicating that the publish is pending approval. After a Save as and a request to publish to Prod has been sent, submitters may no longer make changes to that pending version until the request has been approved or declined. Approving or Declining a Publish Request After a user has submitted a publish request, all approvers receive an email similar to the following regarding the request. Follow the instructions in the email and then navigate to the console to review the request. Use the following steps to approve or decline a publish request: In the sidebar, go to iQ Tag Management. Click the red box next to the Save/Publish button indicating the number of publish requests awaiting your review. The pending requests dialog displays. Click an entry to approve or decline. The publish notes and action buttons display. Mouse-over a the request to view the version notes. Click Approve or Decline. If you click Approve, the Save/Publish window displays and prompts you to save and publish as normal. Ensure that you select the Prod environment before publishing. If you click Decline, the request is declined and an email is sent to the requestor for further action. Click Close. ... View more

Dynamic Ads are a retargeting service that provides product recommendations to your visitors based on the products that they have interacted with. (Learn more). This article describes how to provide Facebook with data about the products a visitor interacted with in order for Facebook to take action on those events. In this article:0 Table of Contents Placeholder Prerequisites The steps describes in this article assume that you already have a Facebook account and that you have set up your Product Catalog in the Facebook Business Manager. This step allows Facebook to accurately retarget events based on the products a visitor has shown interest in. (Learn more). Set up Facebook Pixel in Tealium iQ First, you will need to add the Facebook tag in TiQ. (Learn more). If you have already added the Facebook tag, you can use that one. It is not required to add another instance.  Ensure that you are using the latest version of the Facebook tag template. To check what version you are on, use the Tag Status Checker. If it is not the latest version, update your template.  Set up Required Events The Dynamic Ads service requires you to fire the following three (3) Facebook events: ViewContent AddToCart Purchase Set up the ViewContent Event The ViewContent event indicates that a visitor viewed a product and is typically fired on a product detail page. At a minimum, you must provide the content_ids and content_type parameters with this event for Dynamic Ads, as described below. A ViewContent event is usually associated with the viewing of a product, which can be tied to a page load. For this reason, it is useful to examine the data sources present when the page load occurs. Use the following steps to set up the mapping for the ViewContent event: From the Facebook tag, click the edit icon. Click the Data Mappings tab. From the Data Sources drop-down list, select a data source that uniquely identifies a product page. In this example, page_type is used. Click the Events tab. In the Trigger field, enter the page_type  value for the product page. In this example, “product detail page” is used. From the Event drop-down list, select ViewContent. Click + Add. An orange text field displays with your mapping. Click Close to submit your mapping.   Save and publish your changes to save your settings. Set up the AddToCart Event The AddToCart event indicates that a visitor added a certain product to their cart or shopping basket. This event also requires content_ids and content_type  parameters for Dynamic Ads, as described below. The action of adding an item to a cart is typically tied to a button click on a product page. In order to fire an AddToCart event, you must key off of the value of a data source for that event. In this example, the event_name data source is used. Use the following steps to set up the AddToCart event: From the Facebook tag, click the edit icon. Click the Data Mappings tab. Select the data source that indicates when an AddToCart event fires. In this example, event_name  is used. Click the Events tab. In the Trigger field, enter event_name  value for an add-to-cart event. In this example, “cart add” is used. From the Event drop-down list, select AddToCart. Click + Add. An orange text field displays with your mapping. Click Close to submit your mapping. Save and publish your changes to save your settings. The Purchase Event You do not have to set up a mapping for the Purchase event if you already have the E-Commerce extension set up with the order ID mapped. If you have the e-commerce extension configured, the purchase event will automatically fire when an order ID is populated. (Learn more). If you do not have the E-Commerce extension, set up the Purchase event using theViewContent event setup steps as a guideline. Use a mapping based off of page_type equaling “order confirmation” as an example. Set up Required Parameters to Send with Events Each of these events requires that you send certain parameters, namely content_ids and content_type . Setting up additional parameters such as value , content_name , and currency can help inform your analytics with more meaningful data. If you have the E-Commerce extension set up, these data sources will be automatically mapped for you. The content_ids Parameter The content_ids parameter contains the IDs or SKUs of the products viewed by your visitor. If you have the e-commerce extension configured, these parameters are mapped and populated by the data source you selected for the List of Product IDs field in the extension.  (Learn more). If you do not have the E-Commerce extension or you want to use another data source, map a data source to the content_ids parameter for each of the three (3) events. The content_type Parameter The content_type parameter indicates to Facebook whether the content/product IDs signify a single product or a group of products. You must set this parameter to either “ product ” or “ product_group ”, respectively. To accomplish this, use the Set Data Value extension.. This requirement is specific to Facebook. It is unlikely you already have a data source that is doing this for you. Use the following steps to set content_type with a Set Data Value extension: Add a Set Data Value extension. (Learn more). Use a descriptive title such as “Facebook: Setting content_type”. Set the scope of the extension to your Facebook tag. This extension is only needed for the Facebook tag and only needs to run when the Facebook tag loads. To create a data source, click the plus (+) button next to the Set drop-down list. Use a meaningful name for the data source, such as “fb_content_type”. The purpose of this data source is to provide the value for content_type .   In the To: field, ensure that Text is selected. Enter “product” or “product_group” in the text field. An extension that sets a data source with the proper value for content_type is now created. To add this new data source in mapping for the Facebook tag, click the Data Mappings tab. From the Data Sources drop-down list, select your “ fb_content_type ” data source. Click the Parameters tab. This allows you to set up the parameter mappings for the event of your choice. From the Event drop-down list, select the first event that you want to map content type to, starting with ViewContent . From the Parameter drop-down list, select Content Type. Click + Add\. A blue text field displays in the Mappings dialog indicating that your mapping was successful.   Repeat the steps above for the AddToCart and Purchase events.   Click Close. Click Apply to submit your mappings. Save and publish your changes to save your settings. Troubleshooting Facebook provides the Facebook Pixel Helper browser extension in Chrome. Adding this extension to your Chrome browser will provide information on the events that fired on a page, what parameters the events contained, and errors detected by Facebook. (Learn more). ... View more

These are legacy versions of Tealium's mobile solutions. Please use the new 5.x series libraries.     How Tealium's Mobile Libraries Work Full Library Compact Library Collect Library How Tealium's Mobile Libraries Work In order to leverage Tealium's mobile solution, you must add our code, that is one of our mobile libraries, into your app's code. Depending on what tracking approach you want to take, we offer several libraries to meet your needs. If you're not sure which library is best for you, talk to your Tealium account or deployment manager. Tealium's libraries, with the exception of the Collect library, use a webkit object in order to leverage Tealium's Tag management system. The webkit object is like a web browser, but it doesn't display pages in your app. This allows your app to run JavaScript, primarily Tealium's Tag management code and load Tag vendor code. Your mobile developers must include Tealium's library into the app's code. The instructions that mobile developers need in order to add Tealium's libraries to your app are publicly available on Github. For a directory of the repos for each platform, see this article. So the question remains. Which library should you use? Back to top Full Library Tealium's Full library tracks standard data on stock events and screenviews automatically. The Full library automatically tracks: UI events: interactions with UI elements, such as buttons non-UI information: application data, device info, carrier data, and timestamps lifecycle events; app launch, wake from background, and sleep video event tracking: play, pause, stop The Full library also gives you access to a couple useful tools: Mobile Companion AudienceStream traces for your mobile app In addition, you can track whatever custom data you choose by having your developers set it up in the app's native code. The Full library does track a lot of data automatically, but you may find that you don't want to tracking absolutely everything. This is often too much data! If that's the case, take a look at the Compact library instead. Back to top Compact Library The Compact Library is smaller, taking up less memory and less time to initialize. For the most part you'll have to specify what you want tracked with the Compact library. However, there are a few things it will track automatically: Lifecycle events: app launch, wake from background, and sleep Device info: model, CPU, device specifications, etc. Timestamps: The time when each event occurred If you want to track screenviews and any other events, you need to treat those as custom data tracking and set them up manually in the app's code. While this may take more initial effort, the library ends up being smaller and running more efficiently than using the Full library. Full vs. Compact Comparison Tracking Compact Full Custom Data Tracking Yes Yes Device Data Tracking Yes Yes Lifecycle Tracking Yes Yes Offline Tracking Yes Yes Timestamp Tracking Yes Yes UI Autotracking No Yes Video Tracking No Yes Screenview Autotracking No Yes Tools AudienceStream Trace No Yes Mobile Companion No Yes Note: For more information on the types of tracking described above, see our mobile features list, located in Tealium's Github repo. Back to top Collect Library Use the Collect library when you want to leverage AudienceStream as your primary approach to mobile. Unlike the Full and Compact libraries, the Collect library doesn't use a webkit at all; event tracking and integration with AudienceStream is handled within the app's native code. The main purpose of this library is to capture how users interact with your app and send that data directly to AudienceStream. From there, AudienceStream can connect with other vendors to do things like triggering emails or push notifications. Enriched data can be retrieved as well, allowing your developers to program actions in-app in response to the new visitor data. As a final note, we recommend that you use the latest version of whichever library you select. The latest version addresses bugs and supports the newest features. Back to top ... View more

In most cases where the Customer Container tag might be used, the Tealium Generic Tag is a simpler solution that satisfies most tagging needs. The Custom Container is only needed for advanced tags and will require writing JavaScript code to complete. This article describes how to configure the Tealium Custom Container Tag. The Tealium Custom Container is a tag that provides a JavaScript template with a code framework for implementing any kind of JavaScript tag. See Related: Tealium Generic Tag Tealium Pixel Container Tag In this article: Prerequisites About Tag Templates Manage Templates permission How It Works The Tealium Custom Container uses the same code template as official integrations found in the Tag Marketplace. Tags built with the Custom Container can leverage native functionality of iQ such as built-in E-Commerce extension variables, data mappings, event tracking, and other extensions. While it is best practice to use a pre-built tag from the Tag Marketplace, if your desired tag is not available then you have a few options for adding the tag. The majority of tags can be implemented using either the Tealium Generic Tag or the Tealium Pixel Container tag. Implementing the Tealium Custom Container tag requires writing JavaScript code to modify the tag template. You should be comfortable with reading unfamiliar JavaScript code and customizing it for your needs. Tag Template Overview First, go to the Tag Marketplace and add the Custom Container Tag (see how to add a tag). The Custom Container does not have configuration fields, but it does support the use of load rules, data mappings, and extensions. Data Mappings Configure data mappings just as you would for other tags. Data mappings are stored in the tag template variable u.data .  The Custom Container tag only supports custom data mappings and name you choose in the mapping toolbox is the same you will use in the tag template code to reference the value. For example, if you map customer_id to a custom destination named user_id , then in the tag template, whereever you need to use this value, reference it as u.data['user_id'] . Code Structure Most of the work to set up the Custom Container tag will take place in the tag template, the underlying code of the tag. The following steps assume you are familiar with how to manage tag templates and that you have the necessary permissions. ​​ The following table lists the different sections of code, each of which begins with /* Start */ and /* End */ comments within the template. Template Code Description Notes Tag Library Code Experienced users may add static library functions, or a 3rd party URL to instantiate and load library code. Lines 21-22. This section is empty by default. Tag-Scoped Extensions Code ##UTGEN## is a placeholder area where the publish engine later inserts the code for Tealium iQ extensions, scoped to the tag. Lines 56-59. Do not edit this section. Mapping Code This section makes a one-to-one mapping between the selected values and items that have been mapped into the template as part of the u.data object. Lines 62-71. The default code works for majority of use cases. Test any changes thoroughly. Tag Sending Code The vendor's tag requires specific data to be processed or formatted first before the vendor URL is called. Lines 74-78. Changes typically include URL modifications, changing a datapoint value to meet vendor specifications, formatting data into query string parameters, ect. Loader Callback Function   Some tags may require data be sent after their JavaScript file has been loaded, these data changes should be done within the loader callback to ensure proper timing. If the tag requires any changes or formatting for the data this can also be done in the loader callback function. The same u.data values available before a file is loaded will be available in the callback. Lines 81-93. Uncomment the // comments to enable use of the loader callback function, which allows you to load external JavaScript files. Within the loader callback function, insert the JavaScript code to run after the external JavaScript file has loaded. The line u.initialized=true; prevents the JavaScript file from being loaded a second time if there is a utag.view or utag.link call, as most tags requiring an external JavaScript files should not have it loaded again. Loader Callback Tag Sending Code The JavaScript code that runs after the external JavaScript file has loaded. Lines 86-90. Loader Function Call Allows you to load several types of files by the tag you are implementing, such as external JavaScript files. Uncomment the // lines, as needed. Lines 96-108. Uncomment line 100 for the loader to call for iframe image requests. Uncomment line 101 for the loader to call for script to load the path to an external JavaScript file. Uncomment the if-else code to load the callback of the u object is not inititialized and to prevent the requested files from running twice. If your tag does not need a callback, set "cb":u.loader_cb to "cb":null instead. c.join(u.data.qsp_delim) is a query string sample, where c is a key-value array, and base_url has the '?' pre-appended. Template Variables The following table describes the variables found in the custom container template. Code Description tv Template version, in the format: version.YYYYMMDD. Formatting and content of this comment is important as various systems, such as Tag Status Checker, use them for template control and verification tc Template comments, that describe modifications to the file. u The first thing created is the u object, which will contain all of the properties and functions necessary to construct whatever the vendor tag/service requires. id Property of the u object that is set to the tag’s UID. utag.o[<ACCOUNT.PROFILE>] .sender Global object that gets an entry (object) with property. utag.ut Modern templates depend on this object, and some old versions of utag.js don’t create. This object is referenced, or created if missing. utag.js A match is created from the version of this file as it's executing. The input is in the format similar to ut4.45.201805212154 , grabbing the substring between the two dots (between ut4. and the subsequent . ). utag.ut.loader A function that is referenced for use by the template. If the loader function is undefined, doesn’t see a legitimate match (as determined above), or the second substring of the match is less than the number specified, the template’s definition of the loader function is used. This function is responsible for making the necessary image, iframe, or script request. The exact resource is configured later in the template when the function is invoked. If, for some reason, the loader function comes in undefined, a definition is provided as a fallback. utag.ut.typeOf A function, with a similar check to utag.ut.loader , that provides similar functionality to the typeOf operator, but does not return ‘object’ for null , and returns a more descriptive value for various data types, both basic and abstract, using the toString() function. u.ev This object is created, containing a lookup of which Tealium events ( view or link ) the template will respond to. This check occurs at the beginning of the u.send function. ##UTGEN## The first publish engine marker, where the publish engine inserts the code for Tealium iQ extensions scoped to the tag. u.map Object containing the look ups for the parameter and events mappings. u.extend Array containing the extension function definitions. Occasionally an extension is added with the purpose of returning false as a way to stop the tag from executing fully. u.callBack The callback made by the script/image/iframe request, and will in turn invoke u.loader_cb u.loader_cb Callback function invoked by u.callBack . u.send Function that accepts two arguments, a and b , with various u.send -specific parameters defined: a - The type of event string such as view or link . b - The data layer (copy) passed to the template file. c - The for loop counter that executes extensions. d - The u.map object key iterator for the for…in loop. e - The array that contains the split on , of a particular mapping. This allows checking against multiple mappings f - The for loop iterator of the e array that sets mapped values into the u.data object. g - (reserved/do not use) h - The array that contains the split on : for event mapping. u.data Object populated with configurations from Tealium iQ. ##UTVARconfig_<UI configuration>## is the marker for the publish engine to insert those values. The <UI configuration> corresponds to the ID of the object in the configFields array in utui.config.before-min.js/utui.config.js u.data.base_url The base URL variable. This is the URL to load the vendor file without dynamic values or the fully dynamic URL. utag.DB Debug statements to indicate execution of the tag. E-Commerce Variables When using values from the E-Commerce extension we strongly recommend that you make a template specific variable with a copy of each value. Modifying the original values, for vendor specific formatting, may have adverse affects on your other tags. u.data.order_id = u.data.order_id || b._corder || ""; if (u.data.product_id.length === 0 && b._cprod !== undefined) { u.data.product_id = b._cprod.slice(0); } Tealium Event Variable Using the tealium_event variable can be helpful when different events require different handling. You can create an if or switch statement to determine which vendor tracking calls to make based on the Tealium tracking call recieved. tealium_event defaults to either "view" or "link" when no other event is set. Examples Example 1: Load and Track Purchases The following code was provided by a vendor, and needs to be incorporated into the tag template. The code is separated into two major parts, commented as Part A and Part B. This code demonstrates a common pattern used in JavaScript tags where an external JavaScript file is loaded (Part A) and then a vendor object variable is set with dynamic values to trigger a tracking call (Part B). In the tag template code this convention is accomplished using the following two functions: u.loader - Called once per page load to load the vendor's external JavaScript library. u.loader_cb - Called upon completion of u.loader and upon subsequent tracking calls on the page. This example also shows how to use the built-in E-Commerce variables. Original Script // Part A <script type=text/javascript src="https://services.xg4ken.com/js/kenshoo.js?cid=000-00-00-000-00000"></script> // Part B <script type=text/javascript> kenshoo.trackConversion('0000','000-00-00-000-00000', { /*OPTIONAL PARAMETERS. FILL VALUES OR REMOVE UNNEEDED PARAMETERS*/ conversionType: 'lead', revenue: 0.0, currency:'USD', orderId:'', promoCode:'', customParam1:'', /*any custom parameter. example: Airport: 'JFK'*/ customParam2:'', /*any custom parameter. example: Rooms: '3'*/ customParamN:'' }) </script> Set the Base URL In Part A, a JavaScript URL is being loaded with a custom query string parameter named cid . The cid value needs to be dynamic. To load an external JavaScript file in the Customer Container, set the base_url value within the u.data object on line 51. This value is used later in the code by the u.loader function. 47 u.data = { 48 /* Initialize default tag parameter values here */ 49 /* Examples: */ 50 /* "account_id" : "1234567" */ 51 "base_url" : "https://services.xg4ken.com/js/kenshoo.js?", 52 "cid" : "" 53 /* A value mapped to "account_id" or "base_url" in TiQ will replace these default values. */ 54 }; Loader Callback Function Once the external file is loaded using u.loader , we want the callback function to run. Update the section "Loader Callback Function" by uncommenting lines 84-85 and 91. This callback function, u.loader_cb , is called after the external file is loaded. The following snippet shows the completed section in the tag template: 81 /* Start Loader Callback Function */ 82 /* Un-comment the single line JavaScript comments ("//") to use the Loader callback function. */ 83 84 u.loader_cb = function () { 85 u.initialized = true; 86 /* Start Loader Callback Tag Sending Code */ 87 88 // Insert your post-Loader tag sending code here. 89 90 /* End Loader Callback Tag Sending Code */ 91 }; 92 /* End Loader Callback Function */ Loader Function Call The following snippet shows the completed section in the tag template. Uncomment line 101 as shown in this example: 96 /* Start Loader Function Call */ 97 /* Un-comment the single-line JavaScript comments ("//") to use Loader. */ 98 99 if (!u.initialized) { 100 //u.loader({"type" : "iframe", "src" : u.data.base_url + c.join(u.data.qsp_delim), "cb" : u.loader_cb, "loc" : "body", "id" : 'utag_##UTID##' }); 101 u.loader({"type" : "script", "src" : u.data.base_url, "cb" : u.loader_cb, "loc" : "script", "id" : 'utag_##UTID##' }); 102 } else { 103 u.loader_cb(); 104 } 105 106 //u.loader({"type" : "img", "src" : u.data.base_url + c.join(u.data.qsp_delim) }); 107 108 /* End Loader Function Call */ Tag Sending Code This code runs when the Custom Container tag loads. It's where you initialize the data needed to run the tag. In this case, we append the dynamic cid parameter to the base URL (this requires a mapping to cid or to have put a default value in the u.data variable to load the correct file) and we copy the e-commerce data we need from the built-in variables. Update the Tag Sending code, below line 76, to the following: 74 /* Start Tag Sending Code */ 75 76 // Insert your tag sending code here. 77 u.data.base_url = u.data.base_url + "cid=" + u.data.cid; 78 u.data.orderId = u.data.orderId || b._corder || ""; 79 u.data.revenue = u.data.revenue || b._csubtotal || ""; 80 u.data.currency = u.data.currency || b._ccurrency || ""; 81 u.data.promoCode = u.data.promoCode || b._cpromo || ""; 82 /* End Tag Sending Code */ Next, we have to determine when to track conversions ( kenshoo.trackConversion ). One option is to use tealium_event and key off of specific event names. Another option is to use your own variable with a value which states a conversion or a specific kind of conversion is occurring. This gives you flexibility in what data points are sent with each event. You may use use a check for a conversion code value which is a unique required parameter for the conversion event. This method allows you to check for only one matching value but may limit the way you send optional parameters. In this example we are using the option to check for the conversion code variable. We'll map this value to conversionCode in the UI but not put it into the u.data object manually within the template, like we did with base_url and cid . This method ensures that when we check for conversionCode existing it will only do so because a value of some kind exists. Update the tag template as follows: 84 u.loader_cb = function () { 85 u.initialized = true; 86 /* Start Loader Callback Tag Sending Code */ 87 88 // Insert your post-Loader tag sending code here. 90 if(u.data.conversionCode){ 91 kenshoo.trackConversion(u.data.conversionCode,u.data.cid, { 92 conversionType: 'lead', 93 revenue: 0.0, 94 currency:'USD', 95 orderId:'', 96 promoCode:'', 97 customParam1:'' 98 customParam2:'', 99 customParamN:'' }) 100 } 101 /* End Loader Callback Tag Sending Code */ 102 }; There are a few options for putting the optional data into the object that is sent in the call since any items not used should be removed. Hard Coded Parameters Leave the object directly in the call with only those parameters that you will always use, the values reference to their u.data variables (names will come from your UI mappings). If you are only ever sending the same parameters this option is easy to use but if you need various parameters sent per event this will be difficult without having set up each event type individually. Conditional Parameters Create an object variable for custom parameters and use if statements to conditionally set each parameter. If you have more than a few custom parameters this may become a rather exhaustive list. Loop and Exclude Parameters Create an object variable for custom parameters and loop through the u.data object, setting each variable as a custom parameter but excluding variables known not to be custom parameters. This could have unexpected results if any additional data points are within u.data which you may not wish to send but have not prevented being added. In this example we'll use the loop and exclude method. For each variable in u.data , set a corresponding variable in the custom parameter object optionalParams . Exclude known parameters base_url , cid , and conversionCode . 84 u.loader_cb = function () { 85 u.initialized = true; 86 /* Start Loader Callback Tag Sending Code */ 87 88 // Insert your post-Loader tag sending code here. 89 var key, optionalParams = {}; 90 91 if(u.data.conversionCode){ 92 for (key in u.data) { 93 if (key !== "base_url" && key !== "cid" && key !== "conversionCode") { 94 optionalParams[key] = u.data[key]; 95 } 96 } 97 kenshoo.trackConversion(u.data.conversionCode, u.data.cid, optionalParams) 98 } 99 /* End Loader Callback Tag Sending Code */ 100 } At this point, the JavaScript file loads and a triggers trackConversion if the  conversionCode  condition is met. Check that all values came through as expected in the query string and make adjustments to your individual code as necessary. Example 2: Initialize, Load, and Track Code Snippet The following code was provided by a vendor and needs to be incorporated into the tag template.. This code snippet is separated into four major parts, commented as Part A, Part B, Part C, and Part D. This code demonstrates a common pattern used in JavaScript tags where a vendor object variable must first be initialized (Part A), then an external JavaScript file is loaded (Part B), then dynamic values are used to trigger a tracking call (Part C), and an iframe variant of the tag is provided for pages that don't run JavaScript (Part D). // PART A <script type="text/javascript"> if (!window.mstag) mstag = {loadTag : function(){},time : (new Date()).getTime()}; </script> // PART B <script id="mstag_tops" type="text/javascript" src="//flex.msn.com/mstag/site/b7381bb8-71e7-408c-91d0-3adb90b5c736/mstag.js"> </script> // PART C <script type="text/javascript">mstag.loadTag("analytics", {dedup:"1", domainId:"1516122", type:"1",revenue:"", actionid:"264766"}) </script> // PART D <noscript> <iframe src="//flex.msn.com/mstag/tag/b7381bb8-71e7-408c-91d0-3adb90b5c736/analytics.html?dedup=1&domainId=1516122&type=1&revenue=&actionid=264766" frameborder="0" scrolling="no" width="1" height="1" style="visibility:hidden;display:none"> </iframe> </noscript> Part A: Tag Sending Code This code is used in the "Tag Sending Code" section. The vendor's tag requires specific data to be processed or formatted first before the vendor URL is called. Update the tag template as follows: Delete the comment that says // Insert your tag sending code here. on line number 76 Copy the code between the <script> tags from Part A , and paste it on line number 76. The following snippet shows the completed section in the Template Config file: 74 /* Start Tag Sending Code */ 75 76 if (!window.mstag) mstag = {loadTag : function(){},time : (new Date()).getTime()}; 77 78 /* End Tag Sending Code */ Part B: Loader Function Call This code is used in the "Loader Function Call" section. This script is synchronous and will complete before continuing before the next step. Add a variable to u.data for script_id, which will store the client-specific part of the base URL ( b7381bb8-71e7-408c-91d0-3adb90b5c736 ). Update the tag template as follows: Uncomment line numbers 99 and 101-104. Edit line 101 by replacing the value of "src" with the vendor's base URL, and ID (using mapped variables). The following snippet shows the completed section in the tag template: 96 /* Start Loader Function Call */ 97 /* Un-comment the single-line JavaScript comments ("//") to use Loader. */ 98 99 if (!u.initialized) { 100 //u.loader({"type" : "iframe", "src" : u.data.base_url + c.join(u.data.qsp_delim), "cb" : u.loader_cb, "loc" : "body", "id" : 'utag_##UTID##' }); 101 u.loader({"type" : "script", "src" : "//flex.msn.com/mstag/site/" + u.data.script_id + "/mstag.js", "cb" : u.loader_cb, "loc" : "script", "id" : "mstag_tops" }); 102 } else { 103 u.loader_cb(); 104 } 105 //u.loader({"type" : "img", "src" : u.data.base_url + c.join(u.data.qsp_delim) }); 106 107 /* End Loader Function Call */ Part C: Loader Callback Function This code is used in the "Loader Callback Function" section. Before proceeding, map the variables that appear dynamic, such as domainId and actionid . Update the tag template file as follows: Uncomment line numbers 84-85 and 91. Delete the comment that says // Insert your post-Loader tag sending code here on line number 88. Copy the code between the <script> tags from Part C, and paste it on line number 88. Override the values of domainID and actionid with u.data.~ variables (using mapped variables). The following snippet shows the completed section in the Template Config file: 81 /* Start Loader Callback Function */ 82 /* Un-comment the single-line JavaScript comments ("//") to use this Loader callback function. */ 83 84 u.loader_cb = function () { 85 u.initialized = true; 86 /* Start Loader Callback Tag Sending Code */ 87 88 mstag.loadTag("analytics", {dedup:"1",domainId:u.data.domain_id,type:"1",revenue:"",actionid:u.data.action_id}); 89 90 /* End Loader Callback Tag Sending Code */ 91 92 }; 93 /* End Loader Callback Function */ Part D: No Script Option This code is provides a fallback option for the case when a browser does not support JavaScript, or has JavaScript disabled. Since Tealium requires JavaScript, this fallback code is not an option. Therefore, you can ignore this code. Save Template To save a new version of the template without overwriting the original file, click Save Version Template. Otherwise, click Save Profile Template to overwrite the original file. ... View more

The Previous Page extension is used to persist the name of the previous page for use on the subsequent page. See the full list of available extensions. In this article: Table of Contents Placeholder Prerequisites utag v4.38 or higher. (See: How to upgrade utag.js) How extensions work How it works The Previous Page extension adds a variable to the data layer named previous_page_name . The value of this variable is set to the value of a data layer variable from the previous page. You specify which data layer variable to use as the page name and the extension will save this value in a cookie so that it can be used on subsequent pages. Here is a simple example where page_name is used. It shows what value to expect in previous_page_name as a visitor navigates through a series of pages. Notice that previous_page_name is not set on the first page in the session. Page page_name previous_page_name Home Page "Home - Welcome" (not set) Search Page "Search for iPhone" "Home - Welcome" Product Page "iPhone 10 Product Details" "Search for iPhone" Using the Extension Once the extension is added, the following configuration option is available: Page Value: Select the data layer variable that contains the page's name. The extension automatically saves the value of this variable and sets it to previous_page_name on the next page view. ... View more

The Modal Offer extension enables the insertion of a modal overlay on any pages to alert the user of promotions, call to actions, or offers. See the full list of available extensions. In this article: Table of Contents Placeholder Prerequisites About Extensions How It Works The Modal Offer extension generates a modal pop-up window on the page. The content and appearance of the pop-up is configured based on the Modal Publish Mode selected: Standard: Content is set by entering text into three fields: header, body, and footer. The height and width may also be specified. Custom: Content is coded by editing the CSS and HTML directly. The pop-up is launched based on the condition applied to the extension. Example modal pop-up with placeholder content: The extension runs in the DOM Ready scope on every page, but only runs when the defined condition evaluates to true. Using the Extension To begin setting up the Modal Offer extension be sure to have the content of the modal prepared so that you're ready to enter it into the configuration. Once the extension is added, the following configuration options are available: Modal Publish Mode: Set the content of the modal pop-up using the Modal Publish Modes Standard: (Default) Uses a simple template where you type in the content of the modal and adjust the height and width. In standard mode the window appearance follows these rules: The modal is always centered. The font style of the modal is inherited from the <body> element. The CSS of the modal is a set of Tealium defaults. A dark div element is added to block out the rest of the page while the modal is up. The size of the header, body, and footer elements are a percentage of the window height and width. Custom: Allows you to edit the CSS and HTML of the modal pop-up directly for a custom behavior. To configure the modal pop-up in custom mode edit the CSS code for modal window styling definitions, and the HTML code for the modal window template. The CSS and HTML contain placeholders in the form of ##VALUE## that reference the settings from the standard publish mode. For example, ##MDLWIDTH## refers to the "Window Width" setting. Replace these placeholders with your own custom values or leave them intact to be populated by the values from the standard settings. If you customize the _tealiumModalClose button, be sure you keep the onclick="utag.extn.mdlW.dismiss() function. Click Reset at the bottom of the extension to return all of the code to its default state. Modal Header - The text to appear at the top of the window. Modal Body - The text to appear in the middle of the window. Modal Footer - The text to appear at the bottom of the window, after the line separator. Window Height - (Default: 200) The height of the window in pixels (px). Window Width - (Default: 300) The width of the window in pixels (px). Click Add Condition to control when this modal pops up. Click the + button inside the Condition box to add an AND condition. Click the + button outside the Condition box to add an OR condition. Click the - button inside the Condition box to remove an AND condition. Click the - button outside the Condition box removes an OR condition. If you do not set a condition the modal pops up on every page. Example Launching the Modal Directly By default the modal runs at DOM Ready and pops up if the applied condition is true . To launch the modal window at a different time, or based on more sophisticated logic, apply the following changes: Block the default modal launch: Apply a condition that always evaluates to false to block the modal from launching. Launch the modal directly: Find the UID of your Modal Offer extension (found in your iQ profile on the Extensions screen): Use the following JavaScript code to launch the modal window, replacing {UID} with the UID from above: // Replace {UID} with the UID of the Modal Offer extension to trigger // For example "utag.modalExt_72.js" utag.ut.loader({ src: utag.cfg.path + 'utag.modalExt_{UID}.js?utv=' + utag.cfg.v, cb: function() { utag.extn.mdlW.load(); } }); Use this code anywhere in your iQ configuration to launch the modal offer. By using this code in a JavaScript Code extension or a jQuery onHandler extension, you can customize the launch behavior of the modal offer window. Additional Reading: Triggering the Modal Offer Extension (Use Cases) FAQ Can I add multiple Modal Offer extensions to my profile? Yes, but only one modal offer is displayed on a web page at a time. If you add multiple instances of the Modal Offer extension be sure that each one has a different condition. ... View more

This article is about the Lookup Table extension and how to configure it. The Lookup Table extension is used to map the value from one data layer variable to set the value in another variable. See the full list of available extensions. In this article: Table of Contents Placeholder Prerequisites Universal Tag (utag.js) 4.38 or higher How it Works The Lookup Table extension provides a way to set the value of one data layer variable based on the value of another variable using a list of lookup values.  For example, if you need to set category names but the data layer only provides values for category IDs, the Lookup Table extension provides a mapping of category ID to category name. A sample mapping could be category ID 35 mapped to category name  iQ Tag Management and category ID 38 mapped to category name  Mobile . When configuring the Lookup Table extension, set the Lookup Value In field to the lookup variable, which is the source variable from the data layer.  Then set the Destination field to the variable you want to set based on the lookup entry.  The Variable Type, field specifies the data type of the lookup variable (String or Array). The lookup variable is compared to the lookup match values based on the Match Type. The match type may be set to "Exact" to use an exact, case-sensitive comparison, set to "Contains" to use a substring [contiguous sequence of characters within a string] comparison, or set to a regular expression pattern (for advanced users). The lookup table is configured by adding lookup values and output values entries in the Lookup Match field and the Output field.  From the example above, the lookup value  35 would appear in the Lookup Match field, and the output value  iQ Tag Management would appear in the Output field. If the value of the lookup variable matches an entry, then the Destination variable is set to the Output value. If the value of the lookup variable does not match an entry, then the output value is set according to the default value specified by the Default Output field. For example, if this is set to Unknown , then when no match is found for the lookup variable, the output variable is set to "Unknown" in the data layer. Additional conditions may be applied to the extension by modifying the Conditions setting.  Using the Extension Before you begin, familiarize yourself with how extensions work. To use the Lookup Table extension, set up the following configurations: Lookup Value in: Select the source lookup variable from the data layer that contains the value you want to look up.  Destination: Select the variable to set to the associated output value. Click the + button to create new variable.  Variable Type: Select the data type (string or array) of the lookup variable's value. If you select array, any output goes into the same array index as its corresponding Lookup Match. Match Type: All lookups are done using the selected match type. Exact: Matches the value of the lookup variable exactly (case sensitive). Contains: Matches a substring [contiguous sequence of characters within a string] value of the lookup variable. RegExp: Matches regular expressions to the value of the lookup variable. Escape characters are escaped [given special meaning] with two backslashes \\ . The ignore case flag, i , is automatically applied. Lookup Match: Enter the value of the lookup variable. Do not use quotation marks in the value. Output: Enter the value to be set for the destination variable when a lookup match is found. Do not enter quotation marks in the value. Note: (Optional) Add notes related to each lookup match and output value. The content of the note is not passed to the destination. Default Output: Enter the default value for the destination variable, for the case where the lookup match is not found. Select the "Disable Default" box to disable the default value. Import from CSV Manually entering the mapping data between the lookup variable values and the output values is time-consuming if there are many lookup values. Another option is the Import from CVS feature, which allows you to paste or enter data formatted as comma-separated values (CSV) in a text area box.  The data is entered in the following format, where each value is separated by a comma: Lookup Value, Output Value, Note The Note value is optional and may be left blank.  The following example adds 5 lookup/output values pairs to the mapping: 38, Mobile, forums 35, iQ Tag Management, forums 46, AudienceStream, forums 34, DataAccess, forums 48, Digital Strategy, forums When you have completed entering the mappings for the lookup table, click the Replace button to replace all existing mappings with the new ones from the CVS text area, or click Append to add these new mappings and keep all original mappings in the lookup table.  Export to CSV The Export to CVS button exports the lookup table mapping data to a file called lookup.csv .  The file is automatically downloaded to your computer, and may be opened with either Excel, or any text editor software.  The lookup table mapping data is exported as comma-separated values (CSV), where each row is one entry in the format:  Lookup Value, Output Value, Note At least one mapping row must be present in order to perform a successful export.  If the optional Note field is blank, then only the Lookup Value , and Output Value  displays for that row. If all the fields are blank, data is not exported.  The following example shows the contents of the lookup.csv file, when exporting the mapping from the Import to CVS example shown above: 38, Mobile, forums 35, iQ Tag Management, forums 46, AudienceStream, forums 34, DataAccess, forums 48, Digital Strategy, forums Example Lookup Table for mapping Category IDs to Category Names The Lookup Table extension allows you to match a data layer variable such as category_id to another variable such as category_name , as shown in the following example: Select the lookup variable category_id from the Lookup Value in drop-down menu. Select the readable value variable  category_name  from the Destination drop-down menu. If the variable is not found in the drop-down menu, click + to add the variable. In the Default Output field, enter "none". The value of category_name is set to "none" when the category_id value is not found on the lookup table mapping. Select String for Variable Type, since the variable  category_id  contains only one ID per category. Select "Exact" for Match Type if you know the exact category IDs. Repeat the following steps to create a lookup/output value mapping for each lookup variable, mapping each category ID to a readable category name value: Enter a category ID in the Lookup Match field, such as 38 . Enter a category name in the Output field, such as Mobile . (Optional) Add relevant notes in the Note field. Click the + button to add another lookup/output value. When the Lookup Table extension runs, if one of the lookups matches the output value of the category_id variable, then the  category_name variable is populated with the value set in the Output. For example, if category_id is 46 , then category_name is set to  AudienceStream . FAQ Q: What happens if the lookup variable matches multiple values in the table? A: Lookups are performed in the order they appear in the extension and the first match wins.   Q: Is the match type "Exact" case sensitive? A: Yes. The “Exact” match option is case sensitive. ... View more

The Join Data Values extension combines multiple text values into a single text value using a character seperator character called a delimiter. See the full list of available extensions. In this article: Table of Contents Placeholder Prerequisites How Extensions Work How It Works The Join Data Values extension combines two or more text values into a single text value using an optional delimiter. The delimiter is a single character such as / , - , or : that will separate each joined value in the final value. A default value can be set to be used in place of any variable that does not have a value when the extension runs. The joined value can come from either the data layer or a text value you enter. This extension supports conditions. This extension uses the JavaScript join() method to concatenated multiple variables with the delimiter character. Avoid delimiter characters that could also appear in the joined values. Using the Extension Once the extension is added, the following configuration options are available: Destination: The variable to store the joined values. Choose an existing variable from the drop-down list or create a new one by clicking the + button. Delimiter: The character to separate each variable in the final text value. Enter a single character, such as / , - , or : . Leading Delimiter: (Default: No). Determines if the delimiter will also be applied at the beginning of the joined values. Default Value: The default value to use in place of a joined variable that does not contain a value. For example, ''unset'' or "blank". Join: The list of variables to join into a single value. Click the + button to add another variable. Click the - button to remove a variable. Select the option Text Value to enter a custom text value. Sample: A sample value to validate the correct delimiter and variables. Condition: Click Add Condition to set a condition to determine when this extension will run. Example Dates Join separate date variables to create a standard date string. Use a different delimiter or order of variables to create the desired date format. Input Variables year="2020" month="12" day="31" Delimiter - Joined Value date="2020-12-31" Page Hierarchy Create a structured page hierarchy value by combining site_section , page_category , and other page level variables. Example Input Variables site_region="en-us" site_section="Electronics" category_name="Tablets" Delimiter : Joined Value page_hier="en-us:Electronics:Tablets"   ... View more

Use the Flatten JSON Objects extension to convert a nested data layer object into a new object with only one layer of key/value pairs. For more advanced options in converting a data layer, see the Data Layer Converter. In this article: Table of Contents Placeholder Prerequisites About Extensions Requirements utag v4.38 or higher. (See: How to upgrade utag.js) How It Works   The following are a few examples that demonstrate how the Flatten JSON Objects extension works: Objects such as parent -> child are flattened as parent.child . Array objects such as parent -> array -> [obj1,objN] are flattened as parent.array0.obj1key and parent.arrayN.objNkey . For arrays an additional parent.array.array-size value are set automatically. Using the Extension Once the extension is added, the following configuration options are available: JSON Object: A JSON object variable that you wish to flatten. Output Object: Output object variable to contain the results. Example Here is an example of a JSON object including a parent -> child relationship and an array: var person_object = { "firstName" : "John", "lastName" : "Doe", "age" : 25, "address" : { "streetAddress" : "1234 Main St", "city" : "Los Angeles", "state" : "CA", "postalCode" : "90010" }, "phoneNumber" : [ { "type" : "home", "number" : "310-555-1234" }, { "type" : "fax", "number" : "310-555-5678" } ] }; When flattened the object becomes: var person_flatobject = { "address.city" : "Los Angeles", "address.postalCode" : "90010" "address.state" : "CA", "address.streetAddress": "1234 Main St", "age" : 25, "firstName" : "John", "lastName" : "Doe", "phoneNumber.array-size" : 2 "phoneNumber0.number" : "310-555-1234" "phoneNumber0.type" : "home", "phoneNumber1.number" : "310-555-5678" "phoneNumber1.type" : "fax" }; If items from the new object need to be referenced as data layer variables, use the notation as stated in person_flatobject . For example, access the "state" data in the address as person_flatobject.address.state .  ... View more

Use the Domain-Based Deployment extension to load a QA or Dev version of the Universal Tag (utag.js) based on the hostname. This is typically used for validation purposes when you have the Prod instance of utag.js loading on your QA or Dev sites. See the full list of available extensions. In this article: Table of Contents Placeholder Prerequisites About Extensions  How it Works The Domain-Based Deployment extension loads a QA or Dev version of the Universal Tag (utag.js) based on hostname (the JavaScript window variable  location.hostname ).  When  utag.js  loads in the page, the Domain-Based extension is executed immediately and checks the current hostname for matches to any of your declared environments. If there's a match, the appropriate environment version of utag.js is loaded. Using the Extension Once the extension is added, the following configuration options are available: Dev Domains: Enter the development environment domain that you want to use for testing. For example, dev.tealium.com . QA Domains: Enter the QA environment domain that you want to use for testing. For example, qa.tealium.com . Click the plus button (+) to add a new Dev/QA environment, or the minus button (-) to delete a Dev/QA environment. Example Your production website contains the following script: <script type="text/javascript"> (function(a,b,c,d){ a='https://tags.tiqcdn.com/utag/my_account/main/prod/utag.js'; b=document;c='script';d=b.createElement(c);d.src=a;d.type='text/java'+c;d.async=true; a=b.getElementsByTagName(c)[0];a.parentNode.insertBefore(d,a); })(); </script> In the example, the environment is prod (not qa or dev). When this utag.js file is loaded, the Domain-Based extension is executed immediately and checks to ensure that the current hostname is dev.tealium.com or qa.tealium.com (or other declared environment). If the hostname matches any of the declared environments, the appropriate environment is then loaded. The following examples shows the utag.js files that would load for this example: dev.tealium.com <script type="text/javascript"> (function(a,b,c,d){ a='https://tags.tiqcdn.com/utag/my_account/main/dev/utag.js'; b=document;c='script';d=b.createElement(c);d.src=a;d.type='text/java'+c;d.async=true; a=b.getElementsByTagName(c)[0];a.parentNode.insertBefore(d,a); })(); </script> qa.tealium.com <script type="text/javascript"> (function(a,b,c,d){ a='https://tags.tiqcdn.com/utag/my_account/main/qa/utag.js'; b=document;c='script';d=b.createElement(c);d.src=a;d.type='text/java'+c;d.async=true; a=b.getElementsByTagName(c)[0];a.parentNode.insertBefore(d,a); })(); </script> When you view the site traffic, if a non-production environment is detected, /prod/utag.js loads first and then /dev/utag.js or /qa/utag.js . Any subsequent utag.#.js  files that load are served from the respective Dev or QA environment. ... View more

The Currency Converter extension allows you to convert the value of a data layer variable from one currency to another. In this article: Table of Contents Placeholder Requirements utag v4.38 or higher (How to upgrade utag.js) Tealium Currency Converter Tag (can be scoped to All Tags or any specific tag) How It Works The Currency Converter extension works with the Tealium Currency Converter tag, which makes the exchange rates available to the extension. The extension coverts the value of a data layer variable in one currency into a different currency. The extension may be configured to convert many data layer variables. Each conversion is controlled by a load rule to help run the conversion only when needed. Using the Extension Before you begin, familiarize yourself with how extensions work. Once the extension is added, click Add Currency Conversion to add a new conversion, then set the following fields (repeat this step as needed): Convert: The data layer variable containing the value to convert. On Condition: The load rule used to trigger the conversion. From Currency: The currency of the current value. To Currency: The currency of the new, converted value. Example On your site, customers can make purchases in any currency, but one tag vendor always expects amounts to be sent as USD values. Here are the components needs to convert a data layer variable from many currencies into USD: Currency Load Rules: Create a load rule for each currency that a customer might use, such as: site_currency equals (ignore case) GBP Currency Converter Extension: Add a currency conversion for each currency that your site supports and for each data layer variable that needs to be converted. Notice how this example is scoped to the specific tag that requires all values be sent in USD. ... View more

The Tealium Multi-CDN infrastructure (mCDN) is designed to deliver files to our customers' websites as quickly and reliably as possible. The mCDN leverages multiple content delivery networks (CDNs) in real-time to determine the fastest delivery node in the respective geographic region. In this article: Table of Contents Placeholder How mCDN Works The mCDN is responsible for the delivery of all files from the tags.tiqcdn.com domain. This includes the main iQ Tag Management loader file, utag.js, all tag loader files (utag.#.js), and any hosted data layer files. A web page with Tealium's JavaScript library (utag.js) installed makes a request to tags.tiqcdn.com. The local DNS server instructs the browser to contact DynDNS to resolve the host. DynDNS uses Cedexis to select the best performing CDN. Cedexis uses last mile data coupled with the requesting browser's geographic location to determine which CDN performs best and directs the browser to that CDN. The selected CDN responds with the requested file.   ... View more

Extensions provide a variety of ways to customize your implementation by offering a simple configuration interface to add complex logic without the need for coding. In this article: Table of Contents Placeholder Overview Extensions have many purposes, from setting and updating data layer variables, to adding advanced event tracking to your site. The available extensions are presented in the Extensions Marketplace where they are grouped by category with brief descriptions of their functionality. The extensions categories are: Standard Data Set and modify data layer variables and cookies in a variety of ways. Advanced Extensions that require some knowledge of JavaScript and/or advanced marketing strategies. Events Extensions related to event tracking, either using jQuery, built-in tracking, or mapping the standard Tealium events. Tag Specific Extended functionality for use with certain tags, such as Adobe Test & Target, or tags that require currency conversion. Privacy Extensions to offer opt-in/opt-out, Do Not Track, or tracking preferences for your users. Use the search box to find an extension across any tab. The extension marketplace is like a toolbox filled with a variety of different tools to help you with tag management. We encourage you to familiarize yourself with all of the available extensions so that you'll know exactly how to solve your next tag management challenge. For additional information, see the Master List of Extensions. How It Works When an extension is added to your configuration, then saved and published, the logic in the extension is converted to JavaScript code that then runs in the utag files that load on your website. The timing of the extension depends on several factors, including: the scope setting, the execution order setting, and the position of the extension in the list. Understanding Scope When adding an extension it is important to understand the scope setting. The scope determines which utag file the extension is published in and when the extension runs. Extensions within the same scope will run in the order that they appear in the user interface. The following scope options are available: utag Sync – For use with the JavaScript Code or Advanced JavaScript Code extensions. Associates an extension to the utag.sync.js file. Pre Loader – Runs before the data layer is processed and results are applied globally (code appears in utag.js). Before Load Rules After Load Rules DOM Ready Extensions – Runs once, at the DOMContentLoaded browser event (code appears in utag.js). Tag Scoped Extensions – Runs only when the specified tags run and changes are only applied for that tag (code appears in tag-specific utag.#.js). Any data layer values modified in this scope will not affect other tags. See Execution Order for more information about exact timing. After Tags Extensions – Runs after tags are triggered. If you set Scope to utag Sync, Pre Loader, or DOM Ready Extensions you must set Occurrence to Run Once. The scopes Pre Loader and Tag Scope are guaranteed to run in that order, but DOM Ready extensions will execute independently from the other three. In most standard implementations the DOM Ready scope likely occurs sequentially after the other three, but this timing should not be assumed. Some extensions, such as E-Commerce, Pathname Tokenizer, jQuery, and onHandler 1.7, have a pre-set scope that cannot be changed. Understanding Execution Order The execution setting offers more granular control of the timing of an extension. The following options are available: Before Load Rules – runs after the data layer is processed, for example after Pre Loader but prior to evaluating load rules. After Load Rules (default) – runs after load rules are evaluated. After Tags – runs after tags have been triggered. utag Sync – Runs first when using with JavaScript Code or Advanced JavaScript Code extensions by associating the extension to the utag.sync.js file. For a detailed overview of extension execution order see Order of Operations. Conditions Some extensions support conditions. Conditions are like load rules, but only applied to extensions. A condition applied to an extension will determine if the extension should run within the given scope and execution order. Managing Extensions Adding an Extension Use the following steps to add an extension: In the sidebar, click iQ Tag Management > Extensions. Click + Add Extension. Browse the extension categories using the multi-tab menu and click + Add next to the extension you want to use. Enter a Title to identify the extension. (Optional) Click Apply Labels on the left to add a label to categorize the extension. Under Scope, select a scope from the drop-down list or click Edit Load Order. Learn more about the Load Order Manager. Click Apply. Configure additional settings pertinent to the extension. Editing an Extension Extensions are editable directly from the extensions view. Expand an extension and adjust the configuration. As changes are detected the Save/Publish button will turn orange to indicate unsaved changes exist. Tealium does not recommend editing the uTag Sync extension. Reordering Extensions Use the Load Order Manager to change order of extensions. There are two ways to change the order that extensions execute: by scope and by position. By Scope Changing the scope of an extension will affect the order of its execution. For example, an extension can be made to execute sooner by changing the scope from Before Load Rules to the Pre Loader or by changing the execution from After Tags to Before Load Rules. By Position Click and drag an extension up or down to the new location. This method only affects extensions within the same scope. In other words, changing the position of an extension scoped to Pre Loader only has effects if it also changes the position of other Pre Loader extensions. To learn more, see Load Order Manager. Duplicating an Extension An easy way create an extension is by copying an existing one that has similar functionality. Use the following steps to copy an extension: Expand an extension. In the left side panel, click Duplicate. A copy of the original extension is added to the bottom of the extension list. Adjust the configuration of the new extension as needed. Deactivating an Extension To turn off an extension and still keep it in your account for later use, use the on/off switch. This is usually a better option than permanently deleting the extension because you will not lose the effort of the initial configuration. Use the following steps to deactivate an extension: Click the On/Off toggle next to the extension to deactivate. A confirmation dialog displays. Click Deactivate to confirm your action. Deleting an Extension If an extension is no longer needed, it can be deleted permanently from the configuration. Use the following steps to delete an extension: Expand an extension. In the left side panel click Delete. A confirmation dialog displays. Click Drop Extension to confirm the action. If you accidentally delete an extension and have not saved the profile, you can reload the browser to return to the original state of your extensions. Sort Sort the list view of extensions using the Sort menu. Changing the order of items in the list view does not change the execution order of the extension. The following sort options are available: Load Order First to Last Last to First Title A to Z Z to A UID Ascending Descending View Filters The list of extensions can quickly grow to a large number, so it can be difficult to find what you need. Use the Filter drop-down list to find a specific group of extensions quickly. The following filters are available: Hide Inactive Items Check this box to hide extensions that have been turned off. Label Filter extensions by label. Last Published (Location) Filter extensions by their publish location in the most recent publish. Publish Location Filter extensions by their publish location. Scope Filter extensions by scope, including those scoped to a specific tag. Type Filter extensions by their type, for example all Set Data Values extensions. Publish Locations The publish location settings control which environments the extension will be published to. If you uncheck a publish location, the extension will not be published to that location. For example, if you uncheck Prod for an extension, and then publish to Prod, that extension will be omitted from the files in the Prod environment. The following publish locations options are available: Dev The development (Dev) environment is a non-production environment intended for sandbox configuration. QA The Quality Assurance (QA) environment is a non-production environment intended for testing prior to releasing to production. Prod The Production (Prod) environment is the environment you intend to load on your live website. Custom Optional. The Custom Environments selection only displays if previously configured using Custom Environments. Publish locations can be used to prevent extensions that are in development from accidentally being published to Prod. For example, you may be working on a new extension and need it active for your QA environment, but do not want it to be included in any publishes to Prod. In this case, you simply uncheck the Prod publish location and the extension can remain active and not affect your Prod environment. ... View more

The Set Data Values extension sets the value of a data layer variable using text, another data layer variable, or JavaScript code. See the full list of available extensions. In this article: Table of Contents Placeholder Prerequisites utag v4.38 or higher. (See: How to upgrade utag.js) Familiarize yourself with how extensions work. How it Works Use this extension to set the value of a data layer variable using text, another data layer variable, or JavaScript code. The data layer variable is specified in the Set configuration option, and the new value assigned is specified in the To field. Multiple variables can be assigned in one instance of the extension. An optional condition may be added to control when the value is assigned. Using the Extension Once the extension is added, the following configuration options are available: Set: The data layer variable to set. Select from a drop-down list of variables. Create a new variable by clicking the + button next to the drop-down. To: The value to assign to the variable.  Click the + button to set another variable, or the - button to remove a variable from the extension. The value can be one of these options: Text: set the value to a text value that you type. Variable: set to the value of another data layer variable. JS Code: set to the value of a JavaScript code statement. Condition: (Optional) A condition is added to control when variables are assigned. If a condition is added, it must evaluate to true for the variables to be assigned new values. Examples Set a Text Value This example shows how to set a variable to a text value. In this scenario a condition is used to detect if a query string parameter named q is populated, then the data layer variable page_type is set to the text value "search" to indicate that this is a search results page. Add the Set Data Values extension. Set the Title to "Set search as the page type". Select the variable page_type from the the drop-down menu. Set the value type to Text. In the text box enter "search". Click Add Condition. and set the following: Select the variable q (js) Set the condition to is defined. Set a Variable Value This example shows how to set a variable to the value of another variable. In this scenario, if the variable page_name does not have a value it is set to the value of the document.title variable. Add the Set Data Values extension. Set the Title to "Set page_name". Select the variable page_name from the the drop-down menu. Set the value type to Variable. A variable drop-down list appears. Select document title from the drop-down menu. Click Add Condition and set the following: Select the variable page_name . Set the condition to is not defined. Click + to add an Or condition. Select the variable page_name . Set the condition to is defined. Click + to add an And condition. Select the variable page_name . Set the condition to is not populated. Set a JavaScript Code Value This example shows how to set a variable to the value returned by a JavaScript statement. In this scenario, the number of search results on a search page is determined by using jQuery to select the number of search result link elements on the page. The variable search_results is set to the value returned by the JavaScript code. Add the Set Data Values extension. Set the Title to "Determine number of search results". Select the variable search_results from the drop-down menu. Set the value type to JS Code. In the text box enter JavaScript code, exactly how it would appear in the page (or a browser console). This example uses a simple jQuery selector and the .length property: $('.search-results a').length; . Click Add Condition and set the following: Select the variable page_type . Set the condition to equals and enter "search" in the text field. ... View more

Managing Users In order to manage users' accounts in Tealium iQ, you must have the 'Manage Users' permission enabled for your own user account. To apply this setting to a user account, see the User Permissions Management article. Once you have this permission you can: Add, remove, and manage which users are in your account Manage which profiles your users have access to Manage users' permissions on the account and profile levels Change a user's password You can reach all of the user management options through the User Manager. To access the User Manager: In Tealium iQ, click on your email address in the upper right corner to bring up the Admin Menu. Click on 'Manage Users' located under the Account Admin section to bring up the User Manager. Adding a User 1. In the User Manager window, click on the '+Add User' button. The Create New USer dialog box will appear. 2. Enter the email address for the new user account in the 'New User Email' field, then click 'Next'. 3. Select the account-level permission you want to assign to the user. Note: For more information on user permissions, see the User Permissions Management article. 4. Next, select the profiles for which you want to assign the user's permissions, then click 'Next' to proceed. All Current and Future Profiles - This is a permission that gives the user access to all existing profiles and any that may be created in the future. You may only assign this permission if you currently hold it. Select Profile(s) - From the list of profiles you have access to, select the profiles for which you want to assign the user's permissions. 5. Select the profile-level permissions you want to assign to the user. Click 'Next' to proceed. 6. The final step is to review the permission you have just assigned to the user. You can see if the user has full, partial, or no permissions for each section, as well as to which publish environments the user can publish. Click 'Finish' to confirm the addition of the new user account. The email address you entered will receive an activation email. Managing User Permissions To learn more about managing user permissions at the account and profiles levels, please refer to the User Permissions Management article.   Removing a User From Your Tealium Account You can remove only one user at a time from your Tealium account. 1. In the User Manager, check the box next to the user you wish to remove from your Tealium account. 2. Click on the 'More' drop-down located by User Options to expand the menu. 3. Click 'Delete User'. A 'Delete User' confirmation window will appear. 4. Click 'Remove User' to confirm. You have successfully removed a user from your Tealium account.   Removing a User from a Profile You may remove one user from as many profiles as you specify at one time, or you can remove multiple users from a single profile at one time. You cannot remove multiple users from multiple profiles at one time. To remove a user from a profile: 1. In the User Manager, check the box next to the user you wish to remove from your Tealium account. 2. Click on the 'More' drop-down located by User Options to expand the menu. 3. Click 'Remove from Profile'. 4. A window will appear in which you choose whether to remove the user from all current profiles, or from the profiles you select in the 'Profiles List'. Note: Selecting 'All Profiles' will remove the 'All Current and Future Profiles' permission. See the User Permissions Management article for more information. 5. Click 'Next' to proceed. 6. A confirmation window will appear listing the profiles you are removing the user from. Click 'Remove' to confirm. Even if you remove a user from every profile, if that user still has the 'All Current and Future Profiles' permission, he or she will automatically have access to profiles created in the future. Managing User Passwords   Changing Your Password To change your own password: 1. In Tealium iQ, click on your email address in the upper right corner. The Admin Menu will appear. 2. Click on 'Edit/View User Settings' located under User Preferences. The 'Edit/View User Settings' window will appear. 3. Click on the 'Change Password' item under the User Account menu on the left. 4. In the 'Current password' field enter your old password. 5. In the 'New Password' field, enter your new password. Make sure it meets the minimum password requirements outlined to the right. 6. In the 'Confirm new" field, re-enter your new password. 7. The 'Change Password' button will highlight. Click it to change your password. Creating/Resetting Your Password Outside Tealium iQ If you are having trouble signing into Tealium iQ, e.g. you've forgotten your password or you haven't activated your account yet, please refer to the Creating/Resetting Your Password article.   Creating/Resetting Your Password User Permissions Management Getting Started with Tealium iQ Building Blocks Tag Management Concepts Tealium iQ User Interface Walkthrough Quick Start Guide Universal Data Object Guide Adding Data Sources Adding a Tag Save/Publish a version Publishing Your Tealium iQ Profile Versions Tab Code Center Labels User Administration Creating/Resetting Your Password ... View more

This feature is NOT available in the current 5.x versions of the Android and iOS (ObjC) libraries. Mobile Companion is the mobile device equivalent of Web Companion. It contains much of the same functionality as Web Companion and is available for iOS and Android devices.   You must enable Mobile Companion in Tealium iQ before you can use it for your mobile app. In order to use Mobile Companion, you must meet two criteria:   You app must use the TealiumFull library, not the TealiumCompact library. The Mobile Companion toggle must be on in the Mobile Library Publishing settings. Note that when you activate the mobile library for a profile, Mobile Companion is turned on by default. If you're using the TealiumCompact library, the library disregards this setting.   Enabling Mobile Companion To toggle Mobile Companion: In Tealium iQ click on the Save/Publish button to bring up the Save/Publish dialog. Click on the Configure Publish Settings button in the upper right corner. Navigate to the Mobile Library Publishing tab. If this profile does not have the mobile library enabled, click the Activate Mobile Library button and confirm activation. The Mobile Companion toggle is located under Debugging. Click the on/off toggle button to enable and disable it. Click the Save button. Save/Publish your Tealium iQ profile.   Using Mobile Companion To activate Mobile Companion on your device: Give the device 3 hard shakes, then 3 hard taps in quick succession. The Tealium Icon button and blue overlay buttons will appear. The Tealium Icon can be moved around. The Blue Overlay Buttons appear over all auto-trackable items. To inspect View Data, tap on the Tealium Icon. To inspect an auto-trackable object, double-tap on its blue overlay. Click the 'X' symbol in the top-left corner of the window to close the Mobile Companion. To minimize the window, click the '—' symbol on the top-right corner. The arrow at the bottom-right of the window allows you to adjust the dimensions of the window.   Overview Tab Summarizes the corresponding Tealium iQ account information. account: Name of Tealium iQ account profile: Name of Tealium iQ profile target: Current environment in which the page is running Current Extensions Setting displays the extension's configuration. Published At: Displays the date and time at which the extension was published Mobile companion ON: Displays the status of the Mobile Companion. The value 'True' indicates that the app is enabled Power save call limit: This value points to the number of view/link events in the queue required to make a dispatch. Power save call limit of '0' indicates that no view/link events need to be queued to send out a dispatch. If you set 'Power Save Call limit = 3', the library delays sending dispatches until 4 or more events are queued View Tab Provides a list of the data points sent out with the view event. Currently tracking: Indicates whether or not you are tracking the view event Object Class: Name of the object class that is tracking the view event Tealium Reference ID: Unique identifier assigned to the view event View Data Sources: Data source name-and-value pairs connected to the view event Element Tab Provides a list of the data points and their values sent out with the element. Currently tracking: Indicates whether or not you are tracking the element Object Class: Name of the object class that is tracking the element Tealium Reference ID: Unique identifier assigned to the element View Data Sources: Data source name-and-value pairs connected to the element Log Tab Provides the JSON object and timestamp for every action and event. Queued and Packaged Calls - This shows the current queue of calls as well as the calls that have already been delivered. Tealium Logs - These are internal logs generated by the library for an iOS device. NOTE: While the functionality of the Log tab remains same for an Android device, it has a different appearance. In place of the Tealium logs, this tab displays a list of 'Last Packaged Calls', which are nothing but the preceding calls. Tools Tab The Tools tab lets you join an AudienceStream Trace. ... View more

This content has been updated and combined into the article Creating a Mobile Profile. Migrating to Version 5.0 With the release of 5.0, some mobile data sources were renamed, and many were completely removed, with the elimination of the autotracking feature. When you activate the profile for Mobile 5.0, a notice will appear indicating a number of data sources are deprecated. Click on the link provided to view the list of deprecated and new data sources.   Note: If you do migrate to version 5.0, by activating mobile through the Mobile Library Publish configurations, keep in mind that your configurations from older versions of the library are not carried over. You must manually replicate your old settings in the new Mobile Library Publish configurations.     Activating Mobile 5.0 In order to enable a profile for use with version 5.0 and later of the mobile libraries: In Tealium iQ, click on the Save/Publish button. Click on the Configure Publish Settings button to bring up the Publish Configuration window. Select the Mobile Library Publishing tab. Click the Activate Mobile Library button. A confirmation window will appear prompting you to click Activate.     Note: Activating mobile for the profile will automatically add all mobile data sources, if they're not already added.   Mobile Library Publish Configurations Tracking   Tag  Management Enables mobile tag management tracking on all events and views in your application via webview using utag.js. The default value is OFF, but if you will be adding and configuring tags in Tealium IQ change this to ON. Tealium Collect Allows you to track the properties of iOS classes and Android Activities in your application. Enables native tracking via Tealium's vData technology (requires Tealium EventStream). Learn more about this solution here. The default value is ON, but if you will be adding and configuring tags in Tealium IQ change this to OFF.   Batching   Send Batch Data after every Allows you to set the number of events that need occur before a those events are sent. Entering a value of 0 or 1 essentially turns off batching. The default value is set to 1. WiFi only Sending If enabled, events are only sent when the user's device is connected to a WiFi. The default value is OFF. Battery Saver By enabling ON, data will only be sent when the device has adequate battery levels. The default value is ON. Dispatch Expiration Specify how long (in days) the data persists in the app if no data has been sent back. A value of -1 means there is no dispatch expiration. The default value is set to -1. Minutes Between Syncronization Number of minutes between configuration checks (checks occur at launches and wakes). The default value is 15.0. Queue Capacity Number of events and views to store on the device until ready to send (0 = no offline dispatching, -1 = no limit). The default value is -1. Debugging   Set Debugging Log Level Allows you to enable logging. Force which logs to be shown when debugging your application.  ... View more

This article describes how to configure publish settings for a user. In this article: Table of Contents Placeholder Configuring Publish Settings Use the following steps to configure your publish settings: Click Save/Publish. The Save/Publish dialog displays. Click Configure Publish Settings in the upper right corner. The Publish Configuration dialog displays. Select the General Publishing or Mobile Library Publishing configuration tab. Adjust settings as needed. Click Save to apply your changes. Some settings require you to perform a publish to enable their functionality. See the following section for more information on each of the publish settings. General Publishing The General Publishing configurations are grouped depending on which aspect of your implementation they affect. The following sections provide descriptions of what each publish configuration does. Version Workflow These configurations allow you to fine-tune how this profile's implementation is saved and published. Publish Notify Email If you want to receive emails whenever a version is published, enter the emails into the Publish Notify Email field. You can add multiple email addresses by separating each additional email with a comma. Custom Version Naming Allow users to enter a custom version name rather than the default timestamp ID. Default value is ON. Save/Publish for older versions Control whether or not users can modify and save old versions of your profile. If you select Off then only the latest version can be modified and saved. Default value is ON. Workflow Management  This setting allows you to set up workflow management, whereby users with Dev and QA publish permissions can request permission to publish to Prod. Enabling workflow management will require approval for all publishes to Prod. Default value is OFF. Lock Profile  Prevents multiple users from modifying a profile at the same time. Default value is OFF. Alert Notify Email (DEPRECATED)  To be alerted when errors occur on your website, contact your account manager to enable this feature and then add your email address to this field. if left blank, no alerts will be created. Add multiple email addresses as a comma-separated list. This setting is not longer supported. If this was enabled in your profile, you will no longer receive alerts emails.  Performance Optimization These publish configurations affect the overall performance of the Universal Tag (utag.js) on your site. Ready Wait Flag Enabling the Ready Wait Flag will halt all utag.js operations until the DOM-Ready signal is received from the browser. Extensions scoped to Pre Loader continue to execute before DOM-Ready. Default value is OFF. Bundled Tags  Displays the list of bundled tags that do NOT use the default 'All Pages' Load Rule. Learn more about bundling and page performance. Bundle Tags Loading on All Pages  Bundle tags using the All Pages load rule into utag.js. This reduces the number of network calls made by the browser, potentially improving performance and page load times. Default value is OFF. Tag loading order for bundled tags (tied to All Pages rule) is determined by the order they appear on the Tags screen, not their UIDs.  Learn more about bundling and page performance. Minify Tag Templates Minifies the code for utag.js and all published tags. Default value is ON.. Minification is the process of removing unnecessary characters from code, such as empty spaces and comments. The functionality of the code remains unchanged. This has the benefit of reducing the overall amount of code, making it easier and faster to transfer and download. However, the code becomes more difficult to understand. Implementation These settings affect how you implement the Universal Tag (utag.js). Generate distro.zip file This will generate a distribution archive of all generated tag files. Cookies Domain  Enter the domain you want to set for the utag_main cookie. By default, Tealium automatically detects the domain of the page, so we recommend that you leave this field empty. By doing so, Tealium automatically detects the domain. However, you can set this value to the domain of your site. If you use multiple subdomains, you should set this to the root domain (ex. tealium.com instead of www.tealium.com) Page Data Object To use a data object other than Tealium's utag_data, enter your preferred data object name here. Base Variables  Enter a comma-separated list of utag_data variables to send on every tracking call. Example: page_name,site_language,site_currency,is_logged_in Visitor Session Timeout Set this value, in milliseconds, to override the default session timeout of 30 minutes. (1800000 ms = 30 minutes). Custom Publish Environments  Allows you to create custom publish environments in addition to the defaults Dev, QA, and Prod. Default value is OFF. Generate utag.sync.js File  Allows you to generate and publish the utag.sync.js file when you turn it ON. Default value is OFF. The first time you enable this setting, you must re-publish all of the publish environments for this profile in order to generate the utag.sync.js file. Using a utag.sync.js file also requires that you code a separate file reference on your site, preferably in the head element of your page. If you code the file reference on your site, but fail to publish to all of your publish environments after enabling this setting, your site will fail to load as it is making a synchronous call to a file that does not yet exist. This setting is also required for Tealium's Flicker Free Adobe Test & Target solution. Use UTF-8 Encoding Turn this toggle on if you want the utag.js file to be encoded with UTF-8 instead of the default ISO-8859-1. Default value is ON. For profiles created before Nov. 10, 2015, the default is ‘Off’.  Prevent Tag Load Quickly disable all tags managed by Tealium iQ. You must republish the profile after turning this on. Default value is OFF. Web Companion Toggle on or off to enable or disable support for Web Companion Target Environment swtiching. Enabling this feature allows your website to set a cookie with any arbitrary value, which could expose your system to code injections. This feature is offered as a convenience for those who cannot use the Google Chrome browser. If you can use Chrome, Tealium recommends using the Tealium Tools Environment Switcher as a best practice. Data Layer Enrichment Profile  Specify the AudienceStream profile from which to retrieve visitor data. The on-page data layer will then be enriched with this visitor data. Publishing URLs These configurations allow you to specify a publication location other than Tealium's default multi-CDN infrastructure. If you want to publish your profiles to a non-standard location (if your prod environment is not specified as "prod"), then enter the URL in the appropriate field. You may do this for each of the three environments: Dev, QA, and Prod. Publish Dev URL Use this setting if you are self-hosting your Tealium JavaScript files or if you use first-party domains. For more information, see Self-Hosting utag.js and First-Party Domains. Publish QA URL  Use this setting if you are self-hosting your Tealium JavaScript files or if you use first-party domains. For more information, see Self-Hosting utag.js and First-Party Domains. Publish Prod URL  Use this setting if you are self-hosting your Tealium JavaScript files or if you use first-party domains. For more information, see Self-Hosting utag.js and First-Party Domains. To restrict the delivery of your utag.js files to the Europe geographic region, you must enter //tags-eu.tiqcdn.com/utag/ACCOUNT/PROFILE/ENVIRONMENT  into the URL fields. Restricting the delivery locations to Europe in this way means that you are only using one CDN, Akamai, to deliver your utag.js file and only from servers physically located in the EU and not from Tealium's mCDN infrastructure. Legacy Settings These configurations are deprecated, but remain to support legacy deployments and should not be used for newer implementations (utag.js versions 4.26 and later). Profile Can Be Subloaded  This is required when another profile uses the Profile Loader tag to load this profile. This functionality is deprecated in favor of Profile Libraries. Force Timeout  Set this value, in milliseconds, to cancel slowly loading tags. Only tags that take longer than this value to load are cancelled. This configuration only works for profiles using utag.js versions before version 4.26. This configuration will not affect profiles using more recent utag.js versions. Tealium removes from the load queue any tag libraries that have not loaded by the time the force timeout value expires. The countdown to a forced timeout starts when the initial utag.js call is made, not when the subsequent tag library calls (utag.1.js, utag.2.js, etc.) are made. Be aware that if a visitor's browser is running slowly, the Force Timeout feature could cause a tag to be cancelled even though the utag.js or tag library requests themselves aren't slow. Enter a high Force Timeout value to prevent unnecessary timeouts. Extensions Scoped To Footer Toggle on or off to set this value if this profile uses a utag.footer.js file to load extensions. Mobile Library Publishing In this tab, you can activate mobile library support by clicking Activate Mobile Library. Learn more about Creating a Mobile Profile. ... View more

Code Center is where you get the code to add the Universal Tag (utag.js) to your website. For more information abou installing Tealium on your website, see the Quick Start Guide for Web. In this article: Accessing Code Center Click the user menu in the upper right corner and select Code Center. In the side panel, select the desired environment. Click OK to close the Code Center. Code Center Settings The following settings can be adjusted to customize the code snippet displayed. Environment Title The environment is one of three default environments (Dev, QA, Prod) or any custom environments that Tealium publishes to. Select one of these environments. Notice how the environment in the utag.js path changes as you select different environments. Enter a custom name for one of the default environments. This new name will appear throughout the UI. JavaScript Type This determines whether the tags are loaded synchronously or asynchronously. By default Asynchronous is selected and we recommended it as a best practice as it provides faster page loading and a better visitor experience. Disable Comments Checking this box will remove the comments from the code snippet (recommended). Use the Code Snippet Tealium Script The Tealium Script tab displays the code based on your selections. The code includes the Universal Data Object (a sample of utag_data ) and the Universal Tag code (utag.js). The Universal Data Object displayed here is generated from the variables defined in your data layer. The Universal Data Object seen in Code Center is only a placeholder. You must dynamically populate it with real values in order to send data to your tags. Use the following steps to copy your code snippet: Select the code displayed in the text box by either method: Click and drag to select all the code. Click the Select All button that appears when you mouse over the code. Copy the code. Paste the code into your site authoring tool or back-end system. Sample HTML The Sample HTML tab provides an example of what the code would look like when added to a web page. The sample code appears after the opening <body> tag, in accordance with our best practices. Custom Publish Environments Custom publish environments is a feature that must be enabled to use. To learn more, see Custom Publish Environments. China CDN Tealium offers a separate CDN domain to serve files within the China firewall. To learn more, see Loading the Universal Tag on Websites Behind the China Firewall. ... View more