Tealium Learning Center

This article describes how to set up the Heap connector. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add User Properties ✓ ✗ Track ✗ ✓ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Add User Properties Parameters Parameter Description App ID The app_id corresponding to one of your projects. identity An identity, typically corresponding to an existing user. If no such identity exists, a new user is created with that identity. Limited to 255 characters. For more information, see: Heap: Add User Properties User Properties An object with key-value properties you want associated with the user. Each key and property must either be a number or string with fewer than 1024 characters. For more information, see: Heap: Add User Properties Action - Track Parameters Parameter Description App ID The app_id corresponding to one of your projects. identity An identity, typically corresponding to an existing user. If no such identity exists, then a new user will be created with that identity. Limited to 255 characters. For more information, see the Heap documentation. Event The name of the server-side event. Limited to 1024 characters. For more information, see the Heap documentation. Properties An object with key-value properties you want associated with the user. Each key and property must either be a number or string with fewer than 1024 characters. For more information, see the Heap documentation. Timestamp ISO 8601 or Unix epoch milliseconds. Example: 2017-03-10T22:21:56+00:00 For more information, see the Heap documentation. ... View more

The TiQ interface was written for developers and marketers alike and therefore it does not require JavaScript knowledge to use. However, it is important to understand that the selections we make in the interface are eventually transformed into JavaScript code that runs and evaluates on your website. One key example of this is the conditions utilized in Load Rules and Extensions. Understanding the JavaScript code that is generated based on the selections made in the interface can help prevent errors and improve the efficacy of your business logic. You can see that the conditions selected in the UI and its corresponding JavaScript code below. Notice how the order of the conditions matters. Condition in the Tealium UI:   Corresponding JavaScript Code: ((typeof b['event_name'] != 'undefined' && b['event_name'].toString().toLowerCase().indexOf('add to cart'.toLowerCase()) > -1) || (typeof b['event_type'] != 'undefined' && /cart$/i.test(b['event_type']))) The order of the conditions is critical for the extension or load rule to behave as expected. If the "is defined" check for event_name was placed after the content check for event_name, the code would exit on an error with the condition for event_type not evaluated. This would mean that a potentially valid condition would be missed.  It is best practice to always add the is defined condition in conjunction with other conditional options. This helps prevent any JavaScript errors and ensures the load rule works as intended. Generated JavaScript Code for Conditions: In the table below, you can see the generated JavaScript code for each condition. In all of these examples,  {{VALUE}}  represents the value from the text field in the extension or the load rule. The variables dom.title is used for strings, cart_total_items and va.badges.42 are used for operators relevant to number and badges respectively.  Condition JavaScript code generated contains (b['dom.title'].toString().indexOf('{{VALUE}}') > - 1) contains (ignore case) (b['dom.title'].toString().toLowerCase().indexOf('{{VALUE}}'.toLowerCase()) > - 1) is defined (typeof b['dom.title'] != 'undefined') does not contain (b['dom.title'].toString().indexOf('{{VALUE}}') < 0) does not contain (ignore case) (b['dom.title'].toString().toLowerCase().indexOf('{{VALUE}}'.toLowerCase()) < 0) does not end with (!/{{VALUE}}$/.test(b['dom.title'])) does not end with (ignore case) (!/{{VALUE}}$/i.test(b['dom.title'])) does not equal (b['dom.title'] != '{{VALUE}}') does not equal (ignore case) (b['dom.title'].toString().toLowerCase() != '{{VALUE}}'.toLowerCase()) does not start with (!/^{{VALUE}}/.test(b['dom.title'])) does not start with (ignore case) (!/^{{VALUE}}/i.test(b['dom.title'])) ends with (/{{VALUE}}$/.test(b['dom.title'])) ends with (ignore case) (/{{VALUE}}$/i.test(b['dom.title'])) equals (b['dom.title'] == '{{VALUE}}') equals (ignore case) (b['dom.title'].toString().toLowerCase() == '{{VALUE}}'.toLowerCase()) greater than (parseFloat(b['cart_total_items']) > parseFloat({{VALUE}})) greater than or equal to (parseFloat(b['cart_total_items']) >= parseFloat({{VALUE}})) is badge assigned (typeof b['va.badges.42'] != 'undefined') is badge not assigned (typeof b['va.badges.42'] == 'undefined') less than (parseFloat(b['cart_total_items']) < parseFloat({{VALUE}})) less than or equal (parseFloat(b['cart_total_items']) <= parseFloat({{VALUE}})) is not defined (typeof b['dom.title'] == 'undefined') is not populated (typeof b['dom.title'] != 'undefined' && b['dom.title'] == '') is populated (typeof b['dom.title'] != 'undefined' && b['dom.title'] != '') regular expression (/{{VALUE}}/.test(b['dom.title'])) starts with (/^{{VALUE}}/.test(b['dom.title'])) starts with (ignore case) (/^{{VALUE}}/i.test(b['dom.title'])) ... View more

This article describes some techniques for testing your AudienceStream configuration before releasing it to your production environment. In this article: Setting up Non-Production Configurations in AudienceStream Unlike Tealium iQ, AudienceStream does not have DEV and QA environments for users to publish to and test. Sometimes, during configuration, a user may want to test to ensure that these attributes, audiences, or connectors are configured properly before going live. If Attributes, Audiences, and Connectors are not properly tested before going live, this can lead to unexpected or unwanted behavior, such as visitor profiles storing unwanted or incorrect data, users joining audiences they would not have joined otherwise, or connectors performing actions on actual site users before the connectors have been properly configured.  Configuration To test specific AudienceStream objects, we need to create a new attribute that will allow you or your team to interact with these Attributes, Audiences, and Connectors, while also preventing live users from also doing the same.  The best way to do this is to create a badge specifically for testing purposes.  For this example, we will call this badge “Test User.”  This badge uses a rule that evaluates on “Any Event” when a Query String Parameter contains “tealium_test=true”.  This badge is then set to be removed on any event where the query string parameter contains “tealium_test=false”. The badge can be renamed as appropriate and can use whatever conditions you choose.  Keep in mind that it should be something unique so this badge is not assigned to regular site visitors. If we are looking to test a specific audience, we can set up the audience with desired conditions and simply add an additional condition that the “Test User” badge has to be assigned.  This will prevent all other users from joining that audience, and will allow you to test any connector actions that are tied to that specific audience. If we are testing a specific attribute, we can either add a condition as a part of the rule the attribute uses or we can create a specific rule that “Test User” is assigned and include that along with any other rules that the enrichment uses.  The latter makes it a bit more simple when moving to go live with the configuration. OR Testing When starting your test and Trace, you must qualify for the condition to have this badge applied to you during this session. To do this, you will navigate to the site that you are testing and append the query string parameter used in the rule.   In this case, you would add the following text to the URL and refresh: ? tealium_test = true An example of what the URL will look can be seen in the image below: When the Trace starts, you should see the “Test User” badge assigned: Once the badge is assigned, you are now set up to run through your logic and test your configuration. In conclusion, testing this way before going live will allow the person testing the configuration to perfect the logic at hand, reduce errors, and increase the effectiveness of campaigns. ... View more

