Tealium Learning Center

This article describes how to manage server-side users and permission roles for the Tealium Customer Data Hub. This article covers the following topics: Table of Contents Placeholder 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 for accounts are in Tealium iQ Tag Management. Once 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 (4) 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 the Save/Publish button 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 will have read-only access to the client-side interface and will appear 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. Click Next. Save your changes. Return to the client-side interface. Go to Manage Users and remove the user. (Learn more) The user will no longer have access to the client-side profile, but will retain 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. Click the drop-down menu in the upper right of screen and 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. The details for that user display. To grant access to a profile, select a permission role from the drop-down list. 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 will allow 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. Click the drop-down menu in the upper right of screen and select Manage Users. From the Set permissions for future profiles drop-down 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: Click the drop-down menu in the upper right of screen and select Manage Users. Check the box to the left of each user for which you want to change the permission role. Click Bulk Actions and use the drop-down list to change the permissions for the selected users. Click Apply. Click Save in the upper right corner. 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. Once 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. See the Adding Users section for more information. 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 will 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 will automatically be 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 utilizing 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 checkbox 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 User permission will 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 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 Snapchat connector in your Customer Data Hub account. This connector is now deprecated and no longer available in the tag marketplace. For information about the Snapchat Audience Match connector with Tealium-provided credentials, see Snapchat Audience Match Connector Setup Guide . In this article: Table of Contents Placeholder Snap Audience Match (SAM)  allows you to a nonymously match data from your existing contacts (e-mail or device ID) with our community. Connector Actions Action Name AudienceStream EventStream Add User to Custom Audience ✓ ✓ Remove User from Custom Audience ✓ ✓ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: Client ID To obtain app credentials, request access to the Snapchat Marketing API at Apply for Access to the Snapchat Marketing API. Once you have applied, you will be able to create an OAuth app and get the client_id and client_secret  from (Business Manager) at https://business.snapchat.com under the Billing and Payments section for your organization. Your authorized redirect URIs must be configured to allow redirect URI: https://my.tealiumiq.com/oauth/webhook/callback.html  or if you are using SSO: https://sso.tealiumiq.com/oauth/webhook/callback.html Client Secret See Client ID. Ensure pop-ups are not blocked, and click Establish Connection. Login to your account and confirm access. Once granted, ensure to save your Customer Data Hub profile. When navigating through the connector configuration flow, ensure that you save your Customer Data Hub profile to save your changes. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Add User to Custom Audience Parameters Parameter Description Audience ID The audience ID can be found after clicking on the audience within the Audience Library in Snap Ad Manager. User Identifier - Email Plain Only configure one user identifier. The API supports matching via email or mobile identifier. Only use one identifier (either email or mobile ad id) per action Snapchat API reference User Identifier - Email Already Hashed - SHA256 Only configure one user identifier. The API supports matching via email or mobile identifier. Only use one identifier (either email or mobile ad id) per action. Snapchat API reference User Identifier - Mobile Plain Only configure one user identifier. The API supports matching via email or mobile identifier. Only use one identifier (either email or mobile ad id) per action. Snapchat API reference User Identifier - Mobile Already Hashed - SHA256 Only configure one user identifier. The API supports matching via email or mobile identifier. Only use one identifier (either email or mobile ad id) per action. Snapchat API reference Action - Remove User from Custom Audience Parameters Parameter Description Audience ID The audience ID can be found after clicking on the audience within the Audience Library in Snap Ad Manager. User Identifier - Email Only configure one user identifier. The API supports matching via email or mobile identifier. Only use one identifier (either email or mobile ad id) per action. Snapchat API reference User Identifier - Email Already Hashed - SHA256 Only configure one user identifier. The API supports matching via email or mobile identifier. Only use one identifier (either email or mobile ad id) per action. Snapchat API reference User Identifier - Mobile Plain Only configure one user identifier. The API supports matching via email or mobile identifier. Only use one identifier (either email or mobile ad id) per action. Snapchat API reference User Identifier - Mobile Already Hashed - SHA256 Only configure one user identifier The API supports matching via email or mobile identifier. Only use one identifier (either email or mobile ad id) per action. Snapchat API reference ... View more

