Tealium Learning Center

This article describes how to set up the Amobee Cookie Matching Service tag in your Tealium iQ Tag Management account. In this article: Tag Tips Sends the following server-side attribute back to Tealium:   amobee_id If left blank, the Tealium account and profile names are automatically populated. Tag Configuration First, go to the tag marketplace and add the Amobee Cookie Matching Service tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Amobee Token (Your Amobee Token) 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 amobee_token Amobee token Your Amobee token, as provided by Amobee. tealium_account Tealium account name tealium_profile Tealium profile name ... View more

This article describes how to use the HTTP API - Advanced data source to create an HTTP endpoint to collect real-time event data with support for flattening complex objects. In this article: How It Works The HTTP API - Advanced data source is a generic data source that can conditionally parse incoming request bodies. This data source offers an HTTP endpoint to collect real-time event data with support for flattening complex objects. The endpoint is flexible and can be implemented as a tracking pixel in a web page or as a JSON API in your custom application. This data source is similar to the HTTP API data source, but with additional support for complex JSON objects. Events sent using HTTP POST with a complex JSON object will be flattened as follows: The event attributes names are created by lower-casing and joining the object properties with an underscore ("_"). For example: Source data: "alpha" : { "beta" : true } Flattened event attribute: "alpha_beta" : true Numbers, Booleans, and strings inside of an array are preserved. Objects and arrays inside of an array are stringified. Use this data source type when you need to send data in real-time and cannot modify the request to meet format requirements for the standard Tealium Collect endpoint. Batched Events The HTTP API - Advanced data source HTTP endpoint supports multiple events in a single request. These events are called batched events. For batched events, you receive one response code based on the status of all records. If a single record/event fails, only that event fails, the rest is processed. Requirements Tealium EventStream or Tealium AudienceStream Request Format The HTTP API - Advanced data source supports both the GET and POST methods. API Endpoint Use the following endpoint to access the HTTP API - Advanced data source: https://collect.tealiumiq.com/integration/event/ACCOUNT/PROFILE/DATA_SOURCE_KEY?tealium_trace_id=TRACEID Supported Parameters The following default parameters are supported in each request: Parameter Description tealium_event (Optional) The name of the event. tealium_trace_id (Optional) For use with Trace. Must be set as a query string parameter. Example: ?tealium_trace_id=abc123456 tealium_visitor_id (Optional) For use with Tealium AudienceStream. If tealium_visitor_id is not set in a batched event request, all events in the batch get the same generated anonymous ID value. This implies that the events will be tied together in the same visitor profile, regardless of visitor stitching. Adding the Data Source This section provides guidance on how to add the HTTP API - Advanced data source and create a webhook. Add the HTTP API - Advanced data source before proceeding, then copy the generated endpoint for use in an external system. Related: How to Add a Data Source Response Codes Response Code DESCRIPTION HTTP 204  Request Successful HTTP 400 Malformed JSON request HTTP 404   Examples The HTTP API - Advanced Incoming Webhook is useful when you want to send an HTTP API Advanced call using Javascript, bash scripting or curl. JSON Object Example 1 By default a JSON array will be treated as several events; so: [ { "Id": "1", "Detail": { "Name": "Event A" } }, { "Id": "2", "Detail": { "Name": "Event B" } } ] Will be transformed into several events: // First Event { "Id": "1", "detail_name": "Event A" } // Second Event { "Id": "2", "detail_name": "Event B" } Example 2 Before Flattening { "events": [ { "id": "1", "name": "Event A" }, { "id": "2", "name": "Event B" }, { "id": "3", "name": "Event C" } ] } After Flattening { "events": [ "{\"id\":\"1\",\"name\":\"Event A\"}", "{\"id\":\"2\",\"name\":\"Event B\"}", "{\"id\":\"3\",\"name\":\"Event C\"}" ] } Complex Object This section provides examples of input code and the resulting (flattened) output for complex objects. Before Flattening The following purchase event example shows how client-side e-commerce events with complex objects get flattened. { "ecommerce": { "event": "purchase", "purchase": { "customer": { "id": "8237572", "email": "john.smith@example.com", "city": "San Diego", "state": "CA", "country": "United States" }, "order": { "id": "ORD123456", "store": "mobile web", "subtotal": "2524.00", "total": "2549.00" }, "product": { "name": ["Product One", "Product Two"], "id": ["PROD123","PROD456"], "price": ["12.00","1250.00"], "brand": ["Ralph Lauren","Lucky"], "category": ["Apparel","Apparel"], "quantity": [1,1] } } } } After Flattening After flattening, the purchase event becomes: { "ecommerce_event": "purchase", "ecommerce_purchase_customer_id": "8237572", "ecommerce_purchase_customer_email": "john.smith@example.com", "ecommerce_purchase_customer_city": "San Diego", "ecommerce_purchase_customer_state": "CA", "ecommerce_purchase_customer_country": "United States", "ecommerce_purchase_order_id": "ORD123456", "ecommerce_purchase_order_store": "mobile web", "ecommerce_purchase_order_subtotal": "2524.00", "ecommerce_purchase_order_total": "2549.00", "ecommerce_purchase_product_name": ["Product One", "Product Two"], "ecommerce_purchase_product_id": ["PROD123","PROD456"], "ecommerce_purchase_product_price": ["12.00","1250.00"] "ecommerce_purchase_product_brand": ["Ralph Lauren","Lucky"], "ecommerce_purchase_product_category": ["Apparel","Apparel"], "ecommerce_purchase_product_quantity": [1,1] } Limitations The maximum Payload size is 3.5 MB. The number of records that can be processed per request is limited by the payload size. ... View more

This article describes how to manage server-side users and permission roles for the Tealium Customer Data Hub. This article covers the following topics: How It Works Server-side user permissions provide control over the degree of access users have for each profile by creating a separation of access between the Tealium client-side interface and the server-side interface. From the server-side Manage Users screen, you can do the following: Grant Access to New Users New users are added to accounts in Tealium iQ Tag Management. After new users are added, the new users display in the server-side user permissions list where server-side access can be granted, by profile. To add new users to an account, you must have the Manager Users permission. To assign roles on the server-side, you you must have the Manage Account permission. Specify Access Account administrators can grant access to users only for the areas that they intend to work on as well as grant Save and Publish permissions for client-side products for a profile that do not carry over to server-side products for that profile. Set Permissions for Future Profiles For active profiles, you can set the permissions for future profiles, which allows user admins to define a profile-level permission role for users of new profiles created for an account. Add and Edit Bulk Users You can add and edit users in bulk (up to 25 users at a time) and search user profiles and filter users by permission type. Admin Users Admins of the server-side interface are the only users that have the ability to change the permissions of server-side users. None of the server-side permission roles grant this ability. To be an admin on the server-side, you must have the Manage Account permission in the client-side interface. Only the Manage Users permission on the client-side grants the ability to add users to the account. To learn more about managing user permission in Tealium iQ Tag Management, see Managing User Permissions in iQ Tag Management. Server-Side Permission Roles Server-side access is controlled using predefined permission roles. For each profile in the account, users are assigned a permission role to determine their access level. The following table describes the four available server-side permission roles: PERMISSION ROLE DESCRIPTION No Access (default) This is the default role for all users other than account administrators. The No Access permission role does not grant any access to the server-side profile. If the user attempts to access the server-side, their profile is blocked and an "Access Denied" message displays. Reader The Reader permission grants read-only access to the server-side profile. A user in this role can browse the profile configuration, but Save/Publish is disabled. Users with this role cannot save any changes. Editor The Editor permission grants edit and save access to the server-side profile. With this role, you can save but not publish. Users with this role can also access and edit settings from the Profile Admin > Settings menu. Publisher (Admin default) This is the default role for account administrators. The Publisher permission grants the same access as the Editor role, with the addition of the ability to save and publish the profile. Profile access between the server-side and client-side product is mutually exclusive. For example, you can grant Save and Publish permissions for client-side products without impacting server-side product permissions for a given profile. In addition, if you remove or change user access to a profile on the client-side, it is not removed or changed on the server-side. Add a Server-Side Only User To give a user access to server-side, you must first add them in the client-side interface. In the client-side interface you must have the Manage Users permission to add users to your account and the Manage Account permission to manage permissions in the server-side interface. To add a user with only permission to a server-side profile, follow these steps: In the client-side interface, add the user, but do not select any client-side permissions. The user must verify their email address before you can continue, at which point the user has read-only access to the client-side interface and appears in the Manage Users list in the server-side interface. In the server-side interface, go to Manage Users and assign permission roles to grant the user access to a server-side profile, then click Next. Save your changes. Return to the client-side interface. On the User Menu, select Manage Users. In the User Manager dialog, select the user you want to remove. Click More and select Remove User. In the Remove User dialog, confirm the user to be removed, then click Remove User. The user no longer has access to the client-side profile, but retains access to the server-side profile. Edit Server-Side User Permissions To edit server-side user permissions, you must have the Manage Account permission, which is assigned from the client-side interface. Use the following steps to view and edit server-side permissions for a user: Log into the server-side area of the Customer Data Hub. In the user admin menu, select Manage Users. A list of all server-side users displays, including the user's name, email address, and a timestamp for the last login. Click a user to display the permission details. To grant access to a profile, select a Permission Role. Repeat Step 3 through Step 5 for each user you want to edit. If no changes are needed, click X to close the user details and return to the user list. You will be prompted to confirm your intention to disregard changes if you have made adjustments. Click Save to keep your changes or Cancel to discard the changes. Your changes are saved without the need to publish. Set Permissions for Future Profiles Use the following steps to set permissions for future profiles, which allows user admins to define a profile-level permission role for users of new profiles created for an account. Log into the server-side area of the Customer Data Hub. On the user admin menu, select Manage Users. In the Set permissions for future profiles list, select a role to be assigned to users of new profiles created for an account. Click Save to keep your changes or Cancel to discard the changes. Your changes are saved without the need to publish. Edit User Permission Roles in Bulk Use the following steps to edit the permission role for multiple users: On the user admin menu, select Manage Users. Select each user for which you want to change the permission role. Click Bulk Actions and select the permission to assign to the selected users. Click Apply, then click Save. You do not need to publish for your changes to persist. Frequently Asked Questions (FAQ) If a user is removed from the client-side profile, is the user also removed from the server-side profile? No. When a user exists in both client-side and server-side, removing the user from one does not impact the other. Can I grant a user access to a server-side profile without allowing access to a client-side profile? Yes. If a user already exists in the account and has been granted permission to a profile on the server-side, go to iQ Tag Management > Manage Users and remove that user from the client-side interface. For more information, see Add a Server-Side Only User. How does the "All current and future profiles" option impact server-side permissions? There is no impact to server-side users. All server-side users have the default permission role of No Access to all new server-side profiles. What happens if a user has access to only one profile on the server-side and no profile access on the client-side? If the user selects server-side at the login screen, they are automatically loaded into the account/profile accordingly. If the user attempts to log in to the client-side, a modal displays with a denied access message. Can a server-side admin change their own permissions for server-side profiles? Yes. A server-side admin user (granted by the Manage Account permission) can change permissions for all server-side users, including their own. Can a server-side admin update manage permissions for all server-side profiles? Yes. A server-side admin user's access is granted by the Manage Account permission, which is an account-level permission. Users with this permission level have access to the Manage Users screen in the server-side interface where they can manage user permissions for all profiles. How do the new server-side permissions affect the Omnichannel File Status API? Access control to the Omichannel File Status API will change upon final release of the server-side permissions feature. In addition to the standard requirement of needing an API key to authenticate with the API, users must have read access to the relevant Customer Data Hub account. Users using the v1 API only need read access to the Customer Data Hub account. Can a server-side admin add new users to an account? No. The Manage Account permission does not grant access to add new users or delete users from an account. While they can remove access to profiles, only users who have the Manage Users permission assigned in the iQ Tag Management workflow can invite a new user to an account or completely delete a user from an account. Does this feature change the way user management access is granted or controlled within TiQ? No. The Manage Users permission in iQ Tag Management remains the permission that grants a user access to add or remove users from a business account. Users with only the Manage Users permission do not have access to manage permissions on the server-side. Additional Resources Managing User Permissions in iQ Tag Management ... View more