Finding the correct CSS selector of a page element you want to track is crucial to the success of the jQuery onHandler Extension. This article will show some methods for determining the CSS selector of a page element. In this article: Table of Contents Placeholder Become familiar with jQueries Documentation on selecting an element. jQuery provides excellent documentation and examples on utilizing their library.   Link to basic concepts on using jQuery CSS selectors -  https://learn.jquery.com/using-jquery-core/selecting-elements/ Main Selector categories - https://api.jquery.com/category/selectors/ If you are selecting a specific element and it has a CSS 'ID" or you are slelecting multiple elements that all hace the same CSS 'class' then the process can be direct and simple.  However if the CSS on the page may not provide as easy of a solution.  Some of the prebuilt or automatic tools work best when the selector are easiest.  If the pattern or scheme used in the CSS become more obtuse or difficult to choose a selector you may need to reach out for technical assistance from the support team.   Google Chrome Developer Tools Finding the selector of an element in Chrome when using the built-in Developer Tools. To find the CSS selector of a page element: Right-click the element in the page and click 'inspect' in the dialog that pops up. The Developer Tools window will open. In the Elements tab of Developer Tools, right-click the highlighted element and select Copy > Copy selector. Initially review you selector in the console.  Use the jQuery statement with the selector you just copied as a string value. jQuery('yourcopiedselectorhere');  One the results and validate the selector was as unique as required.  The object returned included an array of items selected. If the returned results match your intended selection then you are done! The selector string is now in your clipboard and you can paste it into the jQuery extension. Tealium Tool: CSS Selector Tool If you already have the Tealium Tools browser plugin, then the CSS Selector Tool makes it easy to find the selector. However, If the resulting selector is long then you may want to review using a manually method to devise a selector. Follow the instructions on how to use the CSS Selector Tool. Web Companion Web Companion offers a slightly less accurate selector tool, but it can help pre-configure a jQuery extension for you.  However, If the resulting selector is long then you may want to review using a manually method to devise a selector. Follow the instructions on how to use the On-Page Element Selector tool in Web Companion. Testing a Selector Use this method to test a selector before using it in an extension. Paste this into the Console of the developer tools and make sure to replace <jQuery selector> with the real selector that should be used: jQuery("<jQuery Selector>").on("mousedown",function(e){ alert("It worked!!"); }); Test this by clicking down (but not up) on the desired element. If your selector was correct then you will see a popup with the word, “It worked!!”. Primary Selectors A primary selector is a legacy option for older jQuery when using older jQuery libraries 1.6 or older only. You should not need to enter a Primary Selector on the current jQuery libraries versions 1.7 and higher. A primary selector should be used when the element you want to target is not available on page load. The primary selector is a higher-level element on the page. For example, let's say you have a table of data that gets populated dynamically with AJAX after the page loads. You want to track certain links within the table, but they don't exist until after the table is populated. If the table tag looks like this: <table id="myTable"></table> And your links looks like this: <td><a href="" class="myLinks">Click Here</a></td> Then the selectors you use might looks like this: Primary Selector: table#myTable Selector: td > a.myLinks ... View more

This is a list of the Tealium Tools developed by community members or the Tealium Team. Bulk Edit for iQ A tool to toggle the active state or delete multiple variables, load rules, tags or extensions all at once. Bulk Download Logs You can use this tool to check the status of a file imported with FileImport/Omnichannel. CSS Selector Tool A tool to help you determine the selector for a specific element in a page. This selector is often used in the congfiguration of a jQuery onHandler Extension. This tool requires that jQuery already be loaded on the page. Data Layer Identifier You can use this tool instead of the browser console to display a nicely-formatted table that display all if the data layer variables on the page Environment Switcher A powerful testing tool that allows you to change the account, profile, and environment from which the Tealium files (utag.js, utag.sync.js) that are loaded. iQ Extension History A tool for reviewing the edit history of an extension. Mobile QR Trace A  tool that enhances the Trace feature by providing a QR code that is scannable by your device, enabling you to quickly view events coming from the Tealium Mobile SDKs. Tag Variables Exporter This tool exports each tag along with each data layer variable referenced in the Load Rule or Data Mappings. Universal Tag Debugger A new tool for validating the Universal Data Object and event tracking calls. The Universal Tag Debugger provides an easy way to validate your data layer and event tracking in real-time as you navigate your site. User Permissions Exporter This tool will export all users' permission settings for an account to a CSV file. Variable Mappings Exporter This tool will export all the data mappings for each tag. This will include the variables used in the tag's assigned load rules and the variables used in the mappings, then export the data to a CSV file. Web Companion A new version of Web Companion that runs within Tealium Tools to improve the diagnostic reporting of tags, load rules, and extensions.   ... View more

This tool provides an easy method for marketers and developers to validate the data layer and tracking events in real-time on their site. In this article: Table of Contents Placeholder How It Works The Universal Tag (UTAG) Debugger is a tool used for validating the Universal Data Object and event tracking calls. The UTAG Debugger is similar to Web Companion, with the difference being that it is focused on the data layer and the data captured by each tracking event within utag.js. The data objects displayed in the tool are captured after extensions scoped to "All Tags - Before Load Rules" and before extensions scoped to "All Tags - After Load Rules". Learn more about order of operations. Install the Tealium Tools Extension To use this tool, you must first add it your Chrome browser using the Tealium Tools extension. To install this extension on Chrome or Firefox, see Tealium Tools Browser Extension. Paste JSON to Custom Tools After you have installed the browser extension, use the following steps to cut and paste the JSON to your Custom Tools: Click the Tealium icon in the upper right of your browser to open Tealium Tools. Click the Custom Tools tab. From the Custom Tools tab, cut and paste the following JSON: { "id" : "teal.sol.debug", "title" : "UTAG Debugger", "description" : "Universal Tag Debugger", "no_ui" : true, "scripts" : { "utag_monitor" : { "js" : "void(window.open(\"\",\"utagmon\",\"width=600,height=600,location=0,menubar=0,status=1,toolbar=0,resizable=1,scrollbars=1\").document.write(\"<script language='JavaScript' id='utagmon' src='//tags.tiqcdn.com/utag/tealium-solutions/main/prod/utag.4.js?opt_show_enrich=0&opt_show_meta=0&opt_show_query=0&opt_show_jspage=0&opt_show_tiq=1&opt_show_cookie=0&_cb=\"+Math.random()+\"'></\"+\"script>\"));", "auto_inject" : true } } } When complete, a new button with the tool name will display under the "Custom Tools" tab. Create a Bookmarklet You can optionally create a bookmarklet from which to launch the tool, as follows: Create a bookmarklet using the following code: javascript&colon;void(window.open("","utagmon","width=600,height=600,location=0,menubar=0,status=1,toolbar=0, resizable=1,scrollbars=1").document.write("<script language='JavaScript' id='utagmon' src='//tags.tiqcdn.com/utag/tealium-solutions/main/prod/utag.4.js? opt_show_enrich=0&opt_show_meta=0&opt_show_tiq=1&opt_show_dom=0&opt_show_jspage=0&opt_show_cookie=0&_cb=" +Math.random() +"'></"+"script>")) Drag and drop the bookmarklet onto your Bookmarks bar. Your bookmark is now ready to use. Using the UTAG Debugger Tool Use the following steps to begin using the UTAG Debugger tool: Navigate to your desired website. Open Tealium Tools and click the Custom Tools tab. Click the Ud button. The Universal Tag Debugger tool displays. If you created a bookmark to use, simply click the bookmarklet in your toolbar. The top section displays which utag.js file was detected on the page and contains the following: account/profile/environment path) the version of utag, a number of display options for changing what data will display in the viewing area. Options The following options are available to help you use and navigate the tool: Bookmarklet – you can re-save your display options by dragging the bookmarklet link from the top-right of the pop-up back to your toolbar Events – the tracking events detected on the page will either be "view" events or "link" events, toggle these checkboxes to filter the display Show Data – the UDO data will always be displayed, but additional data sources collected by utag can be displayed by toggling these checkboxes Data Variables The following data variables are available: iQ – built-in data collected by utag.js, including DOM attributes and variables prefixed with "ut." eg. "ut.profile" Cookie – all first party cookies available in the page JS Page – JavaScript page variables defined in your data layer (variables other than utag_data) Querystring – query string variables found in the URL Meta – all meta data values available in the page AudienceStream – variables populated by data layer enrichment Event Display Area The event display area automatically updates as you navigate or trigger in-page events. New pages are listed as "utag_view" events and in-page events are listed as "utag_link" events. The example above shows two pages visited and one event triggered. This results in two utag_view entries and one utag_link, which are labeled #1, #2, and #3 in the image. The most recent activity always displays at the top. ... View more

