Tealium Learning Center

This article describes how to set up the Teads tag in your Tealium iQ Tag Management account. In this article: Table of Contents Placeholder Tag Tips Use mapping to override standard configuration values and set additional options. Tag Configuration First, go to Tealium's tag marketplace and add the Teads tag (Learn more about how to add a tag). After adding the tag, configure the following settings: pid Your Teads-supplied PID lang Language. Default value is English ( en ). Slot The selector for placing the Ad. Example: .article .article_body > p Format minSlot Mobile css 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 Pid   Lang   Slot   Format   minSlot   mobile Boolean Skip delay   Mute delay   CSS   BTF Boolean Mutable Boolean AdBreaks   avoidSlot   ... View more

This article describes how to set up the Teads Advertiser Tag tag in your Tealium iQ Tag Management account.New  In this article: Table of Contents Placeholder Tag Tips Use mappings to override or dynamically set the tag configurations. Tag Configuration First, go to Tealium's tag marketplace and add the Teads Advertiser Tag tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Advertiser ID Your Teads-supplied Advertiser ID. Example: 123456 Conversion Type The name or type of conversion. 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 advertiserId Advertiser ID conversionType Conversion Type   ... View more

This article describes how to set up the Eloqua tag in your iQ Tag Management (TiQ) account. In this article: Table of Contents Placeholder Tag Tips Keep the default setting of Wait = Yes so that the Eloqua JavaScript file will run on DOM Ready. For form tracking, use mapping to set values for the following parameters: form_tracking (on) elqFormName elqFormGUIDElement Tag Configuration First, go to Tealium's tag marketplace and add the Eloqua tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Site ID Site ID is typically a series of numbers. First-Party Cookie Domain Name The domain name for your first-party cookie 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 form_tracking Form tracking. Values are on or off. elqFormName Form name. elqFormGUIDElement Form element. base_url JavaScript file URL. elqDomainName First-Party Cookie Domain Name ... View more

This article describes how to set up the Quora tag in your iQ Tag Management (TiQ) account. In this article: Table of Contents Placeholder Tag Tips Use mappings to: Override standard configuration values Set up event triggers Tag Configuration First, go to Tealium's tag marketplace and add the Quora tag (Learn more about how to add a tag). After adding the tag, configure the following settings: pixel_id A Quora-provided alphanumeric string uniquely identifying the pixel 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 pixel_id Quora Pixel ID Events Variable Description ViewContent Page View View content Generic Generic Purchase Purchase GenerateLead Generate lead CompleteRegistration Complete registration AddPaymentInfo Add payment Information AddToCart Add to cart AddToWishlist Add to wish list InitiateCheckout Initiate checkout Search Search Custom Custom ... View more

View the Release Notes summary to learn about updated product features, enhancements, and fixes. To view details about how to use a new feature, click the Learn More link next to the description. Tags New/Cool Stuff New marketplace tag: ObservePoint Data Layer Validator (Learn more) Updated Google Analytics (gtag.js) tag to add product-scoped dimensions and metrics for product impression support. Updated the Adobe Analytics (SiteCatalyst) tag to clarify that it is the legacy version of Adobe Analytics AppMeasurement for JavaScript. (Learn more) Updated the Adobe AppMeasurement for JavaScript tag to Version 2.17 and added wrapping debug option parameter. (Learn more) Updated the Adobe Experience Cloud ID service tag to Version 4.4 and added a new drop-down list for version selection. (Learn more) Updated the Google Analytics (gtag.js) tag to support "G-" tracking IDs. Updated the Invoca tag template to use Version 4.0 and added additional data mappings. Updated Webtrends templates to support the disablecookie  setting. Fixes Corrected issue with the Tealium Collect tag visitor service override URL when using a custom endpoint. Corrected various issues with the Awin marketplace tag. (Learn more) Updated the Adobe Targeting tag description in the interface to remind TiQ users to scope the extension to the Adobe Target tag. (Learn more) Connectors New/Cool Stuff New marketplace connector: AppsFlyer Enterprise, SDKless (BETA Experiment) (Learn more) New marketplace connector: Everflow (Learn more) New marketplace connector: Salesforce Journey Builder with OAuth 2.0 to enforce new Salesforce authentication, the legacy Salesforce Journey Builder is now deprecated. (Learn more) Updated the APSIS connector to remove the optional password field from all available actions and limit the ISO country code prefix and phone number parameters to stings and numbers. (Learn more) Updated the Facebook Ads connector to Version 3.3. (Learn more) Updated the Facebook Server-Side Events connector to display custom data values up to 2 decimal points in precision. Updated the Google DCM Floodlight connector to Version 3.3. (Learn more) Updated the Salesforce Email DataExt Batch connector to handle error messages in the same manner as the Salesforce Email Studio connector. Fixes Corrected issue causing NumberFormatExceptions for large Webhook number (integer) attributes. Corrected issue with the Optimizely Events connector to send the integer number type as an integer value instead of a string. (Learn more) Corrected various issues with the LeanPlum marketplace connector. (Learn more) iQ Tag Management New/Cool Stuff General performance updates to improve profile loading speed. Added conditions and load rule support to enable conditional execution of the Lookup Table extension. Updated the tag UID link to utag.x.js to indicate when a tag is not published. Upon duplicating an extension, the word "Copy" is now added to the title of the new extension. In Code Center, updated the path to  utag.js   to use a hard-coded "https://" protocol. (Learn more) Fixes Corrected issue causing data source names to not fully display in the "Set" drop-down list when a variable is added with a period ( . ) character in the jQuery extension name. Corrected issue causing interface to redirect to the dashboard page when the Concurrent Users notification displays. Corrected issue causing slow rendering for the display of tags in the tag marketplace. Corrected issue with the Bulk Import from CSV option when adding variables so that changes are correctly flagged as "Not Saved". Corrected the link to the utag.js Release Notes on the "uTag Loader (Profile) UID:loader" confirmation page that displays when updating your utag.js template file. Corrected the Data Layer Enrichment (DLE) profile drop-down list to show "None" as a selection. Corrected title in client-side browser tab to match the title in the server-side tab. Corrected user interface issue causing the "Not Saved" warning to display when no changes were made. Updated custom extension functionality to correctly serialize saved data containing double or single quotes in the custom CSS and HTML code blocks used for configuring a custom extension. Updated the drop-down language selector in the Consent Prompt Manager window to correct the ability to scroll up or down to view all available languages. Updated the JavaScript Code Draft extension to support custom environment names. Universal Data Hub Fixes Added validation to event specifications to prevent duplicate attributes. Updated Omnichannel attribute rules to differentiate which file configuration the rule came from when multiple attributes have the same name. ... View more