Learn about the new features and fixes released in February 2021. Tags New/Cool Stuff Updated The Trade Desk Cookie Matching Service template to trigger only once per session by default. (Learn more) The Cookie Reports tag is now rebranded to Digital Control Room. (Learn more) Updated the createContexts function for the Snowplow tag to allow arrays of variables to be passed and support sending multiple contexts. (Learn more) Updated the Fullstory tag to support page events for the FS.setVars API. (Learn more) Updated mobile timestamp handling for the Adobe AppMeasurement tag, Versions 1.6.3 and later. (Learn more) Updated the Adobe Target tag to support Version 2.4. (Learn more) Updated the Adobe Experience Cloud ID Service API to support Version 5.2. (Learn more) Connectors New/Cool Stuff Added batching support for the Sailthru connector. (Learn more) Added new, required parameters for the Facebook Conversions connector. (Learn more) Upgraded the Twitter Ads API from from Version 7 to Version 8. Fixes Corrected issue in Facebook Conversions that caused the "Action Source" key in Event Data mapping to display in the wrong area. iQ Tag Management New/Cool Stuff New marketplace extension: Usercentrics CMP, V1. (Learn more) New marketplace extension: Usercentrics CMP, V2. (Learn more) Reintroduced the original JavaScript extension as the JavaScript Code Extension (Basic), which is now available in addition to the Advanced JavaScript extension. (Learn more) Fixes Corrected a cosmetic issue to ensure that single items do not scroll on a page when performing a Load Order Manager bulk move. Corrected an issue where child profiles were able to inherit an "add-once" extension from a parent library, which resulted in multiple extensions in the child profile. Corrected an issue where changing JavaScript Extension scopes from Tag Scoped to DOM Ready created a duplicate of the extension. Corrected an issue that occurred when importing variable bundles that created an additional e-commerce extension for the first time and did not map variables by default as expected. Corrected an issue in Consent Manager (Preferences) that caused omitted tags to fire twice for events with a UIDs array that occurred before a consent decision when the omitted tags were included in the UIDs array. Customer Data Hub Fixes Corrected an issue in the display of server-side versioning that caused the graph to not display property. Corrected issue causing the Data Source tab to not load if the profile contains a deprecated data source. Corrected issue causing problems when filtering Live Events using TraceId . Corrected the visit expiration estimate calculation for visitor profiles. Installations New/Cool Stuff Mobile Android Updated React Native to support the latest Kotlin libraries. Corrected issue causing offline tracking to not be dispatched when an application is started offline. Added public API method to reset and regenerate the Tealium Visitor ID. iOS Applied various enhancements to improve the user experience when working with the Tealium and Adobe visitor services. Swift Updated the Airship remote command integration to support JSON configuration files for Swift 2.0. Updated React Native to support the latest Kotlin libraries. Added NativeScript integration support for mobile SDKs. NativeScript Released Tealium for NativeScript, a set of cross-platform classes that interface with the native Tealium iOS SDKs. (Learn more) ... View more

This article describes how to set up the Digital Control Room (formerly Cookie Reports) tag in your Tealium iQ Tag Management account. In this article: Requirements The unique 8-digit code and language code for your site, supplied by Digital Control Room. Tag Tips Use mapping to override standard configuration values dynamically. Tag Configuration First, go to the tag marketplace and add the Digital Control Room (formerly Cookie Reports) tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Policy Code: //policy.cookiereports.com/XXXXXXXX_panel-en-gb.js Language Code: //policy.cookiereports.com/XXXXXXXX_panel-XX-XX.js 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 policy_code Policy Code language_code Language Code ... View more

The Tealium Usercentrics extension is used to enable third party CMP support. The extension simplifies the integration between Tag Management and Consent Management by allowing you to map data processing services to specific tags. Implementing this extension ensures the enforcement of end-user privacy preferences (consent) and that only consented services have the ability to transmit data to third parties. The implementation additionally ensures that only mapped tags can actively run on the website, which reduces the privacy risk exposure when changes are introduced. In this article: Table of Contents Placeholder How it Works The Tealium iQ Tag Management Usercentrics extension is used to ensure that your CMP policy is enforced at the source level, thus blocking or firing tags according to the user's consent preferences. Simple bookmarklet functionality is used to import the Data Processing Services JSON object text to a bookmark in your browser, which is then used to create a mapping table. To use, add the extension, enter the required information, and then use the mapping table to map consent preferences to your tags. Using this method significantly reduces implementation time and provides an extra layer of protection by preventing tags from firing until they are mapped to a CMP service. To prevent privacy risk exposure in instances where a tag is added without being mapped to a Usercentrics data processing service, only mapped tags fire once the extension is active. Prerequisites Knowledge of your Usercentrics Implementation You must have knowledge of the current or planned version of your Usercentrics implementation. To obtain all of the Data Processing Services in your Consent Management Platform (CMP), follow the instructions outlined in the Usercentrics Direct Implementation Guide. Use a Test Environment for your First Implementation Tealium recommends using a testing environment for your first implementation in order to fully access the CMP to create the mapping table within the extension. Using a testing environment ensures that no end-user data is processed prior to applying the extension in your development environment. Once you have completed the mapping of all data processing services to their corresponding tags, you can release it to production and Tealium iQ Tag Management will handle the enforcement of end-user privacy preferences (consent). Requirements Tealium Universal Tag (utag.js), Version 4.48. (Learn more) The Usercentrics CMP must load before Tealium iQ Tag Management. For this reason, you must do one of the following: Implement the Usercentrics Script (tag) directly within the HTML code of your website. - OR - Go to the Implement the Usercentrics Tag section below and follow the instructions to implement the tag within Tealium iQ Tag Management. Create a Data Processing Service for Tealium iQ Tag Management in your Usercentrics CMP setup. To learn more, see the Usercentrics documentation, Assign a data attribute. Know the name of your Data Processing Service before you begin, as it is required in the configuration steps. Implement the Usercentrics Tag Use the following steps to implement the Usercentrics tag within Tealium iQ Tag Management using the JavaScript Code extension: Go to Tealium iQ Tag Management > Extensions > Add Extension and select the JavaScript Code extension to add the script for Usercentrics V1 or Usercentrics V2. Add the JavaScript Code extension. If you have not previously used the JavaScript Code extension and need to learn how, see JavaScript Code Extension. Name the extension Usercentrics Tag, and set the scope to Pre Loader. Use the script from one of the following examples to create the extension: Usercentrics V1 Script: Supports Usercentrics CMP v1. (function(a, b, c, d) { b = document; c = 'script'; d = b.createElement(c); d.src="XXXXXXXXXXX"; // URL for Usercentrics CMP Version 1 Script. d.type = 'text/java' + c; d.async = true; d.id = 'XXXXXXXXX'; // Usercentrics Settings-ID a = b.getElementsByTagName(c)[0]; a.parentNode.insertBefore(d, a); } )(); Usercentrics V2 Script: Supports Usercentrics CMP V2 Browser SDK (function(a, b, c, d) { b = document; c = 'script'; d = b.createElement(c); d.src="XXXXXXXXXXX"; // URL for Usercentrics CMP Version 2 Script. d.type = 'text/java' + c; d.async = true; d.id = 'usercentrics-cmp'; d.setAttribute('data-settings-id', "XXXXXXXXXXX"); // Usercentrics Settings-ID a = b.getElementsByTagName(c)[0]; a.parentNode.insertBefore(d, a); } )(); Save and publish the JavaScript Code extension to your environment. Create a Tealium Data Processing Service in your Usercentrics CMP You must create a Tealium Data Processing Service in your Usercentrics account to ensure that user consent preferences are enforced and third parties can only process data if allowed to do so. Use the following steps to create a Data Processing Service for Tealium iQ Tag Management in your Usercentrics CMP account: Go to your Usercentrics account . Select the most recent Data Processing template for Tealium iQ Tag Management. Mark the template as Required to ensure that it cannot be opted out. If you customized the Tealium iQ Tag Management service name, it will not be automatically detected by the CMP extension. In the Configuration section of this document, you will manually add the custom service name using the Service Name input field. Configure the Extension The steps in this section describe how to add the extension, install the bookmarklet, copy the data processing services, import the data processing services, and map your tags to your data processing services. Add the Extension Use the following steps to add the Usercentrics extension: Go to iQ Tag Management > Extensions > Add Extension and click the Privacy tab. Select one of the Usercentrics extensions: Usercentrics V1 or Usercentrics V2. Select the version that corresponds with the version currently in use by your organization. In the Title field, enter a meaningful title to be used for this extension. Note that the Scope field cannot be modified. Enter the Settings-ID (Optional) Under Usercentrics Settings ID, in the Settings ID field, you can manually add your Usercentrics Settings_ID . This step may not be needed as the Usercentrics Settings-ID is automatically added to the extension while importing the data processing services. Under the Tealium iQ Service Name, in the Service Name field, enter the exact name that was given to the Tealium Data Processing Service within Usercentrics. Continue to the next section to install and use the Service Mapper bookmarklet. Install the Service Mapper Bookmarklet Use the following steps to install the bookmarklet: Click the Bookmarklet button. The Usercentrics Service Mapper Bookmarklet dialog displays. Click the Usercentrics Service Mapper link and drag and drop the bookmarklet onto the bookmark bar for your browser. The bookmarklet now displays in your browser bar. Click Close to dismiss the Usercentrics Service Mapper Bookmarklet window. Create a Mapping Table Use the following steps to copy and import your data processing services to create a mapping table: Open another browser tab and navigate to the Usercentrics test environment where your CMP is implemented and click the Usercentrics Service Mapper bookmarklet to launch. A pop-up window displays the text for your Data Processing Services JSON object. Copy the entire text from this window. Navigate back to the Usercentrics configuration dialog in iQ Tag Management and click the Import button. The Import Services dialog displays. Paste the copied JSON text into the window, as shown in the following example. Click Create Mapping Table. Your Usercentrics Settings ID and Tealium iQ Service Name are now automatically populated and the Service Mappings to your data processing services display in a mapping table. The mapping table must be updated each time a new tag is introduced or when your Data Processing Services with the Usercentrics configuration is changes, as described in the Update the Mapping Table section of this document. Map Data Processing Services to Tags Use the following steps to map your data processing services to tags: For each item in the mapping table, click the To UID field and use the prepopulated list to select the appropriate tag UID. You can map more than one tag to a data processing service. The bookmarklet automatically adds a list item for Tealium iQ Tag Management and Usercentrics in the mapping table. Use the trash can icon to delete the Tealium iQ Tag Management and Usercentrics services, as they are not used for consent enforcement. (Optional) Click Add Service to manually add additional services and map them accordingly. When complete, consent is immediately enforced without the necessity of a page reload, which guarantees that end-user privacy preferences are enforced before any data processing takes place. Save and Publish your changes. Update the Mapping Table The mapping table must be updated when a new tag is introduced or when your Data Processing Services within the Usercentrics setup changes. Use the bookmarklet functionality as described in the configuration steps and repeat the process to update. The Import function identifies Data Processing Services that already exist, including any that have been recently added and those that were previously deleted, as follows: If the Data Processing Service already exists, mapping is not impacted. If the Data Processing Service was deleted, it also deletes the mapping entry. If the Data Processing Service is newly introduced, a new line item is added to the mapping table and you must map at least one corresponding tag. Troubleshooting To view typical events, log messages, and error messages that may require attention, enable console logging. Use the following steps to enable console logging: Go to JavaScript (Web) Debugging and follow the steps to add the debugging cookie. After the debugging cookie is set, use the "/SENDING|\*\*\*\*/" filter to display only relevant entries. FAQ Can this extension be used in mobile installations? No. Mobile installations, such as iOS and Android, do not support the Tealium iQ Tag Management Usercentrics extension. Additional Information Usercentrics Direct Implementation Guide Usercentrics CMP, Version 1 Usercentrics Web CMP, Version 2 Tealium: Master List of Extensions Become a Tealium Techology Partner ... View more