This article describes how to use the Tealium Tools version of Web Companion. In this article: Table of Contents Placeholder How it Works This version provides a more accurate status of iQ tags, load rules, and extensions that run on a page. Resource URL Add this tool to the Tealium Tools browser extension using the following URL: https://solutions.tealium.net/hosted/tealiumTools/twc/twc.json Using Web Companion When loading the tool, a status screen displays with information about the utag.js installation detected and which tags, load rules, and extensions were active on the page. The status information includes the following: Path – the path of the utag.js file in the format of "account / profile / environment" Version – the iQ version name  Timestamp – the version and published timestamp from utag.js (available from utag.cfg.v ) Published – a localized time period showing when utag.js was last published Each tab displays a counter for the number of active items on the page. The following example displays 13 Tags, 10 Extensions, and 9 Load rules. Tags Tags are sorted by the Tag UID found in TiQ. The status of a tag will be one of the following: OK – Tag has loaded and fired Loaded – Tag was loaded, however the send function was never called. Failed – Tag was requested, but failed to be brought to the page. Extensions The extensions report is limited to the "All Tags" scope. Tags display in order of execution and show a runtime status of "Completed" or "Failed", as shown in the following examples. Load Rules Load rules display by status, "Fired" or "Not Fired", and then by the Load Rule ID. Load Rules that "Fired" are listed first. Event Notification Once Web Companion has loaded, a handler is created and any further tracking requests create a Chrome notification containing the event called: 'Tealium Tools TWC - "event"' with the following message body: 'Event fired by: "domain of site"   ... View more

This article describes the Environment Switcher, which is available as a Tealium Tools browser extension. In this article: Table of Contents Placeholder How it Works The Environment Switcher is a powerful testing tool that allows you to change the Tealium files (utag.js, utag.sync.js) that are loaded on a page by specifying a specific environment (Dev, QA, or Prod) and/or a specific Account/Profile. Add the Environment Switcher plug-in directly from Google Chrome or Mozilla Firefox by adding the Tealium Tools extension. The Environment Switcher is included by default. Description When you launch the Environment Switcher, the current account and profile detected on the page displays, along with configuration tabs that allow you to adjust the switcher according to your input. Once you have the Environment Switcher available in Tealium Tools, use the following steps to launch it: Click the Tealium Tools icon in the upper right of the screen. Click the Home tab. Click Environment Switcher. The Environment Switcher configuration screen displays a set of configuration tabs. Use the sections below as a guideline to configure the settings on each tab as desired. Basic Configuration The Basic tab allows you to switch to different environments (Dev, QA, or Prod) by swapping the utag.js and utag.sync files to the environment selected. Use the following steps to switch environments: Click the Basic tab. Click the Environment you want to switch to. When you select a new environment, the environment detected on the page is outlined in orange and the active environment on the page (the one you switched to) is highlighted in blue. Click the Start button to apply your changes. This action forces a refresh of the current page. Advanced Configuration The Advanced tab is used for the following: Advanced Redirects to redirect the source account, profile, and environment to a new destination. URL Redirects to redirect the source URL to a new destination. Changing which account or profile to load Tealium files from, which is helpful if your profile uses inherited libraries or custom publish environments. Use the following steps to configure settings the settings on the Advanced tab: Click the Advanced tab. (Optional) To redirect the Account, Profile, or Environment, click Advanced Redirect to expand. Type the source name for each in the Source column and the destination name for each in the Destination column. (Optional) To redirect the URL, click URL Redirect to expand. Type the source URL in the Source column and the destination URL in the Destination column. (Optional) Click Advanced Options to select or deselect how your redirects are applied. Select or deselect one or more of the the following: Current Domain Only Current Tab Only Apply to utag.js Apply to utag.sync.js Set utag_cfg_ovrd.path Click Start to apply all changes made. Active Redirects After making any changes using the Environment Switcher, the Active Redirects tab is the default tab that displays the next time you initiate the switcher. This tab displays environments that are currently being switched. Disable an Active Redirect To disable an active redirect, click Stop in the Action column. The page is automatically refreshed and the Tealium files load normally, as coded in the page. In subseqent visits to this tab, you can select Refresh or Stop in the Action column. Recent Redirects The Recent Redirects tab provides a history of recently used configurations, which makes it simple to reactivate a switcher that was previously configured. To reactivate a previously configured switcher: Click the Recent Redirects tab. A list of recently configured switchers displays. Click the Start button next to the switcher that you want to reactivate. The page refreshes automatically and the changes are applied. Troubleshooting The Help tab provides troubleshooting options to force stop all active redirects or completely reset the Environment Switcher. Force Stop All Active Redirects To force stop all active redirects: Click the Help tab. Click Force Stop all Active Redirects. The Active Redirects tab is now empty and all active redirects are stopped. Reset Environment Switcher to the Default State Resetting the Environment Switcher to the default state and stop all current redirects, remove all information saved in the UI setting, remove recent redirects, stop the backend service, and close the Tealium Tools window. Use the following steps to reset the Environment Switcher: Click the Help tab. Click Force Reset to expand. Click Reset Environment Switcher. The Active Redirects and Recent Redirects tabs are now empty. All active redirects are stopped and recent redirects are purged. Additional Information Tealium Tools Browser Extension An overview of the Tealium Tools browser extension and how to install in on Google Chrome or Mozilla Firefox. List of Custom Tealium Tools Detailed information about available custom tools. Creating Custom Tealium Tools Detailed developer information and migration steps for existing utilities. ... View more

Overview A simple tool that helps you determine the selector for a specific element in a page. This selector is often used in the congfiguration of a jQuery onHandler Extension. This tool requires that jQuery already be loaded on the page. Resource URL Add this tool to the  Tealium Tools browser extension  using the following URL : https://solutions.tealium.net/hosted/tealiumTools/css_selector/selectortool.json Usage Upon launching the tool click the Init button, the navigate to the page that contains the element you want to inspect, then click the Start button. The next element you click in the page will be inspected by the CSS Selector Tool and the proper selector will be determined. Simply relaunch the tool to see the selector. This value can then be used in the Selector field of the jQuery onHandler extension.   ... View more

