Tealium Learning Center

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

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

This article describes how to set up the Userlist.io connector in your Universal Data Hub (UDH) account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Track User Data ✓ ✓ Track 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: Push API key To start sending data into Userlist.io, you first have to get your Push API Key, which is used to authenticate your requests to the Push API and connect the data with your account. Keep this Push API Key secure. For more information, see: https://docs.userlist.io/article/15-integration-guide 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 - Track User Data Parameters Parameter Description Identifier Unique identifier for this user. This can be either the user's primary key in your database, a generated tracking identifier or their email address. For more information, see: https://docs.userlist.io/article/15-integration-guide Email The email address that will be used to send messages to this user. Signed Up At The time the user signed up, formatted using ISO 8601. If it is not set, Userlist will use the current time. Last Seen At The time the user was last seen inside your application. Formatted using ISO 8601. If it is not set, Userlist will use the current time. Userlist will update this property whenever an event happens for this user. Properties Custom properties that further describe the user. What you store here is totally up to you. The object's keys are normalized to snake_case . If they are set, we will use name , or first_name and last_name to represent the user inside of Userlist. Action - Track Event Parameters Parameter Description Name The name of the event that is triggered. The name will be normalized to snake_case . For more information, see: https://docs.userlist.io/article/15-integration-guide User If the identifier is not known to the system, it will create a new user. If the user already exists it will update it using the given information. Occurred At The time at which the event occurred. Formatted using ISO 8601. The system will use the current time if you do not provide input. Properties Custom properties that further describe the event. What you store in there is totally up to you. The object's keys will be normalized to snake_case . ... View more

This article describes how to set up the Tamber connector in your Universal Data Hub (UDH) account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send 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: Project Key Most requests can be made with only a Project key. All requests can be made with only an Engine key, as the Project will be automatically inferred. For more information, see: https://tamber.com/docs/api/#authentication Engine Key Most requests can be made with only a Project key. All requests can be made with only an Engine key, as the Project will be automatically inferred. For more information, see: https://tamber.com/docs/api/#authentication 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 Parameters Parameter Description User Unique identifier for the user. If the user does not yet exist, this action will create one. For more information, see: https://tamber.com/docs/api/#event-track Behavior The unique behavior name. Item Item associated with the event. Amount The amount that the behavior was performed. Example: Percentage of the movie that was watched, rating given, etc.). Defaults to 1.0 if a value is not supplied. Created Time the event occurred. Defaults to the current time if a value is not supplied. Hit Set to true to indicate that the event represents a successful recommendation. Example: The item in the event was presented to the user as a recommendation. Context Data The context in which the event occurred. Useful for segmenting events data to determine the impact of interface elements and other contextual variables on user behavior. Also useful for A/B testing interface changes. ... View more

This article describes how to set up the Braze connector in your Universal Data Hub  (UDH) account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Track User by External ID ✓ ✓ Track User by User Alias ✓ ✓ Delete User by External ID or Braze ID ✓ ✓ Delete User by User Alias ✓ ✓ 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: REST API Key API Keys are used to authenticate an API call. When you create a new REST API Key, you need to give it access to specific endpoints. By assigning specific permissions to an API Key, you can limit exactly which calls an API Key is able to authenticate. For more see https://www.braze.com/documentation/REST_API/#app-group-rest-api-keys This connector requires an API Key that has the User Data (users.track) permission ) to record user attributes, custom events, and purchases. For more see: https://www.braze.com/documentation/REST_API/#user-track-endpoint 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 - Track User by External ID Parameters Parameter Description Endpoint URL Required. Your endpoint will correspond to your Braze instance. This endpoint can be used to record custom events, user attributes, and purchases for users, see: https://www.braze.com/documentation/REST_API/#user-track-endpoint External ID The External ID serves as a unique user identifier for whom you are submitting data. This identifier should be the same as the one you set in the Braze mobile SDK in order to avoid creating multiple profiles for the same user. External IDs that Braze is unaware of will return a non-fatal error. See Server Responses for details. User Attributes An API request with any fields in the Attributes Object will create or update an attribute of that name with the given value on the specified user profile. Use the Braze User Profile Field names or your own custom attribute data. For more Information, see: https://www.braze.com/documentation/REST_API/#user-track-request. Action - Track User by User Alias Parameters Parameter Description Endpoint URL Required. Your endpoint will correspond to your Braze instance. This endpoint can be used to record custom events, user attributes, and purchases for users, see: https://www.braze.com/documentation/REST_API/#user-track-endpoint User Alias Value Map the actual identifier value for the alias. Example: "Bobby". An alias serves as an alternative unique user identifier. Use aliases to identify users along different dimensions than your core user ID. When using a User Alias, the "Update Only" mode is always true. For more detail on definitions, see: https://www.braze.com/documentation/REST_API/#basics User Alias Label The label for the Alias. Example" "my_internal_ids". An alias serves as an alternative unique user identifier. Use aliases to identify users along different dimensions than your core user ID. When using a User Alias, "Update Only" mode is always true. For more detail on definitions, see: https://www.braze.com/documentation/REST_API/#basics. User Attributes An API request with any fields in the Attributes Object will create or update an attribute of that name with the given value on the specified user profile. Use the Braze User Profile Field names or your own custom attribute data. For more information, see: https://www.braze.com/documentation/REST_API/#user-track-request Action - Delete User by External ID or Braze ID Parameters Parameter Description Endpoint URL Required. Your endpoint will correspond to your Braze instance. This endpoint can be used to record custom events, user attributes, and purchases for users, see: https://www.braze.com/documentation/REST_API/#user-track-endpoint External ID External ID of the user to delete. Must include either External ID or Braze ID For more information, see: https://www.braze.com/docs/api/endpoints/user_data/#user-delete-request Braze ID Braze ID of the user to delete. Must include either External ID or Braze ID. Action - Delete User by User Alias Parameters Parameter Description Endpoint URL Required. Your endpoint will correspond to your Braze instance. This endpoint can be used to record custom events, user attributes, and purchases for users, see: https://www.braze.com/documentation/REST_API/#user-track-endpoint Alias Name The alias name of the user to be deleted. For more information, see: https://www.braze.com/docs/api/endpoints/user_data/#user-delete-request Alias Label The alias label of the user to be deleted. ... View more