Beginning February 15th, 2021, website events that are shared using the Facebook Conversions API require additional parameters to remain operational. This notification describes the new parameters and how to configure them using your Facebook Conversions connector. About The new parameters for the Facebook Conversions connector are intended to improve the quality of events used for ad delivery and campaign performance. These parameters are required and must be added to your current Facebook Conversions connector configuration in order for the connector to remain operational. In addition to ensuring the new parameters are added and configured, Tealium recommends checking the following items throughout your Facebook Conversions connector configuration: action sources website events URLs sent User Agent attributes sent What's New The following new parameters are now available in the connector marketplace for the Facebook Conversions connector and must be added and configured before February 15, 2021: Web client_user_agent Required if the Action Source is set to website. The user agent for the browser corresponding to the event. EventStream If the Action Source is set to website and this field is not mapped, it will automatically be mapped to the attribute User Agent in EventStream. AudienceStream If the Action Source is set to website and this field is not mapped, it will automatically be mapped to the vistor's last User Agent in AudienceStream. Customer Information Parameters (Facebook Documentation). action_source Required. This field allows you to specify where your conversions occurred. Valid action sources are: email website app phone_call chat physical_store system_generated other Server Event Parameters (Facebook Documentation). event_source_url Required if the Action Source is set to website. The browser URL where the event happened. EventStream If the Action Source is set to website and this field is not mapped, it will automatically be mapped to the attribute Current URL in EventStream. AudienceStream If the Action Source is set to website and this field is not mapped, it will automatically be mapped to the attribute Last Event URL in AudienceStream. Server Event Parameters (Facebook Documentation). Non-Web action_source Required. This field allows you to specify where your conversions occurred. Valid action sources are: email website app phone_call chat physical_store system_generated other Server Event Parameters (Facebook Documentation). For detailed information about using and configuring the Facebook Conversions connector, see the Facebook Conversions Connector Setup Guide. ... View more

This article describes how to set up the Google Analytics 4 tag (GA4) in your Tealium iQ Tag Management account and considerations to be aware of during implementation. In this article: Overview Google Analytics 4 (GA4) is the new version of Google Analytics. One of the differences between GA4 and Google Universal Analytics is that GA4 uses a different reporting method. If your site is currently running Google Universal Analytics, it is recommended that you run both Google Universal Analytics and GA4 concurrently for a few months before switching completely to GA4. This approach allows historical data to continue to be collected in Google Universal Analytics while you gain familiarity with the reporting in GA4. Note that Google Universal Analytics will stop processing data on July 1, 2023 (October 1, 2023 for 360 accounts). Google Universal Analytics has several hit types, including event tracking, pageviews, timing events, and social shares. GA4 is completely event-based, meaning that there are only event hits. GA4 does not have the event categories, actions, labels, and values used in Google Universal Analytics. Instead, the data sent with GA4 events includes an event name and customizable event parameters that contain contextual data for the event. For more information on migrating to GA4 from Google Universal Analytics, see Migrating from Universal Analytics to Google Analytics 4. Configuring the Google Analytics 4 Tag Go to the tag marketplace and add the Google Analytics 4 tag. For information on adding a tag, see Tags. After adding the tag, configure the following settings: Measurement ID Measurement ID of the Google Analytics property for which you want to send data. The measurement ID begins with "G-". For example, G-12345678M . Use a comma-separated list of measurement IDs to send data for multiple GA4 properties. Global Object The name of the Global Object used for the event queue. If not specified, gtag is used. For most implementation, the default is used. Data Layer Name By default, the data layer initiated and referenced by the global site tag is named dataLayer . For most implementation, the default is used. Send Page View By default, Page View events are automatically recorded for each page on your site. If you do not want to send Page View events to Google Analytics, set this option to false. Clear Vars Clears items usually set for the lifetime of the tracker after each tracking request. GA4 Event Types GA4 is event-based and provides the following types of events: Automatically Collected Events Enhanced Measurement Events Recommended Events  Custom Events The following diagram shows how to determine which type of event to for your use case: Automatic Events GA4 automatically generates some events, with no configuration required. For more information on automatically generated events and their parameters, see Google Analytics 4 Automatically Collected Events. Enhanced Measurement Events You can enable enhanced measurement options (events) in the Google Analytics interface to measure interactions with your content. No configuration in Tealium iQ is required. When you enable enhanced measurement options, additional events are sent that provide information on user activity such as file downloads and searches. For more information, see the GA4 documentation for Enhanced Measurement Events. Recommended Events GA4 provides recommended events, including events recommended for all sites, as well as events specific to online sales and to games. Each recommended event has one or more parameters that provide additional context for the event. For more information on these events and their parameters, see the Google Recommended Events documentation. Custom Events If your event does not fit one of the three event types described above, send a custom event. For more information, see GA4 Custom Events. Event Mapping Examples This section provides mapping examples of event mapping for two events that will be sent to GA4: Visitor logs in Visitor clicks a contact us link To map an event in Tealium iQ, map a data layer variable value that specifies when an event should be fired. These examples use the  tealium_event  variable to identify the event to be sent. Login Event Example For the login event, the following data is sent to Tealium iQ in a utag.link call: utag.link({ "tealium_event" : "sign in", "signin_method" : "email" }); Login is one of the GA4 recommended events, and has one parameter, method , that indicates how the user logged in. When you configure the GA4 tag, use the mapping toolbox to map the tealium_event and signin_method variables, as follows: tealium_event – Select Event Triggers for the Category, and then enter sign in in the Trigger field and select login  for Event.  signin_method – Select Event-specific Parameters for the Category, and then enter method in the Event parameter field and select login for For event. For more information on mapping variables, see Data Mappings. Contact Us link Event Example For the contact us link event, the following data is sent to Tealium iQ in a utag.link call: utag.link({ "tealium_event" : "contact us" }); This is event is not one of the GA4 recommended events, so it's mapped as a custom event, as follows: tealium_event – Select Event Triggers for the Category, and then enter contact us in the Trigger field. Select Custom Event  for Event and enter contact_us_click in the Custom Name field. For more information on mapping variables, see Data Mappings. Tracking Ecommerce Events GA4 has ecommerce events that are equivalent to the enhanced ecommerce events for Google Universal Analytics. The differences in the GA4 ecommerce events are as follows: The checkout_step and checkout_options events have been replaced with the view_cart , begin_checkout , add_shipping_info , and add_payment_info events in GA4. The product_click and select_content (with an  items array parameter) events have been replaced with the select_item event in GA4. The promotion_click  and  select_content (with a promotions array parameter) events have been replaced with the select_promotion event in GA4. Items Parameter for Recommended Events Some ecommerce events have an items parameter. For these events, the items array is automatically populated from E-commerce extension values, such as product name, category, and price. For more information, see E-commerce Extension. Custom Dimensions Currently, GA4 has two scopes for custom dimensions: User Scoped Event Scoped Google Universal Analytics has four scopes: Hit (similar to Event in GA4) Session User (similar to User in GA4) Product When translating requirements from Google Universal Analytics to GA4, consider passing session scoped variables as user scoped variables where it makes sense. GA4 does not currently offer an alternative for product scoped events. Validating a GA4 Implementation Event Batching In Google Universal Analytics, one network call is made for each hit that was triggered. GA4 is different in that it batches events that occur within a few seconds into a single call. When investigating network calls to validate the implementation, be aware that multiple events may be sent with a single network request. Reporting Latency Per the Google documentation, it can take 24-48 hours after the call is made for GA4 reports to be generated. You can use Realtime reports and Debug View in GA4 to verify that data is being sent to your GA4 property. ... View more

This article describes how to set up the Exactag tag in your Tealium iQ Tag Management account.. In this article: Tag Tips Supports the E-Commerce extension for: Order ID Order Subtotal Order Total Order Coupon Code Customer ID Product ID Product Name Product Category Product Quantity Product Unit Price Conversion data automatically added when Order ID is present. Conversion data can be manually triggered by setting the Is Conversion Flag to true Additional data points can be added through the UI Add Custom Destination option Tag Configuration First, go to the tag marketplace and add the Exactag tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Campaign Code Your brand-specific Campaign Code 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 Campaign Code (campaign) Referrer URL (referrer) Host Domain (host) Site Path (site) Search Parameters (search) Site Group (sitegroup) Cross Device ID (crossid) Subid (subid) Is Conversion Flag (is_conversion) E-Commerce Variable Description Level Value (level) Customer Gender (customer_gender) Customer Type (customer_type) Order ID (order_id) (Overrides _corder) Revenue/Order Total (order_total) (Overrides _ctotal) Total Price/Sub Total (order_subtotal) (Overrides _csubtotal) Promo Code (order_coupon_code) (Overrides _cpromo) Cart or Order Type (order_type) (Overrides _ctype) Customer ID (customer_id) (Overrides _ccustid) List of Product IDs (product_id) (Overrides _cprod) [Array] List of Names (product_name) (Overrides _cprodname) [Array] List of Categories (product_category) (Overrides _ccat) [Array] List of Quantities (product_quantity) (Overrides _cquan) [Array] List of Prices (product_unit_price) (Overrides _cprice) [Array] ... View more