Th e Data Layer Identifier tool  identifies many of the popular tag management systems and their respective data layers that  may  be loaded on the page.   In this article: Table of Contents Placeholder How it Works You can use this tool instead of the browser console to display a nicely-formatted table that display all if the data layer variables on the page. This tool can also be used to display the data within any custom object that you enter into the tool. How To Use The tool uses two (2) methods to identify data layers on the page: Automatic detection of standard TMS data layer objects A custom data layer object name. Add the Resource URL to Tealium Tools Add this tool to  Tealium Tools  using the following URL : https://solutions.tealium.net/hosted/tealiumTools/dataLayerIdentifier/datalayer_identifier.json TMS Data Layers The automatic detection of standard TMS data layer objects method scans the page for popular TMS data layer objects and displays all of the objects found and their contents. The results are displayed in a view where each TMS data layer detected can be expanded and collapsed for easy inspection. Currently detected TMS vendors (and data layer name) are: Tealium (utag.data) Ensighten (n/a) Google Tag Manager (dataLayer) Adobe DTM (digitalData and s for Adobe Analytics) Segment (analytics.identify) Signal (page_data) Identifying Standard TMS Data Layer Objects on the Page Use the following steps to identify standard TMS data layer objects on the page: Open the Data Layer Identifier tool. On the TMS Data Layers tab, click Auto-Detect. The results screen displays. Expand and collapse each TMS vendor to inspect the data layer. Custom Data Layer Object Some data layers are implemented using a custom variable name. If you know the custom object name, you can enter it on this tab to display the data. Use the following steps to identify a custom data layer object: Open the Data Layer Identifier tool. Click the Custom Data Layer tab . Enter the following fields: Custom Object – the name of the JavaScript object to read Inclusions – the name of data layer properties to display (all other values will be ignored) Exclusions – the name of data layer properties to ignore Click Read Custom Object. The results screen displays. Expand the custom object to view the data layer properties. ... View more

Overview This tool will export all users' permission settings for an account to a CSV file.  This tool must be run while viewing the iQ page. You must have the Manage Users permission in the active account for this tool to run. Resource URL Add this tool to the  Tealium Tools browser extension  using the following URL : https://solutions.tealium.net/hosted/tealiumTools/permission_export/permission_export.json  Description Upon launching the tool you'll be prompted to get permissions for the account you're currently logged into on iQ.    Click Start and permissions for the account will be fetched. Once all users permissions are checked, you'll be prompted to download a CSV file.   The CSV file will output each users permissions on a line and specify which profiles each user has access to as well as the permissions for each profile. The value for each permission will be "Y" or "N", representing "Yes, has the permission" or "No, does not have the permission" respectively.  ... View more

Overview This tool will export all variables and their tag mappings to a CSV file.  This tool will only run within the TiQ page. This will only work for the specific profile the user is currently logged into, each profile will need to be logged into seperately.  Resource URL Add this tool to the  Tealium Tools browser extension  using the following URL : https://solutions.tealium.net/hosted/tealiumTools/mappings_export/mappings_export.json Description Upon launching the tool you'll be prompted to get the variables and their tag mappings for the profile you're currently logged into on TiQ. Select the option to gather data for either All Tags, Active Tags, or Inactive Tags. Click Start and variables and their tag mappings for the profile will be fetched. Once all variables and their tag mappings are fetched, you'll be prompted to download a CSV. The CSV will output the following columns of data, including a header line: Variable Name   - the name of the data layer variable Variable Type   - the type of the variable (js, dom, cp, etc.) Variable Description   - the description of the variable Tag Title (Tag UID)   - the tag title and UID where the variable is referenced Tag Mappings   - the tag vendor data mappings used with this variable Example line from file where the Tealium variable "page_name" is mapped in a Tealium Generic Tag to the parameter "pg": Variable Name,Variable Type,Variable Description,Tag Title (Tag UID),Tag Mappings page_name,js,"User Friendly Page Name.",Tealium Generic Tag (498),"pg" If a variable is not mapped to any tags, the name/type/description will still be included in the spreadsheet. ... View more

This bookmarklet is a quick way to view the Tealium data layer on a web page. Once added to your browser as a bookmark, navigate to a page where Tealium is installed and click the bookmark. A pop-up window will appear with a text representation of the Universal Data Object (utag_data). How It Works This is a simple tool intended for basic testing of the Universal Data Object (utag_data) on a page. When launched, this tool looks for the page variable utag_data and displays its contents. This tool does not detect the data passed to any tracking calls (utag.view() or utag.link()). It only displays the contents of the utag_data object. For a more advanced tool that displays all event tracking data, see the Universal Tag (UTAG) Debugger). The utag_data object often contains variables other than the ones populated on the page. To simplify what information is displayed, only the following variable types will be displayed: Universal Data Object (e.g. utag_data['page_name'] ) DOM (e.g. utag_data['dom.pathname'] ) JavaScript Page (e.g. utag_data['js_page.my_global'] ) Query String Parameters (e.g. utag_data['qp.campaign'] ) Built-In Tealium (e.g.  utag_data['tealium_event'] ) Additional resources: How the Universal Data Object Works Using the Simple Data Layer Viewer The viewer is added to you browser as a Javascript bookmark. Simple Tealium Data Layer Viewer JavaScript code:  (function(){ function align_json (str, del) { del = del || ":"; var lines = str.split("\n"); var fields = []; var max_indent = 0; var new_string = ''; var in_array = false; for(var i=0; i < lines.length; i++) { var line = lines[i]; if(line.indexOf(": ") > 0) { if(line.indexOf("[") == line.length-1) { in_array = true; } var new_indent = line.indexOf(':'); if(new_indent > max_indent) { max_indent = new_indent; } fields.push(line); new_string = new_string + '@'; } else { if(in_array) { line = line.replace(/^\s+/, " "); fields[fields.length-1] = fields[fields.length-1] + line; if(line.indexOf("]") > 0) { in_array = false; } } else { new_string = new_string + line + "<br>"; } } } var new_fields_str = ''; var sorted_fields = fields.sort(); for(var j=0; j < sorted_fields.length; j++) { var two_parts = []; var split_ch = sorted_fields[j].indexOf(':'); two_parts.push(sorted_fields[j].slice(0, split_ch)); two_parts.push(sorted_fields[j].slice(split_ch+1)); two_parts[1]=two_parts[1].replace(/\[\s+/, "["); two_parts[1]=two_parts[1].replace(/\s+\]/, "]"); if(two_parts[1].lastIndexOf(",") != two_parts[1].length-1) { two_parts[1] = two_parts[1] + ","; } var line_length = two_parts[0].length; var padding = max_indent - line_length; for(var k=0; padding > 0 && k < padding; k++) { two_parts[0] = two_parts[0] + ' '; } new_fields_str = new_fields_str + two_parts[0] + ' :' + two_parts[1] + "<%2Fbr>"; } new_string = new_string.replace(/@+/, new_fields_str); return new_string; } delete Array.prototype.toJSON; var udo_string = align_json(JSON.stringify(utag.data, function(key, value) { if(typeof key == 'number') { return value;} if(key.indexOf("_t_") == 0 || key.indexOf("va.") == 0 || key.indexOf("cp.") == 0 || key.indexOf("meta.") == 0 || key.indexOf("_c")==0 || key.indexOf("ut.")==0) { return undefined; } else { return value; } }, 4)); window.open("","udo_pretty_print", "width=600,height=600,location=0,menubar=0,status=1,toolbar=0,resizable=1,scrollbars=1").document.write('<title>Simple Tealium Data Layer Viewer<%2Ftitle><pre style="font-family:\'Courier New\',Monaco,monospace; font-size:12pt;" id="udo_string">'+udo_string+'<%2Fpre>'); })(); To add the bookmarklet to your browser: Copy the code above. In your browser, add a new bookmark, then edit it so you can modify the URL field. First, type  at the beginning of the field, then paste the code after it. To use the bookmarklet: Navigate to a site with Tealium installed. Click the bookmark. A pop-up appears displaying the data layer (UDO) variables and values.       ... View more