This article describes how to set up the Braze connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Track User ✓ ✓ Delete User ✓ ✓ 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 API Endpoints. API Key Required. Provide API key with "users.track" and "users.delete" permissions enabled. Use Authentication to ensure that your API key is valid. For more information, see App Group REST API Keys. For additional information see Braze Documentation Braze Technology Partners: Tealium. 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. The Track User action contains functionality that is the same for AudienceStream and EventStream. As a best practice, Tealium recommends using User Attribute features with AudienceStream and Event and Purchase features with EventStream. Use cases that do not fit these criteria may ignore this best practice. Action - Track User Tealium recommends mapping all User ID parameters for this section. When an action triggers, Tealium evaluates which User IDs to send to Braze for the best performance. When multiple IDs provided, the first non-blank values is selected based on the following priority order: User ID Parameters (Required) External ID Braze ID Alias Name Alias Label For more information, see vendor documentation for User Track. Parameter Description External ID External ID of the user to be tracked. When importing Push Tokens, External ID and Braze ID should not be specified. Braze ID Braze ID of the user to be tracked. When importing Push Tokens, External ID and Braze ID should not be specified. User Alias Name The alias name of the user to be tracked. 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 tracked. When specifying a user alias, Alias Name and Alias Label should both be set. User Attributes Parameters (Optional) Tealium recommends using the Braze best practice of sending only 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. Parameter Description Country The country of the user to be tracked. Empty values are converted to null and removed from the Braze user profile. Current Location - Latitude The current latitude for the user to be tracked Empty values are converted to null and removed from the Braze user profile.. Current Location - Longitude The current longitude for the user to be tracked. Empty values are converted to null and removed from the Braze user profile. Date of First Session The date of the first session of the user to be tracked. Empty values are converted to null and removed from the Braze user profile. Date of Last Session The date of the last session of the user to be tracked. Empty values are converted to null and removed from the Braze user profile. Date of Birth The date of birth for the user to be tracked. Empty values are converted to null and removed from the Braze user profile. Email Address The email address for the user to be tracked. Empty values are converted to null and removed from the Braze user profile. Email Subscription Status The email subscription status for the user to be tracked. Empty values are converted to null and removed from the Braze user profile. Facebook The Facebook account for the user to be tracked. Empty values are converted to null and removed from the Braze user profile. First Name The first name of the user to be tracked. Empty values are converted to null and removed from the Braze user profile. Gender The gender of the user to be tracked. Values are Male (m) or Female (f). Empty values are converted to null and removed from the Braze user profile. Home City The home city for the user to be tracked. Empty values are converted to null and removed from the Braze user profile. Image URL Optional The URL for the user's image. Empty values are converted to null and removed from the Braze user profile. Language The language preference of the user to be tracked. Empty values are converted to null and removed from the Braze user profile. Last Name The last name of the user to be tracked. Empty values are converted to null and removed from the Braze user profile. Marked Email As Spam At User marked email as spam. Empty values are converted to null and removed from the Braze user profile. Phone Number The telephone number of the user to be tracked. Empty values are converted to null and removed from the Braze user profile. Push Subscription Status The Push Subscription status of the user to be tracked. Empty values are converted to null and removed from the Braze user profile. Push Tokens ID Array Array. The Push Token ID for the user to be tracked. Empty values are converted to null and removed from the Braze user profile. Push Tokens Array Push tokens array. Empty values are converted to null and removed from the Braze user profile. Push Tokens Device ID Array The Push Token Device ID for the user's device. Empty values are converted to null and removed from the Braze user profile. Time Zone The time zone for the user to be tracked. Empty values are converted to null and removed from the Braze user profile. Twitter The Twitter account for the user to be tracked. Empty values are converted to null and removed from the Braze user profile. Update Existing Only (Users) Optional Values are true or false. If no user value exists, one is created by default. If set to true, only existing users are updated and no new users are created. Empty values are converted to null and removed from the Braze user profile. Modify User Attribute Parameters (Optional) Parameter Description Modify User Attributes Increment Integer attributes by positive or negative integers. Modify Array attributes by adding or removing values from existing arrays. Event Parameters (Optional) To map data for events, you must map a value for the Braze event name. If the Tealium and Braze event names are not mapped, no data is sent to Braze. Parameter Description App ID The User App ID to be tracked. Name Required The application name to be tracked. Time Time Update Existing Only (Events) Optional Values are 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 Map Array type attributes to add multiple events. Array type attributes must be of equal length. Single value attributes can be used and will apply to each event. Purchase Parameters (Optional) To map data for purchases, you must map the values for Product ID, Currency, and Price. Example: The following code sample shows a Braze best practice example for receiving a single Tealium purchase 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 arrays to Braze as follows: 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 to be tracked. Product ID Required for every mapped purchase. Currency Required for every mapped purchase. Price Required for every mapped purchase. Quantity Map Array type attributes to add multiple purchase items. Array type attributes must be of equal length. Purchase Time Time of purchase. Automatically set to "now" unless explicitly mapped. Update Existing Only (Purchases) Optional Values are true or false. If no purchase value exists, one is created by default. If set to true, only existing purchases are updated and no new purchases are created. Map Array type attributes to add multiple events. Array type attributes must be of equal length. Single value attributes can be used and will apply to each event. Action - Delete User Parameters Parameter Description External ID Required Must be mapped. External ID of the user to delete. When multiple IDs are specified, the first non-blank values is selected based on the following priority order: External ID Braze ID Alias Name Alias Label For more information, see User Delete Endpoint. Braze ID Required Must be mapped. Braze ID of the user to delete. When multiple IDs are specified, the first non-blank values is selected based on the following priority order: External ID Braze ID Alias Name Alias Label Must include either External ID or Braze ID. User Alias Name Required The alias name of the user to be deleted. When specifying a user alias, Alias Name and Alias Label should both be set. For more information, see User Delete Endpoint. User Alias Label Required The alias label of the user to be deleted. When specifying a user alias, Alias Name and Alias Label should both be set. Frequently Asked Questions How does this connector complement or replace other Braze integrations with Tealium? 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 by the Events and Purchases features of the Braze 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 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: Table of Contents Placeholder 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 Lookup 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/revisions/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 provides detailed descriptions of model strength quality scores. In this article: Table of Contents Placeholder Understanding the Quality of Your Model The quality of any machine learning model created in Tealium Predict or any other machine learning tool varies depending on several factors, including (but not limited to) the following: The attributes which comprise the dataset and how complete of a picture the combined attributes provide. The daily volume of visitors and visits in the dataset. A larger volume means there is more data available for the model to learn on. The training date range selected for the model. Training a model for a longer time period generally equates to more data available for the model to learn on. In order to understand whether a given model has high quality for use in the real world, machine learning experts typically use a combination of interrelated metrics. The specific combination varies depending on the type of model being evaluated. Using Tealium Predict, non-experts can create models, evaluate the quality of the model, and take real-world actions in a streamlined manner, while retaining models with enough transparency for an expert to see the typical metrics they expect. The following sections provide explanations of the metrics and ratings available when using Tealium Predict that help you understand the quality of your models. For a more comprehensive explanation of other scoring reports, such as the F1 Score, Confusion Matrix, the ROC/AUC Curve, and Probability Distribution, see Model Scores and Ratings. Accuracy In Tealium Predict, accuracy equates to the ratio of correct predictions to the total number of predictions. However, accuracy alone cannot be used to determine the quality of a machine learning model. As an example, assume that you have red and green apples and 99% of the apples are green. In this case, our model could easily train to obtain a 99% accuracy score by simply predicting that every single apple is green, since that would be correct 99% of the time. This model, with 99% accuracy, would not be a good predictor of which apples are red. Model Strength Ratings The model strength ratings provide a label for the quality (strength) of a version of a trained model. The rating system has four labels that are based on the F1 Score, which is the typical metric used to evaluate the quality of a propensity model. F1 Score values are labeled using the following scale: Excellent - F1 score greater than 0.80 Good - F1 score greater than 0.60 but less than 0.80 Fair - F1 score at greater than 0.50 but less than 0.60 Poor - F1 score less than or equal to 0.50 The quality of a model is a relative judgment, not an absolute fact. The makeup of each team differs as do goals, testing abilities, and dataset quality. For these reasons, model strength ratings are not regarded as absolute. The intention is to use the ratings as a general guideline for quality. Strength Ratings for Trained Versions There are two types of strength ratings: static ratings for each trained version, and ongoing (dynamic) ratings for each deployed model. The strength rating for each trained version of each model provides a rating of the quality (strength) of the training and the model that resulted from the training. Models not yet deployed are not yet assigned a strength score. Each retraining represents a new and separate event, which makes this type of strength rating static and specific to each version. The rating for a version does not change over time. The strength rating displays next to each version on the Model Explorer page, in the Training Details panel, and in the overview page (for the latest trained version). Strength Ratings for Deployed Models 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. Live Model Performance Scores 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 F1 score is 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". In order 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. ... View more