This article describes how to set up the Yahoo! Japan Site General Tag tag in your Tealium iQ Tag Management account. In this article: Tag Tips IMPORTANT: To trigger a particular tag, set up the trigger condition in the Tag Types tab in the mapping toolbox. Otherwise, no tags will be triggered. Use mappings to override the standard configurations. You may enter more than one ID or Label in a comma-separated list. If you enter one ID and multiple Labels, you will trigger one call for each Label, each using the same ID. If you enter multiple IDs and a single Label, you will trigger a call for each ID, each using the same Label. If you enter multiple IDs and Labels for a single tag type, make certain the numbers of IDs and Labels match. Supports these E-Commerce extension values: Order ID ( _corder) Order Subtotal ( _csubtotal ) List of Product IDs ( _cprod ) List of Product Categories ( _ccat ) List of Product Quantities ( _cquan ) List of Product Prices ( _cprice ) Tag Configuration First, go to the tag marketplace and add the Yahoo! Japan Site General Tag tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Auto Tagging: Enable or disable auto tagging. Enabling this setting performs the ytag({"type":"ycl_cookie"}); call after the tag loads. Display Network Conversion IO: Enter your Yahoo! Japan Display Network (YDN) Conversion IO. Display Network Conversion Label: Enter your Yahoo! Japan Display Network (YDN) Conversion Label. Display Network Retargeting ID: Enter your Yahoo! Japan Display Network (YDN) Retargeting ID. Display Network Retargeting Label: Enter your Yahoo! Japan Display Network (YDN) Retargeting Label. Sponsored Search Conversion ID: Enter your Yahoo! Japan Sponsored Search (YSS) Conversion ID. Sponsored Search Conversion Label: Enter your Yahoo! Japan Sponsored Search (YSS) Conversion Label. Sponsored Search Retargeting ID: Enter your Yahoo! Japan Sponsored Search (YSS) Retargeting ID. 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. To fire any tags, you must set up the trigger condition in the Tag Type category. The available categories are: Display Network (YDN) Conversion Variable Description Conversion IO ( yahoo_ydn_conv_io ) [String] Conversion Label ( yahoo_ydn_conv_label ) [String] Conversion Transaction ID ( yahoo_ydn_conv_transaction_id ) [String] Conversion Value ( yahoo_ydn_conv_value ) [String] Display Network (YDN) Retargeting Variable Description Retargeting ID ( yahoo_retargeting_id ) [String] Retargeting Label ( yahoo_retargeting_label ) [String] Retargeting Page Type ( yahoo_retargeting_page_type ) [String] Retargeting Items ( yahoo_retargeting_items ) [Array] Category ID ( category_id ) (Overrides _ccat ) [Array] Item ID ( item_id ) (Overrides _cprod ) [Array] Price ( price ) (Overrides _cprice ) [Array] Quantity ( quantity ) (Overrides _cquan ) [Array] Sponsored Search (YSS) Conversion Variable Description Conversion ID ( yahoo_conversion_id ) [String] Conversion Label ( yahoo_conversion_label ) [String] Conversion Value ( yahoo_conversion_value ) [String] Sponsored Search (YSS) Retargeting Variable Description Retargeting ID ( yahoo_ss_retargeting_id ) [String] Custom Params ( yahoo_sstag_custom_params ) E-Commerce Variable Description Order ID ( order_id ) (Overrides _corder ) [String] Sub Total ( order_subtotal ) (Overrides _csubtotal ) [String] List of Product Categories ( product_category ) (Overrides _ccat ) [Array] List of Product IDs ( product_id ) (Overrides _cprod ) [Array] List of Product Quantities ( product_quantity ) (Overrides _cquan ) [Array] List of Product Prices ( product_unit_price ) (Overrides _cprice ) [Array] Tag Types Variable Description Display Network Conversion yjad_conversion Display Network Retargeting yjad_retargeting Sponsored Search Conversion yss_conversion Sponsored Search Retargeting yss_retargeting Custom Custom Type-Specific Parameters Variable Description Conversion IO ( yahoo_ydn_conv_io ) yahoo_ydn_conv_io Conversion Label ( yahoo_ydn_conv_label ) yahoo_ydn_conv_label Conversion Transaction ID ( yahoo_ydn_conv_transaction_id ) yahoo_ydn_conv_transaction_id Conversion Value ( yahoo_ydn_conv_value ) yahoo_ydn_conv_value Retargeting ID ( yahoo_retargeting_id ) yahoo_retargeting_id Retargeting Label ( yahoo_retargeting_label ) yahoo_retargeting_label Retargeting Page Type ( yahoo_retargeting_page_type ) yahoo_retargeting_page_type Retargeting Items ( yahoo_retargeting_items ) yahoo_retargeting_items Item ID ( item_id ) item_id Category ID ( category_id ) category_id Price ( price ) price Quantity ( quantity ) quantity Conversion ID ( yahoo_conversion_id ) yahoo_conversion_id Conversion Label ( yahoo_conversion_label ) yahoo_conversion_label Conversion Value ( yahoo_conversion_value ) yahoo_conversion_value Retargeting ID ( yahoo_ss_retargeting_id ) yahoo_ss_retargeting_id Custom Parameters ( yahoo_sstag_custom_params ) yahoo_sstag_custom_params Custom Parameter Custom_Parameter Display Network (YDN) Conversion yjad_conversion Display Network (YDN) Retargeting yjad_retargeting Sponsored Search (YSS) Conversion yss_conversion Sponsored Search (YSS) Retargeting yss_retargeting Custom Tag Type Custom_Type Use cases Trigger YDN Retargeting on every page that matches load rules To set up a tag which fires on every page according to load rules: On the Tag Configuration tab, enter the appropriate value for the Display Network Retargeting ID box. Set Auto Tagging to True. This will trigger the ytag({"type":"ycl_cookie"}); call. Set up your load rules as needed. On the Data Mappings tab in the Variables dropdown, click Use Custom Value. In the upper-left section of the dialog, enter true in the box. In the Category section, select Tag Types. In the When mapped variables equals box, enter true. In the Trigger tag type dropdown, select Display Network Retargeting. Click +Add. Click Done. Click Apply. Trigger YDB Conversion on a purchase event while retargeting on other pages To set up a YDN Conversion tag which fires on a page with a tealium_event variable value of purchase and a Retargeting tag on every other page according to load rules: Set up your Retargeting tag as described in the Trigger YDN Retargeting on every page that matches load rules section above. On the Tag Configuration tab, enter the appropriate values for the Display Network Conversion IO and Conversion Label boxes. On the Data Mappings tab in the Variables dropdown, select tealium_event . Click +Select Destination. In the Category section, select Tag Types. In the When mapped variables equals box, enter purchase . In the Trigger tag type dropdown, select Display Network Conversion. Click +Add. Repeat steps 3 through 8 for similar mappings, such as Conversion Transaction ID and Conversion Value, by Selecting Display Network (YDN) Conversion from the Category section. To fire the conversion on multiple pages, either repeat these steps or create a vendor-specific variable (for example: yahoo_conversion_value ), which can be dynamically assigned via extensions. Click Done. Click Apply. Trigger YDB Conversion on a specific page's URL while retargeting on other pages To set up a YDN Conversion tag which fires on a specific page's URL (for example: /cart/thankyou ) and a Retargeting tag on every other page according to load rules: Set up your Retargeting tag as described in the Trigger YDN Retargeting on every page that matches load rules section above. On the Tag Configuration tab, enter the appropriate values for the Display Network Conversion IO and Conversion Label boxes. On the Data Mappings tab in the Variables dropdown, select Custom Value. Click +Select Destination. In the Category section, select Tag Types. In the When mapped variables equals box, enter the path to the page where your version should be triggered (for example: /cart/thankyou ). In the Trigger tag type dropdown, select Display Network Conversion. Click +Add. Repeat steps 3 through 8 for similar mappings, such as Conversion Transaction ID and Conversion Value, by Selecting Display Network (YDN) Conversion from the Category section. To fire the conversion on multiple pages, either repeat these steps or create a vendor-specific variable (for example: yahoo_conversion_value ), which can be dynamically assigned via extensions. Click Done. Click Apply. ... View more

Learn about the new features and fixes released in January 2021. Tags New/Cool Stuff New marketplace tag: Exactag (Learn more) New marketplace tag: Yahoo! Japan Site General (Learn more) Introduced the beta version of the Google Analytics 4 (gtag.js) tag. (Learn more) Updated the Google Analytics (gtag.js) tag to add support for adding or removing multiple items from cart. Added Custom Dimension and Session ID support for the Decibel Insight tag. Updated URL configuration data overrides for the Piwik Pro tag. Added new tag configuration fields and data mappings for the Webtrakk tag, deprecated the heatmap and safetag parameters, and updated to version 4.5.3. Updated the Adobe Experience Platform Web SDK to Version 2.3.0. Updated the AT Internet tag to add support for privacy methods and updated the hosted template to include version 5.27.0 of the AT Internet library. Updated the Criteo OneTag to remove the tag tip indicating that the retailer visitor ID and email are required. Connectors New/Cool Stuff Updated the Google Customer Match connectors to add a clickwrap agreement and an addendum to the MSA for Google Match. Deprecated the Insightly connector and replaced with the Insightly CRM connector, which preserves previous functionality and also allows multiple tag names to be sent per API request. (Learn more) Fixes Added an authorization cache layer and updated the API authentication error messaging for the Salesforce (Classic SOAP) connectors. iQ Tag Management New/Cool Stuff Released new Getting Started guide for web developers. (Learn more) Fixes Corrected an issue where, when performing a global search for a load rule, the results did not direct users to the selected search item. Corrected an issue causing an unrecognized expression error when searching for data layer variables. Corrected an issue where custom environments were not displaying in the Publish Location filters drop-down list. Corrected an issue that allowed users to move extensions out of their scope restrictions. Corrected issue to ensure that, when viewing a profile with inherited tags and extensions, you can view and filter items by publish location in the profile to ensure a clear view of where tags and extensions are published and to what environment. Corrected an issue in Load Order Manager that erroneously displayed special characters in tag titles. Corrected issue in Load Order Manager where the Publish history displayed as empty when the user reordered items prior to saving and publishing. Customer Data Hub New/Cool Stuff New data source: Adobe Launch (Learn more) The number attribute now supports two numeric value types: decimal or integer. (Learn more) Removed the estimated time remaining progress bar from the Audience Sizing interface and changed the same-day date range query from midnight to 11:59 PM. Applied usability enhancements to the Audience Sizing interface and the timing of the tool tip display when the user hovers over the Venn diagram. Enhanced filtering functionality for unpublished feeds in Live Events to improve the ability to filter EventStream data for use in debugging tasks. Updated messaging on the Usage Reports screen to more accurately reflect billing for volume and usage. Applied error messaging enhancements to the search feature in the Manage Users screen. Fixes Corrected an issue in EventStream that caused the query string parameters from a Tealium Collect call to be ignored. Installations New/Cool Stuff Mobile Android Released Tealium for NativeScript, a set of cross-platform classes that interface with the native Tealium iOS and Android SDKs. (Learn more) Added the option to expire consent user preferences in Kotlin. (Learn more) Added crash reporting module for Kotlin. (Learn more) Added support for the Ad Identifier module in Kotlin. (Learn more) Added a public API method to reset and regenerate the Tealium Visitor ID in Kotlin. Enhanced the user experience when working with Tealium and Adobe visitor services. Added a module to interface with the Adobe visitor service from the Tealium SDK. Swift Added a public API method to reset and regenerate the Tealium Visitor ID in Swift. (Learn more) ... View more

Learn about the new features and fixes released in December 2020. Tags New/Cool Stuff New marketplace tag: Microsoft Clarity Updated the Movable Ink tag to allow users to input a subdomain. Added Tealium Trace ID support for the Krux Cookie Matching tag. (Learn more) Added event-specific parameters to the Kochava Remote Command tag. (Learn more) Added support for Version 5.1.1 of the Adobe Visitor API for JavaScript. (Learn more) Updated the Data Integration Library for Adobe Audience Manager to Version 9.5. (Learn more) Added support for Adobe Target, Version 2.3.3. (Learn more) Fixes Corrected an issue where viewTrigger calls were made too early for Adobe Target Versions 2.2.0 through Version 2.3. Connectors New/Cool Stuff New marketplace connector: Agillic Recipients (Learn more) New marketplace connector: Snapchat Audience Match (Learn more) The legacy Snapchat connector is supported but no longer available to new users in the connector marketplace. (Learn more) Fixes Corrected issue that reduced the size of field widths in mapping drop-down menus when using the Safari browser in connector configuration screens. Corrected issue with the HTTP API - Flattened data source to correctly view incoming events and enrichment data in Trace. Corrected issue with the Salesforce Standard Objects connector where required properties for standard objects displayed in an optional section. Updated the Braze connector to ensure that empty user attribute values are converted to null and and then removed from Braze user profile. iQ Tag Management New/Cool Stuff You can now click a library label in a profile to quickly switch to another library for which you have appropriate permissions. Consent Manager CCPA templates are now available in the Template Status Checker when CCPA is enabled and active. (Learn more) Applied enhancements to the manner in which templates are saved in profiles and libraries. (Learn more) Fixes Corrected an issue where some users were not able to view the "X" to quickly remove a tag from a tag-scoped extension. Corrected an issue where Consent Manager v3.0.8 did not check to ensure that Consent Manager was active in instances where partial consent was granted. Corrected a scrolling issue that occurred when viewing Load Order Manager screens. Customer Data Hub New/Cool Stuff Updated the Trace testing and inspecting tool to display date formats using international date formatting standards. (Learn more) Updated the Edit Users screens to offer an optional slide-out panel that walks the user through the workflow. (Learn more) Installations New/Cool Stuff Mobile Android Added module to interface with the Adobe visitor service from the Tealium SDK. Added the option to support consent expiration in Kotlin user preferences. Added ProGuard rules to new Kotlin library to minify and obfuscate specified classes. Added Crash Reporter module to Kotlin. Swift Added NativeScript integration support to Swift library for mobile SDKs. ... View more