This article describes how to set up the Google Analytics (gtag.js) tag in your Tealium iQ Tag Management account. Google Analytics provides APIs to collect, configure, and report on user-interactions with your online content. Using gtag.js lets you benefit from the latest tracking features and integrations as they become available. In this article: Tag Tips Use mappings to: Dynamically override the E-Commerce extension values Setup event triggers Add custom Metrics, Dimensions, and Content Groups Replace cst in custom event variables with your desired event name Supports the following E-Commerce extension values: Order ID Order Total Shipping Amount Tax Amount Store Promo Code Customer ID List of Product IDs List of Names List of Brands List of Categories List of Prices List of Quantities List of Discounts Tag Configuration First, go to Tealium's tag marketplace and add the Google Analytics (gtag.js) tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Tracking ID Tracking ID of the Google Analytics property to which you want to send data Example: UA-XXXXXX-13 Use a comma-separated list to send data for multiple properties.  Enable App + Web by including the measurement ID in the Tracking ID value.  For example; UA-XXXXXX-13,G-XXXXXXXXXX Global Object The name of the Global Object used for the event queue. If not specified, "gtag" is used. Not required for most implementations. Cross-Tracking Domains A comma-separated list of domains to use with Cross-Domain Tracking ( setAllowLinker ). To use this list, Cross-Domain Tracking must be set to true. Should be the top level domain, such as tealiumiq.com. Cross-Domain Tracking Sets the value for setAllowLinker and enables the cross-domain tracking plug-in. To use this feature, one or more domains must be specified in the "Cross-Tracking Domains" field or be mapped to crossDomainTrack . Transport Type Specifies the transport mechanism with which hits are sent. Allow Advertising Features Enables Google Analytics to collect data about your traffic via the Google Ad Manager (DoubleClick) cookie, in addition to data collected through the standard Google Analytics implementation. Setting this to Off disables all advertising, reporting, and remarketing features, overrides any property settings established in the Google Analytics user interface. Enhanced Link Attribution If unsure, use the default value (false). Google Analytics provides enhanced link attribution to improve the accuracy of report data by automatically differentiating between multiple links to the same URL on a single page and using link element IDs. Track Screen Views Enables App/Screen tracking. When enabled, a separate screenview request is sent after the initial pageview. Anonymize IP Tells Google Analytics to anonymize the information sent by the tracker objects by removing the last octet of the IP address prior to its storage. Slightly reduces the accuracy of geographic reporting. Clear Vars Clears items usually set for the lifetime of the tracker after each tracking request. Optimize Container ID Sets the optimize_id and enables the Google Optimize plug-in. This ID is found in your Optimize accounts page. Example: GTM-XXXXXX Use AMP Client ID The Google AMP Client ID allows you to uniquely identify users that engage with your content on AMP and non-AMP pages. If you opt-in, Google Analytics uses the AMP Client ID to determine that multiple site events belong to the same user when those users visit AMP pages via a Google AMP viewer. Data Layer Name By default, the data layer initiated and referenced by the global site tag is named dataLayer . Only rename the data layer if your project requires a separate name. Allow Anchor When true, the _ga parameter is added to the query portion of the URL rather than the anchor portion ("#"). 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 Variable Description tracking_id Tracking ID Tracking ID of the Google Analytics property to which you want to send data Example: UA-XXXXXX-13 Use a comma-separated list to send data for multiple properties. transport_type Transport type page_title Page Title page_location Page Location page_path Page Path cookie_name Cookie Name cookie_domain Cookie Domain cookie_expires Cookie Expires cookie_prefix Cookie prefix cookie_update Cookie update config.linker.accept_incoming Boolean Cross-Domain Tracking Sets the value for setAllowLinker and enables the cross-domain tracking plug-in. To use this feature, one or more domains must be specified in the "Cross-Tracking Domains" field or be mapped to crossDomainTrack . config.linker.domains Array Cross-Tracking Domains A comma-separated list of domains to use with Cross-Domain Tracking ( setAllowLinker ). To use this list, Cross-Domain Tracking must be set to true. Should be the top level domain, such as tealiumiq.com. allow_ad_personalization_signals Boolean Allow ad personalization signals. Enables Google Analytics to collect data about your traffic via the Google Ad Manager (DoubleClick) cookie, in addition to data collected through the standard Google Analytics implementation. config.link_attribution.cookie_name Link Attribution Cookie Name config.link_attribution.cookie_expires Link Attribution Cookie Expiration config.link_attribution.levels Link Attribution Levels config.campaign.id Campaign ID config.campaign.name Campaign Name config.campaign.source Campaign Source config.campaign.medium Campaign Medium config.campaign.content Campaign Content config.campaign.term Campaign Term/Keyword config.anonymize_ip Boolean Anonymize IP Tells Google Analytics to anonymize the information sent by the tracker objects by removing the last octet of the IP address prior to its storage. Slightly reduces the accuracy of geographic reporting. clear_global_vars Boolean Clear Vars Clears items usually set for the lifetime of the tracker after each tracking request. config.optimize_id Optimize Container ID Sets the optimize_id and enables the Google Optimize plugin. This ID is found in your Optimize accounts page. Example: GTM-XXXXXX config.use_amp_client_id Boolean Use AMP Client ID The Google AMP Client ID allows you to uniquely identify users that engage with your content on AMP and non-AMP pages. If you opt-in, Google Analytics uses the AMP Client ID to determine that multiple site events belong to the same user when those users visit AMP pages via a Google AMP viewer. config.sample_rate Sample Rate config.site_speed_sample_rate Site Speed Sample Rate customer_id User ID Overrides _ccustid config.client_id Client ID Event Variable Description event_name Event Action event.event_category Event Category event.event_label Event Label event.value Event / Timing Value event.name Timing Variable Name event.description Exception Description event.non_interaction Non-Interaction event.fatal Boolean Fatal Error event.search_term Search Term event.method Method event.content_type Content Type event.content_id Content ID event.destination Destination event.start_date Start Date Date format is YYYYMMDD. event.end_date End Date Date format is YYYYMMDD. event.custom Custom Event Data event.anonymize_ip Boolean Anonymize IP Tells Google Analytics to anonymize the information sent by the tracker objects by removing the last octet of the IP address prior to its storage. Slightly reduces the accuracy of geographic reporting. event.send_to Override Default Routing event.event_callback Event callback App / Screen Tracking Variable Description screen_view Boolean Track Screen Views Enables App/Screen tracking. When enabled, a separate screenview request is sent after the initial pageview. event.screen_name Screen Name config.app_name Application Name config.app_id Application ID config.app_version Application Version IDconfig.app_installer_id Application Installer Content Groups Variable Description content_group1 Content Group 1 content_group2 Content Group 2 content_group3 Content Group 4 content_group4 Content Group 4 content_group5 Content Group 5 Dimensions Variable Description dimension1 Dimension 1 dimension2 Dimension 2 dimension3 Dimension 3 dimension4 Dimension 4 dimension5 Dimension 5 dimension6 Dimension 6 dimension7 Dimension 7 dimension8 Dimension 8 dimension9 Dimension 9 dimension10 Dimension 10 dimension11 Dimension 11 dimension12 Dimension 12 dimension13 Dimension 13 dimension14 Dimension 14 dimension15 Dimension 15 dimension16 Dimension 16 dimension17 Dimension 17 dimension18 Dimension 18 dimension19 Dimension 19 dimension20 Dimension 20 -- Premium Dimension-- 0 dimension21 - dimension200 Dimension 21 through Dimension 100 Metrics Variable Description metric1 Metric 1 metric2 Metric 2 metric3 Metric 3 metric4 Metric 4 metric5 Metric 5 metric6 Metric 6 metric7 Metric 7 metric8 Metric 8 metric9 Metric 9 metric10 Metric 10 metric11 Metric 11 metric12 Metric 12 metric13 Metric 13 metric14 Metric 14 metric15 Metric 15 metric16 Metric 16 metric17 Metric 17 metric18 Metric 18 metric19 Metric 19 metric20 Metric 20 -- Premium Metric-- 0 metric21 - metric200 Metric 21 through Metric 200 Enhanced E-Commerce Variable Description code>checkout_step Number Checkout step. checkout_option Checkout Option. order_currency Currency Overrides _ccurrency . code>order_id Transaction ID Overrides _corder . order_total Value/Order Total Overrides _ctotal . order_shipping Shipping Amount Overrides _cship . order_tax Tax Amount Overrides _ctax . order_store Affiliation/Store Overrides _cstore . order_coupon_code Promo Code/Coupon Overrides _cpromo . customer_id User ID Overrides _ccustid . product_id Array List of IDs Overrides _cprod . product_name Array List of Names Overrides _cprodname . product_brand Array List of Brands Overrides _cbrand . product_category Array List of Categories Overrides _ccat . product_variant Array List of Variants product_unit_price Array List of Prices Overrides _cprice . product_quantity Array List of Quantities Overrides _cquan . product_discount Array List of Discounts Overrides _cdisc . product_promo_code Array List of Promo Codes/Coupons product_action_list Array Product Action List product_list_name Array Product Name product_list_id Product List ID product_list_position Array Product Position product_location_id Product Location ID Enh E-Comm: Engagement Variable Description impression_id Array Product Impression ID impression_name Array Product Impression Name impression_category Array Product Impression Category impression_brand Array Product Impression Brand impression_variant Array Product Impression Variant impression_price Array Product Impression Price impression_list_name Array Product Impression List impression_list_position Array Product Impression Position promo_id Array Promotion ID promo_name Array Promotion Name promo_creative_name Array Promotion Creative promo_creative_slot Array Promotion Position App+Web Travel Variable Description event.trip_type Trip Type start_date Array Start Date end_date Array End Date origin Array Origin destination Array Destination flight_number Array Flight Number travel_class Array Travel Class fare_product Array Fare Product booking_code Array Booking Code event.passengers.total Total Number of Passengers event.passengers.adult Number of Adult Passengers event.passengers.child Number of Child Passengers event.passengers.infant_in_lap Number of Infant Passengers in Lap event.passengers.infant_in_seat Number of Infant Passengers in Seat App+Web Game Variable Description event.achievement_id Achievement ID event.character Character event.group_id Group ID event.item_name Item Name event.level Level event.level_name Level Name event.score Score event.success Success event.virtual_currency_name Virtual Currency Name Google Analytics 4 Support Google Analytics 4 (GA4) is currently supported through the App and Web mappings for this tag. ... View more