This article describes how to set up the Everflow Conversion Tracking connector in your Universal Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send Advertiser Conversion ✓ ✓ Send Advertiser Post-Conversion Event ✓ ✓ 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: Everflow Network ID: Enter your network ID which will be the subdomain for your conversion tracking endpoint. For example, https://MY_NETWORK_ID.servecvr.com. 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 - Send Advertiser Conversion Parameters Parameter Description Transaction ID Pass the unique click ID tracked by Everflow captured from the landing page. For more information, see Everflow support. Action - Send Advertiser Post-Conversion Event Parameters Parameter Description Transaction ID Pass the unique click ID tracked by Everflow captured from the landing page. For more information, see the Everflow Helpdesk. Event Data Add event data to track your post conversion events, including the event_id which is available in the offer view. ... View more

This article describes how to set up the AppNexus Cookie Matching Service tag in your Tealium iQ Tag Management account. AppNexus Cookie Matching Service enables a buyer to associate the cookie that identifies a Tealium visitor and the cookie that identifies the user for AppNexus. In this article: Table of Contents Placeholder Tag Tips This tag will only fire once per Tealium Visit Session. If left blank, Tealium Account and Tealium Profile is automatically populated. Tag Configuration First, go to the Tealium tag marketplace and add the AppNexus Cookie Matching Service tag. (Learn more) After adding the tag, configure the following settings: Tealium Account Tealium Profile 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 tealium_account Tealium Account tealium_profile Tealium Profile ... View more

This article describes how to set up the ObservePoint Data Layer Validator tag in your iQ Tag Management account. In this article: Table of Contents Placeholder How it Works Use the ObservePoint Mobile Data Layer to validate your data layer within ObservePoint. This enhances the ObservePoint mobile app testing to match the capabilities of the web testing in reviewing the data layer. Tag Tips This tag should not be run in a production environment The ObservePoint object name defaults to the value utagdata . The Data Layer object defaults to the value b . Tag Configuration First, go to Tealium's tag marketplace and add the ObservePoint Data Layer Validator tag (Learn more about how to add a tag). After adding the tag, configure the following settings: ObservePoint Object Name This is the name that displays in the ObservePoint user interface. 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 op_object_name ObservePoint Object Name op_object Data Layer Object ... View more

This article describes how to set up the Salesforce Journey Builder connector in your Universal Data Hub account. This connector replaces (Deprecated) Salesforce Journey Builder Connector. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send Event to Initiate Journey ✓ ✗ 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: Client ID Required. Provide your app client ID. See: Get OAuth Client Credentials Client Secret Required. Provide your app client secret. Account ID Required. Provide account identifier (MID) of the target business unit. Tenant-specific subdomain Required. Provide tenant-specific subdomain for your application. 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 - Send Event to Initiate Journey Parameters Parameter Description Event Entry Definition Required. Select event entry definition. See: Admit Contacts via API Contact Key Required. Provide contact key. Event Data Required if defined in a custom event or by the event. Map values to contact event attributes. See the Salesforce Fire the Event documentation. Vendor Documentation Get OAuth Client Credentials Admit Contacts via API Entry Events and Data Definitions ... View more