This article describes how to set up the Braze connector in your Customer Data Hub account. In this article: Connector Actions Action Name AudienceStream EventStream Track User (Batch) ✓ ✓ Track User (Non-Batch) ✓ ✓ Delete User (Non-Batch) ✓ ✓ Update User Subscription Group Status (Non-Batch) ✓ ✗ Consent Categories Analytics Mobile Personalization 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 Endpoint Required: Select API endpoint for the instance your account is provisioned to. For more information, see Braze API Endpoints. API Key Required: Provide API key with permission enabled for "users.track" and "users.delete". For more information, see Braze App Group REST API Keys. For additional information see Braze Documentation Braze Technology Partners: Tealium. Action Settings - Parameters and Options This section describes how to set up parameters and options for each action. The Track User action contains the same functionality for both AudienceStream and EventStream. As a best practice, set the user attribute mappings for the AudienceStream action and the event and purchase mappings for the EventStream action. Action - Track User (Batch/Non-Batch) We recommend mapping as many ID parameters as possible. When an action triggers with multiple IDs mapped, the first non-blank value is selected based on the following priority order: External ID Braze ID Alias Name/Alias Label When For more information, see Braze API: User Track. Batch Limits This action uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following thresholds is met: Max number of requests: 75 Max time since oldest request: 10 minutes Max size of requests: 1 MB User ID Parameter Description External ID External ID of the user. Braze ID Braze ID of the user. User Alias Name The alias name of the user. When specifying a user alias, both Alias Name and Alias Label should be set. User Alias Label The alias label of the user. When specifying a user alias, both Alias Name and Alias Label should be set. User Attributes We recommend following the Braze best practice of only sending changed user attributes and avoiding sending unchanged attributes. You can do this using visit and visitor attribute enrichments and rules that recognize when an attribute has changed. For more information, see Enrichment Rules. Empty values are converted to null and removed from the Braze user profile. Parameter Description Country The country of the user. Current Location - Latitude The current latitude for the user to be tracked Current Location - Longitude The current longitude for the user. Date of First Session The date of the first session of the user. Date of Last Session The date of the last session of the user. Date of Birth The date of birth for the user. Email Address The email address for the user. Email Subscription Status The email subscription status for the user. Facebook The hash containing any of id (string), likes (array of strings), num_friends (integer). First Name The first name of the user. Gender The gender of the user. "M", "F", "O" (other), "N" (not applicable), "P" (prefer not to say) or nil (unknown).. Home City The home city for the user. Image URL The URL of an image to be associated with user profile. Language The language preference of the user in ISO-639-1 format. See list of accepted language codes. Last Name The last name of the user. Marked Email As Spam At Date at which the user’s email was marked as spam. Appears in ISO 8601 format or in yyyy-MM-dd’T’HH:mm:ss:SSSZ format. Phone Number The telephone number of the user. Push Subscription Status Set to "opt_in" (explicitly registered to receive push messages), “unsubscribed” (explicitly opted out of push messages), or “subscribed” (neither opted in nor out). Push Tokens ID Array An array of app ID's to use with push token migration. For more information, see Braze API: Migration via API. Push Tokens Array An array of push tokens. Push Tokens Device ID Array An array of device ID's to use with push token migration. For more information, see Braze API: Migration via API. Time Zone The time zone name from IANA Time Zone Database . Example: "America/New_York" or "Eastern Time (US & Canada)". Invalid time zone values are ignored. Twitter Hash containing any of ID (integer), screen name (string, Twitter handle), followers count (integer), friends count (integer), statuses count (integer). Update Existing Only (Users) Set to true or false. If no user value exists, one is created by default. If set to true, only existing users are updated and new users are not created. Modify User Attributes Modify numeric user attributes with the following operations: Increment (accepts positive or negative values) Decrement Add Modify array attributes by adding or removing values from existing arrays. Events An event name must be mapped to Name. Map array attributes of equal length to send multiple events. Single value attributes can be used and will apply to each event. Parameter Description App ID The App Identifier API key or app_id associated with a specific app in your app group. For more information, see Braze API: App Identifier API key. Name (Required) The name of the event. Time The time of the event. Automatically set to "now" unless a value is mapped. Update Existing Only (Events) Set to true or false. If no event value exists, one is created by default. If set to true, only existing events are updated and no new events are created Event Template Variables Provide template variables as data input (see: template variables). Name nested template variables with the dot notation (Example: items.name ). Nested template variables are typically built from data layer list attributes. Event Templates Provide templates to be referenced in Body Data (see: Trimou templating engine). Templates are injected by name with double curly braces into supported fields (Example: {{SomeTemplateName}} ). Purchases To map data for purchases, you must map the values for Product ID, Currency, and Price. Map array attributes of equal length to send multiple events. Single value attributes can be used and will apply to each event. The following code sample shows a Braze best practice example for receiving a single event containing purchases for multiple products: // event to Tealium: { [...] "tealium_event": "purchase", "product_name": ["Backpack", "Pencil", "Notebook"], "product_quantity": [1, 5, 3], "product_category": ["Travel", "Office", "Office"], "product_price": [39.95, 1.99, 3.99], "order_currency": "USD" } Map the corresponding product array attributes to the Braze parameters: product_name > Product ID product_quantity > Quantity product_price > Price The results of this example sends the following purchases object to Braze, representing each product accordingly: // payload to Braze via Tealium Connector: { "purchases": [ { "external_id" : "user1", "app_id" : "11ae5b4b-2445-4440-a04f-bf537764c9ad", "product_id" : "Backpack", "currency" : "USD", "price" : 39.95, "time" : "2013-07-16T19:20:30+01:00", }, { "external_id" : "user1", "app_id" : "11ae5b4b-2445-4440-a04f-bf537764c9ad", "product_id" : "Pencil", "currency" : "USD", "price" : 1.99, "time" : "2013-07-16T19:20:30+01:00", }, { "external_id" : "user1", "app_id" : "11ae5b4b-2445-4440-a04f-bf537764c9ad", "product_id" : "Backpack", "currency" : "USD", "price" : 3.99, "time" : "2013-07-16T19:20:30+01:00", } ] } Parameter Description App ID The Event Application ID. Product ID An array of product IDs. Required for purchase events. Currency The ISO 4217 alphabetic currency code of the purchase. Required for purchase events. Price An array of product prices. Required for purchase events. Quantity An array of product quantities. Purchase Time The time of the purchase in ISO 8601 format. Automatically set to "now" unless explicitly mapped. Update Existing Only (Purchases) (Optional) Values are true or false. By defauilt, if a purchase value exists, one is created by default. If set to true, only existing purchases are updated and no new purchases are created. Purchase Template Variables Provide template variables as data input (see: template variables). Name nested template variables with the dot notation (Example: items.name ). Nested template variables are typically built from data layer list attributes. Purchase Templates Define a template to send nested objects. When a template is defined, the mappings from the Purchases section are ignored. Provide templates to be referenced in Body Data (see: Trimou templating engine). Templates are injected by name with double curly braces into supported fields (Example: {{SomeTemplateName}} ). Action - Delete User (Non-Batch) Only one of External ID, Braze ID, and User Alias is needed in each action. However, we recommend mapping as many attributes as you can. When IDs are mapped, the first non-blank value is selected based on the following priority order: External ID Braze ID Alias Name Alias Label For more information, see Braze API: User Delete Endpoint. Parameters Parameter Description External ID External ID of the user to delete. Braze ID Braze ID of the user to delete. User Alias Name The alias name of the user to be deleted. When specifying a user alias, Alias Name and Alias Label should both be set. User Alias Label The alias label of the user to be deleted. When specifying a user alias, Alias Name and Alias Label should both be set. Action - Update User Subscription Group Status (Non-Batch) For more information, see Braze API: Subscription Groups Endpoints. Parameters Parameter Description Group Type (Required) The subscription group type to manage (SMS or EMAIL). Update Type (Required) The subscription state to set (SUBSCRIBE or UNSUBSCRIBE). Subscription Group ID (Required) The ID of the subscription group. External ID The external ID of the user or users. Email (Used with EMAIL subscription groups.) The email address of the user. Email is required if External ID is not set. Phone (Used with SMS subscription groups.) The phone number in E.164 format. Example: +1415555371 Phone is required if External ID is not set. Frequently Asked Questions How does this connector work with other Braze integrations? In addition to the Track User API, Braze has additional data collection methods, both of which support mapping of user attributes in Braze. Tealium supports Braze SDKs for Web and Native Mobile in the following two independent, but similar integrations: Braze Web SDK Tag Setup, Braze Initial SDK Setup Tealium Remote Command for Braze on Android and iOS/Swift (Learn more) These integrations are alternative methods used for Braze to collect user behavior data that is similar to the data collected in the event and purchase actions of the connector. ... View more

Learn about the new features and fixes released in November 2020. Tags New/Cool Stuff Update the Criteo OneTag to support the viewItem and viewList events. (Learn more) Updated the Adobe AppMeasurement for JavaScript tag to support Version 2.22. (Learn more) Fixes Fixed an issue in the Google Analytics (gtag.js) tag that prevented the settings for Allow Advertising Features and Advertising Personalization to be passed correctly. Fixed an issue with the Facebook Pixel tag that prevented additional pixel IDs from being initialized. Fixed an issue with the Facebook Pixel tag that caused duplicate purchase events to occur when the Purchase event was mapped and the Order ID was populated. Connectors New/Cool Stuff New marketplace connector: Salesforce Standard Objects (Learn more) The CheetahMail connector was rebranded to Cheetah Digital and the vendor links have been updated. (Learn more) Fixes Corrected the Responsys REST API connector to include hashed email lookup for custom event actions. Updated the response timeout for the beta version of the Responsys Marketing Cloud connector. (Learn more ) iQ Tag Management New/Cool Stuff Users can now search for a data layer variable from the tags list view page to view a list of all tags with the variable mapped to it. When filtering extensions, active filter labels now display with the option to remove them. Fixes Fixed an issue in Web Companion loaded that caused it to make an HTTP request on HTTPS pages. Fixed an issue on the Consent Management dashboard that caused a partial display of the load rules. Fixed an issue with filtering on the extensions screen that caused deprecated extensions to be incorrectly displayed. Fix an issue with the JavaScript Code extension in libraries that caused it to display as "Ready to Publish" when it had already been successfully published. Fixed the terms used for scopes across all screens for naming consistency. Customer Data Hub New/Cool Stuff File Import data sources now display the file prefix on the Service Configuration tab. Trace audience counters now keep individual running counts of audiences that have joined or left throughout a session and the tooltips are now updated to display a historical log of the audiences that were joined or left. Fixes The Slack incoming webhook (data source) has been deprecated. Installations New/Cool Stuff Mobile Android Added support to track and measure the duration of specific in-app journeys for timed events in Kotlin. Added "model" as a new device variable in the Kotlin library. Added support to override the Kotlin collect dispatcher URL and Batch Event URL. Applied Firebase updates to use the latest Firebase SDK and Kotlin 1.0.0, including support for JSON remote commands. Applied Facebook updates to use latest Facebook SDK and Kotlin 1.0.0, including support for JSON remote commands. Applied Braze updates to use latest Braze SDK and Kotlin 1.0.0, including support for JSON remote commands. Swift Added support to track and measure the duration of specific in-app journeys for timed events in Swift. Fixes Mobile Swift Corrected issue causing the Swift Collect dispatcher custom URL to not respect a full URL path. ... View more

