Tealium Learning Center

This article describes how to set up the SMARTASSISTANT 1.1 tag in your Tealium iQ Tag Management account. With SMARTASSISTANT, businesses can create Guided Selling solutions to share their expert advice much quicker and shoppers can receive helpful and immediate support to make more confident and smarter purchase decisions. In this article: Tag Tips Use mapping to dynamically override the standard config values. Tag Configuration First, go to Tealium's tag marketplace and add the SMARTASSISTANT 1.1 tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Advisor Code: Your SMARTASSISTANT supplied Advisor Code. Subdomain: The first part of your advisor context path. Example: //{subdomain}.smartassistant.com/advisor-fe-web Div ID: This is the Div ID on your page where the advisor-container div will be added. Advisor Container Div ID: This is the integration container on your page where your advisor will go. 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 Advisor Code (advisorCode) Subdomain (subdomain) Div ID (divId) Advisor Container Div ID (advisorDivId) ... View more

Bazaarvoice is a network that connects brands and retailers to the authentic voices of people where they shop. Tag Configuration First, go to Tealium's Tag Marketplace and add the Bazaarvoice Pixel tag to your profile (how to add a tag?). After adding the tag, configure the below settings: Client Name: The client name provided by Bazaarvoice Site ID: The Site ID is found in the Conversations configuration hub in the Bazaarvoice workbench under deployment zone. Default main_site Environment: The deployment environment where you want to implement the BV Pixel. Choose from production or staging Locale: The locale used by the BV Pixel implementation. Default en_US Load Rules Load Rules determine when and where to load an instance of this tag on your site. Recommended load rule: All Pages 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 the Bazaarvoice Pixel tag are built into its Data Mapping tab. Available categories are: Standard Destination Name Description Client Name Use to dynamically set or override the configuration value Site ID Use to dynamically set or override the configuration value Environment Use to dynamically set or override the configuration value Locale Use to dynamically set or override the configuration value RatingsAndReviews Present Set to true to send the current data with bvProduct value equal to RatingsAndReviews AskAndAnswer Present Set to true to send the current data with bvProduct value equal to AskAndAnswer Present Curations Present Set to true to send the current data with bvProduct value equal to Curations Present E-Commerce Since the Bazaarvoice Pixel tag is e-commerce enabled, it will automatically use the default E-Commerce Extension mappings. Manually mapping in this category is generally not needed unless: You want to override any extension mappings Your desired e-commerce variable is not offered in the extension Destination Name Description Order Delivery Date ( order_delivery_date ) The expected delivery date for this order Order Label ( label ) The label associated with this conversion Order Deployment Zone ( order_deployment_zone ) The deployment zone for this order Order ID ( order_id ) Unique identifier for this order. Use this to override the default e-commerce value _corder Order Total ( order_total ) The total revenue for this order. Use this to override the default e-commerce value _ctotal Order Shipping Amount ( order_shipping ) Shipping applied to the order. Use this to override the default e-commerce value _cship Order Tax Amount ( order_tax ) The tax applied to the order. Use this to override the default e-commerce value _ctax Order Currency ( order_currency ) Use this to override the default e-commerce value _ccurrency Customer City ( customer_city ) Use this to override the default e-commerce value _ccity Customer State ( customer_state ) Use this to override the default e-commerce value _cstate Customer Country ( customer_country ) Use this to override the default e-commerce value _ccountry List of Names ( product_name ) Use this to override the default e-commerce value _cprodname List of SKUs ( product_sku ) The product SKU for each line item. Use this to override the default e-commerce value _csku List of Categories ( product_category ) The product category for each line item. Use this to override the default e-commerce value _ccat List of Quantities ( product_quantity ) Quantity of product for each line item. Use this to override the default e-commerce value _cquan List of Prices ( product_unit_price ) The price of each item at point of sale. Use this to override the default e-commerce value _cprice List of Image URLs ( product_img_url ) The image URL of each line item. Conversion Destination Name Description Type The type of this conversion e.g. (Download, Compare, Coupon) Label The label associated with this conversion Value A value associated with this conversion. Do not send PII data E-Commerce and Conversion PII Destination Name Description Email The email address for the user associated with the transaction or conversion Locale The local for the user associated with the transaction or conversion e.g. en_US Nickname The nickname for the user associated with the transaction or conversion Customer/User ID Use this to override the default e-commerce value _ccustid Order Shipping Date Defines specific date to send a post-interaction email for this order Order Shipping Delay Defines the number of days after purchase to send a post-interaction email for this order List of Shipping Dates The shipping date for each line item List of Shipping Delays The shipping delay for each line item Events Map to these destinations for triggering specific events on a page. To trigger an event: Select an event from the dropdown list. You may choose from the predefined list or create a 'Custom' event. For a 'Custom' event, enter a name with which to identify it. In the Trigger field, enter the value of the variable being mapped. To map more events, click the + button and repeat steps #1 and #2. Click 'Apply'. The event triggers when the supplied value is found in the data layer. Destination Name Description Pageview ( trackPageView ) Track a view of a page Impression ( trackImpression ) Track the presence of consumer generated content on a page CGC In View ( trackInView ) Track that consumer generated content is visible on a page CGC Viewed ( trackViewedCGC ) Track that consumer generated content is visible on a page for a set amount of time Non-commerce Conversion ( trackConversion ) Track when a non-commerce user event has occurred eCommerce Transaction ( trackTransaction ) Track when a e-commerce user event has occurred Helpfulness Vote (helpfulness`) Track when a user event indicating a helpfulness vote has occurred Profile ( profile ) Track when a user event indicating a profile view has occurred Report ( report ) Track when a user event for clicking a report button Read More ( read_more ) Track when a user event for clicking a read more button Filter ( filter ) Track when a user event for filtering content has occurred Link ( link ) Track when a user has clicked a link Paginate ( paginate ) Track when a user event for requesting content from a different page occurs Ask ( ask ) Track when a user event for asking a question occurs Statistics ( statistics ) Track when a user event for viewing a histogram has occurred Write ( write ) Track when a user event indicating interaction with a contribution control has occurred Sort ( sort ) Track when a user event for rearranging the order of content has occurred Search ( search ) Track when a user event for searching consumer-generated content has occurred Submission ( submit ) Track when a user event for submitting consumer-generated content has occurred Custom Send a custom event type Event Parameters Map to these destinations if you wish to pass additional data with the Event(s) you mapped earlier. Note: Parameters are only used with pre-defined Events. See Custom Event Data to learn how to pass a Parameter with a Custom event. To pass a Parameter with a pre-defined Event: Event - Select a BazaarVoice event from the drop-down list. Parameter - Select a BazaarVoice Parameter from the dropdown list. For a Custom parameter, enter a name with which to identify it. Click +Add. Destination Name Description Content Container ID (containerId) ID of the HTML element containing the consumer-generated content Page Type (type) For view events - the type of page currently being viewed. For Feature events - defaults to "Used" if there is no value Product ID (productId) ID of the currently viewed product Category ID (categoryId) ID of the currently viewed product or page's category Root Category ID (rootCategoryId) ID of the top level category of the currently viewed product or page's category Brand Name (brand) Name of the brand of the currently viewed product or page HTML Control Name (name) Used to describe the purpose of the HTML control Number of Reviews (numReviews) The total number of reviews on the current page Number of Questions (numQuestions) The total number of question on the current page Number of Answers (numAnswers) The total number of answers on the current page Average Rating (avgRating) The average overall rating for the product on the current page Percent Recommended (percentRecommended) The number of recommendations divided by the total review count Metadata Detail1 (detail1) This value aims at capturing secondary metadata about the Feature Used active event Metadata Detail2 (detail2) When applicable, this attribute should capture additional metadata about the HTML control Minimum Pixels (minPixels) Minimum number of pixels the consumer-generated content container must be view for the analytics event to execute Minimum Time (minTime) Minimum amount of time, in milliseconds, that a portion (minPixels) of the element be continuously on screen Custom A custom variable Custom Event Data Map to these destinations if you wish to pass a custom parameter with a custom Event that you mapped in the Events tab. To map a Custom Event Data variable: Event Action - Enter the name of the Custom Event exactly as specified in the Events tab. Parameter - Enter the name of the Parameter you wish to send. Click +Add. Vendor Documentation Implement Collection BV Pixel Conversations API BV Pixel ... View more

