Tealium Learning Center

This article describes how to set up the Maxymiser (Async) tag in your Tealium iQ Tag Management account. Maxymiser empowers brands to transform every digital interaction into seamless, relevant and engaging customer experiences with its cloud-based testing, personalization and cross-channel optimization solutions. In this article: Tag Tips Contact Maxymiser before using this tag to confirm that your Maxymiser library is set up to be loaded asynchronously. If you need to load Maxymiser synchronously, paste the Maxymiser code into utag.sync.js or use the Maxymiser (Sync) tag instead of this one. For best performance: Advanced Settings: Set Tag Timing to Prioritized. Move this tag to the top of your list of tags (so that it loads first). Publish Settings: Enable Bundling Move utag.js to the top of the body Use mapping to: Disable the tag on a page-by-page basis. Pass additional data to Maxymiser (must be enabled on your Maxymiser account). Tag Configuration First, go to the tag marketplace and add the Maxymiser (Async) tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Library URL: The mmcore.js library URL provided by Maxymiser. Example:   //service.maxymiser.net/cdn/tealium/js/mmcore.js This should start with "//". Do not include "http:" or "https:". 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 Library URL (library_url) Disable Maxymiser (mm_disable) Load Test Content Asynchronously (mm_async) (Overrides default of "true") Custom (custom.myvar) ... View more

You can now select to use the decimal or integer type for number attributes. This feature applies to number attributes in Tealium EventStream and AudienceStream. There are no changes to preloaded attributes. About Number Attributes Previously, number attributes were stored as decimals, with no ability to change the type. This meant that connector actions would automatically receive a value with a decimal, even if the vendor expected an integer in their API. For example, a vendor that collects product purchase data might expect whole number values for product quantities, but if you mapped the product_quantity attribute with a value of [2, 1, 1] in a connector action, the value would be sent to the vendor's API as [2.00, 1.00, 1.00] . This could cause unexpected results. What's New Number attributes now have a type property: decimal (default) or integer. This setting determines how the value is stored and transmitted. All existing number attributes will have the default type of decimal. The number type option can be changed after the attribute is created, so you can adjust existing attributes as needed. To specify the number type, simply select an option from the Type drop-down list. The available options are: Decimal (default) Decimal values can have zero (0) or more decimal digits. This type is recommended for attributes that represent monetary values. Examples: 12, 12.0, 12.345  Integer Integer values are stored as whole numbers. This type is useful for attributes that represent quantities, counters, or scores. Examples: 12, -4, 3214 This feature is available for the following attributes: Number Array of Numbers Tally ... View more