This article describes data compliance as it pertains to General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA) and how data is used, shared, and stored when using Tealium Predict. In this article: Table of Contents Placeholder CCPA and GDPR Compliance Tealium Predict uses the same data as the Tealium AudienceStream product. Your data is fully protected and is both GDPR and CCPA compliant, including advanced considerations such as opting in or out of automatic profiling. For detailed information about Tealium Consent Management compliance and Consent Management tools, see Consent Management. Data Collection The models you create are processed at the end of the session aggregation stage for every visitor at the end of each visit. This is the stage at which data used by Tealium Predict is collected. After collecting the data for a model, data is categorized as "per Visit" vs. "per Visitor" and a prediction percentage value between zero (0) and one (1) is assigned from this score. Data Usage, Sharing, and Access Controls All data related to Tealium Predict remains within the Tealium system and infrastructure, and is subject to the same Tealium security and privacy protocols. Data usage is consistent with your contracted terms for Tealium AudienceStream. Your data is only used for Tealium features. Data is not shared or sold, does not cross regions, and is protected by Tealium security and privacy protocols. Visitor Data Usage Model training in Tealium Predict is a continual and repeated process. For that reason, visitor data is not purged by default. There is always a need for new versions of visitor data to be trained and the data must therefore be available to retrain. After a successful model is deployed, the model degrades over time and must be refreshed with current visitor data. For information about purging specific visitor data, contact your account manager. Access Controls General use of Tealium Predict does not require a third party or other entity to access or view your data. For Tealium Predict packaging and services that include assistance with data readiness, the Tealium internal data science team has access to your models and training datasets to help ensure the quality of your machine learning models. Data Storage Tealium Predict data is stored using S3 Server-Side Encryption (SSE) and strict Identity and Access Management (IAM) policies to ensure that only necessary internal services can access the data. The product is implemented on each of the Tealium regional infrastructures to ensure that none of your data changes regions during use. For example, if your Tealium account uses an Australia-based infrastructure, your usage of Tealium Predict occurs on that same infrastructure to ensure security. Data Retention The length of time set to retain your data is up to you. You can set the retention and storage period when signing up to use the Tealium Predict product. Contact your account manager if you have concerns about data retention periods. ... 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: Stirista Visitor ID Graph (VIG) (Learn more) New marketplace tag: Sovendus (Learn more) New marketplace tag: Xandr Universal Pixel (Learn more) Updated the Facebook Pixel tag for additional uniqueness in the generation of the Facebook Event ID, added unique Event ID keys for use when multiple tags are fired at the same time, and added an Advanced Matching parameter for External IDs. (Learn more) Updated the Econda Monitor tag to support Econda Monitor Tag Tracking Library, Version 4. (Learn more) Applied several event support and mapping enhancements to the Snap Pixel tag. (Learn more) Updated Tooltips for the CJ Affliate tag (Learn more) Updated event action handling for the Bing UET tag. (Learn more) The Tealium Collect tag is now updated to remove support for the deprecated version 1.1 of the IAB Transparency and Consent Framework. (Learn more) Cookie Matching tags no longer support the deprecated version 1.1 of the IAB Transparency and Consent Framework. (Learn more) Connectors New/Cool Stuff Updated the Salesforce Journey Builder connector to fetch all event definitions by paging through all available results. (Learn more) Added batch support for the Webhook 2-Legged OAuth2 and 3-Legged OAuth2 connectors. (Learn more) Updated the Salesforce Email Studio connector to provide more helpful error messaging with the ability to drill down into listed issues for additional details. (Learn more) Added validation checking and error messaging when the required User/Device ID mapping field for the DCM Floodlight connector is empty. (Learn more) Updated the Salesforce Email Studio connector to remove the Upsert Record action and added the Record Lookup field for adding, deleting, and updating mapped data. (Learn more) The Userlist.io connector is rebranded and available as the Userlist connector. (Learn more) The domailer connector is rebranded and available as the dotdigital connector. (Learn more) Customer parameters, payment type, and order rebate for the Impact Radius Conversions connector are now optional parameters and no longer required. (Learn more) Additional mapping fields are now available when using the Update Lead action for the Salesforce AudienceStream connector. (Learn more) Updated the vendor links for the TUNE In-App Events connector and updated the Consent Category to "Mobile". (Learn more) Updated the "Add to Action List and Trigger Campaign" action for the Selligent connector. (Learn more) Updated the vendor links for the Leanplum connector and updated the Track Event action to support AudienceStream. (Learn more) Updated the Facebook Conversions connector to support the new version of Event ID generation. (Learn more) Fixes The Adition connector is no longer available from the connector marketplace. The beta release for the TUNE In-App Push is no longer available in Experiments or in the connector marketplace. iQ Tag Management New/Cool Stuff Introduced the China CDN Deployment extension to facilitate the usage of China CDN by detecting a users location and dynamically serving that user from the appropriate CDN. (Learn more) Enhanced search functionality for extensions to hide irrelevant results from results view. (Learn more) Enhanced functionality to allow users to filter the extensions list view by specific tags that are scoped to extensions. (Learn more) Reordered the columns in the beta experiment version of Load Order Manager to be consistent with Tags and Extensions list views. (Learn more) The filter drop-down list on the Tags and Extensions tab now highlights as the user scrolls and allows the user to select a filter by clicking on the line as an alternative to checking the checkbox. (Learn more) Enhanced the extensions list view search functionality to allow users to search by tags that are scoped to an extension. (Learn more) Fixes Corrected an issue that occurred when adding a tag using "Detect Tag from Code" and a match was not detected, the "Add to Profile" button was hidden from view. (Learn more) Corrected an issue with the Publish Location filter on the Tags and Extensions screens where multiple selections were incorrectly applied using AND logic instead of OR logic. (Learn more) Corrected a visual issue where load rule names were not updated in the accordion headers on the Tag list view. (Learn more) Corrected an issue where users were not able to search for text inside JavaScript extensions from the extensions list view (Learn more) Corrected an issue where variables and open text fields did not return results when searching for an extension. (Learn more) Corrected an issue that required "Manage Account" instead of "Manage Profiles" permission to manage libraries. (Learn more) Corrected the following issues encountered with the beta version of Load Order Manager enabled in experiments (Learn more): Changing the scope of a tag or extension did not mark it as edited in the main view. Error messages displayed disproportionately. Creating a tag-scoped extension and not applying any tags prevented the extension from being viewable inside Load Order Manager. Warning messages in Load Order Manager were not highlighted in red as expected for new items. Customer Data Hub New/Cool Stuff Added a documentation link to the interface for the Visitor Lookup Tool to provide additional details about how to use the Visitor Lookup API with tokens. (Learn more) Fixes Corrected the "Enable Tealium Collect" warning confirmation pop-up in the JavaScript data source setup screen. (Learn more) Updated the File Import data source mapping feature to display only date attributes for columns marked as dates. (Learn more) Corrected an issue where editing the title of an event attribute used in a rule caused problems with the associated rule. (Learn more) Corrected an issue where the server-side browser tab for new users was labeled "Undefined" at profile activation. The trace overview panel now correctly tallies the counts of every audience the visitor has joined and left, regardless of whether the same audience has been joined and left within the same session, which was previously not counted. (Learn more) Corrected an issue where some users were unable to use the shortcut to navigate from a job to an associated connector and were instead redirected to the main connectors screen. (Learn more) Corrected issue that erroneously triggered a tag generation failure message when publishing a JavaScript data source (Learn more) Corrected an issue in the interface to display the correct status (ON or OFF toggle) in the list of connectors activated for an audience. (Learn more) Installations New/Cool Stuff Mobile For the Android SDK Remote Commands, the custom remote command template now applies lowercase to command IDs before they are sent. Applied Xamarin iOS upgrade (UIWebView) and upgraded Tealium-Xamarin to use the latest Tealium iOS library. Updated the Tealium Remote Commands 1.0.0 library to provide backwards compatibility for existing remote commands to use the older Java Android library as well as support the new Kotlin Android library. Added support for attribution tracking with SDKAdNetwork in iOS 14. Applied updates to enable use of the latest Facebook SDK and latest Swift 2.1.0 library, including support for JSON remote commands. Updated the Usabilla Android remote command to use the latest remote commands 1.0.0 dependency and updated the sample app to use the JSON remote command feature. Applied updates to use the latest Usabilla SDK and Tealium-Swift 2.1.0, including support for JSON remote commands. Applied updates to use the latest AppsFlyer SDK and the latest Kotlin 1.0.0 library, including support for JSON remote commands. Updated the custom JSON remote command tool to export customers' mobile remote command tag configurations to JSON (can also be used by the new JSON remote command feature in Kotlin and Swift). Updated the Contentsquare Android remote command to use the latest remote commands 1.0.0 dependency and latest Contentsquare SDK v3.2 and updated sample app updated to use the JSON remote command feature. Applied updates to use latest Contentsquare SDK and latest Swift 2.1.0 library, including support for JSON remote commands. Server Updated Objective-C to Swift Migrator Tool for C-Platform frameworks. Fixes Mobile Corrected issue where connectivity checks caused crashes on Android 6.1 and below. Corrected issue causing writes to empty strings before deleting files in Tealium Android. Corrected issue where visitorId was nil in the latest version of Swift. ... View more

This article describes how to set up the Xandr Universal Pixel tag in your Tealium iQ Tag Management account. In this article: Table of Contents Placeholder Tag Tips You may enter multiple Pixel IDs in a comma-separated list. Purchase tracking occurs automatically when an order ID is populated. To disable automatic Purchase tracking, toggle the automatic_purchase_tracking destination via mappings. PageView tracking occurs automatically. To disable automatic PageView tracking, toggle the automatic_pageview_tracking destination via mappings. By default the PageView event executes without additional data. If you want to pass data with the PageView event, you must map the desired variables in the Event-specific Parameters tab of the mapping toolbox. Supports these E-Commerce extension parameters: Order ID ( _corder ) List of Product IDs ( _cprod ) List of Product Names ( _cprodname ) List of Product Categories ( _ccat ) Tag Configuration First, go to Tealium's tag marketplace and add the Xandr Universal Pixel tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Pixel ID Enter your Xandr Universal Pixel ID. You may enter multiple IDs in a comma-separated list. 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: Tag Configurations Variable Description Universal Pixel ID (pixel_id) [String] Toggle Automatic PageView Tracking (auto_pageview_tracking) [Boolean,String] Toggle Automatic Purchase Tracking (auto_purchase_tracking) [Boolean,String] Base URL (base_url) [String] E-Commerce Variable Description List of Item Categories (item_type) (Overrides _ccat) [Array] List of Item IDs (item_id) (Overrides _cprod) [Array] List of Item Names (item_name) (Overrides _cprodname) [Array] Events Variable Description AddPaymentInfo AddPaymentInfo AddToCart AddToCart InitiateCheckout InitiateCheckout ItemView ItemView LandingPage LandingPage Lead Lead PageView PageView Purchase Purchase Custom Custom Event-specific Parameters Variable Description Item Type (item_type) item_type Item ID (item_id) item_id Item Name (item_name) item_name Custom Parameter Custom_Parameter AddPaymentInfo AddPaymentInfo AddToCart AddToCart InitiateCheckout InitiateCheckout ItemView ItemView LandingPage LandingPage Lead Lead Purchase Purchase Custom Event Custom_Event ... View more