This article describes how to set up the Beamer tag in your Tealium iQ Tag Management account. In this article: Table of Contents Placeholder How it Works Beamer is a notification center and changelog plugin that lets you send announcements to users and site visitors for important news, latest products, special offers, and more. Tag Tips Widget configurations are set via mappings. If you do not add an Element ID by default, Beamer will display a notification icon in the bottom-right corner of your page. You can provide the callback, onclick, onopen, and onclose functions by providing via mappings either the name of the functions (as a string) or a reference to the functions. If providing the name of the function, it is assumed that the function is defined at the window level. Tag Configuration First, go to Tealium's tag marketplace and add the Beamer tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Product ID The Product ID is the unique identification code that appears in the top bar of your Beamer dashboard. Selector HTML identifier for the DOM element to be used as a trigger to show the panel. 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 Beamer Customer ID (product_id) Widget Configurations Variable Description Selector ID (selector) Display Mode (display) Display Position (display_position) Top Offset (top) Right Offset (right) Bottom Offset (bottom) Left Offset (left) Embed Toggle ["true"/"false"] (embed) Button Toggle ["true"/"false"] (button) Button Position (button_position) Icon (icon) Bounce Toggle ["true"/"false"] (bounce) Notification Prompt (notification_prompt) Notification Prompt Delay (notification_prompt_delay) Language (language) Filter (filter) Filter By URL Toggle ["true"/"false"] (filter_by_url) Mobile Toggle ["true"/"false"] (mobile) Lazy Toggle ["true"/"false"] (lazy) Alert Toggle ["true"/"false"] (alert) Delay (delay) Callback Function (callback) Onclick Function (onclick) Onopen Function (onopen) Onclose Function (onclose) User Data Variable Description User First Name (user_firstname) User Last Name (user_lastname) User Email   User ID (user_id) Button Position Variable Description Bottom Left (bottom-left) bottom-left Bottom Right (bottom-right) bottom-right Top Left (top-left) top-left Top Right (top-right) top-right Display Variable Description Left (left) left Right (right) right In-app (in-app) in-app Popup (popup) popup Display Position Variable Description Bottom (bottom) bottom Bottom Left (bottom-left) bottom-left Bottom Right (bottom-right) bottom-right Left (left) left Left Bottom (left-bottom) left-bottom Left Top (left-top) left-top Right (right) right Right Bottom (right-bottom) right-bottom Right Top (right-top) right-top Top (top) top Top Left (top-left) top-left Top Right (top-right) top-right Icon Variable Description Bell Full (bell_full) bell_full Bell Lines (bell_lines) bell_lines Flame (flame) flame Flame Alt (flame_alt) flame_alt Alert Bubble (alert_bubble) alert_bubble Alert Circle (alert_circle) alert_circle Bullhorn (bullhorn) bullhorn Thumbtack (thumbtack) thumbtack Notification Prompt Variable Description Popup (popup) popup Sidebar (sidebar) sidebar ... View more

View the Release Notes summary to learn about updated product features, enhancements, and fixes. To view details about how to use a new feature, click the Learn More link next to the description. Tags New/Cool Stuff New marketplace tag: Beamer (Learn more) New marketplace tag: Braze Remote Command (Learn more)  New marketplace tag: Flashtalking Cookie Matching Service New marketplace tag: Flashtalking OneTag New marketplace tag: SmarterHQ Updated mapping toolbox for the Clicktale Carmel tag to add send_udh_data  destination. Updated the Adobe AppMeasurement tag library to support Version 2.15. (Learn more) Updated the Adobe Target tag to support Versions 1.7.1 and 2.1.1 and added new mapping destinations. (Learn more) Updated the Conversant Media - Direct to Brands tag to add support for additional parameters in Conversant Media. Updated the Taboola Pixel tag to add the  item-url  parameter and automatically populate it with document.location.href . Updated the Tealium Collect tag to allow users to override the normal Visitor Service endpoint with a CNAME. (Learn more) Updated Tealium Tools to Version 1.14.1 on Google Chrome and Mozilla Firefox. (Learn more) Fixes Corrected issue with Google Analytics (analytics.js) tag to prevent empty dimension/metrics values in the tracking call. (Learn more) The Acxiom AbiliTag is no longer available in the tag marketplace. Custom implementations may continue to use the tag as-is. Updated unique IDs for script elements in the Tealium Collect tag for WCAG 2.0 compliance. Connectors New/Cool Stuff Applied enhancement to batch connectors when Trace is enabled to trigger off of the API call and display feedback in Trace. Fixes Corrected OAUTH2 issue with the Google AdWords Customer Match connector. iQ Tag Management New/Cool Stuff Added the Environment Switcher to the official Tealium Tools plug-in, available in both Chrome and Firefox. (Learn more) Introduced the new View-Through Tracking extension for the US and EMEA regions. (Learn more) Fixes Corrected issue with the Tealium Web Companion causing the Save Queue not to save to the profile when adding variables using Web Companion interface. (Learn more) Universal Data Hub New/Cool Stuff Applied usability enhancements to the File Import Data Source (Omnichannel) feature. (Learn more) Updated the Event Feeds chart to display "prettified" numbers. Fixes Corrected an issue with event feeds containing a condition that uses the tealium_datasource attribute. Corrected issue with the Event Spec attribute causing values automatically populated to be flagged as "no value provided" when the correct value is listed under the section titled "These values were provided by your Tealium data source". Updated the Android data source code snippet. Installations New/Cool Stuff Added the Tealium Flutter plugin to allow users to use the Tealium native mobile libraries (Android/iOS) within Flutter applications. (Learn more) ... View more