This article describes how a Tealium Predict ML data model works and the components of a model. In this article: Table of Contents Placeholder How it Works Tealium Predict works with the Tealium AudienceStream CDP product to evaluate visit and visitor-level attributes. These attributes are used to create data models used to predict specific user actions. Here's how it works: Examine attribute readiness Select a target attribute Name your output attribute Train the model and review Select attributes to exlcude (optional) Retrain and refine Determining Attribute Readiness The readiness of an attribute displays next to each attribute in the drop-down list of available attributes. This feature helps you determine, in advance, whether an attribute candidate is a Ready or Not Ready to use as a target output attribute, as shown in the following example. Target, Output, and Exclusion Attributes When defining a model, each attribute in your AudienceStream profile is reviewed to automatically determine the top attributes that have a predictive relationship for the action you want to predict. Target Attribute The target attribute is AudienceStream attribute selected to define your model and represent the user action being predicted. When building a model, you select a target attribute from the visit or visitor-level booleans attributes that display in the drop-down list. Target attribute are used to signal that an action has been performed. For example, a boolean visit attribute named "Has Purchased" signals that a purchase event has occurred during a visit. Output Attribute The output attribute is an attribute created as a result of model training. Exclusion Attributes You can select to exclude attributes that are not relevant for the results you are seeking. These are referred to as exclusion attributes. When deciding which attribute types to exclude, Tealium recommends that you first train the model for initial insights with no attributes excluded. Training without including exclusion attributes provides insight into which attributes the model finds the most relevant and can lead you to consider introducing new AudienceStream attributes to help future model trainings. Example: After the initial training, you can exclude attributes with values that occur outside of the training period. After excluding these types of attributes, your training F1 score results may be lower when you retrain; however, your model produces better results when deployed. Attributes based on dates of visit or dates of purchase. These attributes do not repeat their values outside of the training period. Attributes based on unique user information, such as a User ID or Analytics ID. These attributes do not apply to other users outside of the training period. See Advanced Configuration Options for the specific steps used to exclude one or more attributes from your model. Get Started Go to Adding a Model to get started. ... 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 the model overview screen and how to use the sparkline graph as a guideline to the ongoing health of a deployed model. In this article: Table of Contents Placeholder Deployed Model Dashboard The dashboard lists each deployed model as a tile. A tile contains a snapshot of the prediction results for that model. Click a tile to view the details of a that model. To access the dashboard view, go to Predict > Overview. A tile may display the following information about a model: The status of a model, such as "In Training" or "Deployed", in the upper right corner of each tile.  The strength score rating of a model, such as "Fair" or "Excellent". Strength ratings are recalculated automatically and the sparkline graph reflects the latest rating. A sparkline graph depicting the general performance trend of the model. The version of the deployed model. Strength Score Ratings In the dashboard view, the strength score displays in parentheses as a decimal number, such as (0.91). This number represents the F1 score that the rating is based on. The strength rating cannot be known or calculated for a deployed model until the initial prediction timeframe has elapsed. For this reason, the strength rating of a model is not available until the day after the prediction timeframe. For example, if a model to predict the likelihood to purchase in the next 10 days is deployed on January 1st, the rating cannot be calculated until after January 10th. Expanded View Click a tile to display an expanded view of the model. In the expanded view, the sparkline graph shows the trend of the prediction ranges over time. The prediction ranges are based on the following strength scores: Most Likely (0.76 - 1) More Likely (0.51 - 0.75) Less Likely (0.26 - 0.50) Least Likely (0 - 0.25) Version Adaptation The sparkline graph adapts to versioning. For example, if you first deploy "Version 1" and later undeploy "Version 1" and deploy "Version 2", the graph automatically switches from "Version 1" to "Version 2". The adaptive chart ensures that you see the strength of the output attribute for the latest deployed version of the model. Additional Information See the following articles for additional information about model scores and evaluation: Evaluating the Trained Version Deployed Model Health Scores ... View more

Description: Tealium IP Address collection in server-side products is a setting that must be enabled by a Tealium employee and is not enabled by default. Please reach out to your Customer Success Manager for further assistance.  It is important to note that with this request, you assume all responsibility for ensuring compliance with applicable laws and regulations regarding the collection and storage of IP addresses by Tealium. If you would like to see some sample language to facilitate transparency and consent in your privacy policy, please visit Tealium Learning Community. About the IP Address: If present, Tealium sources the IP address from 'X-forwarded-for' If not present, the secondary source is 'Forwarded'. If several IPs are present, only the first is collected. For additional information, see: List of HTTP Header Fields ... View more