This article describes how to set up the Sovendus tag in your Tealium iQ Tag Management account.. In this article: Table of Contents Placeholder Tag Tips Supports these E-commerce extension parameters: Order ID ( _corder ) Order Subtotal _csubtotal ) Currency ( _ccurrency ) Promo Code ( _cpromo ) Customer Zip ( _czip ) Tag Configuration First, go to Tealium's tag marketplace and add the Sovendus tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Traffic Source Number Enables Sovendus to allocate your shop in their system. Traffic Medium Number If you are using several traffic media enter the active traffic medium here. Iframe Container ID Determines at which position on the page the generated iframe should be implemented. 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: Iframe Configurations Variable Description Traffic Source Number (trafficSourceNumber) Traffic Medium Number (trafficMediumNumber) Iframe Container ID (iframeContainerId) Session ID (sessionId) Timestamp (timestamp) Order ID (orderId) (Overrides _corder) [String] Order Value (orderValue) (Overrides _csubtotal) [String] Order Currency (orderCurrency) (Overrides _ccurrency) [String] Used Coupon Code (usedCouponCode) (Overrides _cpromo) [String] Consumer Data Variable Description Consumer Salutation (consumerSalutation) Consumer First Name (consumerFirstName) Consumer Last Name (consumerLastName) Consumer Email (consumerEmail) Consumer Zipcode (consumerZipcode) (Overrides _czip) [String] ... View more

This article describes how to set up the Stirista Vistitor ID Graph (VIG) tag in your Tealium iQ Tag Management account. In this article: Table of Contents Placeholder Tag Configuration First, go to Tealium's tag marketplace and add the Stirista VIG tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Field i An alphanumeric value found in your generated code snippet. Example: i=000a000b123c Field s An alphanumeric value found in your generated code snippet. Example: s=000a000b123c 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 i Must be mapped. t Must be mapped. p Must be mapped. s Must be mapped. r Must be mapped. u Must be mapped. ... View more

The Visitor Privacy API (formerly Visitor Lookup API) is used to query visitor profile records from the Customer Data Hub. This API allows you to retrieve known data about a specific visitor, delete a visitor record, and check the status of a delete request. These requests can also be used in support of General Data Protection Regulation (GDPR) compliance to satisfy the requirement of responding to data subject access requests. In this article: How It Works Server-side Editor permission within CDH permissions is required for this API. Visitor lookups are based on a Visitor ID attribute from your account. Limits and Intended Use The Visitor Privacy API is intended to satisfy regulatory requirements such as GDPR and CCPA and is not designed for high volume usage. Tealium recommends that you have a maximum of one (1) connection open to this API at any given time. Contact your account manager if you estimate that your usage will exceed 1000 API calls per day. Permission Requirements Server-side Editor permission Required Parameters attributeId – The numeric ID of this attribute. attributeValue – The value to search for. Authentication The bearer token is used to authenticate all API calls and not the API key. The API key is only used in the authentication call. See the Getting Started guide to learn about generating a bearer token from the API key. Example For a Visitor ID attribute named Email Address with an attribute ID of 86, the attributeID would be used as a parameter to the API calls, as shown in the following example: attributeId=86 attributeValue=user@example.com Visitor Fields Visitors are returned as JSON objects that contain the following fields: Object Name Type Description transaction_id string A unique ID returned in every response for logging purposes and the status API. live Boolean Set to True if the visitor is currently in a live session. visitor object The visitor object with sub-objects for each of the attribute data types: Visitor IDs secondary_ids : { } Numbers/Array of Numbers "metrics" : { } "metric_lists" : { } Strings/Array of Strings/Set of Strings "properties" : { } "property_lists" : { } "property_sets" : { } Booleans/Array of Booleans "flags" : { } "flag_lists" : { } Dates "dates" : { } Badges "badges" : { } Tallies "metric_sets" : { } Example { "transaction_id": "a1b23bcb4b5b56", "live": false, "visitor": { "metrics": { "Weeks since first visit": 0.14, "Total referred visits": 11, "Lifetime visit count": 12, "Average visit duration in minutes": 0.36, "Lifetime event count": 35, "Total time spent on site in minutes": 4.27, "Total direct visits": 1 }, "dates": { "Last visit": 1521217490000, "last_visit_start_ts": 1521217490000, "First visit": 1521134626000 }, "properties": { "Lifetime browser versions used (favorite)": "Chrome", "Lifetime browser types used (favorite)": "Chrome", "profile": "main", "Lifetime devices used (favorite)": "Mac desktop", "Lifetime platforms used (favorite)": "browser", "Last event URL": "http://www.tealium.com/", "account": "tealium", "Lifetime operating systems used (favorite)": "Mac OS X" }, "flags": { "Returning visitor": true }, "badges": ["Unbadged"], "metric_sets": { "Lifetime operating systems used": { "Mac OS X": 12 }, "Lifetime devices used": { "Mac desktop": 12 }, "Lifetime browser versions used": { "Chrome": 12 }, "Lifetime browser types used": { "Chrome": 12 }, "Lifetime platforms used": { "browser": 12 } } } } GET Visitor Use the following GET command to retrieve a visitor record: GET /v2/visitor/accounts/{account}/profiles/{profile}?attributeId={attributeId}&attributeValue={attributeValue}&prettyName={prettyName} This command uses the following parameters: attributeId The numeric ID representing a Visitor ID attribute from your account. attributeValue The value to look up. Values containing special characters must be URL encoded. prettyName A Boolean value indicating how attribute keys display in the response: True – Attributes display as user-friendly names, such as "Lifetime Order Value". False – Attributes display as numeric ID's, such as "28471". Example cURL Request curl -H 'Authorization: Bearer {token}' \ -G \ 'https://api.tealiumiq.com/v2/visitor/accounts/my_account/profiles/main' \ --data-urlencode 'attributeId=86' \ --data-urlencode 'attributeValue=user@example.com' \ --data 'prettyName=true' Example Response See the example visitor object for the format of the response. Error Messages Potential error messages for this task are: Error Message Description 404 Not Found { "returnCode" : 1240, "message" : "Account was not found" } { "returnCode" : 1250, "message" : "Profile was not found" } DELETE Visitor Consider the following prior to deleting one or more visitor records: Requests to delete visitor records result in the deletion of all data associated to the visitor ID value, including stitched visitor records. Delete requests are queued for processing and may take up to 1-4 days to complete. If a visitor replaces or has been replaced by another visitor, all visitors that have been stitched are deleted. The parameters to the DELETE command must be passed as URL-encoded form fields using the content-type " application/x-www-form-urlencoded ", and not as query string parameters. Use the following DELETE command to delete a visitor record: DELETE /v2/visitor/accounts/{account}/profiles/{profile} attributeID={value} attributeValue={value} This command uses the following parameters: attributeId The numeric ID representing a Visitor ID attribute from your account. attributeValue The value to look up. Example cURL Request curl -H 'Authorization: Bearer {token}' \ -X DELETE \ 'https://api.tealiumiq.com/v2/visitor/accounts/my_account/profiles/main' \ --data-urlencode "attributeId=86" --data-urlencode "attributeValue=user@example.com" Example Response The response to a delete request includes a transaction_id and a status. The transaction_id is used in the GET transactions call to check the status of a previous request. The following status strings are possible: PENDING, SUCCESS, or FAILED. A successful response displays the 202 Accepted message with a transactionId value. If a request with the exact same account , profile , attributeId , and attributeValue already exists with a transaction status of PENDING, the existing transaction ID is returned, as follows: { "transactionId" : "{transactionId1}" } Error Messages Potential error messages for this task are: Error Message Description 404 Not Found { "returnCode" : 1240, "message" : "Account was not found" } { "returnCode" : 1250, "message" : "Profile was not found" } GET Transaction A transaction refers to any GET visitor or DELETE visitor request. DELETE visitor requests are queued for later processing, which makes the transaction_id the unique record for that request and ID to be used when checking the processing status. Use the following GET command to check the status of a transaction: GET /v2/visitor/accounts/{account}/profiles/{profile}/transactions/{transaction_id} Example cURL Request See the Getting Started guide to learn about generating a bearer token from the API key. The bearer token is used in the API calls, rather than the API key. curl -H 'Authorization: Bearer {token}' \ https://api.tealiumiq.com/v2/visitor/accounts/my_account/profiles/main/transactions/0123456789 Example Response The response contains an object with one key/value pair where the key is a transaction_id and the value is one of the following status strings: PENDING, SUCCESS, or FAILED. { "0123456789" : "SUCCESS" } GET Visitor ID Attributes Use the following GET command to retrieve a list of the Visitor ID attributes available in your account: GET /v2/visitor/accounts/{account}/profiles/{profile}/ids Example cURL Request curl -H 'Authorization: Bearer {token}' \ https://api.tealiumiq.com/v2/visitor/accounts/my_account/profiles/main/ids Example Response The response for this command is an object of key/value pairs representing the numeric ID and name of the Visitor ID attribute. { "43" : "Email Address", "57" : "Tax ID Number" }   ... View more

This article describes how to set up the Leanplum connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Set User Attributes ✓ ✓ Send Message ✓ ✓ 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: 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 - Set User Attributes Parameters Parameter Description App ID The application ID. To find your application ID: Select your application in the navigation column, and click Edit Apps. Under Keys, click Show. For more information on this endpoint, see: https://docs.leanplum.com/reference#post_api-action-setuserattributes. Client Key The Production key for your Leanplum application. API Version The version of the Leanplum API to use. At time of publishing this version, the most recent version is 1.0.6. User ID The current user ID. Set to an email address or what you use at your company for user IDs. Leave blank to use the device ID. For more information, see: https://docs.leanplum.com/reference#user-and-device-tracking. Create Disposition The policy that determines whether users are created by the API. The default value for this method is CreateIfNeeded. Possible values are: CreateIfNeeded Creates a user with the given IDs if one does not already exist. CreateNever Requires that the user already exists, otherwise the API call is skipped and a warning will be returned. Dev Mode Whether the user is in Development mode (the caller is a developer and not a user). Important for reporting purposes. Value options are true or false . Default Value: false . User Attributes A map of user attributes as key-value pairs. Each key must be a string. Attributes are saved across sessions. Only supplied attributes are updated. If you omit an existing attribute, it will be preserved. Example: {"gender":"F","age":21} . User Attribute Values To Add A map of values to add to existing user attribute sets. For example, supply {"Interests":"Sports"} to add Sports to the existing set of interests. Action - Send Message Parameters Parameter Description App ID The application ID. To find your application ID: Select your application in the navigation column, and click Edit Apps. Under Keys, click Show. For more information on this endpoint, visit: https://docs.leanplum.com/reference#post_api-action-setuserattributes. Client Key The Production key for your Leanplum App. API Version The version of the Leanplum API to use. At time of publishing this version, the most recent version is 1.0.6. User ID The current user ID. Set to an email address, or what you use at your company for user IDs. Leave blank to use the device ID. For more information, see: https://docs.leanplum.com/reference#user-and-device-tracking. Message ID The ID of the message, found in the URL when viewing a message. For example: www.leanplum.com/dashboard#/{APP_ID}/messaging/{MESSAGE_ID} . For more information on this endpoint, see: https://docs.leanplum.com/reference#post_api-action-sendmessage. Dev Mode Whether the user is in Development mode (the caller is a developer and not a user). Important for reporting purposes. Value options are true or false . Default Value: false . Device ID A unique ID for the device targeted by the call. A deviceID and/or a userID is required. For more information, see: https://docs.leanplum.com/reference#user-and-device-tracking. Create Disposition The policy that determines whether users are created by the API. The default value for this method is CreateIfNeeded. Possible values are: CreateIfNeeded Creates a user with the given IDs if one does not already exist. CreateNever Requires that the user already exists, otherwise the API call is skipped and a warning will be returned. Force Whether to send the message regardless of whether the user meets the targeting criteria. Value options are true or false . Default Value: false . Values A JSON object of key-value pairs to override Jinja values in the message. Action - Track Event Parameters Parameter Description App ID To find your application ID: Select your application in the navigation column, and click Edit Apps. Under Keys, click Show. For more information, see: https://docs.leanplum.com/reference#post_api-action-setuserattributes. Client Key The Production key for your Leanplum application. API Version The version of the Leanplum API to use. At time of publishing this version, the most recent version is 1.0.6. User ID The current user ID. Set to an email address, or what you use at your company for user IDs. Leave blank to use the device ID. For more information, see: https://docs.leanplum.com/reference#user-and-device-tracking. Event The name of the event. Use "Purchase" to identify a monetization event, with the event value being the revenue. You can change the default monetization event name in Analytics by going to the metric chooser and clicking the Monetization metric category. For more information, see: https://docs.leanplum.com/reference#post_api-action-track Device ID A unique ID for the device targeted by the call. A Device ID and/or a User ID is required. For more information, see: https://docs.leanplum.com/reference#user-and-device-tracking. Dev Mode Whether the user is in Development mode (the caller is a developer and not a user). Important for reporting purposes. Value options are true or false . Default Value: false . Create Disposition The policy that determines whether users are created by the API. The default value for this method is CreateIfNeeded. Possible values are: CreateIfNeeded Creates a user with the given IDs if one does not already exist. CreateNever Requires that the user already exists, otherwise the API call is skipped and a warning will be returned. Value The event value. Example: For a purchase event, this would be the purchase price. Currency Code The ISO 4217 currency code associated with value. Leanplum automatically converts the value into your preferred currency, while retaining the original price and currency code as event parameters localCurrency and localPrice . Currency conversion rates are updated every hour. Info Any information attached to the event. Time Option to provide the Unix timestamp for when the event occurred, which may be different from the current time. Parameters Parameters as key-value pairs. Each key must be a string, and up to 50 parameters may be set. Message ID The message ID this event is associated with. Set this to track a user's interaction with a message. To track a message Send or a View, set the event argument to an empty string. For other interactions, set the event argument to the type of action. Example values: Open , Cancel , Accept . The Leanplum SDK does this automatically, so this should be used for advanced use cases only. Disposition Determines how tracked events affect sessions and user activity. If present, the disposition must have one of the following values: active This is the default value. Used for events reflect user activity. Active events should mark the user as active and should be tracked within a session. Replaces the deprecated option allowOffline: false . passive Used for events that do not correspond to user activity. These events do not need to occur within a session and do not mark a user as active. Example: Sending a user a message would be tracked passively, since it affects a user, but does not represent user activity. Replaces the deprecated option allowOffline: true . requireActive Used for events that must only be tracked within a session. These events are rejected and return a warning response with ignored: true if the user does not have an active session. Clients should detect the warning by the ignored field, as warning messages may change. ... View more