Tealium is excited to announce that we recently won the 2020 Khoros Community award in the category of All-Ways Connected.  We flexed our own integration muscles to show how using Tealium on Tealium can improve the customer experience. That's right, you're reading this post on an award-winning community site. But maybe you knew that because you remembered that TLC won an award in 2018. This year Khoros, the community platform behind TLC, gave awards to community sites that demonstrated excellence in different categories.  This year we won the category called All-Ways Connected! What is All-Ways Connected? This category recognizes a community that is successfully integrating Khoros to strategically align people, processes, and technology to connect with their customers in all ways. This category was made for Tealium. With over 1,000 vendors in our integrations marketplace , we were in the perfect position to showcase how we use our own product on our own site.  Each of the integrations highlighted in our winning entry takes advantage of our own Tealium Customer Data Hub account. Tealium on Tealium Our integration with Khoros starts with an implementation of Tealium iQ Tag Management. TLC has a solid data layer and extensive event tracking in place. This allows events to flow into Tealium EventStream where real-time connector actions send messages to Slack to keep our internal teams alerted to events on TLC.  Then we use Tealium AudienceStream to create audiences that trigger data flow to our Marketo instance to help onboard new community members. Award Showcase Khoros has been a great platform for TLC and we're humbled to have been chosen as the winner in a category that means so much to us. Please enjoy this showcase of our award and a brief message from our rockstar Senior Community Manager, Kristen Meren. Khoros Kudos - All-Ways Connected Winner - Tealium None of this could be possible without you, our amazing Tealium community members. Your passion for Tealium and contributions to TLC are what keep us going each day, so thank you! For more information, check out our winning entry and the full list of submissions to the 2020 Khoros Kudos Awards. ... View more

Question I'm not seeing some records in AudienceStore and/or AudienceDB. What would cause this? Answer A single-page visit (session) occurs when a visitor leaves your website (or mobile app) from the landing page (or launch screen) without any further interaction. As a result, AudienceStream only receives one event for that visitor session. These "single-page visits" are handled differently from multi-page visits. A single-page visit meets all of the following conditions: Only 1 Event Received at End of Visit The number of events received by the end of the visit is equal to 1. No Visitor Stitching The single event does not result in visitor stitching. No Badges Assigned The visit does not result in the assignment of a badge attribute. If all of these conditions are met, the visit will be treated as a single-page visit. In addition, if a single-page visitor returns for a new session, it will be treated as a new visitor in AudienceStream. Single-page visits and visitors are not persisted in AudienceStream, are not passed to AudienceStore, and therefore not stored in AudienceDB. Things to consider: File Import These conditions do not apply to events received from an offline file import. EventStore and EventDB There will be records in EventStore and EventDB that do not have a matching record in AudienceStore and AudienceDB.   ... View more

This article describes how to set up the DialogTech connector. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Click To Virtual Receptionist ✓ ✓ Click To Voicemail ✓ ✓ Click To Agent ✓ ✓ Send SMS Message ✓ ✓ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: Name - a name for the connector. Description - a description of the connector. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Click To Virtual Receptionist Parameters Parameter Description Access Key Access Key from the Key Manager within a DialogTech account. For more information on this endpoint, see: https://apidocs.dialogtech.com/v1.0/docs/click-to-virtual-receptionist. Secret Access Key Secret Access Key from the Key Manager within a DialogTech account. Menu ID An existing Virtual Receptionist ID must be utilized. To find IDs for any existing Virtual Receptionist within your account, go to: Developer Tools > Building Block IDs. Phone to Call Can be any unformatted phone number. Action - Click To Voicemail Parameters Parameter Description Access Key Access Key from the Key Manager within a DialogTech account. For more information on this endpoint, see: https://apidocs.dialogtech.com/v1.0/docs/click-to-voicemail. Secret Access Key Secret Access key from the Key Manager within a DialogTech account. Voicemail Box ID An existing Voicemail ID must be utilized. To find IDs for any existing voicemail within your account, go to: Developer Tools > Building Block IDs. Phone To Call Can be any unformatted phone number. Action - Click To Agent Parameters Parameter Description Access Key Access key from the Key Manager within a DialogTech account. For more information on this endpoint, visit: https://apidocs.dialogtech.com/v1.0/docs/click-to-agent. Secret Access Key Secret Access Key from the Key Manager within a DialogTech account. Queue ID The building block ID of the queue the agent is a member of. Agent ID The Agent ID of the agent receiving the call. Phone to Call Can be any unformatted phone number. First Caller ID Must be a registered number, one of the two numbers being dialed, or tracking number within the DialogTech account. Second Caller ID Must be a registered number, one of the two numbers being dialed, or tracking number within the DialogTech account. Record 0 or 1. 0: do not record the call (default). 1: record the call. Warning 0 or 1 or 2 or 3. 0: do not play a call recording warning. 1: play a call recording warning for both parties (default). 2: play call recording warning for just the agent. 3: play call recording warning for just the phone_to_call third party. Action - Send SMS Message Parameters Parameter Description Access Key Access Key from the Key Manager within a DialogTech account. For more information on this endpoint, see: https://apidocs.dialogtech.com/v1.0/docs/sms-send-message. Secret Access Key Secret Access Key from the Key Manager within a DialogTech account. To Can be any unformatted phone number. From Must be a DialogTech SMS enabled tracking number. Message Defines the message being sent to the thrid party. DialogTech does not limit or break texts into smaller batch messages. This behavior is dependent on the recipient's carrier. ... View more