Event specifications are a way to organize and validate the quality of incoming data. Specifications define the attributes required for types of events and provide code examples for your installation. Once created, specifications allow the data quality of your events to be validated in real-time using Live Events. This article covers the following topics: Table of Contents Placeholder How It Works Event specifications represent your data layer in the Customer Data Hub . Events entering the Customer Data Hub are identified by the  tealium_event  attribute. The value of this attribute represents the name of the event and the specification associated with it. The specification also indicates which event attributes are required to be populated in the event. Example Specification Let's look at an example of an event specification for the event named video_complete which occurs upon the completion of watching a video. Event Data Object {     "tealium_event" : "video_complete", // name of event and specification     "video_id" : "xWlEk2i9r5Q",     "video_length" : 300,     "video_name" : "How to track videos in Tealium",     "video_platform" : "YouTube", } The   tealium_event  attribute identifies the type of event, in this case video_complete . The additional attributes provide contextual information about the event and the corresponding event specification defines the required attributes and their expected data types, as shown in the following example. Event Specification Specification Code Sample Tracking code for the cart_add event for an iQ Tag Management data source named "My iOS App" Event specifications provide two primary benefits for data management: To standardize the implementation of events across all platforms. To evaluate the data quality of incoming events. Live Events and Feeds Each event specification automatically creates a matching event feed. This feed can be configured for data storage via DataAccess, or linked to connector actions. Feeds linked to an event specification cannot be deleted and their names cannot be changed. Example: Once an event specification is created and the tracking code is implemented, use Live Events to view incoming events in real-time to evaluate their data quality. As events arrive in the Customer Data Hub, when the tealium_event  attribute matches an event specification, the incoming attributes are compared against the requirements of the specification and marked as valid or invalid. Example: Valid cart_empty  event Example: Invalid  cart_empty  event due to lack of matching event specification Using Event Specifications The following sections describe the steps required to add custom event specifications or add events from the event specification marketplace or live events. Event specifications can be added as custom events or added from the marketplace of built-in events. Custom events can use any event name and any attribute requirements. Creating a Custom Event Specification Custom specifications use a  tealium_event value that you determine. Once you create a custom event specification, the name of the event cannot be changed. Use the following steps to add a custom event specification: In the sidebar, select EventStream > Event Specs. Click + Add Event Specification and select Add Custom Specification from the drop-down list. Enter the name of the event (value of   tealium_event ). Optional. In the Notes field, enter notes to describe the event, such as how the event is triggered and what the event is to accomplish. Click Add Label to apply labels. This step is optional. From the drop-down list, select an event attribute and mark the attribute as required or not required. Click + Define New Attribute to create a new attribute for this specification. Remove an attribute clicking the (-) button. You can add additional attributes by clicking + Add Attribute and then repeating Step 6. Click Finish. The following example shows a custom event specification named gallery_view . Click Save and Publish to save and publish to your account. Adding a Marketplace Specification The event specification marketplace contains commonly used pre-built events. Once an event is added, the only change that can be made to a marketplace specification is the addition of attributes to the definition. When adding an event specification from the marketplace, the original event name and attribute list cannot be changed. Use the following steps to add a marketplace specification: In the sidebar, select EventStream > Event Specs. Click Add Event Specification > Add From Marketplace. Click an event name to preview the specification. Click Select All or select one or more specifications by ticking the box next to the event name. Click Finish. Click Save and Publish to save and publish to your account. Creating Event Specification from Live Events Event specifications can be added directly from the event details view of Live Events. Live events detect events that match a marketplace specification and provide a preview of the requirements to make it easy to add the specification without leaving the screen. Events that are unknown can be defined as custom specifications directly from the event details view. The event attributes from the event will be pre-filled in the Add Event Specification modal.  Learn more about using Live Events. Tealium Events Extension For users of iQ Tag Management, use the Tealium Events extension to populate the tealium_event variable to match your event specifications. Getting Event Specification Code Creating event specifications is the first step in defining and standardizing your data layer. The second step is implementing the event tracking code on your platform of choice. While each platform has different code syntax, the event and attribute names implemented should be consistent across each of them. Event specifications combine the event definitions with each of your data sources to provide a full installation guide, complete with the base code and examples for each specification. The resulting installation guide can be downloaded as a PDF and shared with your development team. Use the following steps to get the code for your event specifications: In the sidebar, select EventStream > Event Specs. Click Get Code. From the drop-down menu, select a data source. The base code for the selected data source displays. Click Event Tracking Code to preview the sample code for each event specification. Click Download as PDF to generate a full installation guide for the selected data source. Click Close. ... View more

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

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 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 the Tealium 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. EnableApp + 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.allow_google_signals Boolean Allow advertising features. 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. Values accepted to activate: "true", "on") 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 checkout_step Number Checkout step. checkout_option Checkout Option. order_currency Currency Overrides _ccurrency . 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 Array 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_item_list_id Product Impression List ID 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 promo_location_id Array Promotion Location 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 IAB Transparency and Consent Framework v2 Variable Description gtag_enable_tcf_support Enable TCF Support Values are true or false. 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

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