This article describes how to set up the Sizmek connector in your Universal Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add User To Sizmek Segment(s) ✓ ✓ Remove User From Sizmek Segment(s) ✓ ✓ Replace all Sizemek Segments for 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: 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 To Sizmek Segment(s) Parameters Parameter Description   cookie_id Required. Obtain the value from the visitor's browser.   segments Required. Pipe-separated list of segment IDs. If you pass an array type, Tealium will correctly format the data to be passed.   advertiser_id Optional. Sizmek Advertiser ID.  Set advertiser_id to zero ( 0 ) for a third-party advertiser.   account_id Optional. Account ID   adid Optional. Android ID used for mobile users.   idfa Optional. Apple IDFA used for mobile users. Additional Information This action is an incremental update of the user's segments. To send any other query parameter key-value pairs, map a Custom value key to the value. Action - Remove User From Sizmek Segment(s) Parameters Parameter Description   cookie_id Required. Obtain the value from the visitor's browser.   segments Required. Pipe-separated list of segment IDs. If you pass an array type, Tealium will correctly format the data to be passed.   advertiser_id Optional. Sizmek Advertiser ID.  Set advertiser_id to zero ( 0 ) for a third-party advertiser.   account_id Optional. Account ID   adid Optional. Android ID used for mobile users.   idfa Optional. Apple IDFA used for mobile users. Additional Information This action is an incremental update of the user's segments. To send any other query parameter key-value pairs, map a Custom value key to the value. Action - Replace all Sizemek Segments for User Parameters Parameter Description   cookie_id Required. Obtain the value from the visitor's browser.   segments Required. Pipe-separated list of segment IDs. If you pass an array type, Tealium will correctly format the data to be passed.   advertiser_id Optional. Sizmek Advertiser ID.  Set advertiser_id to zero ( 0 ) for a third-party advertiser.   account_id Optional. Account ID   adid Optional. Android ID used for mobile users.   idfa Optional. Apple IDFA used for mobile users. Additional Information This action is an incremental update of the user's segments. To send any other query parameter key-value pairs, map a Custom value key to the value. ... 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: Confirmit New marketplace tag: ContactWare for CX New marketplace tag: Jornaya New marketplace tag: LiveIntent In-App Tracking Updated the Adobe AppMeasurement for JavaScript tag to Version 2.14. (Learn more) Updated the Adobe Experience Cloud ID service tag to Version 4.3. (Learn more) Updated Facebook Pixel to support passing an event. Updated the Tealium Collect tag to capture downstream tag data. Fixes Corrected the network ID parameter name for the Adition tag. Updated the tab description for User ID and AuthState for the Adobe Experience Cloud ID Service tag. Connectors New/Cool lStuff Updated API error messaging for the Google Adwords Customer Match connector to include more detailed information. Fixes Corrected an issue with connector HTTP request retries that caused an abnormal number of reported errors (excludes SOAP and older connectors). Updated the Facebook Ads connector to remove the MULTI_HASH filter from the audience lookup options. iQ Tag Management Fixes Corrected issue causing the Go Live Notification email to be sent more than once for some accounts Updated the Tealium welcome email template to include updated links to Documentation, Forums, and Tealium Education Online. Universal Data Hub New/Cool Stuff Added rule and audience support for "matches regular expression (Regex)" for string operands. The Visitor Profile Sampler now displays a stitching distribution graph and five dashlets displaying a report of the most frequently asked questions. (Learn more) Fixes Corrected issue causing an error when selecting the Visitor ID attribute as a perspective in Audience Discovery. Corrected issue in AudienceDB to display all attributes instead of only displaying the enabled attributes. Installations Fixes Corrected issue causing Android application crashes when running multiple webviews. ... View more