This article describes how to set up the AppNexus Instant Audience service. In this article: Table of Contents Placeholder How it Works The Instant Audience Service is a server-side method that uses streaming architecture to add individual or small groups of users to segments using the AppNexus API. Rather than aggregating and periodically sending large batches of data using the Batch Segment Service, the Instant Audience Service associates users to segments in near real-time. Integration Type Tealium Product(s) Release Date S2S Connector EventStream, AudienceStream 01 Sep 2019 Prerequisites AppNexus Member ID shared with Tealium's AppNexus member Must contact your Tealium account manager for access This integration is currently available by request only. The underlying integration uses features or functionality currently in either Alpha or Beta phase and is therefore subject to change. To request access, contact your Tealium account manager. Getting Started Obtain Authorization To enable this integration, the Tealium AppNexus member needs to share segments with the advertiser AppNexus member. You need your AppNexus member ID in order to submit your request. Use the following steps to access the AppNexus Console and retrieve your Member ID: Log into AppNexus console. Navigate to the Advertisers page. Scroll to the bottom of the page and locate the Member ID. Copy the Member ID. This is a 4-6 digit number. Use the following steps to access the new Xander Invest DSP: Log into the Xandr Invest DSP. Find the Member Name shown in the top right corner. This is the AppNexus Services Network in the example. Hover over the Member Name to view the Member ID Copy the Member ID. This is a 4-6 digit number. The example uses 958. Submit a Product Support Request Next, submit a Product Support request to https://help.appnexus.com/, and copy Tealium partnertech@tealium.com using the following email template: Dear Support team, Please allow Tealium (member ID 9537) access to share segments into my seat ID: <YOUR ID HERE>. Sincerely, <YOUR NAME, POSITION, AND EMAIL ADDRESS) Once this request is received, AppNexus typically responds in 1-3 business days. Request New Segments from Tealium After your AppNexus seat has been shared with Tealium, submit a request to the Tealium Support Desk detailing the new segments to be created and shared with your AppNexus seat. Note: existing segments cannot be used with this integration. In your email, provide the following information: Segment Names Segment Descriptions Segment Expiration, in days. Member ID Segments with no expiration time expire from the AppNexus server-side data store within 90 days. Changing this value does not retroactively affect users already in the segment. If a user is re-added, the expiration window resets. The maximum expiration is 180 days . Tealium responds to requests within 2-3 business days with the requested segment IDs and Segment codes for configuration in connector actions. Once the segments have been created and shared with your member, you can see them in the AppNexus console under Network > Segments > Segment Manager. In addition to configuring the connector, we recommend pairing with the AppNexus Cookie Match Tag. This tag performs a cookie sync to exchange device IDs, which facilitates the server-to-server actions described below. Connector Actions Actions Currently Supported Add User to Segment – Adds a Tealium visitor to an AppNexus segment Remove User from Segment – Removes a Tealium visitor from an AppNexus segment Looking for a different action? We are constantly updating and enhancing our integrations. If there is an action would like to see supported, let us know! Action Endpoint https://streaming-data.appnexus.com/rt-segment User ID Field Field Name Description AAID Android Advertising Identifier. The mobile device ID for Android devices. Example: AEBE52E7-03EE-455A-B3C4-E57283966239 AppNexus User ID The AppNexus User ID returned by the cookie match endpoint. Example: 12345678900987654321 IDFA Identifier for Advertisers. The mobile device ID for iOS devices. Example: 6D92078A-8246-4BA4-AE5B-76104861E7DC MD5 UDID The MD5 hashed value of the AppNexus User ID. Example: 4a8a2b374f463b7aedbb44a066363b81 Open UDID Deprecated, do not use. SH1 UDID The SHA1 hashed value of the AppNexus User ID. Example: F12877BFFD9C07E7224C9A6EFB7A709F4E29FDEA Tealium Visitor ID Deprecated, do not use. SH1MAC UDID Deprecated, do not use. Segment Information Fields Field Name Description Example Value Expiration The lifetime of the user-segment association in minutes, starting from when we read it. A value of zero (0) means that the segment never expires. A value of negative one (-1) means that the user is to be removed from this segment. 1440 Member ID The ID of the member that owns this segment or has been shared the segment by data provider Tealium. 9537 Segment Code A user-defined name for the segment. mysegment-003 Segment ID The AppNexus segment ID. 12693755 Value A numeric value that you assign to a segment. 0 Testing and Validation After segments have been shared with your AppNexus member, you can see the segments listed in your segment manager. Once actions begin firing correctly in Tealium, you will see the size of the segments begin to grow. If you do not see Loads in Segment Manager after a few hours of triggering the connector successfully, raise a support request to Xandr and provide the segment ID(s) and your member ID. Batching and Rate Limits This connector leverages batch actions so that Tealium can manage high-volume data transfers to the vendor. Data queues in batched actions to be sent when the first one of the following three (3) thresholds is met: 500 records 10 minutes Greater than (>) 1MB The batching behavior described in the previous section is defined at the Action Level. This means that for a given account and profile, each individual action is batched. If a profile contains multiple actions, Tealium individually batches each unique action when evaluating batch behavior. Frequently Asked Questions What are some example use cases that this integration supports? Search or time-sensitive retargeting in RTB As a buyer or DMP, this service is useful if you would like to mimic search retargeting capabilities. As a user enters search keywords, you receive a server-side signal that triggers a server-side association to the segments. The user can then see ads that are relevant to their search, which enables you to capitalize on the immediate relevancy of the content for the user. Page performance sensitive targeting Use this service if you want to avoid any page load strain, but still be able to conduct retargeting without increasing the pixels present on the page. Alternative real-time audience targeting The Instant Audience Service can also be used for transactional retargeting, in which user scores are computed based on offline data or modeling. This only requires an additional trigger to have the user added to a segment that you wish to buy against in real time. A concrete example is, based on Clickstream data, a buyer computes a score for a user that has browsed three (3) products in the kitchen category of its site and pushes a segment value to AppNexus based on this user score to immediately show them an ad for additional kitchen items. De-targeting users who have converted To use your budget as efficiently as possible, this enables you to quickly de-target users who have already converted. How often do AppNexus User IDs expire? AppNexus expires UIDs on a rolling basis such that the user IDs who have not been seen for the longest period of time are removed from our database to make room for new user IDs. If you upload UIDs that are very old, you may have a high percentage of invalid user IDs in your status report. Tealium keeps your cookie mapping fresh by requesting new UIDs at the start of each session. How quickly are updates to segments activated by AppNexus? AppNexus sets their target Service Level Agreement (SLA) for adding users to segments with the Instant Audience Service to two (2) minutes. In order to adhere to a maximum of two (2) minutes activation time, the Instant Audience Service currently has some limits, which Tealium has incorporated into the batching functionality. For additonal details, see the batching section. Additional Resources AppNexus Streaming Server-Side Segmentation ... View more