This article describes how to set up the DoubleClick Bid Manager connector in your Customer Data Hub account. In this article: 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 are prompted to accept the vendor's data platform policy. After adding the connector, configure the following settings: Client Customer ID Required Your (DoubleClick 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 displays 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 DoubleClick Bid Manager audience. When your audience list is visible inside DoubleClick Bid Manager, 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

This article describes how to set up the Xandr (Formerly AppNexus) Real Time Segments (Tealium-Provided Credentials) connector. To request access to this connector, you must first contact your Tealium account manager. The underlying integration for this connector uses Xandr functionality that is also in the Alpha-Beta phase with Xandr and is therefore subject to change. (Learn more) In this article: Table of Contents Placeholder How it Works The Instant Audience Service is a server-side method that uses streaming architecture to add individual or small groups of users to segments using the Xandr API. Rather than aggregating and periodically sending large batches of data using the Batch Segment Service, the Instant Audience Service associates users to segments in near real-time. Prerequisites Xandr Member ID shared with Tealium's Xandr member. To request access, you must first contact your Tealium account manager. Getting Started Obtain Authorization To begin using the Instant Audience Service and enable this integration, you will need to open a ticket with Xandr to have your member shared with Tealium's Member (9537). Provide the following information in a support request to Xandr: Are you using external user IDs? For example, do you use mapUID to store the mapping with Xandr? If you use another member's external user IDs, include their member_id as well. Do you need to populate segments belonging to other members? If so, provide the associated member_ids . Tealium's Member ID is 9537. When you would like your segments to expire by default? For example, never expire, expire 60 days from now, etc.? If you include EXPIRATION in your seg block, your default expiration will not be used. The following questions are for internal capacity planning: What is the number of unique user IDs per post? What is the number of expected posts per day? What is the number of unique segments per post? Xandr typically responds to these requests within 1-3 business days. Action Endpoint https://streaming-data.appnexus.com/rt-segment Connector Actions Action Name AudienceStream EventStream Add User to Segment ✓ ✓ Remove User From Segment ✓ ✓ Configure Settings Go to the Connector Marketplace and add the connector. Read the Connector Overview article for general instructions on how to add a connector. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Add User to Segment Parameters Parameter Description AAID Android Advertising Identifier. The mobile device ID for Android devices. Example: AEBE52E7-03EE-455A-B3C4-E57283966239 Xandr/AppNexus User ID The User ID returned by the cookie match endpoint. Example: 12345678900987654321 In addition to configuring the connector, Tealium recommends pairing with the Cookie Match tag. This tag performs a cookie sync to exchange device IDs, which facilitates the server-to-server actions described below. (Learn more IDFA Identifier for Advertisers. The mobile device ID for iOS devices. Example: 6D92078A-8246-4BA4-AE5B-76104861E7DC MD5 UDID The MD5 hashed value of the User ID. Example: 4a8a2b374f463b7aedbb44a066363b81 Open UDID Deprecated, do not use. SH1 UDID The SHA1 hashed value of the User ID. Example: F12877BFFD9C07E7224C9A6EFB7A709F4E29FDEA SHA1 MAC Deprecated, do not use. Tealium Visitor ID Deprecated, do not use. Expiration The lifetime of the user-segment association in minutes, starting from when we read it. A value of zero (0) means that the segment never expires. A value of negative one (-1) means that the user is to be removed from this segment. Example: 1440 Member ID The ID of the member that owns this segment or has been shared the segment by data provider Tealium. Example: 9537 Segment Code A user-defined name for the segment. Example: mysegment-003 Segment ID The segment ID. Example: 12693755 Value A numeric value that you assign to a segment. Example: 0 Action - Remove User From Segment Parameters Parameter Description AAID Android Advertising Identifier. The mobile device ID for Android devices. Example: AEBE52E7-03EE-455A-B3C4-E57283966239 Xandr/AppNexus User ID The User ID returned by the cookie match endpoint. Example: 12345678900987654321 IDFA Identifier for Advertisers. The mobile device ID for iOS devices. Example: 6D92078A-8246-4BA4-AE5B-76104861E7DC MD5 UDID The MD5 hashed value of the User ID. Example: 4a8a2b374f463b7aedbb44a066363b81 Open UDID Deprecated, do not use. SH1 UDID The SHA1 hashed value of the User ID. Example: F12877BFFD9C07E7224C9A6EFB7A709F4E29FDEA SHA1 MAC Deprecated, do not use. Tealium Visitor ID Deprecated, do not use. Segment ID The segment ID. Example: 12693755 Segment Code A user-defined name for the segment. Example: mysegment-003 Member ID The ID of the member that owns this segment or has been shared the segment by data provider Tealium. Example: 9537 Testing and Validation Batching and Rate Limits This connector leverages batch actions so that Tealium can manage high-volume data transfers to the vendor. Data queues in batched actions to be sent when the first one of the following three (3) thresholds is met: 500 records 10 minutes Greater than (>) 1MB The batching behavior described in the previous section is defined at the Action level. This means that for a given account and profile, each individual action is batched. If a profile contains multiple actions, Tealium individually batches each unique action when evaluating batch behavior. Frequently Asked Questions What are some example use cases that this integration supports? Search or time-sensitive retargeting in RTB As a buyer or DMP, this service is useful if you would like to mimic search retargeting capabilities. As a user enters search keywords, you receive a server-side signal that triggers a server-side association to the segments. The user can then see ads that are relevant to their search, which enables you to capitalize on the immediate relevancy of the content for the user. Page performance sensitive targeting Use this service if you want to avoid page load strain, but still want to be able to conduct retargeting without increasing the pixels present on the page. Alternative real-time audience targeting The Instant Audience Service can also be used for transactional retargeting, in which user scores are computed based on offline data or modeling. This only requires an additional trigger to have the user added to a segment that you wish to buy against in real-time. A concrete example is, based on Clickstream data, a buyer computes a score for a user that has browsed three (3) products in the kitchen category of its site and pushes a segment value to based on this user score to immediately show them an ad for additional kitchen items. De-targeting users who have converted To use your budget as efficiently as possible. This enables you to quickly de-target users that have already converted. How often do User IDs expire? Expires UIDs on a rolling basis such that the user IDs that have not been seen for the longest period of time are removed from our database to make room for new user IDs. If you upload UIDs that are very old, you may have a high percentage of invalid user IDs in your status report. Tealium keeps your cookie mapping fresh by requesting new UIDs at the start of each session. How quickly are updates to segments activated by Xandr? Xandr sets its target Service Level Agreement (SLA) for adding users to segments with the Instant Audience Service to two (2) minutes. In order to adhere to a maximum of two (2) minutes activation time, the Instant Audience Service currently has some limits, which Tealium has incorporated into the batching functionality. For additional details, see the Batching and Rate Limits section above. Vendor Documentation Xandr Streaming Server-Side Segmentation Xandr Instant Audience Service API Help Xandr Add/Remove Users From Segment ... View more