The China CDN Deployment Extension is a Pre Loader extension that runs before the Data Layer Processing. This extension determines a user's location (inside or outside China), which allows web site content to be sent to the user from the appropriate CDN. You can use this extension when you cannot modify the source code for a web site to add logic to determine the user's location. In this article: Table of Contents Placeholder Prerequisites To create a draft of a China CDN Deployment extension, you need the   Manage JavaScript Code Extensions   account-level permission. How it Works The China CDN Deployment Extension consists of a code editor pre-filled with JavaScript code that is executed during the pre-loader scope. This code contains logic to do the following: Determine the users location based on the users browser language, timezone, and IP address. Set a cookie with the best CDN for that user. All subsequent site visits read the cookie value, if it is present, and fetch all utag content from the most specified CDN. Setting the cookie in the pre-loader scope means that the initial page request is served from the appropriate CDN. Configuring the Extension When you add the China CDN Deployment Extension to a profile, an Ace Editor window is displayed, which contains the default code for the extension. You can configure the domainMap, languageMap, and gmtMap variables for the extension.  In addition, you can specify the matchLogic to determine a user's location. Setting Up Domain Mapping If you have multiple domains associated with a profile, you can use the domainMap to direct all domain traffic to a specific CDN. domainMap = { 'www.yourwebsite.cn': 'cn' }, Adjusting Language Mapping The languageMap lists the most common Chinese language variations and maps them to a single CDN. languageMap = { 'zh': 'cn', 'zh-HK': 'cn', 'zh-CN': 'cn', 'zh-TW': 'cn' }, Adjusting Timezone Mapping The gmtMap specifies the Chinese time zone. gmtMap = { '-480': 'cn' }, Adjusting the Match Logic The default matchLogic for all defined variables requires them to all be true. Set it to 'or' if only some of the variables need to be true. matchLogic = 'and'; // 'or' Turning IP Location Detection On or Off If locationTest is true, fetch the users IP address and return a location. If locationTestForce is true, runs the location logic every time regardless of the cookie value or other match logic results. Both default to true to provide optimal location detection for every user session. var locationTest = true; // Use location test logic var locationTestForce = true; // Use location test in all scenarios Adjusting the Cookie Duration and When to Trigger a Retest The retestTime variable is specified in milliseconds and specifies when the retest is done to determine the user's location. The default is one day. var retestTime = 86400000; // 1 day       ... View more

The data layer is the foundation of your Tealium solution and will serve as the one true definition of your data across all digital assets and customer interactions. The data layer comprises all of the various data elements that will be collected across your site and the visitor interactions and events that will be tracked. In this article: Table of Contents Placeholder Universal Data Object (UDO) The data layer is implemented on your website as a JavaScript object called utag_data in which you expose data from the page to the Tealium tag. The properties in this object should be named using plain-English, vendor neutral terms that are tailored to your business. Example declaration of utag_data : <script type="text/javascript"> var utag_data={ "tealium_event" : "search", "page_name" : "Search Results", "search_results" : "42", "search_keyword" : "Tealium shirt" }; </script> The utag_data  object variable should be defined and populated prior to loading the Universal Tag (utag.js). When utag.js loads in the page it looks for the utag_data variable and uses its data to automatically trigger an page view tracking call with utag.view() . If you have a single page application, or are calling utag.view() manually, you might not need utag_data. Learn more about your page tracking options. Syntax Guidelines When implementing the UDO there are certain guidelines to follow, not only to avoid errors or inconsistencies in your implementation but also to conform to JavaScript and Tealium standards. String Values Use string values for all variables, including boolean and numeric data. Escape Quotes Enclose all values in double quotes or single quotes and escape any quotes that might appear in the value itself (eg. utag_data.page_name = 'It\'s All About the Data!'; ). Boolean Values For boolean values use "1" and "0" to represent true and false. This is the simplest way to represent a boolean using strings. Amount Values Use strings for all dollar amounts and exclude all currency symbols and commas eg. utag_data.order_total = "1234.00"; instead of "$1,234.00" .   Array Values Use array values for all product related variables. The Tealium library, and each vendor tag integration, is designed to use arrays for all product-related data (ID, price, quantity, etc.) eg.  utag_data.product_id = ["P1234", "P4567", "P7890"]; Avoid Extra Code Do not add extra code to the UDO script block. If any code in the same script block fails, the UDO may not be defined correctly which might lead to unexpected data being passed to your vendor tags. Examples Standard Page The following is a sample UDO as it would appear on a page. This specific example shows properties that might appear on a "Shopping Cart" page with two products in the cart. <script type="text/javascript"> var utag_data = { "tealium_event" : "cart_add",     "country_code"       : "US",         "currency_code"      : "USD",         "page_name"          : "Cart: View Shopping Bag",        "page_type"          : "cart",         "product_id"         : ["PROD123", "PROD456"],         "product_name"       : ["Red Shoes", "Black Socks"],     "product_category"  : ["Footwear", "Apparel"],         "product_quantity"  : ["1", "2"],         "product_unit_price" : ["65.00", "4.75"],         "cart_total_items"  : "3",         "cart_subtotal"      : "74.00"     }; </script> The UDO can be updated with additional values outside of the declaration block, as long as the data gets set prior to loading utag.js. UDO variables set after loading utag.js will be ignored.   <script type="text/javascript"> utag_data["page_name"] = "View Cart"; <script> Page Specific Data When populating the UDO, only include variables pertinent to the current page type. This reduces clutter in the page code and eliminates confusion about what data is expected. Below is an example of a search page UDO that omits unnecessary items such as product and order data. <script type="text/javascript"> var utag_data={ "page_name" : "Search Results", "page_type" : "search", "search_results" : "42", "search_keyword" : "tennis shoes" }; </script> Product Arrays Product variables are to be populated as arrays, even when a single product is being set. Below are examples of setting the product ID variable with one product ID (eg. on a Product Detail page) and with three product IDs (eg. on a Shopping Cart page). // Single product (eg. product detail page) utag_data["product_id"] = ["PROD123"]; // Multiple products (eg. cart page) utag_data["product_id"] = ["PROD123", "PROD456", "PROD789"]; Array Alignment All product array variables should have the same number of elements to ensure data alignment. In this example, notice that the first element in each array corresponds to the first product. Properties associated with this product (such as ID, price, and quantity) all appear in the first element in each array, while the properties of the second product will appear in the second element in each array, and so on. // Product 1: // ID = PROD123 // Price = 3.00 // QTY = 1 // // Product 2: // ID = PROD456 // Price = 5.00 // QTY = 1 // utag_data["product_id"] = ["PROD123", "PROD456"]; utag_data["product_price"] = ["3.00", "5.00"]; utag_data["product_quantity"] = ["1", "1"]; Additional Reading Data Layer Variables in iQ Tag Management An Introduction to the Data Layer ... View more