Companies today are looking for ways to better measure how display influences the customer journey. Using the new View-Through Tracking extension, you can measure the impact of display ads on your customers' behavior by tracking which ads are seen by your visitors on other websites within a certain time frame, regardless of whether or not an ad click was generated. This requires information to be captured when the ad is displayed and for that information to be available when they come to your site. Read on for more information or read the following user guide: View-Through Extension Guide Use Case A user is reading an article on a news site. An ad displays for a wristwatch but the user does not click on the ad as they are busy reading an article. Later in the day, or the following day, the user looks up the wristwatch from the display ad to find out more. The user is then converted. By the end of the customer's session, more is known about the customer and what they are looking for, such as watch type or feature preferences, potential price range, and whether or not the customer visited blogs or knowledge bases to learn more about a specific model. Webinar Video Click the following video for an in-depth look at the View-Through extension: How It Works View-through tracking measures the impact of display ads on your customers' behavior by tracking which ads are seen by your visitors on other websites. This requires information to be captured when the ad is displayed and for that information to be available when they come to your site. Only one View-Through Tracking extension can be added per profile. The View-Through Tracking extension uses two simple components to allow the sharing of data between your display ads and your iQ Tag Management account. Display Ad Image Pixel Used to send the relevant data to the Tealium View-Through tracking service. This is a standard URL containing query string parameters for the ad data to collect. Custom JavaScript Code Extension An extension is created in your TiQ account to extract the view-through data collected during the visitor's journey to your site. For detailed information about how to use this feature, view usage reports, and view answers to Frequently-Asked Questions (FAQ), see the View-Through Tracking Extension user guide. ... View more

The following topics describe Tealium Consent Management tools designed to simplify GDPR compliance. Consent Management - Global Consent Parameters Learn how to use consent parameter variables to generate the consent prompt and preferences pop-ups.  Explicit Consent Prompt Manager Learn how to deploy a prompt to your website that allows users to opt-in or opt-out of tracking. This tool offers full access to customize the code behind the scenes and options for translated content.  Consent Preferences Manager Learn how to deploy a tracking preferences option to your website that will allow customers to specify which categories of tags they allow. This tools offers full access to customize the code that generates the preferences pop-up and the ability to translate content for your global customers. ... View more