This article describes how to set up the Clicktale tag in your iQ Tag Management (TiQ) account. In this guide: Table of Contents Placeholder How it Works Clicktale empowers brands to act on unique behavioral insights to turn user experiences into measurable advantages. For more information about Clicktale, a Contentsquare company, visit contentsquare.com. What to Expect from this Integration A working integration of iQ Tag Management with the Clicktale tag from the Tealium tag marketplace enables customers to seamlessly execute session replays associated with clickstream data in order to detect and minimize end customer friction associated with tagged web pages. Prerequisites Tealium iQ Tag Management AudienceStream EventStream (optional) Clicktale Clicktale real-time signals are available to all customers with access to the Data Export Signals Clicktale signals enable joint Tealium and Clicktale customers to identify real-time behaviors, trigger events, and activate on those signals through AudienceStream. Once a potential friction or fraud behavior is detected, these signals are automatically sent to both Clicktale and AudienceStream. From there, customers can build powerful behavior-based segments that can be used across their marketing and advertising ecosystem. The Clicktale Signals settings provide the following capture points associated with web page activity and can easily be enabled by toggling them to True: Friction Repeated Scrolling Identifies when a visitor scans the page quickly and scrolls repeatedly from top to bottom. Identifies a potentially poor user experience or a frustrated visitor. Constant Hovering Identifies when a visitor consistently hovers over the same element without clicking. This signal indicates a visitor’s intent or interest without clicking the element. Consecutive Clicking (Clickable Element) Identifies when a visitor repeatedly clicks the same (clickable) element without a response from the page. The customer does not click any other element between clicks. This signal indicates a potential issue with the element. Consecutive Clicking (Un-clickable Element) Identifies when a visitor repeatedly clicks the same (un-clickable) element without a response from the page. The customer does not click any other element between clicks. This signal indicates a potential design flaw. Rage Clicking Identifies when a customer repeatedly clicks the same element without a response from the page. This event triggers regardless of whether customers click other elements in between clicks. JavaScript Click Error Identifies each time a click triggers a JavaScript error. Fraud Excessive Pasting Triggers when thresholds are met that identify abnormal and potentially fraudulent pasting behavior within the same visitor session. There are three (3) levels of Fraud likelihood: low, medium, and high. Excessive Reload Triggers when thresholds are met that identify abnormal and potentially fraudulent reload behavior within the same visitor session. There are three (3) levels of Fraud likelihood: low, medium, and high Ad Blocking Ad Blocker Signal Identifies when or if certain files are blocked, which identifies that an ad-blocker is present. You can optionally use signals from your EventStream event specifications and your AudienceStream visitor attributes. Tag Configuration First, go to Tealium's tag marketplace and add the Clicktale Carmel tag (Learn more about how to add a tag). After adding the tag, configure the following settings in the Data Mappings section. Tag Tips Conversion fires when Order ID is set. In order to send your Clicktale Replay Link to UDH, you must: Contact your Clicktale representative to enable the generation of the replay link. Set the Send Replay Link configuration to True. The Contentsquare tag automatically detects the Tealium account and profile loading on the page and sends the replay link there. To send the replay link to a different account or profile, override the default values by mapping the desired account and profile to the tealium_account and tealium_profile destinations, respectively To pass Tealium Audiences and Badges to Clicktale: Contact your Clicktale representative to enable the receiving of this data. To send a Badge to Clicktale, navigate to the Badges tab in the mapping toolbox and enter the name by which the Badge will be identified in the Clicktale system. To send all Audiences to Clicktale, toggle the Send UDH Audiences toggle to True. Applying Load Rules Load Rules determine when and where to load an instance of this tag. The 'Load on All Pages' rule is the default load rule. To load this tag on a specific page, create a new load rule with the relevant conditions. Load this Tag on the page where you want to track the visitor's mouse movements. 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 title Required. Identifies the tag instance. Clicktale Carmel is the default name. When using multiple tags by the same vendor, assign a unique name. partition Partition. The partition where data is sent. Map to this variable to dynamically configure the server partition value. project_guid Project GUID. Map to this variable to set the project guide field. send_replay_link Send Clicktale Replay Link Values are true or false. send_udh_audiences Send UDH Audiences. Values are true or false. tealium_account Tealium Account. tealium_profile Tealium Profile. E-Commerce Variable Description order_id Order ID. Overrides _corder . Required for transactions. order_total Order total. Overrides _ctotal . Required for transactions. order_shipping Shipping amount. Overrides _cship . order_tax Tax amount. Overrides _ctax . product_id Array List of Product IDs. Overrides _cprod . product_name Array List of Names. Overrides _cprodname . Required for transactions. product_sku Array List of SKUs. Overrides _csku . Required for transactions. product_category Array List of Categories. Overrides _ccat . product_quantity Array List of Quantities. Overrides _cquan . Required for transactions. product_unit_price Array List of Prices. Overrides _cprice . Required for transactions. Badges Variable Description title Badge Identifier. To send the mapped badge to Clicktale, enter the name by which the badge will be identified in Clicktale. Tealium automatically includes the badge title as a child property of a new object send_udh_data Your badge name will appear as mapped to send_udh_data . ... View more