Tealium is proud to introduce our newest product, Tealium Predict, a fully-managed product that simplifies machine learning. Predict is a built-in machine learning technology product used with Tealium AudienceStream CDP. With this release, Tealium takes the complicated discipline of machine learning and distills it down to specific functions. In just a few clicks, Predict can create a model with a new output attribute that is immediately made actionable in AudienceStream. How it Works Using Predict, you can create, optimize, and deploy data models that make meaningful predictions about your visitor behavior. Deployed models are managed by Tealium in real-time using a predictive attribute that is made available to you after your model is trained and deployed. Coupled with Tealium AudienceStream, Tealium Predict activates trustworthy machine learning insights across your entire implementation by helping you create more intelligent audiences Video Demo Enjoy the following video overview about how to create a model and interpret results using Tealium Predict. Get Started To learn more and get started, see the Tealium Predict User Guide. ... View more

The previously announced Load Order Manager experiment has several improvements planned in preparation for its general release.  You can be notified of the updates by following this post -- just click Follow at the top of the page.  The Load Order Manager has been released. In this article: Table of Contents Placeholder Overview Since the launch of the Load Order Manager experiment we have received feedback from many users and will be incorporating those suggestions into upcoming releases. The Load Order Manager is an essential part of tag management that will benefit all users so we encourage you to enable the experiment and try it out.  You will notice new features getting released over the coming weeks, so we’d love to hear your feedback or know of any issues you might come across. For detailed information about using Load Order Manager, see Load Order Manager (BETA). Planned Improvements The following updates are planned for the Load Order Manager: Display the Load Order Manager in a slide-out instead of a modal window to provide a larger workspace. Ability to collapse scope groups. Ability to hide inactive tags and extensions. Ability to sort tags or extensions on the list view. Ability filter tags or extensions on the list view. Ability to edit extension scope directly from the list view. Ability to add tags to tag-scoped extensions directly from the list view. Various bug fixes. Releases 2020-11-10 Moved out of experiments and into general availability. 2020-08-28 Ability to edit extension scope directly from the list view. 2020-07-23 Ability to hide inactive tags and extensions. 2020-07-02 Display the Load Order Manager in a slide-out instead of a modal window. ... View more