Anura is an ad fraud detection solution that analyzes your traffic to identify real users versus bots, malware, and fraudulent human users. This article describes how to configure the Anura marketplace tag for Tealium iQ Tag Management (TiQ). In this article: Table of Contents Placeholder How it Works The Anura tag places your basic Anura response, such as "good", "suspect", etc. Response Variable Name in your requested Response Location. If you are using Script Response the Response Object Variable Name will be available in the default Anura window object. Tag Configuration First, go to Tealium's tag marketplace and add the Anura tag to your profile (Learn more about how to add a tag). After adding the tag, configure the following settings: Title The default is Anura. You may replace it with a custom name of choice. Assign a unique name when using multiple tags by the same vendor. Instance ID The Instance ID assigned by your account representative. Source Tracking ID A variable that you declare to identify traffic within the Anura interface. Campaign Tracking ID A subset variable of the Source Tracking ID that you declare to help identify traffic within the Anura interface. Response Object Variable Name The variable name of the JavaScript object that initial response data will be assigned to. Result Method The method used to query for results. Options are Script Response or Direct Response. Response Location The location to put the results in. Options are Window Variable, Session Storage, or Local Storage. Response Variable Name The name of the Response Location variable in which to place the final Anura response. Load Rules Load Rules determine when and where to load an instance of this tag on your site. Recommended Load Rule: Load on 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 Anura tag are built into its Data Mapping tab. Available categories are: Standard Tag Destination Description Variable Instance Required. Your instance ID. instance Source Tracking ID Optional. A variable, declared by you, to identify source traffic within the Anura dashboard. Maximum of 128 characters. M ay not equal the following values: "all sources", "all campaigns", "&", "*", "?", "%". Allowed to start with: "$", "_", or "a-z" characters, followed by "a-z" and "0-9" characters. source Campaign Tracking ID Optional. A subset of the source variable, declared by you, to identify campaign traffic within the Anura dashboard. Maximum of 128 characters. M ay not equal the following values: "all sources", "all campaigns", "&", "*", "?", "%". campaign Unique External ID Optional. A unique external tracking ID, declared by you, that is used to query the result from Anura servers. Maximum of 128 characters. exid Response Object Variable Name Optional. The variable name of the JavaScript object that response data will be assigned to. This variable contains the response ID, in addition to other data, that allows you to make real-time decisions. Maximum of 128 characters. variable Result Method Optional. The result method. result_method Result Location Optional. The result location. result_location Response Variable Name Optional. The Response Variable Name. response_variable Visitor IP Address Required. The IP address of your visitor. IPv6 addresses are also supported. ip Visitor User Agent Optional. The user agent string of your visitor. ua E-Commerce Since the Anura 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 extension mappings or your desired e-commerce variable is not offered in the extension. Destination Description E-Commerce Extension Variable Order ID Unique identifier assigned to the final order. _corder Sub Total Sub total amount of the final order. _csubtotal Currency Currency used in the payment. _ccurrency List of Product IDs Unique identifier of each product in the product array. _cprod List of Product Names Name of each product in the product array. _cprodname List of Brand Brand of each product in the product array. _cbrand List of Categories Name of each product in the product array. _ccat List of Quantities Quantity of each product in the product array. _cquan List of Prices Unit price of each product in the product array. _cprice e-comm destination name Insert description. N/A Vendor Documentation Anura Docs ... View more

View the Release Notes summary to learn about updated product features, enhancements, and fixes. To view details about how to use a new feature, click the Learn More link next to the description. Tags New/Cool Stuff Changed branding for Xiti name, logos, and QuickBase to AT Internet. (Learn more) Updated the Adobe Target tag to support Versions 1.7 and 2.0 and updated tool tips to explain that unbundling is not supported and will be overwritten at publish if the bundled flag is turned off. (Learn more) Updated the Clicktale tag to send audiences and badges to Clicktale. Updated the Clicktale tag to send replay links to Tealium Collect. Fixes Corrected Promo ID drop-down list for the Conversant Media - Direct to Brands tag. Corrected gtag.js issue for pages manually tagged with GTM. Updated the Google Analytics (gtag.js) connector to add support for event-scoped content groups. Connectors New/Cool Stuff New marketplace connector: Adobe Campaign Standard, Experiments - Beta (Learn more) New marketplace connector: Chameleon (Learn more) New marketplace connector: Criteo Audience Match (Learn more) New marketplace connector: Domo JSON Webhook (Learn more) New marketplace connector: Emailicious (Learn more) New marketplace connector: Flashtalking User Segments, Experiments - Beta (Learn more) New marketplace connector: iSpot TV (Learn more) New marketplace connector: Klenty (Learn more) New marketplace connector: Mailrelay (Learn more) New marketplace connector: Retently (Learn more) New marketplace connector: SmartSurvey (Learn more) New marketplace connector: Tamber (Learn more) New marketplace connector: Userlist.io (Learn more) Added Delete User action for the Braze connector. (Learn more) Added support for integer type number attribute. (Learn more) Updated the Optimizely Events connector to latest version. (Learn more) Fixes Corrected error with the Send a Custom App event for the Facebook Server-Side Events (BETA) connector. (Learn more) Corrected issue causing the AppsFlyer App Events connector to not send successful requests via Postman. (Learn more) Corrected issue with the Create or Update Contact actions for the Listrak connector passing wrong key. (Learn more) Corrected issue with the timestamp format for the date attribute when using the Responsys connector. (Learn more) Corrected issue with the "Subscribe User to List" action for the Iterable connector. (Learn more) Corrected XML structure issue with the SmartFocus connector. (Learn more) Corrected issue with select connectors causing the Active Campaign List ID to not send. iQ Tag Management New/Cool Stuff Introduced the Load Order Manager interface for tags and extensions under Experiments: BETA. (Learn more) Fixes Applied various security fixes. Universal Data Hub New/Cool Stuff Added missing us-east-2 (Ohio) Amazon Web Services (AWS) S3 bucket region for use with the File Import feature. Added the "Remove a String from the array" enrichment to the Array of Strings attribute. Fixes Corrected a text wrapping issue in the Trace window. Corrected issue causing console error when using the Timeline attribute in a rule. Corrected issue causing Visitor Profile Sampler charts to not update properly for specific profiles. (Learn more) Installations New/Cool stuff Introduced Tealium remote command integration for Braze on Android and Swift/iOS. (Learn more) Updated iOS library to support WKWebView for tag management for devices running iOS 11.0 or greater. (iOS Learn more, Swift Learn more) ... View more