This article describes how to use the data types array of strings, array of numbers, and array of booleans. In this article: 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 for browsing metrics such as visits, page views, and purchase events. Numeric values are stored as decimals or integers. Choose the type that matches your needs: Decimal (default) Decimal values can have zero (0) or more decimal digits. Example:   12,   12.0,   12.345 Recommended for attributes that represent monetary values. Integer Only whole number values are stored. Example:   12, -4,   3214 Useful for number attributes that represent quantities, counters, or scores. 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 purchase_total_history value array. Attribute Name: purchase_total_history 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 type can only be an array of numbers or iQ variable. For example, you may wish to add the array of purchased product prices to an array of all purchased product prices. Attribute Name:  purchased_products_history Starting Value [24.99, 12.95] Enriched With [5.99, 10.00] Resulting Value [24.99, 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:  purchase_total_history Starting Value [12.95, 5.99] 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: did_purchase_on_visit 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 type can only be an array of booleans or iQ variables. Attribute Name: my_booleans Starting Value [true] Enriched With [false, true] Resulting Value [true, false, true] Reset This enrichment removes all values from the boolean array. Attribute Name: did_purchase_on_visit Starting Value [true, false, true] Resulting Value [] ... View more

This article lists the conditional operators available for creating load rules and extension conditions. It also shows the JavaScript code that is generated when those configurations are built into utag.js. In this article: Overview The Tealium iQ Tag Management interface was designed for developers and marketers alike and therefore it does not require JavaScript knowledge to use. However, it is important to understand that your configuration is eventually transformed into JavaScript code that runs on your website. One example of this are the conditions used in load rules and extensions. Understanding the JavaScript code that is generated by these components can help prevent errors and improve your business logic. Order of Conditions The first thing to notice is that the order that conditions appear in the interface is the same order that they appear in the generated code. In this example, notice that the order of the conditions in the UI matches the order in the JavaScript code. Example of two extensions conditions in the interface:   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. For example, if the is defined  condition checks for event_name  after the condition for contains (ignore case) , the code would exit with an error and the condition would not evaluate as expected.  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 This table lists the generated JavaScript code for each condition. In these examples,  {{VALUE}}  represents the value from the text field in the extension or the load rule. The variable  dom.title is used for strings, cart_total_items  for numbers, and va.badges.42  for badges.  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 how to manage templates and how to update to the latest version of a template. In this article: Requirements To manage templates you need the Manage Tag Templates permission. How it Works A template contains the JavaScript code for the core logic of a vendor tag or a component of the consent manager. Each marketplace vendor tag has its own template that converts the tag configuration, data mappings, and extensions from the iQ Tag Management interface into the JavaScript code that runs on your site. And each component of the consent manager has a template that controls its behavior on your site. There are a number of scenarios where you might need to edit a template, including: Updating to the latest release of a vendor tag. Updating to the newest features of the consent manager. Changing the core logic of a tag. Customizing components of the consent manager. Fixing a bug in a tag. Some customizations and fixes can be achieved using an extension scoped to the tag rather than editing the template. This approach should be considered first because it is easier to maintain over time. Template Types Templates are used for vendor tags, Tealium tags, and the consent manager. When you view a list of templates, each type can be identified by the following names: Tealium Tags uTag Loader The template for utag.js. uTag Sync The template for utag.sync.js. uTag Footer (deprecated) The template for utag.footer.js Consent Manager Dom Ready (cmDomready) General (cmGeneral) Show Explicit (cmShowexplicit) Show Preferences (cmShowpreferences) Marketplace Tags All marketplace templates are identified by their vendor name (as it appears in the marketplace), tag name (as entered in the tag configuration), and the tag UID. For example: Twitter Conversions: Twitter Conversions (Retargeting): Tag UID: 2042 Workflow When you edit or update a template you must apply your changes and then save the profile. If a marketplace tag template is changed, the tag will be marked as Updated. If you change a template and don't save the profile, the changes are discarded. Accessing Templates The following methods are available for accessing templates: User Menu From the the user menu, click Manage Templates. This method allows you to browse all templates in the profile and quickly access them from a drop-down list. Tag Configuration From the tag configuration screen, expand the Advanced Settings area and click Edit Templates. This method takes you directly to the template for that tag. Template Status Checker From the user menu, click Template Status Checker then click a template in the report. This method displays a status report of your templates, including the consent manager templates and the Tealium uTag templates. Learn more about the template status checker. Updating a Template Updating a template replaces the current template with the latest system version. If a template has been customized, this action will overwrite those changes. To update a template: Use a method to access the template. Click Update. A confirmation dialog appears. Click Update to confirm and replace the template with the latest system version of the template. Click Apply. You must save the profile to preserve the changes to the template.  Reverting a Template Reverting a template discards any changes that have been made since the last time the profile was saved. If a template has been updated or edited, this action will undo those changes. To revert a template: Use a method to access the template. Click Revert. A confirmation dialog appears. Click Revert to confirm and revert to the last saved version of the template. Click Apply. ... View more

An improved workflow is now available for managing templates. About Templates A template is the underlying JavaScript code that runs various parts of your iQ Tag Management configuration. Templates are used for marketplace tags, Tealium tags, and the consent manager. Previously, templates were edited, updated, and saved separately from the account publish workflow, which often led to confusion about which template was active.  This goal of this release is to address the following shortcomings of the previous way that templates were managed: Eliminate the confusing options of "Save Profile Template" and "Save Version Template". Provide intuitive steps for updating a template to the latest system version. Include templates in the version history notes. What's New This release brings the following improvements to managing templates: Standard Publish Workflow Previously, to edit or update a template, you would save the changes immediately without needing to save the profile. In this release, after you edit a template and apply your changes, you must save your profile to preserve those changes to the profile. Version History Previously, after editing and saving a template, the change would not be displayed in the version history. Now, since you must save your profile to preserve changes to a template, the version history displays a note whenever a template is edited. You may notice this message for templates edited prior to this release, it is recommended that you validate these before publishing to production. Update and Revert Options Previously, to update to the latest system version of a template you would click the trash icon. Now, when you view a template there are two clear options: Update Click this button to replace the current template with the latest system version of the template. Revert Click this button to revert the template back to the most recently saved version in the profile. This action discards any unsaved changes to the current template.   Learn more Managing Templates Template Status Checker ... View more

Overview When implementing the Firebase Tag in Tealium IQ, there are three components to be implemented that will require both edits in the native code and within Tealium. First, the Firebase SDK needs to be included in the app. Second, there are remote commands that need to be added to your native code through the Tealium SDK. Lastly, the Firebase Tag will be added to Tealium IQ. All three parts need to be implemented or Firebase will not receive data. Native Code Configuration Step 1 – Add the Firebase SDK to the Native App Step 2 – Add the Tealium SDK to the Native App Step 3 – Include the Remote Command Classes in the Native App For all libraries, you will need to register the Firebase Analytics Remote Command before it can be used. This should be done when you initialize the library. Follow the guide to implement the remote command based on the mobile platform being used. Tealium IQ Configuration Step 1 – Add the Firebase Tag The Firebase Tag is a special tag that contains an implementation of the API required to trigger custom native code blocks you have registered with the Tealium mobile libraries. This tag is available in the tag marketplace and communicates with “Step 3” of the native app configuration. How It Works The Tealium event (view or event) is triggered by the native code, which is then ingested by utag.js in the webview. The Firebase tag and associated extensions review the event and send a Firebase event to the remote command that was added to the native code. The remote command takes the request from the tag and formats and sends the event so that it can be collected by the Firebase. Step 2 – Set the Tag Configuration The only option for configuration is whether to enabled debug mode. This is up to your developers whether they need this option enabled. The default setting is "False". Step 3 – Add Mappings Set-Up Certain mappings need to be present for the tag to work. These are the general settings that need to be applied. Session Timeout (seconds) Session Minimum (seconds) Firebase Log Level Screen Name Command Name Firebase Event These can be set as static values or can be set dynamically using extensions. Variable Description firebase_session_timeout_seconds Integer as String firebase_session_minimum_seconds Integer as String firebase_analytics_enabled Boolean as String firebase_log_level String td> firebase_event_name String firebase_event_params JSON firebase_screen_name String firebase_screen_class String firebase_property_name String firebase_property_value String firebase_user_id String command_name String Automatic Events Some of the events that will be used are automatically collected by the Firebase SDK and do not need to be set up using the Tealium Firebase Tag. For a list of these events, click here. Standard Events The event name is the event occurring in the app that needs to be captured (cart events, search events, payment events, etc.) Below is a list of standard events available through the Firebase SDK. If your event is not available in the list, it can be sent using a logEvent custom event. Variables   config event_level_end setScreenName event_login setUserProperty event_post_score setUserId event_present_offer logEvent event_purchase_refund resetData event_remove_cart event_add_payment_info event_search event_add_to_cart event_select_content event_add_to_wishlist event_set_checkout_option event_app_open event_share event_begin_checkout event_signup event_campaign_details event_spend_virtual_currency event_checkout_progress event_tutorial_begin event_earn_virtual_currency event_tutorial_complete event_ecommerce_purchase event_unlock_achievement event_generate_lead event_view_item event_join_group event_view_item_list event_level_up event_view_search_results event_level_start Firebase events are mapped as they would be in any other tag. Values can come in either from the data layer or set through an extension and then mapped to the tag in the following manner: Custom Events If the event you want to send is not included in the list of default events, you’ll need to send a logEvent event with a custom value attached for the event name. Map your variable value to the logEvent event. Add a parameter to send the event name with your logEvent event. Standard Parameters Event parameters are sent along with the event and can be mapped to the parameters in the list below. Params can be mapped in two ways: As a standard param sent with any event As an event param sent only with specified events Variable Description param_achievement_id String param_ad_network_click_id String param_affiliation String param_cp1 String param_campaign String param_character String param_checkout_option String param_checkout_step Integer param_content String param_content_type String param_coupon String param_creative_name String param_creative_slot String param_currency String param_destination String param_end_date String param_flight_number String param_group_id String param_index String param_item_brand String param_item_category String param_item_id String param_item_list String param_item_location_id String param_item_name String param_item_variant String param_level Integer param_location Integer param_medium String param_number_nights Integer param_number_pax Integer param_number_rooms Integer param_origin String param_price Double param_quantity Integer param_score Integer param_search_term String param_shipping Double param_method String param_source String param_travel_class String param_virtual_currency_name String param_start_date String param_term String param_tax Double param_transaction_id String param_value Integer or Double param_level_name String param_success String E-Commerce order_id String Overrides _corder order_total Integer or Double Overrides _ctotal order_shipping Double Overrides _cship order_tax Double Overrides _ctax order_currency String Overrides _ccurrency order_coupon_code String Overrides _cpromo product_id Array Overrides _cprod product_name Array Overrides _cprodname product_brand Array Overrides _cbrand product_category Array Overrides _ccat product_quantity Array Overrides _cquan product_unit_price Array Overrides _cprice param_item_list Array param_item_variant Array param_index Array Custom Parameters If your param is not available in the list above, a custom param will need to be sent with the event. When adding custom parameters to any event, note that they are sent along with the event (either standard or custom) and must be in a JSON format. The value of the mapped variable must be set up in a JavaScript code extension. Multiple events can be formatted as shown. The mapping to send custom params would be configured as shown. Tips Below are some items to keep in mind when setting up the Firebase Remote Command Tag. The config command is automatically sent on the first load if it is not found in the event list. If the appropriate data is provided (variable mapped to user ID), the event_login and event_signup events will automatically send setUserId and setUserProperty events. If the appropriate data is provided (variable mapped to screen name), the event_view_item_list , event_view_item , event_ecommerce_purchase , and event_begin_checkout can automatically send a setScreenName event. Use only the singular parameters or the e-commerce arrays, not both. Notes About Firebase Firebase is not the same as Google Analytics and has different terminology and a completely different setup. The variables/mappings do not translate one for one, therefore, custom dimensions are not included in Firebase. Params take the place of custom dimensions and should be used accordingly. If you need a custom param, they can be configured within Firebase. A/B testing parameters are stored in Firebase and are not accessible to Tealium. If the A/B testing data needs to be used within Tealium, the data can be exported from Firebase for FREE using BigQuery. The data can then be imported into Tealium server-side products for use in connectors/audiences. Resources Tealium Firebase Remote Command Integration Firebase Remote Command Example – iOS (Github) Firebase Remote Command Example – Android (Github) Google Firebase Guide Automatically Collected Events – Firebase ... View more

This article describes the Environment Switcher, which is available as a Tealium Tools browser extension. In this article: How it Works The Environment Switcher is a powerful testing tool used 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. Use the Environment Switcher in Google Chrome or Mozilla Firefox by adding the Tealium Tools extension. Learn more about the Tealium Tools Browser Extension. Using the Environment Switcher 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. Basic Configuration The options on the Basic tab allows you to load utag.js and utag.sync.js from different environments. 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 refreshes the current page. Advanced Configuration The options on the Advanced tab provide the following features Advanced redirects to load the Tealium files from a different account, profile, and environment. This is helpful if you use profile libraries or custom publish environments. URL redirects to load the Tealium files from a custom URL location. Separate settings for each Tealium file and your browsing session.. Advanced Redirects 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. URL Redirects To redirect to a custom URL, click URL Redirect to expand. Type the source URL in the Source column and the destination URL in the Destination column. Advanced Options 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 - only apply the redirects to the current domain. If you navigate to a different subdomain, the redirects are not applied. Current Tab Only - only apply the redirects to the current browser tab. Other browser tabs, even if viewing the same page, will not be affected. Apply to utag.js - apply the redirect to utag.js. Apply to utag.sync.js - apply the redirect to utag.sync.js. Set utag_cfg_ovrd.path - set a custom cookie 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

This article describes the Tealium Predict ML product and how it is used to create, train, and deploy machine learning models to make predictions about visitor behavior. In this article: Table of Contents Placeholder How it Works Tealium Predict is a built-in machine learning technology product used with the Tealium AudienceStream CDP product that takes a complicated discipline (machine learning) and distills it down to a fully-managed feature. Coupled with AudienceStream, the product allows you to build and create more intelligent audiences and activate trustworthy machine learning insights across your entire tech stack. Using Tealium 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 output attribute that is made available to you after your model is trained and deployed. In just a few clicks, you can then create a model using the new output attribute, which is immediately available and actionable in AudienceStream. Key Benefits Key benefits of Tealium Predict include the following: Leverage Machine Learning Intelligence Across your Entire Implementation You can automatically activate predictive insights in any of Tealium's over 1,200 integrations. Simplification Tealium Predict simplifies the implementation of machine learning for you without the need for a Data Scientist or dedicated team. You can create a model, deploy it, and immediately activate the value in AudienceStream without writing a single line of code. Predict Customer Actions Automatically draw conclusions about what actions customers are likely to take in the future and design tailored programs that directly address their needs. Personalization The Tealium Customer Data Hub allows you to pinpoint meaningful visitor personalization data. Reduce Time Spent on Machine Learning Projects that Involve User Data Data collection and data activation are natively integrated with machine learning intelligence, which greatly reduces time spent for data preparation and activation. Score Customers with Predictive Potential Technology built into the model produces a score for visitors with the likelihood to return or complete a specific behavior. You can then leverage the scores to generate audiences for further proactive action, such as re-engagement campaigns. Choosing What to Predict A target attribute is a AudienceStream attribute that defines or signals the visitor behavior that you seek to predict with any Tealium Predict model. The target attribute must be either a Boolean/Flag or a Badge type attribute and be Visit or Visitor-scoped. Selecting a Target Attribute When you create a model using Tealium Predict, potential target attributes from your AudienceStream dataset display. To the right of each attribute, a rating of Ready or Not Ready displays to signify whether or not the attribute selected is ready for training. This rating simplifies model creation by clarifying which of your flags and badges are ready to be used to create models. A rating of Not Ready does not mean that the attribute is problematic in other contexts. It simply means that this attribute is currently deemed insufficient for successful training of a Tealium Predict model. Machine learning technology in general requires a relatively high volume of data to succeed and machine learning models provide better results when trained on a large amount of data. The following two factors to define target attributes that are Ready or Not Ready: The volume of data for the attribute The distribution of that volume between true and false values. Both the true and false groups must be above a minimum threshold. For example, for the dates that span the Training Date Range, the median daily counts of True and False visitors must be greater than or equal to 200. This threshold is intentionally set as low as possible to provide the most options possible for target attributes. A model that uses a target attribute that is labeled Not Ready typically fails during the training process due to insufficient data for the model to learn on. If the target attribute you want to use is labeled as Not Ready, try one of the following common solutions: Wait for more data to accumulate. The problem often solves itself over a longer time period. Identify ways to drive additional traffic to the AudienceStream data source. Add additional data sources to your AudienceStream profile so that the volume of daily data increases for this target. Learn More About the Technology To learn more about machine learning technology, see Machine Learning Concepts and Technology. ... 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 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, s elect 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

The following diagram lists the visit and visitor attributes types, available enrichments, and inter-dependencies between them. Related articles: EventStream Event Attributes Diagram ... View more

The following diagram lists the event attributes types, available enrichments, and inter-dependencies between them. Related articles: AudienceStream Visit and Visitor Attributes Diagram   ... 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 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