This article describes how to get the most out of Tealium and Contentsquare by setting up the Contentsquare UX Analytics tag in your Tealium iQ Tag Management account and enabling the transmission of Tealium audiences and Visitor badges to Contentsquare. In this guide: Table of Contents Placeholder How it Works Contentsquare empowers brands to act on unique behavioral insights to turn user experiences into measurable advantages. Contentsquare daily transforms trillions of digital behaviors into intelligent visualizations and recommendations that can be used to grow revenue, increase loyalty, and fuel innovation. Users can access benchmarks and predictive scoring based on leading global data sets of digital behavior across geographies and industries. For more information, visit contentsquare.com. What to Expect From This Integration A working integration of iQ Tag Management with the Contentsquare tag from the Tealium tag marketplace enables customers to execute session replays associated with clickstream data in order to detect and minimize end customer friction associated with tagged web pages. Prerequisites Tealium iQ Tag Management AudienceStream EventStream (optional) Contentsquare Contentsquare Business Edition or higher Signals Contentsquare signals enable joint Tealium and Contentsquare customers to identify real-time behaviors, trigger events, and activate on those signals through AudienceStream. Once a potential friction or fraud behavior is detected, these signals are automatically sent to both Contentsquare and AudienceStream. From there, customers can build powerful behavior-based segments that can be used across their marketing and advertising ecosystem. The Contentsquare Signals settings provide the following capture points associated with web page activity and can easily be enabled by toggling them to True: Friction Repeated Scrolling Identifies when a visitor scans the page quickly and scrolls repeatedly from top to bottom. Identifies a potentially poor user experience or a frustrated visitor. Constant Hovering Identifies when a visitor consistently hovers over the same element without clicking. This signal indicates a visitor’s intent or interest without clicking the element. Consecutive Clicking (Clickable Element) Identifies when a visitor repeatedly clicks the same (clickable) element without a response from the page. The customer does not click any other element between clicks. This signal indicates a potential issue with the element. Consecutive Clicking (Un-clickable Element) Identifies when a visitor repeatedly clicks the same (un-clickable) element without a response from the page. The customer does not click any other element between clicks. This signal indicates a potential design flaw. Rage Clicking Identifies when a customer repeatedly clicks the same element without a response from the page. This event triggers regardless of whether customers click other elements in between clicks. JavaScript Click Error Identifies each time a click triggers a JavaScript error. Fraud Excessive Pasting Triggers when thresholds are met that identify abnormal and potentially fraudulent pasting behavior within the same visitor session. There are three (3) levels of Fraud likelihood: low, medium, and high. Excessive Reload Triggers when thresholds are met that identify abnormal and potentially fraudulent reload behavior within the same visitor session. There are three (3) levels of Fraud likelihood: low, medium, and high Ad Blocking Ad Blocker Signal Identifies when or if certain files are blocked, which identifies that an ad-blocker is present. You can optionally use signals from your EventStream event specifications and your AudienceStream visitor attributes. Tag Configuration First, go to the Tealium tag marketplace and add the Contentsquare tag (Learn more about how to add a tag). After adding the tag, go to the Data Mappings section to configure any additional mappings. Tag Tips Conversion fires when Order ID is set. In order to send your Contentsquare Replay Link to UDH, you must: Contact your Contentsquare representative to enable the generation of the replay link. Set the Send Replay Link configuration to True. The Contentsquare tag automatically detects the Tealium account and profile loading on the page and sends the replay link there. To send the replay link to a different account or profile, override the default values by mapping the desired account and profile to the tealium_account and tealium_profile destinations, respectively. To pass Tealium Audiences and Badges to Contentsquare: Contact your Contentsquare representative to enable the receiving of this data. To send a Badge to Contentsquare, navigate to the Badges tab in the mapping toolbox and enter the name by which the Badge will be identified in the Contentsquare system. To send all Audiences to Contentsquare, toggle the Send UDH Audiences toggle to True. Applying Load Rules Load Rules determine when and where to load an instance of this tag. The 'Load on All Pages' rule is the default load rule. To load this tag on a specific page, create a new load rule with the relevant conditions and load the Contentsquare tag on the page where you want to track the visitor's mouse movements. 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 title Required. Identifies the tag instance. Contentsquare UX Analytics is the default name. When using multiple tags by the same vendor, assign a unique name. id_project The Project Tag ID specific to your project. Map to this variable to set the project guide field. base_url Base URL send_replay_link Send Contentsquare Replay Link Values are true or false. Also known as contensquare_replay_link . This variable and session replay capability is currently in development for Contentsquare tag and is expected to be released in H1 2020 send_udh_audiences Send Customer Data Hub (CDH) audiences. Values are true or false. tealium_account Tealium account. tealium_profile Tealium profile. E-Commerce Variable Description order_id Order ID. Overrides _corder . Required for transactions. order_total Order total. Overrides _ctotal . Required for transactions. order_shipping Shipping amount. Overrides _cship . order_tax Tax amount. Overrides _ctax . product_id Array List of Product IDs. Overrides _cprod . product_name Array List of Names. Overrides _cprodname . Required for transactions. product_sku Array List of SKUs. Overrides _csku . Required for transactions. product_category Array List of Categories. Overrides _ccat . product_quantity Array List of Quantities. Overrides _cquan . Required for transactions. product_unit_price Array List of Prices. Overrides _cprice . Required for transactions. Badges Variable Description title Badge Identifier. To send the mapped badge to Contentsquare, enter the name by which the badge will be identified in Contentsquare. Tealium automatically includes the badge title as a child property of a new object send_udh_data Your badge name will appear as mapped to send_udh_data . ... View more