The BETA version of our new client-side feature called Load Order Manager is now available. Using this feature, you can now control the order of operations for the Universal Tag (utag.js) to simplify the way you view and manage extensions and tag ordering. In this article: Table of Contents Placeholder Reasons for the Change Until now, the ability to reorder extensions and tags was limited and could only be performed on one extension or tag at a time by dragging and dropping the execution order from the main extensions and tags view or using the drop-down menu. Though this process is simple, is has the following limitations: When adding or editing an extension or tag, selecting the scope from the drop-down list does not always represent the true execution order. This is because the load order for extensions and tags is dictated by both execution order and extension and tag organization. There is no option for bulk reordering. It is difficult to reorder large lists that span beyond the visible view. Searching for specific extensions and tags is difficult What Improved The new Load Order Manager feature provides a more scalable and user-friendly method to manage tag and extension ordering. The process is still simple but without the previous limitations. Using Load Order Manager you can now: Display a single view of all of your marketplace extensions and tags, in execution order. Reorder extensions and tags more efficiently using improved drag-and-drop capabilities and numeric list ordering. Use the bulk feature to simultaneously reorder and move multiple extensions and tags. Use the improved search to filter extension and tag searches by label, title, type, or UID. What Changed Extensions Screen Extensions are now sorted and grouped by scope, according to the order of operations. Tags Screen Under Tag Configuration > Advanced Settings, the Wait Flag is now called Tag Timing. This setting determines if tags fire at the DOM Ready event, or immediately when utag.js loads. The options are Prioritized or DOM Ready (the default value). Where do I get it and how do I use it? Load Order Manager is currently launched as a client-side experiment that any user can enable at the profile level. To enable the feature, click iQ Tag Management (TiQ) > Client-Side Experiments in the left sidebar. Once enabled, the profile is saved to activate the feature. Once published, the feature is available to all users of that profile. To begin using Load Order Manager , simply click the new Edit Load Order button in the list view for any extension or tag. For detailed information about using Load Order Manager, see Load Order Manager (BETA). Can I provide feedback? Yes! To provide feedback, go to TiQ: Load Order Feedback. All feedback will be reviewed during the BETA release and considered for implementation in the final release. ... View more

This article describes how to set up the Mailrelay connector in your Universal Data Hub (UDH) account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add Subscriber ✓ ✗ 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: 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 Subscriber Parameters Parameter Description Your Account Your Mailrelay address or account name. For more information, see: https://mailrelay.com/en/api-documentation API key Your API key. Found in your account under settings. Email Email address of the subscriber. Name Name of the subscriber. ... View more

This article describes how to set up the SmartSurvey connector in your Universal Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add Contact to List ✓ ✗ 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: API Token The API token and token secret must be passed with each request. \ For more information, see: SmartSurvey: Getting Started API Token Secret The API token and token secret must be passed with each request. For more information, see: SmartSurvey: Getting Started 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 Contact to List Parameters Parameter Description Contact list ID The unique ID for the contact list. For more information, see: https://docs.smartsurvey.io/v1/reference#contactlists_contacts_insert Email The email address for the contact. Name The name of the contact. Custom Fields Custom data fields pertaining to the contact. ... View more

This article describes how to set up the Emailicious connector in your Universal Data Hub account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create Subscriber and Add Them to List ✓ ✗ 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 The username for your Emailicious account. For more information, see: https://emailicious-api.readthedocs.io/en/latest/topics/authentication.html Password The password for your Emailicious account. 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 Subscriber and Add Them to List Parameters Parameter Description Account Name The name of your Emailicious account. For more information, see: https://emailicious-api.readthedocs.io/en/latest/topics/introduction.html List ID The unique identifier for the list the subscriber will be added to. For more information, see: https://emailicious-api.readthedocs.io/en/latest/resources/subscribers.html#post--api-v1-lists-(int-list_id)-subscribers Email The subscriber's email. First Name The subscriber's first name. Last Name The subscriber's last name. Gender The subscriber's gender. Date of Birth The subscriber's date of birth. Language The subscriber's language. Region The subscriber's region. ... View more