This article describes how to set up the Zendesk connector. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create or Update User ✓ ✗ Create New Ticket with Requester ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: Username Password access must be enabled in the Zendesk Support admin interface at Admin > Channels > API. If an agent or admin has enabled 2-factor authentication in their user profile, they will not be able to use basic authentication. Password For more information, see Zendesk Authentication. Subdomain The unique subdomain for your Zendesk account. Example: <subdomain>.zendesk.com . Only input the subdomain, not the full domain. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Create or Update User Parameters Parameter Description Email Email address of the user. Name Name of the user. User Properties Any custom user properties to add to the user profile. Role If you don't specify a role parameter, the new user is assigned the role of end-user. For more information, see Create or update user. User Verified If you need to create users without sending out a verification email, pass a "verified": true parameter. Organization Name The user can also be added to a named organization by adding an organization name. Action - Create New Ticket with Requester Parameters Parameter Description Subject The subject of the ticket. Comment An object that adds a comment to the ticket. For more information, see Creating at ticket with a new requester. Requester Name Name of the user submitting the ticket. Requester Email Email of the user submitting the ticket. Priority Allowed values are urgent, high, normal, or low. Type Allowed values are problem, incident, question, or task. Tag A tag to add to the ticket. Note that the tags replace any existing tags. ... View more

This article describes how to use the data types array of strings, array of numbers, and array of booleans. In this article: Table of Contents Placeholder How it Works Before you begin, familiarize yourself with the following: Using Attributes Using Enrichments Arrays are used to store a list of values. Whereas a string or number attribute can only contain a single value, such as "Home Page" or 12.95 , an array can contain multiple values, such as  ["Pants", "Shirts"] or [5.99, 12.95] . Arrays are available for the number, string, and boolean attribute data types. In this article, arrays are represented in JSON format in all examples. ["Pants", "Shirts", "Shoes"] [2, 4, 6] [true, false, false] [] Arrays can contain duplicate values. Array of Strings Enrichments The array of strings attribute stores a list of text values. The array of strings is available in the following scopes: Event, Visit, Visitor. Add a String This enrichment adds the value of a string attribute to the array. The added attribute can only be a string, iQ variable, or omnichannel attribute. Attribute Name: product_name STARTING VALUE ["Pants"] ENRICHED WITH "Shirts" RESULTING VALUE ["Pants", "Shirts"] Add an Array of Strings This enrichment adds all the values from another array to the array. The added attribute can only be an array of strings or an iQ variable. Attribute Name: product_name STARTING VALUE ["Pants"] ENRICHED WITH ["Shirts", "Shoes"] RESULTING VALUE ["Pants", "Shirts", "Shoes"] Difference Between Two Arrays This enrichment takes two arrays as input, and returns a new array containing all values found in the first array but not the second. In this example, values from "Wishlist Products" that do not also occur in "Purchased Products" are added to the resulting array.   Attribute Name: Unpurchased Products STARTING VALUE [] ENRICHED WITH Difference between: Wishlist Products ["Pants", "Shirt", "Shoes", "Belt"] and Purchased Products ["Pants", "Shirt"] RESULTING VALUE ["Shoes", "Belt"] This example shows that the resulting attribute value is replaced, not appended to and that repeated values in the first array are removed. STARTING VALUE [7, 8, 9] ENRICHED WITH Difference between: Some Numbers [1, 3, 1, 2, 3] and Some Other Numbers [3] RESULTING VALUE [1, 1, 2] Reset This enrichment removes all values from the array. Attribute Name: product_name STARTING VALUE ["Shoes", "Belt"] ENRICHED WITH   RESULTING VALUE [] Lowercase This enrichment lowercases every value in the array. Attribute Name: product_name STARTING VALUE ["Shoes", "BELT"] ENRICHED WITH   RESULTING VALUE ["shoes", "belt"] Set to Set of Strings Sets an array of strings to a set of strings. This enrichment replaces all values in the array. Attribute Name: Active Browser Types STARTING VALUE ["IE"] ENRICHED WITH ["Chrome" "FireFox", "Opera"] RESULTING VALUE ["Chrome" "FireFox", "Opera"] Add a Set of Strings Adds a set of strings to a string array. This enrichment preserves the existing values in the array, therefore there can be duplicate items in the resulting value. Attribute Name: product_name STARTING VALUE ["Pants"] ENRICHED WITH ["Pants", "Shoes", "Ties"] RESULTING VALUE ["Pants", "Pants", "Shoes", "Ties"] Remove a String from the Array Specify a first, last, or all instances of a string to remove. This enrichment removes from an array every instance of the item selected for removal. Attribute Name: product_name STARTING VALUE ["Pants", "Pants", "Shoes", "Ties"] ENRICHED WITH "Pants" RESULTING VALUE ["Shoes", "Ties"] Array of Numbers Enrichments The array of numbers attribute stores a list of numeric values. The array of numbers is available in the following scopes: Event, Visit, Visitor. String representations of numbers ("0", "123", "12.95") are converted to their numeric values. All other non-numeric values are ignored. Add a Number This enrichment adds a number value to the array. The added attribute can only be a number, iQ variable, or omnichannel attribute. For example, you may wish to add the last purchase value to the rolling total_purchase value array. Attribute Name: last_purchase Starting Value [12.95] Enriched With 5.99 Resulting Value [12.95, 5.99] Add an Array of Numbers This enrichment adds all the values from another array to the array. The added attribute can only be an array of numbers or iQ variable. For example, you may wish to add the array of last purchased purchase values to the array of all purchases. Attribute Name: last_purchase Starting Value [12.95] Enriched With [5.99, 10.00] Resulting Value [12.95, 5.99, 10.00] Reset This enrichment removes all values from the array. For example, you may wish to remove the last purchase items from the array of last purchases. Attribute Name: last_purchase Starting Value [12.00, 5.00] Resulting Value [] Set Array of Numbers to be the Difference of Two Arrays This enrichment takes two arrays as input, looks for values that occur in one and not the other, and inserts them into the array. In this example, values from "Gift Card Amounts" that do not also occur in "Gift Cards Purchased" are added to the resulting array. Attribute Name: gift_card_not_purchased Starting Value [] Enriched With Difference between: Gift Card Amounts [5.00, 10.00, 25.00, 50.00, 100.00, 250.00] and Gift Cards Purchased [25.00, 50.00] Resulting Value [5.00, 10.00, 100.00, 250.00] Array of Booleans Enrichments The array of booleans attribute stores a list of true/false values. The array of booleans is available in the following scopes: Event, Visit, Visitor. The strings "true" and "false" (any mix of upper/lowercase) are converted to their respective boolean values. All other non-boolean values are ignored. Add a Boolean This enrichment adds a value to the array. The added attribute can only be a boolean, iQ variable, or omnichannel attribute. For example, you may wish to add a boolean to the array to represent that the customer purchased on their last visit. Attribute Name: last_purchase Starting Value [true] Enriched With false Resulting Value [true, false] Add an Array of Booleans This enrichment adds all the values from another array to the array. The added attribute can only be an array of booleans or iQ variables. For example, you may wish to add to the boolean array those visits in which the customer purchased items. Attribute Name: last_purchase Starting Value [true] Enriched With [false, True] Resulting Value [true, false, true] Reset This enrichment removes all values from the boolean array. Attribute Name: last_purchase Starting Value [true, false, true] Enriched With   Resulting Value [] ... View more