This article describes how to use the HTTP API - Flattened data source to create an HTTP endpoint to collect real-time event data with support for flattening complex objects. In this article: Table of Contents Placeholder How It Works A Webhook API sends outgoing requests to an endpoint that you specify. These requests inform Tealium EventStream and AudienceStream about customer activity from your external systems. When you add a webhook data source, a unique endpoint is generated. This endpoint is used to configure a webhook in your external system. Once configured, you can create subscriptions based on topics and receive related push notifications to automate use cases, stay informed, and increase productivity. The HTTP API - Flattened 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 objects. Events sent using HTTP POST with a complex JSON object will be flattened as follows: Event keys are created by lowercasing and connecting key paths to a prefix. For example, a value of true located at alpha.beta  displays as "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 do not have the ability to modify the request to meet format requirements for the standard Tealium Collect endpoint. Requirements Tealium EventStream or Tealium AudienceStream 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. tealium_visitor_id Optional For use with AudienceStream Setup The following sections provide guidance on how to add the HTTP API - Flattened data source and create a webhook. Add the Data Source The HTTP API - Flattened data source supports both the GET and POST methods using the following endpoint: https://collect.tealiumiq.com/integration/event/ACCOUNT/PROFILE/DATA_SOURCE_KEY Add the HTTP API - Flattened data source before proceeding, then copy the generated endpoint for use in an external system. Related: How to Add a Data Source Examples The following sections provide examples of input code and the resulting (flattened) output for complex objects. Complex Object Before Flattening { "boolean": true, "number": 12.34, "string": "value", "array_of_strings": ["first", "second"], "array_of_arrays": [ [1, 2], [3, 4] ], "array_of_objects": [{ "ordinal": "first" }, { "ordinal": "second" }], "object": { "child_boolean": true, "child_number": 12.34, "child_string": "value", "child_array_of_strings": ["first", "second"], "child_array_of_arrays": [ [1, 2], [3, 4] ], "child_object": { "gchild_boolean": true, "gchild_number": 12.34, "gchild_string": "value", "gchild_array_of_strings": ["first", "second"], "gchild_array_of_arrays": [ [1, 2], [3, 4] ] } } } After Flattening { "boolean": true, "number": 12.34, "string": "value", "array_of_strings": ["first", "second"], "array_of_arrays": ["[1,2]", "[3,4]"], "array_of_objects": ["{\"ordinal\":\"first\"}", "{\"ordinal\":\"second\"}"], "object_child_boolean": true, "object_child_number": 12.34, "object_child_string": "value", "object_child_array_of_strings": ["first", "second"], "object_child_array_of_arrays": ["[1,2]", "[3,4]"], "object_child_object_gchild_boolean": true, "object_child_object_gchild_number": 12.34, "object_child_object_gchild_string": "value", "object_child_object_gchild_array_of_strings": ["first", "second"], "object_child_object_gchild_array_of_arrays": ["[1,2]", "[3,4]"] } JSON Object Before Flattening A JSON object is treated as a single event by default. { "events": [ { "id": "1", "name": "Event A" }, { "id": "2", "name": "Event B" }, { "id": "3", "name": "Event C" } ] } After Flattening Unless the parser is overwritten by custom logic used to parse out batched events, the JSON object is transformed into a single event with stringified JSON array values. { "events": [ "{\"id\":\"1\",\"name\":\"Event A\"}", "{\"id\":\"2\",\"name\":\"Event B\"}", "{\"id\":\"3\",\"name\":\"Event C\"}" ] }   ... View more

To improve application security, the ability to use the target environments feature of Web Companion is now controlled by a setting in the publish settings, which now defaults to off for all accounts. Learn more about what was updated, how it works, and how to use it. Use of this tool allows the system to set a cookie with any arbitrary value which could expose your system to code injections. This feature is offered as a convenience for those who cannot use the Google Chrome browser. If you can use Chrome, Tealium recommends using the Tealium Tools Environment Switcher  as a best practice. About Target Environments If you're not familiar, "target environments" refers to the feature of Web Companion that allows you to load a different version of your iQ configuration on a page. This feature is a convenience for users that don't have access to change the underlying code of the page and want to test a different configuration. To use, you simply click the environment that you want to load and Web Companion reloads the page with that version of the Universal Tag (utag.js). What's New To improve application security, the ability to use this feature is now controlled in the publish settings of your account. By default, this setting is set to off for all accounts upon release of this change. When you use Web Companion with this setting turned off, it looks like this: Enable Web Companion Target Environments To use target environments in Web Companion, you must enable the feature in the publish settings and publish the changes. This change only impacts Web Companion and has no effect on Tealium Tools. To enable target environments for Web Companion: Log in to iQ Tag Management. Click Save/Publish in the upper right corner. The Save/Publish dialog displays. Click Configure Publish Settings in the upper right corner. The Publish Configuration dialog displays. From the General Publishing tab, scroll down to the Implementation section. Next to Web Companion, click On. Click Save and continue to publish. Additional Information Publish Configuration Settings Web Companion Methods to Switch Publish Environment ... View more