This article describes how to set up the Retently connector in your Universal Data Hub (UDH) account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create or Update Customer ✓ ✗ Send Survey ✓ ✗ Unsubscribe Customer ✓ ✗ Delete Customer ✓ ✗ 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: API key: Your API key can be found in your Retently account under Settings. 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 Customer Parameters Parameter Description Email Email address of the customer. For more information, see: https://www.retently.com/api/#api-create-or-update-customers-post First Name First name of the customer. Last Name Last name of the customer. Company Company name assigned to the customer. Tag A tag to be assigned to the customer. Action - Send Survey Parameters Parameter Description Campaign The campaign identifier. Must be a transactional campaign type. For more information, see: https://www.retently.com/api/#api-send-survey-post Email Email address of the customer. For more information, see: https://www.retently.com/api/#api-create-or-update-customers-post First Name First name of the customer. Last Name Last name of the customer. Company Company name assigned to the customer. Tag A tag to be assigned to the customer. Action - Unsubscribe Customer Parameters Parameter Description Email Email address to be unsubscribed. For more information, see: https://www.retently.com/api/#api-unsubscribe-customers-post Message Opt out message. Action - Delete Customer Parameters Parameter Description Email Email address of the customer to be deleted. For more information, see: https://www.retently.com/api/#api-delete-customers-delete ... View more

This article describes how to set up the Chameleon connector in your Universal Data Hub account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create User ✓ ✓ Update User ✓ ✓ 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: API key Found here: https://www.trychameleon.com/integrations 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 User Parameters Parameter Description User ID An ID that uniquely identifies the user in your database. For more information, see: https://help.trychameleon.com/articles/1229862-send-user-properties Email An email address to connect their data in integrations you enable. User Data Any and all parameters pertinent to the user. Action - Update User Parameters Parameter Description User ID An ID that uniquely identifies the user in your database. For more information, see: https://help.trychameleon.com/articles/1229862-send-user-properties Email An email address to connect their data in integrations you enable. User Data Any and all parameters pertinent to the user. ... View more

This article describes how to set up the Klenty connector in your Universal Data Hub (UDH) account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create Prospect ✓ ✓ Update Prospect ✓ ✓ 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: API key To access the Kenty REST API's, you must have a Klenty account from which to generate your API key. Use the following steps to obtain this API key: Log into your Klenty account. Go to Settings > User Preferences > Klenty API Key. Click on the Generate API Key key icon to. For more information, see: http://support.klenty.com/articles/2530207-klenty-api 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 Prospect Parameters Parameter Description Username The username associated with the account. For more information, see: http://support.klenty.com/articles/2530207-klenty-api Email The email address of the prospect. First Name The first name of the prospect. Phone The phone number of the prospect. Company The company associated with the prospect. Full Name The full name of the prospect. Last Name The last name of the prospect. Middle Name The middle name of the prospect. Department The department associated with the prospect. Company Domain The company domain associated with the prospect. Title The title of the prospect. Location The location of the prospect. City The city associated with the prospect. Country The country associated with the prospect. List The list associated with the prospect. Tag The tag associated with the prospect. Action - Update Prospect Parameters Parameter Description Username The username associated with the account. For more information, see: http://support.klenty.com/articles/2530207-klenty-api Prospect Identifier The identifier of the prospect, typically email. Email The email address of the prospect. First Name The first name of the prospect. Phone The phone number of the prospect. Company The company associated with the prospect. Full Name The full name of the prospect. Last Name The last name of the prospect. Middle Name The middle name of the prospect. Department The department associated with the prospect. Company Domain The company domain associated with the prospect. Title The title of the prospect. Location The location of the prospect. City The city associated with the prospect. Country The country associated with the prospect. List The list associated with the prospect. Tag The tag associated with the prospect. ... View more

This article describes how to set up the iSpot TV Conversion Tracking connector in your Universal Data Hub (UDH) account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send Pixel ✓ ✓ 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: Site ID The tracking code requires a unique Site ID for each unique web site or app, which will be provided by iSpot. The format for Site ID is TC-1234-1, where: TC stands for tracking code 1234 is the client's account id -1 is the site identifier, which increments per site. 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 - Send Pixel Parameters Parameter Description IP Address IP address should be IPv4 only. Example: 23.123.223 Tealium will pass the value as part of the X-Forwarded-For request header. User Agent Pass the user agent of the original client device. Tealium will pass the User-Agent in the request header. Cookies The iSpot cookie will be sent as part of the Cookie request header. The value of this cookie can be derived from the original client-side browser via JSON response from the service. Example: https://ps.ispot.tv/v2/your-site-id.gif Referrer Referrer of the original visit, which is sent in the referer request header. Event Time If the time difference between the client visit and server-side request is greater than a few minutes, pass the original UTC time of the client visit formatted as yyyy-MM-dd hh:mm:ss If you do not specify an Event Time, Tealium will generate one at execution time. Custom Data The iSpot Tracking Code supports passing custom data for your business goals. Pass individual fields in this section and Tealium will combine them into a URL-encoded JSON object. ... View more