This article describes different ways to monitor the health of your deployed model. In this article: The following sections provide explanations of the metrics and ratings available when using Tealium Predict ML that help you understand the quality of your deployed models. For information about viewing trained model health, see Evaluating Trained Models. Deployed Model Health The Model Dashboard lists each deployed model in a list. Each row contains a snapshot of the prediction results for that model. To access the model dashboard view, navigate to Predict > Model Dashboard > Deployed Models. A model overview may display the following information about a model: The recall of a model with indicators that show whether this metric has increased or decreased. Strength ratings are recalculated automatically and the sparkline graph reflects live performance metrics. A sparkline graph depicting the general performance trend of the model. The version of the deployed model. Evaluating the Strength of Deployed Models The model strength ratings provide a label for the quality (strength) of a version. There are two types of strength ratings, deployed and training. The deployed strength is an ongoing (dynamic) rating for each deployed model. The training strength is a static ratings for each trained version. For more information about strength scores, see Model Scores and Ratings. Live Model Performance Details The deployed live performance score allows you to understand the ongoing quality of your model and know when it has degraded, which inevitably happens over time. In Tealium Predict, the recall, precision, and F1 score are automatically recalculated daily for deployed models using the most recent time window available. This window is defined in the Prediction Timeframe, which equates to the number of days specified in the model as "in the next x days". For the daily recalculation to begin, the model must be deployed for the initial Prediction Timeframe so that actual true/false results are known and can be used in the calculation. The calculation window then moves forward one day, every day. On the Live Performance screen, the daily recall, precision, and F1 scores show you changes in model health over time. The Live Performance window also allows you to explore the Prediction Value over the Prediction Timeframe using the Prediction Distribution chart. The Prediction Value represents the likelihood that the target attribute results are set to True during the Visitor's next Visit within the Prediction Timeframe. In the Prediction Distribution chart, the y-axis is the number of times the Target Attribute behavior was either True or False within the prediction timeframe, while the x-axis is the prediction value. Ideal results demonstrate True counts falling in the upper range of the prediction value (for example, above 0.5) and False counts falling in the lower range of the prediction value (for example, below 0.5). If the shape of the prediction distribution is similar to the probability distribution from the training model, it is an indicator of strong model health over time.  You can use live performance prediction distribution to help you decide thresholds for audience creation. For example, the Probability Distribution chart above shows most of the actual True counts in the range 0.75 to 1, so you can use 0.75 as a threshold to define an audience that are going to have a high likelihood of purchasing in the next two days. Similarly, you can define an audience below the 0.4 threshold as being less likely to purchase in the next two days. Degradation and Retraining All machine learning models naturally degrade in quality over time, just as the real world continually changes. Models eventually stagnate and degrade in their ability to make accurate predictions about the changing environment. Therefore, models must be retrained periodically to ensure that they are based on the most current dataset available. ... 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 The Cheetah Mail tag is rebranded and now available as Cheetah Digital in the tag marketplace. (Learn More) Fixes Updated the iAdvize tag template to only declare an empty idzTrans object when an order ID is defined. (Learn more) Connectors New/Cool Stuff Webhook batch actions now include headers, cookies, and query parameters when your batch consists of a single record. Fixes Corrected an issue in the Braze connector that removed endpoint names from the drop-down list after editing the title. Corrected issue in the sampled errors report of connector actions that caused some categories of errors to be unavailable. iQ Tag Management New/Cool Stuff On the tags and extensions screens, the active view filters are now displayed at the top of the list. Enhanced view filters are now available from the extensions screen. With the Load Order Manager feature enabled in Experiments, you can now sort tags by Load Order, Title, Vendor, and UID. (Learn More) With the Load Order Manager feature enabled in Experiments, you can now collapse Load Order groups from the Load Order Manager view. (Learn More) Fixes The Labels view filter is now applied across all iQ Tag Management screens using "OR" logic instead of "AND" logic. Customer Data Hub Fixes Corrected an issue that did not allow the user to save or cancel attribute edits when an existing enrichment on the attribute had previously been deleted. Corrected an issue where the overview for some attributes did not match the enrichments in the attribute edit view. Corrected an issue with the Trace feature causing the connection action message to display twice when the visitor session ended. Corrected an issue where the Select All button incorrectly displayed as inactive when adding an event specification by selecting Event Specs > Add from the menu. The message displayed to validate a date field in an audience rule has been clarified. Fixed an issue that mistakenly allowed read-only preloaded badge attributes to be edited. Installations New/Cool Stuff Android/Swift iOS AppsFlyer Updated to support the use of the JSON remote command feature. (Learn more) Braze Updated to support the use of the JSON remote command feature. (Learn more) Firebase Updated to support the use of the JSON remote command feature. (Learn more) Android/Swift (iOS 14 only) Added support for the Consent Management interface (Consent Manager SDK). (Learn more) Android/Kotlin Added an adapter module to enable existing remote command integrations to work with Tealium-Android and Tealium-Kotlin. Added support for Android Wear components. Added support to enable running multiple instances of Tealium. ... View more

This article describes how to set up the Cheetah Digital tag in your Tealium iQ Tag Management account. In this article: Table of Contents Placeholder Tag Tips Supports the following E-Commerce extension parameters: Order ID Order Subtotal List of Product Names List of Product Quantities List of Product Prices Use mapping to: Override the standard configuration values Override the E-Commerce extension values Pass additional data Tag Configuration First, go to Tealium's tag marketplace and add the Cheetah Digital tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Tag Type Client Domain The Client Domain is the same as the click-through domain for the client, such as e.clientdomain.com. If the client is using clientname.chtah.com, this should be p.chtah.com.   Affiliate ID Affiliate ID used to send mailings to be tracked. For multiple affiliates in the same pixel, use a period to separate affiliates. Example: 123456789.987654321 . The number of affiliates should be small, between 2 and 3. The maximum is 10. Client Name Only required for Image tag type. Alphanumeric name, 10 characters or less, typically an abbreviation of the client name. N Value Only required for iFrame tag type. Value of n querystring parameter. 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 tagtype Tag Type img or iframe cdomain Client Domain aid Affiliate ID cname Client Name nval N Value custom.myvar Custom E-Commerce Variable Description order_id Order ID Overrides _corder . order_subtotal Sub Total Overrides _csubtotal . product_name Array List of Names Overrides _cprodname . product_quantity Array List of Quantities Overrides _cquan . product_unit_price Array List of Prices Overrides _cprice . ... View more

This article describes how to set up the Google Display & Video 360 connector in your Customer Data Hub account. Before you use this connector, you must request that Google add your account to their whitelist. This allows Tealium AudienceStream to create segments in your Google account. (Learn more) In this article: API Information This connector uses the following vendor API: API Name: Google Authorized Buyers API Endpoint: https://cm.g.doubleclick.net/upload Documentation: Google Authorized Buyers API Connector Actions Action Name AudienceStream EventStream Add Visitor to User-List or Segment ✓ ✓ Remove Visitor from User-List or Segment ✓ ✓ It may take up to 72 hours from when the connector fires before the visitor becomes available for use. For more information, see Tips for using third-party audience lists. 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. When you add this connector, you must accept the vendor's data platform policy that appears. After adding the connector, configure the following settings: Client Customer ID Required Your customer identifier in the selected product Select the Target Product Required The account that establishes a connection here should have access to the target product selected. Create a New Segment Use the following steps to create a new segment in AudienceStream: Click Create a New Segment from the top of the Actions selection drop-down list. Enter the Segment Name, Segment Member Lifespan, Integration Code, and Segment Description. Click Create Segment. The Integration Code is an ID used by user list sellers to correlate IDs on their systems. If no ID is available, you can manually enter a random number between 1 and 1000. Confirmation will appear in the form of a check mark next to the Create Segment button to verify that the segment has been created. Allow 3 to 4 hours before using new audiences within an action when you create a new Google Display & Video 360 audience. When your audience list is visible inside Google Display & Video 360, you can then use your audience without error. For more information, see Google Display & Video Help: Audience list targeting. 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 Visitor to User-List or Segment Parameters Parameter Description Select the Target User-list/Segment Required User map identifier. Specifies the user that this operation applies to. This is the target User-list/Segment where the user will be added to. Google User ID Google User ID Provided by the ADX cookie-matching service. iOS Advertising ID iOS Advertising ID Android Advertising ID Android Advertising ID RIDA Roku ID AFAI Amazon Fire TV ID MSAI Xbox/Microsoft ID Data Source ID Optional An ID indicating the data source that contributed this membership. Required to be in the range of 1 to 1,000. Any ID greater than 1,000 results in a BAD_DATA_SOURCE_ID error. These IDs do not have reference or meaning for Google and are only used as labels for reporting purposes. Action - Remove Visitor from User-List or Segment Parameters Parameter Description Select the Target User-list/Segment Required This is the target User-list/Segment where the user will be removed from. Google User ID Google User ID Provided by the ADX cookie-matching service. iOS Advertising ID iOS Advertising ID Android Advertising ID Android Advertising ID RIDA Roku ID AFAI Amazon Fire TV ID MSAI Xbox/Microsoft ID Data Source ID Optional An ID indicating the data source that contributed this membership. Required to be in the range of 1 to 1,000. Any ID greater than 1,000 results in a BAD_DATA_SOURCE_ID error. These IDs do not have reference or meaning for Google and are only used as labels for reporting purposes. ... View more