This article describes how to get the most out of Tealium and Leanplum. In this article: Table of Contents Placeholder How it Works Leanplum helps forward-looking brands meet the real-time needs of their customers by transforming data into an understanding of user needs and wants. By optimizing engagement campaigns and using multiple communication channels, the Leanplum platform delivers a timely, tested, and relevant unified experience to build customer loyalty and fuel business growth. See the Tealium + Leanplum Technology Partnership Overview for more information. Server-Side Integration The following table lists descriptions and prerequisites for the server-side Leanplum Integration types and provides links to detailed setup documentation. Integration Type What to Expect from this Integration Product Requirements Setup Guides Leanplum Connector Leverage the Leanplum Connector to pass user attribute data from Tealium to Leanplum and trigger real-time messages. Tealium EventStream and/or AudienceStream Leanplum Leanplum account Leanplum Connector Setup Guide Specifying Endpoint and API Versions When configuring the Leanplum connector, you must specify which endpoint and API version is used for each action. API Version Leanplum API version is 1.0.6 for all actions. Available Endpoints Track User Attributes (setUserAttributes API) Track Events (track API) Send Message (sendMessage API) Additional Resources Leanplum Tealium and Leanplum Partner Brief ... View more

The following product features, enhancements, and fixes were released in June, July, and August of 2020. Tags New/Cool Stuff Updated Adobe Visitor Service to Version 5.0. Updated the Adobe Experience Cloud ID Service to support Adobe library, version 5.0.1 Updated the AT Internet SmartTag to support AV insights and version 5.20.0 of the AT Internet library. Fixes Corrected collection domain issues impacting the AT Internet SmartTag. Connectors New/Cool Stuff New marketplace connector: Swrve App Events (Learn more) New Beta Experiments connector: Google Ads Conversions (Learn more) New data source: Tealium Collect for Google Tag Manager. (Learn more) Updated the Google Adwords Customer Match connector to support email address, phone number, and address information. Updated the Klaviyo connector API to support version 2.0. Updated the Google DCM Floodlight connector to validate custom variable name and to remove invalid names from the outgoing requests. (Learn more) Updated the Facebook Conversions, Facebook Offline Conversions, and Facebook App Events connectors to support Facebook's Limited Data Use feature for CCPA compliance. (Learn more) Updated the Beta Experiments version of the Flashtalking User Segments connector to add pagination and increase timeout to 10,000 milliseconds (ms). (Learn more) Updated the Beta Experiments version of the Apsis connector to add the ability to send real-time API requests from AudienceStream using the Apsis bulk API. (Learn more) Fixes Corrected issue with batch actions for the Facebook Audiences beta connectors. Corrected an issue with the Braze connector that caused the User Delete action to fail. (Learn more) iQ Tag Management New/Cool Stuff The ability to use the target environments feature of Web Companion is now controlled by a setting in the publish settings, which defaults to off for all accounts. (Learn more) When using the extension search function, you can now filter extensions by type. When searching for a tag, you can now filter tags by scope or category. With the Load Order experiment feature enabled, you can now edit tag-scoped extensions in the Extensions view. With the Load Order experiment feature enabled, you can now sort extensions by load order, title, or UID. In the accordion view for tags, extensions, and load rules, the headers are now fixed and always visible when you scroll up or down. Fixes Corrected issue causing the help documents link on the Display Rule tab in the CCPA banner with pop-up modal to not load properly. Corrected issue where adding and removing tags from tag-scoped extensions in the Load Order view did not prompt user to apply changes. The interface is now updated so that the "Scroll to Top" button displays on all tabs in the accordion view. Corrected issue with the Web Companion tool that prevented users from adding variables to the data layer, load rules, and extensions. Corrected issue causing a user with appropriate permissions to not be able to generate Data Bridge keys for the View-Through extension. Customer Data Hub New/Cool Stuff Introduced the Tealium Predict Machine Learning product. (Learn more) Updated server-side permissions to allow admins to filter users by permission, perform a keyword search on user profiles, and update profile level user permissions in bulk from the Manage Users screen. (Learn more) The server-side account/profile switcher now displays accounts and profiles in alphabetical order in the drop-down list. New data source: HTTP API - Flattened (Learn more) Fixes Corrected an array of strings mapping issue that occurred when an enrichment was applied to remove all entries. Corrected an issue with the Scheduled Jobs launcher to ensure that it continues to be triggered even if the last expected schedule date did not occur. Corrected an issue where previewing the product_view specification caused the Live Events interface to freeze. Corrected File Import column label fields to not allow tabs or spaces in the field name. Corrected an issue that caused the Add Attribute dialog not to close as expected when adding a custom attribute as an enrichment. Updated the connectors screen to display additional meta-data: Action ID and Consent Categories. Installations New/Cool Stuff AppsFlyer 1.0.0 Updated remote commands. Firebase (iOS) 1.1.0 Added support for e-commerce items array. Firebase (Android) 1.1.0 Added support for e-commerce items array. Swift 2.0.0 and Tealium Kotlin 0.1.0 (Beta) Apps with Tealium for Mobile can now take advantage of the Consent Manager module to stay compliant with the California Consumer Protection Act (CCPA). Apps with Tealium for Mobile can now leverage client-side enrichment of event data using JSON stored on the Tealium Hosted Data Layer in their mobile apps. QR Code Debugging for mobile implementations. Enabled single track event for mobile apps (vs. trackView and trackEvent methods) to improve developer experience and make it easier to use Tealium SDKs. In the latest mobile SDKs, expiry options for your data layer variables makes Tealium SDKs more configurable for complex use cases. Native session counting logic in the native SDKs removes the reliance on the webview to count. To use, the user must first update their mobile.html template. In both Kotlin and Swift, a single track call is now 2.5X faster than previous versions of their respective library. Fixes Android 5.7.2 Added Tealium.Config API setOverrideCollectDispatchProfile to override profile for Collect module. ... View more