Tealium Learning Center

Tony_Taliaferro · ‎04-09-2019

This article describes how to set up the Cordial connector. In this article: Connector Actions Action Name AudienceStream EventStream Update List Value of a User ✓ ✓ Upsert Contact ✓ ✗ Contact Activities ✓ ✗ Configure Settings Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see the About Connectors article. After adding the connector, configure the following settings: API key Cordial uses HTTP Basic Authentication (BA). From within the Cordial platform, you can generate an encoded API key for your account. This key is then used as the "username" for your BA credentials. For more information, see RESTful API Summary and Usage in the Cordial documentation. Click Done when you are finished configuring the connector. Action Settings — Parameters and Options Click Continue to configure the connector actions. Enter in a name for the action and then select the action type from the drop-down menu. The following section describes how to set up parameters and options for each action. Action — Update List Value of a User Parameters Parameter Description Primary Key The Primary Key is defined by the contact's unique email address value. List Name Name of the list the contact will be added to within the Cordial database. Note that the lists are created prior to updating the contact. For more information about updating Cordial database contacts, see Contacts in the Cordial documentation. Action — Upsert Contact Parameters Parameter Description Email Email address of the contact to upsert. Subscribed Status (Optional) Set the subscription status to one of the following: subscribed, unsubscribed, none. Contact Attributes Contact attributes to set or update for the user (string or number values). For list updates use boolean values. For example: {list_name} : true . Action — Contact Activities Parameters Parameter Description Action Name Set the name of the action or activity to record for the user to one of the following: click, open, send, or any user defined actions. Contact Primary Key The name of the primary key used to identify the user. For example: email . Contact Primary Key Value The value of the primary key used to identify the user. For example: user@test.com . Action Properties Additional data about the action or activity to record for the user. Action Timestamp Timestamp of the action or activity. Cordial automatically populates the timestamp if not provided in the request.

Tony_Taliaferro · ‎04-01-2019

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: Adition Cookie Matching Service Updated Adobe AppMeasurement for JavaScript tag to Version 2.12. (Learn more) Updated Adobe Audience Manager tag library to Version 9.1. (Learn more) Updated Adobe Experience Cloud ID Service tag to Version 4.1. (Learn more) Updated AT Internet Smarttag to prevent an erroneous page tracking event with a click event. Updated the Bing UET tag to support events and new parameters. Updated the Conversant Media - Direct to Brands tag to support mapping to dtm_fid parameter. Updated the Facebook Pixel tag to add support for new standard events. (Learn more) Updated Google Ads Conversion Tracking and Remarketing (gtag.js) tags to add phone conversion mappings. (Learn more) Updated Rakuten Marketing tag to make additional mappings available as basic configuration options to support SPAs and optional data. Fixes Corrected issue with Google Ads Conversion Tracking and Remarketing tag to only add conversion event if no event is currently set. Corrected issue with The Tradedesk tag causing properties from previous events to persist. Corrected the page_view scope for the Google Analytics (gtag.js) tag and added support for product-scoped dimensions and metrics. Connectors New/Cool Stuff Updated Google DMP AdWords connectors to the latest API versions, including DoubleClick Bid Manager, DoubleClick for Publishers (DFP), Google AdWords, DoubleClick Ad Exchange, and AdWords Customer Match. iQ Tag Management New/Cool Stuff Updated Amazon Web Services ( AWS) region support for the Tealium Collect tag (JavaScript tealium.js) and added support for a more compact page code snippet. Fixes Corrected issue causing insufficient session expiration resulting in logout or removal of user. Updated deprecated Google Chart API to correctly generate QR code for multi-factor authentication (MFA). Universal Data Hub New/Cool Stuff Introduced new Concurrent User Management options and support feature. (Learn more) Introduced new Data Supply Chain View feature. (Learn more) Introduced new File Import Data Source (Omnichannel) feature. (Learn more) Introduced new GitHub Integration feature. (Learn more) Introduced new Minified Trace feature. (Learn more) Fixes Applied updates to allow UDO string variables declared in the UDH to be used with the "Set Date" enrichment. Corrected issue created when two (2) conditions for a rule are saved and published and the second is subsequently removed. Corrected issue introduced by the lastest version of Google Chrome (73.0.3683.86) where user is not able to select an account in the UDH UI when using this version of the Chrome browser. Corrected issue preventing pop-up dependencies warning from displaying when deleting a rule that contains linked enrichments. Corrected issue with latest deployment causing mismatched event feeds.

Tony_Taliaferro · ‎03-21-2019

The new interface design is built to streamline the flow between Tealium products with a more consolidated look and feel, regardless of which platform you log into. You can now access all Tealium products in one centralized interface and enjoy a more intuitive and robust end-to-end experience. In this article: Preview Click the following video for a quick preview of new and changed features by Rana Salce, Education Operations Manager. What's New? Announcements Bell Bell icon to alert you recent product announcements. This icon illuminates if there are items you have not yet viewed. Administrative Settings A new icon displaying the initials of the user displays in the upper right corner. Click the icon to view or edit administrative settings. Your administrative settings are based on the permissions you currently have assigned within the application. Client and Server Side Indicators A small "C" displays under the Tealium logo on your window tab if you are currently in the client-side application and a small "S" displays if you are working in the server-side application. Help and Support Section A new Help and Support section is available in the left navigation bar that allows you to quickly access product guides, developer documentation, community forums, education and training information, contact the Support Desk, or view the current production status for the product. Vertical Left Navigation Bar The vertical left navigation bar is updated with a more modern look and feel. The contents of the menu items are dependent on the platform you are accessing. The vertical navigation bar is updated to display more modern product icons and is now split between Client-Side and Server-Side applications. Click on a product to reveal the main sections for that product and then click on a section to display the workspace for that section on the right. You can now view versions in a new menu item called Client-Side versions. You can quickly view a history of all saved versions, from the first save to the latest publish, or view a specified date range. You can collapse the left navigation bar to allow more display room in the workspace area or expand it to view the full description of the menu items. What Changed? Global Settings Global settings, include account and profile name, are now at the top left of the screen. Search Bar The search bar is now at the top left, next to global settings and allows you to search for any term within the application. Save and Publish Button The Save and Publish button is in the same location and now illuminates to alert you of unsaved changes. Client-Side Tools The previous tools menu selection displays an updated icon and is now called Client-Side Tools. From this section, you can quickly access browser tools, tag reporting, site map scans, the Site Scan Companion, and Consent Management features. TiQ Dashboard (Client-Side) The iQ Tag Management (TiQ) dashboard displays a summary of the profile you are currently working in. You can click on the different sections of the interactive dashboard summary to quickly navigate through your Variables, Rules, Tags, or Extensions. Provides easy access to tag reporting. Shows a visual display of recent changes made to the profile. Resource links display at the bottom of the page, which allow you to easily access community forums and support documentation, provide feedback for product ideas, or log in to the Tealium Eduction On-Demand portal. UDH Dashboard (Server-Side) Now features a light interface versus the previous dark interface for server-side applications. No longer displays "UDH", simply access the server-side applications by clicking EventStream, AudienceStream, or DataAccess. Data Supply Chain Displays a visual overview of your currently implemented solution, from start to finish, while validating the flow of your data and flagging any areas that need to be resolved. View your Data Supply Chain for all server-side products, or narrow it down to a specific view and time range, such as EventStream in the last 24 hours. Interactive items in the overview allow you to drill-down into the data that makes up each visual representation. Easy access to Usage Reports provide insight into your account usage, how usage varies over time, and helps you estimate cost and make informed decisions about your implementation. Sources Access Data Sources to define your data sources. Data sources consist of any system that sends sources to the Universal Data Hub (UDH), such as websites, mobile applications, or other custom applications that contain visitor activity. Access Omnichannel features to import offline data to UDH and then use this data to enrich your visitor profile data and take meaningful actions within your connectors. EventStream, AudienceStream, and Data Access Access each of these server-side products with the updated light background. Menu items previously displayed as tabs in the workspace now display as secondary menu items under the respective product. Click the menu item and the workspace displays on the right.

Tony_Taliaferro · ‎03-14-2019

Tealium Customer Data Hub now offers basic concurrent user management for users that are logged into the server-side products at the same time. Users are informed when changes are introduced by other active members, regardless of whether or not the change has been saved and published. When another active user saves changes to the profile, you are prompted to integrate their changes into your working environment or to keep working. With concurrent user management, you can now: View other active users and what product component the user is working in. Acknowledge that another user has initiated a change. See when a profile update from another user is saved and published. Update to the latest published version. Keep working and update later. For detailed information, see Concurrent User Management (UDH).

Tony_Taliaferro · ‎03-12-2019

This article describes how active concurrent users are managed in the Customer Data Hub product. In this article: Table of Contents Placeholder How it Works Customer Data Hub offers basic concurrent user support for users that are logged into Customer Data Hub at the same time. The options available to you are dependent on whether you have unsaved changes of your own. To begin, all active users should be working on the latest published version of a profile. Users are informed when changes are introduced by other active members, regardless of whether or not the change has been saved and published. Viewing other active users When you log in to Customer Data Hub, the product component that you are working in is highlighted in blue in the left navigation bar. If another user is also logged into Customer Data Hub and active, that user's profile initials display as a circle with a unique background color at the top of the screen. The same unique color is used to highlight which area of the product the other user is currently working in, as shown in the following example. Acknowledging that another user has initiated a change If another active user has started a change, whether or not they have saved and published the change, a message displays to let you know that a change that has not been saved and published is in progress. Click Got it to acknowledge the message. Before you save, contact the user displayed to ensure that your changes do not overwrite each other. When a profile update from another user is detected When another active user saves and publishes an update, a message displays to inform you that your profile is now out of date. The message contains the email of the user that made the change and the version name. Select one of the following options: Get the Latest Click this option if you have not made changes that you want to save. If unsaved changes are pending, your changes will be lost. Keep Working If you select this option, you can continue with your own work and then save and publish. Once you save and publish, the previous changes by other users are overwritten. Additional Resources For information about concurrent users in TiQ, see Concurrent Users (TiQ).

Tony_Taliaferro · ‎03-06-2019

The new File Import Data Source (previously known as Omnichannel Upload) adds new functionality, a more intelligent and intuitive workflow, the ability to view import activity, and better error handling and reporting. Enjoy the following new enhancements: Upload a Sample File Upload a sample file to automatically detect the column names. Map CSV Columns Directly to Event Attributes There's no more need for special omnichannel attributes, simply map column names directly to event attributes. Configure a File Transfer Service Configure a file transfer service: Amazon S3 (Tealium bucket or your own bucket), Microsoft Azure File/Blob Storage, or FTP/SFTP View Import Status Reports View the status of files and imported rows, including detected errors. For more detailed information, see File Import Data Source (Omnichannel).

Tony_Taliaferro · ‎03-05-2019

Take your data orchestration abilities to new levels, in real time, using the new Data Supply Chain view in the Universal Data Hub (UDH). Upon login, the dashboard displays a comprehensive, live action view of your UDH configuration at a glance to illustrate what your currently implemented solution provides. From this view, you can quickly click filtering options to take a deeper dive into areas of interest and view high-level snapshots of how your data flows through the system. From the Data Supply Chain view, you can: Select the All Products view, or click to view only EventStream, AudienceStream, or DataAccess. Sort your DataAccess view by EventStore, EventDB, AudienceStore, or AudienceDB Select to view only the last 24 hours, the last week, or the last 30 days Click into summary data to view details and interact with your data, in real time. Expand or collapse the details for an item Sort results by volume or whether an action fired successfully or failed to fire View error messages and warnings with direct links to corrective action, and more For detailed information, see The Data Supply Chain Dashboard.

Tony_Taliaferro · ‎02-28-2019

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: DialogOne ID Matching New marketplace tag: Digioh New marketplace tag: Rubicon Project Cookie Matching Service Added support for "purchase-details" to Floodlight (gtag.js) tag. (Learn more) Updated AB Tasty tag to include mapping for quantity and custom parameters. Updated library code in the deckers/lib-deckers library for the Catchpoint RUM real user monitoring tag. Updated the Facebook tag to support the disablePushState flag. (Learn more) Updated the Mixpanel tag template to allow for the dynamic mapping of the token parameter. Updated the Moxie Concierge tag to the vendor's latest version. Fixes Updated the Facebook tag template to allow passing multiple entries in the content_name parameter. Connectors New/Cool Stuff New marketplace connector: Clickatell (Learn more) New marketplace connector: Discord (Learn more) New marketplace connector: Dynamic Yield (Learn More) New marketplace connector: Kiip (Learn more) New marketplace connector: Madvertise (Learn more) New marketplace connector: OneSignal (Learn more) New marketplace connector: Pipedrive (Learn more) New marketplace connector: PushCrew (Learn more) New marketplace connector: Sendlane (Learn more) New marketplace connector: SendX (Learn more) New marketplace connector: Singular Events (Learn more) New marketplace connector: TVSquared (Learn more) Fixes Corrected Facebook CA connector issue causing problems with multi-key matching. Corrected issue causing problems with running the Floodlight connector when Trace is not enabled. (Learn more) iQ Tag Management New/Cool Stuff Applied updates to add the e-commerce extension (if not already present), and populate the appropriate drop-down lists with best practice naming convention variables. (Learn more) When expanding an extension, it now scrolls into the view. Fixes Corrected issue causing insufficient session expiration resulting in logout or removal of user. Installations New/Cool Stuff Added iOS Objective-C (Objc) public headers for visitor attributes. (Learn more) Added the Ruby library and Ruby as a data source for the UDH to allow users to add the Tealium RubyGem to track user activity. (Learn more)

Tony_Taliaferro · ‎02-22-2019

This article describes how to set up the DialogOne connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send Content ✓ ✗ 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 - Send Content Parameters Parameter Description Domain Domain value based on the environment in use: Production: secure-ip-api.dialogone.jp Staging: secure-ip-apistg.dialogone.jp Development: secure-ip-apidev.dialogone.jp For access to the API documentation, contact your DialogOne Account Manager. Account ID Account ID for LINE business account. Typically a 16-digit alpha-numeric value. For additional help, contact your DialogOne Account Manager. User ID User ID retrieved from the TiQ DialogOne User Match tag. This is the ID of the user that will be receiving the message. For additional help, contact your DialogOne Account Manager. Content ID 1 Content ID that correlates to the message configured in the DialogOne Platform. This is the content the user will receive. Content ID 2 Content ID that correlates to the message configured in the DialogOne Platform. This is the content the user will receive. A single request can contain up to five (5) Content IDs. When adding content, set Content ID ID 2 to Content ID 5. Content ID 3 Content ID that correlates to the message configured in the DialogOne Platform. This is the content the user will receive. A single request can contain up to five (5) Content IDs. When adding content, set Content ID ID 2 to Content ID 5. Content ID 4 Content ID that correlates to the message configured in the DialogOne Platform. This is the content the user will receive. A single request can contain up to five (5) Content IDs. When adding content, set Content ID ID 2 to Content ID 5. Content ID 5 Content ID that correlates to the message configured in the DialogOne Platform. This is the content the user will receive. A single request can contain up to five (5) Content IDs. When adding content, set Content ID ID 2 to Content ID 5.

Tony_Taliaferro · ‎02-22-2019

This article describes how to set up the Discord connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Discord is a voice, video, and text chat app designed specifically for gamers. You will need to configure a Webhook in your Discord Server to utilize the actions. Connector Actions Action Name AudienceStream EventStream Send Message to Channel ✓ ✓ 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 - Send Message to Channel Parameters Parameter Description Endpoint URL Required. Copy the value from your Webhook and paste in the box below. For more information, see: https://support.discordapp.com/hc/en-us/articles/228383668. Message Value This is the message that will be sent to the channel. For more information, see: https://discordapp.com/developers/docs/resources/channel#create-message.

Tony_Taliaferro · ‎02-22-2019

PushCrew provides a platform for marketers to send push notifications to their subscribers from within their website. This article describes how to set up the PushCrew connector in your Customer Data Hub account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add Subscriber To Segment ✓ ✓ Remove Subscriber from Segment ✓ ✓ Send Notification to a Subscriber ✓ ✓ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: API Token Each API request is authenticated by an authentication token in the request header. To get your authentication token, send an email to info@pushcrew.com. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Add Subscriber To Segment Parameters Parameter Description Segment ID The ID of the segment to which you are adding the subscriber. For more information, see: Add subscribers to a segment Subscriber ID The ID of the subscriber to be added to the segment. The Subscriber ID can be set from the PushCrew cookie or by using the PushCrew JavaScript API. For more information, see: Get SubscriberID of Current User. Action - Remove Subscriber from Segment Parameters Parameter Description Segment ID The ID of the segment to remove the subscriber from. For more information, visit: Remove Subscribers from a Segment. Subscriber ID The ID of the subscriber you are removing from the segment. The Subscriber ID can be set from the PushCrew cookie or by using the PushCrew JavaScript API. For more information, see: Get SubscriberID of Current User. Action - Send Notification to a Subscriber Parameters Parameter Description Title Title of the push notification. Maximum of 35 characters. For more information, see: Send to an Individual Subscriber. Message Message to be displayed in the push notification. Maximum of 80 characters. URL URL to open upon clicking the push notification. Subscriber ID Subscriber ID of the subscriber. Image URL URL of the icon to be shown in the notification. URL must use HTTP and point to a 192x192 PNG file. If this is not provided, the default company logo will be shown in the notification. Hero Image URL URL of the hero image to be shown in the notification. URL must use HTTPS and point to an image file. This feature can only be used by business and enterprise accounts. Only works for Chrome subscribers. Mozilla Firefox does not yet support. Button One Label This is the label of the first call-to-action button which will be shown in the notification. Maximum length of this parameter is 12 characters. This feature can only be used by business and enterprise accounts. Only works for Chrome subscribers. Mozilla Firefox does not yet support. Button One URL This is the URL which will open upon clicking the first call-to-action button shown in the notification. This feature can only be used by business and enterprise accounts. Only works for Chrome subscribers. Mozilla Firefox does not yet support. Button Two Label This is the label of the second call-to-action button which will be shown in the notification. Maximum length of this parameter is 12 characters. This feature can only be used by business and enterprise accounts. Only works for Chrome subscribers. Mozilla Firefox does not yet support. Button Two URL This is the URL which will open upon clicking the second call-to-action button shown in the notification. This feature can only be used by business and enterprise accounts. Only works for Chrome subscribers. Mozilla Firefox does not yet support. Time to Live Must be an integer attribute type. This parameter is used to control the time up until which the notification should be attempted if the subscriber is offline. Pass the number of seconds lapsed after which the notification should not be sent. Default value ( 2419200 ) stands for 4 weeks. Auto Hide Notification Must be an integer attribute type. The number 1 denotes that the notification will remain on-screen until it's clicked or closed. A zero ( 0 ) denotes that the notification will auto-hide if not clicked on or closed after 20 seconds.

Tony_Taliaferro · ‎02-22-2019

This article describes how to set up the Clickatell connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send SMS ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: API Key: You will be given an API key for each integration you set up in the Clickatell platform. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Send SMS Parameters Parameter Description Content Content of your SMS message. For more information, see: https://www.clickatell.com/developers/api-documentation/rest-api-send-message/. To Phone Number The phone number that will be receiving the SMS message. From Phone Number Only pertains to the two-way SMS set-up. You will find more information on this in your Clickatell account. Scheduled Delivery Time Scheduled time of delivery if the message is not intended to be sent in real time. Format example: 2018-12-12T14:03:00+0200 .

Tony_Taliaferro · ‎02-22-2019

OneSignal is a complete push notification solution for mobile apps. This article describes how to set up the OneSignal connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send Push Notification Based on Player ID ✓ ✗ Send Email Based on Player ID ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: REST API Key Your REST API key for app-specific operations (getting users of an app, modifying users, getting notifications, sending notifications) listed in the Keys & IDs section. For more information, see: OneSignal Team and Keys. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Send Push Notification Based on Player ID Parameters Parameter Description App ID Your OneSignal application ID, which can be found in Keys & IDs. For more information, see: create notification. Player ID Specific player to send your notification to. Template ID ID of the Push template in your OneSignal account. Action - Send Email Based on Player ID Parameters Parameter Description App ID Your OneSignal application ID, which can be found in Keys & IDs. For more information, see: create notification. Player ID Specific player to send your notification to. Email Subject Subject of the email. Email Body Body of the email.

Tony_Taliaferro · ‎02-22-2019

Kiip is an in-app mobile advertising platform that uses moments to create meaningful customer interactions and generate highly targeted, custom audiences. This article describes how to set up the Kiip connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Start/End a Session ✗ ✓ Record a Moment ✗ ✓ 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: App Key: Kiip application key found in the dashboard. 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 - Start/End a Session Parameters Parameter Description Event ID Should be either ‘session_start’ or ‘session_end’ depending whether the user opens or closes the app. For information, see: https://docs.kiip.me/en/sdk/server.html#session-endpoint. Device ID The ADID or Identifier. Device IP A valid IP address provided by device Device Operating System This should always include a version number. Device Density The screen density. Device Locale The user’s setting for locale. Device Language The default language on the device. Device Model The model of the device. Device Resolution The resolution of the device. Device Manufacturer The manufacturer of the device. Device User Agent The device user agent. App Version The current client version number. Carrier Example: ATT. Connection Type Example: WIFI. SDK Version User Age User Gender Example values: m or f . User ID A string containing a user’s ID for use in virtual currency rewards. Latitude This is always a number between -90 and 90. Longitude This is always a number between -180 and 180. Close Button By default, a close button is shown when rewards are earned. When set to 0 or false, can be used to hide the close reward button. Email Address When supplied with an email address, this component will be used to prefill a user’s email address when a reward is earned. Timstamp ISO 8601 formatted timestamp of the action. Defaults to time connector is triggered. Action - Record a Moment Parameters Parameter Description Moment ID The UUID associated with the a given moment from the Kiip dashboard. For information, see: http://docs.kiip.me/en/sdk/server.html#moment-endpoint Device ID The ADID or Identifier. Device IP A valid IP address provided by device. Device Operating System This should always include a version number. Device Density The screen density. Device Locale The user’s setting for locale. Device Language Device Model Device Resolution Device Manufacturer Device User Agent App Version The current client version number. Carrier Example: ATT. Connection Type Example: WIFI. SDK Version User Age User Gender Example values: m or f User ID A string containing a user’s ID for use in virtual currency rewards. Latitude This is always a number between -90 and 90. Longitude This is always a number between -180 and 180. Close Button By default, a close button is shown when rewards are earned. When set to 0 or false, can be used to hide the close reward button. Email Address When supplied with an email address, this component will be used to prefill a user’s email address when a reward is earned.

Tony_Taliaferro · ‎02-22-2019

This article describes how to set up the Sendlane connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add Subscriber To List ✓ ✗ Remove Subscriber From List ✓ ✗ Unsubscribe User ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: Subdomain – The subdomain of your Sendlane account. For more information, see: #list-subscriber-add. API Key –Your API and Hash keys are available in your Account Settings. Hash Key – Your API and Hash keys are available in your Account Settings. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Add Subscriber To List Parameters Parameter Description Email Valid email address of the user to be subscribed to the list. List ID ID of the list the user is being subscribed to. First Name First name of the subscriber. Last Name Last name of the subscriber. Custom Fields You can add any number of custom fields. Action - Remove Subscriber From List Parameters Parameter Description Email Valid email address of the user to be deleted from the list. List ID ID of the list the user is being deleted from. Action - Unsubscribe User Parameters Parameter Description Email Subscriber email to delete. List ID If not provided, user will be unsubscribed from all lists.

Tony_Taliaferro · ‎02-22-2019

This article describes how to set up the Singular Events connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Install Event ✗ ✓ Post Install Events ✗ ✓ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: API Key: API Key is required. Clients can retrieve their API key from within their account from the Singular's portal. 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 - Install Event Parameters Parameter Description Device ID At least one device identifier is required, for example: Advertiser Identifier ( idfa ) Identifier for Vendor ( idfv ) for iOS apps Android advertising ID ( aifa ), Android ID ( andi ) for Android. Reference the following API documentation for more information. Platform "Android" or "iOS". Application Name Package Name (Android) or Bundle ID (iOS) of your application. Example: com.mycompany.app IP Address IP address of the device session (with decimal points or colons). Both IPv4 and IPv6 are supported. Device Make Make of the device hardware, which is typically the consumer-facing name. Example: Samsung, LG, or Apple. Device Model Model of the device hardware. Example: iPhone 8, or Galaxy S10 Device Build The build of the device, URL-encoded. Example: Build%2F13D15 . OS Version Version of the OS on the device. Example: 9.2. Language & Country Code The IETF local tag for the device, using two-letter language and country code separated by an underscore. Example: en_US . Optional Parameters Add all other optional parameters here. For more information on supported parameters, reference the Singular API documentation. Action - Post Install Events Parameters Parameter Description Event Name Name of the event to report in Singular. Example: ViewItem Application Name Package Name (Android) or Bundle ID (iOS) of the mobile application. Example: com.yourcompany.app Device ID At least one device identifier is required, for example: Advertiser Identifier ( idfa ) Identifier for Vendor ( idfv ) for iOS apps Android advertising ID ( aifa ), Android ID ( andi ) for Android. Reference the following API documentation for more information. Platform Android or iOS. IP Address Raw IP address of the device (with decimal points or colons). Both IPv4 and IPv6 are supported. Device Make Make of the device hardware, typically the consumer-facing name. Example: Samsung, LG, or Apple Device Model Model of the device hardware. Example: iPhone XS, or Galaxy S10 Device Build Build of the device, URL encoded. Example: Build%2F13D15 OS Version Version of the OS on the device. Example: 9.2 Language & Country Code The IETF local tag for the device, using two-letter language and country code separated by an underscore. Example: en_US Optional Parameters Add all other optional parameters here. For more information, see the Singular Server-to-Server documentation.

Tony_Taliaferro · ‎02-22-2019

This article describes how to set up the SendX connector in your Customer Data Hub account. In this article: Table of Contents Placeholder SendX is a cloud-based SaaS platform that provides easy-to-use email marketing automation and lead generation solutions for your web business. Connector Actions Action Name AudienceStream EventStream Add or Update Visitor ✓ ✗ Add Tag To Visitor ✓ ✗ Remove Tag From Visitor ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: API Key: Your API key can be found on your SendX settings page. 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 or Update Visitor Parameters Parameter Description Team ID Your Team ID can be found on your SendX settings page. Email In case email of an already existing contact needs to be updated, then specify current email under Email property and updated email under New Email property. For more information, see: https://app.sendx.io/playground/#!/Contact/post_contact_identify. First Name First name of the visitor. Last Name Last name of the visitor. New Email In case email of an already existing contact needs to be updated, then specify current email under Email property and updated email under New Email property. Company Company of the visitor. Birthday Birthday of the visitor. Format: YYYY-MM-DD . Custom Fields If a custom field doesn't exist, then it is created and associated with the contact along with the corresponding value. If the custom field already exists, then the value is updated. Tags If a tag doesn't already exist, this call will create it. Note that you can only send one tag with this API call, but a visitor can have multiple tags associated with them. To add additional tags or remove tags, use the Add Tag to Visitor or Remove Tag from Visitor action. Action - Add Tag To Visitor Parameters Parameter Description Team ID Your Team ID can be found on your SendX settings page. Email Email of the visitor. Tag Tag to be added to visitor profile. Action - Remove Tag From Visitor Parameters Parameter Description Team ID Your Team ID can be found in your SendX settings page. Email Email of the visitor. Tag Tag to be removed.

Tony_Taliaferro · ‎02-22-2019

This article describes how to set up the madvertise connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream iOS Install ✗ ✓ Android Install ✗ ✓ Send Custom 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 - iOS Install Parameters Parameter Description Click ID Custom IDFA Custom Device IP Custom Action - Android Install Parameters Parameter Description Click ID Custom GAID Custom Device IP Custom Action - Send Custom Event Parameters Parameter Description Event Name Custom Click ID Custom

Tony_Taliaferro · ‎02-22-2019

This article describes how to set up the Pipedrive connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create a Person ✓ ✗ Update a Person ✓ ✗ Merge Two Persons ✓ ✗ Delete a Person ✓ ✗ 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: Subdomain The subdomain for your Pipedrive account. API Token If you are working with a manual integration, the API token must be provided as part of the query string for all requests, using the api_token variable. You can obtain the API token manually from the Pipedrive app or by fetching the objects of Authorizations. For more information, see: https://pipedrive.readme.io/docs/core-api-concepts-authentication. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Create a Person Parameters Parameter Description Name Name of person to be created. For more information, see: Add a Person. Owner ID ID of the user who will be marked as the owner of this person. When omitted, the authorized user ID will be used. Organization ID ID of the organization this person will belong to. Email Email address of the person. Phone Phone number of the person. Visible To Visibility of the person. If omitted, visibility will be set to the default visibility setting of this item type for the authorized user. Add Time Optional creation date and time of the person in Coordinated Universal Time (UTC) format. Example: YYYY-MM-DD HH:MM:SS . Requires admin user API token. Action - Update a Person Parameters Parameter Description ID Person ID. For more information, see: Update a Person Name Name of person to be created. Owner ID ID of the user who will be marked as the owner of this person. When omitted, the authorized user ID will be used. Organization ID ID of the organization this person will belong to. Email Email address of the person. Phone Phone number of the person. Visible To Visibility of the person. If omitted, visibility will be set to the default visibility setting of this item type for the authorized user. Add Time Optional creation date and time of the person in Coordinated Universal Time (UTC) format. Example: YYYY-MM-DD HH:MM:SS Requires admin user API token. Action - Merge Two Persons Parameters Parameter Description ID ID of the person that will be merged. For more information, see: Merge Two Persons Merge With ID ID of the person that the person will be merged with. Action - Delete a Person Parameters Parameter Description ID ID of the person to be deleted. For more information, see: Delete a Person.

Tony_Taliaferro · ‎02-21-2019

This article describes how to set up the TVSquared connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream 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: Client Host Client-specific collector hostname. A static value supplied by TVSquared. Example: collector-1233.tvsquared.com . Site ID Client-specific collector siteid. A static value supplied by TVSquared. Example: TV1234-1 . Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Track Event URL Parameters The following table lists URL parameter to be encoded in the server-to-server request: The servertrack and RAND parameters are automatically set by Tealium. Parameter Description Visitor ID ( VISITORID ) Required. Unique ID for the visitor. URL parameters to be encoded in the server-to-server request. Example: 0123456789ABCDEF User Agent ( UA ) User agent, if applicable. Example: Mozilla/5.0 Browser Language ( LANG ) Browser language, if applicable. Example: en Session Parameters ( _cvar ) The following table lists the fine-grained session-level tracking information: Parameter Description appid ID of the app. App ID Example: com.myapp.appster appname Name of the app. App Name Example: My Application country Country Example: US deviceid Device ID Example: e3f5536a141811db40efd6400f1d0a4e deviceidtype Device ID type. The deviceid field type. Example: AAID or IDFA ip Required IP Address. The IP address of the mobile device. Example: 8.8.8.8 lang User Language Example: en medium Required. Set to app for mobile app. Example: app os Operating System Example: ANDROID source Required Identifies the name of the partner supplying the data. Example: myApplication ua User Agent. Example: Mozilla/5.0 user User ID. Client-supplied private unique user identifier, such as an internal id from a billing system. Example: U1234 Action Parameters ( cvar ) The following table lists the fine-grained per-action tracking information: Parameter Description Action Name Required. Name of the action being performed. Example: INSTALL adchannel Ad Channel Advertising channel name. Example: Social campaign Campaign Campaign name. Example: NY_Acquisition currency Currency Currency of revenue. Example: USD id Action ID Identity of an individual user action, such as an order id. Example: 42342 preattributed Pre-Attributed Whether the event has already been attributed. Example: 1 prod Product Area of the product concerned. Example: angry birds promo Promocode The promocode, if the user used one. Example: ABCD rev Revenue Revenue amount. If not specified, 0 is supplied by default. Example: 12 ts Unix Timestamp Exact Unix timestamp of event, in UTC format. If not provided, will be provided by default. Example: 1538996046

Tony_Taliaferro · ‎02-12-2019

You can now access TiQ and UDH features in beta mode using Experiments. Learn about and experiment with upcoming features that can help you take your account to the next level by gaining access to cutting edge experimental features. The Early Access program will continue to work for the features it has been enabled for. Future iterations of major releases will be released under Experiments. To enable an experiment, log in, open the Experiments window, and select the feature to enable. Experiments are exciting new features that we want you to get your hands on. We think you'll love them, but we also want your feedback. To get started, see Enabling Experiments in TiQ and UDH.

Tirrusri · ‎02-05-2019

Any detailed implementation guide for "New marketplace tag: Curalate" using Tealium IQ ? if yes please share.

Tony_Taliaferro · ‎01-31-2019

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: Acquia Lift New marketplace tag: Anura New marketplace tag: Exponential Interactive New marketplace tag: Kenshoo Infinity New marketplace tag: Oracle Infinity New marketplace tag: Relay42 New marketplace tag: Teads Advertiser Added a flag to the Floodlight connector to only fire purchase event when Order ID is present. Rebranded IfByPhone SourceTrak to DialogTech SourceTrak and Mongoose Metrics AccuTrack to DialogTech East Rules Engine. Rebranded the Sperse tag to Green Blue Analytics and updated base URL. Updated AT Internet SmartTag tag to version 5.13.3. Updated AT Internet SmartTag to prevent erasure of the vrn parameter. Updated the Global Vars setting for the Google Analytics (analytics.js) tag to clear custom dimensions and metrics on view events and link events. Updated Webtrekk tag to support versions 4.3.3 and 4.4.4. Connectors New/Cool Stuff New marketplace connector: Facebook Offline Conversions (Learn more) Updated action guidelines in the UI for the MailChimp connector. (Learn more) Fixes Corrected formatting of variables passed in to user lookup for the Selligent connector. Corrected issue with the Tool Tips interface for the DoubleClick for Publishers connector. Universal Data Hub New/Cool Stuff Added "Set String to Date" string enrichment. (Learn more) Updated connector batch processing methods to enhance performance. Updated UDH to enable Redshift Spectrum for users enabling DB products for the first time. Fixes Corrected issue causing clientip IP address with restricted flag to display in EventStore. Corrected issue with month calculations when using number enrichment. Applied recommended OWASP data encoding updates to mitigate risks associated with DOM-based Cross-Site Scripting (XXS) vulnerabilities. Corrected issue with causing incorrect display of new audience trend graphs. iQ Tag Management Fixes Corrected Cross-Site Scripting (XSS) issue in the TiQ Chat feature. Corrected issue with editing, saving, and then merging environments when using the JavaScript extension. Corrected issue with tag template Edit button to ensure that "Save Version Template" and "Save Profile Template" are clearly visible for user. Installations New/Cool Stuff Added Xamarin plugin and support for mobile libraries. (Learn more) Updated React Native integration to support Consent Management, advanced configuration options, and VisitorID. (Learn more) Updated iOS mobile install library VisitorProfile to no longer check that the Collect module is enabled when using the Visitor Service API. Fixes Corrected issue causing Android VisitorProfile to default lookup to main profile. Updated Android minSdkVersion to newer Google-supported version and corrected WebView onReceivedError() error encountered.

Tony_Taliaferro · ‎01-28-2019

This article describes how to enable experiments for both client-side and server-side products. Experiments are beta features that can be enabled for your account. The Early Access program will continue to work for the features it has been enabled for. In this article: Table of Contents Placeholder How It Works With experiments you can take your account to the next level by accessing cutting edge experimental and pre-release features that are still in the beta stage. To enable an experiment, log in to your account, open the Experiments dialog, and select the features to enable. Once enabled, the new feature is immediately available in your session. To make the experiment available for all other users of your account, save your account. If you log out without saving, the experiment does not persist for future sessions. Experiment Stages New features are promoted through stages and go to General Availability (GA) based on usage, hours, and enablement. Alpha Experiments in the Alpha stage are typically items an initial release of a large feature in order to gather customer feedback and apply enhancements prior to release. Beta Experiments in the Beta stage include features that will soon be available for GA, with minor fixes and enhancements. Enabling an Experimental Feature Use the following steps to enable an experimental feature in iQ Tag Management or Customer Data Hub: Log into iQ Tag Management. In the left side bar, click Client-Side Experiments or Server-Side Experiment, which resembles a laboratory beaker. The Experiments dialog displays. Use the toggle to turn a selected feature On or Off. Click Apply. If you select On, the experiments is immediately applied to your current session. The next time you save or publish, the experiment is activated for all users of your profile. How do I provide feedback? To provide feedback on experiments, visit the Experiments and Early Access Announcements forum. For documentation on features in early access, see Early Access Documentation.

Tony_Taliaferro · ‎01-17-2019

Note that Mongoose Metrics has been rebranded and is now DialogTech East Rules Engine.

Date Registered	‎09-25-2017 12:25 PM
Date Last Visited	‎12-31-2021 03:10 AM
Total Messages Posted	356
Total Kudos Received	62

Tealium Learning Center

Cordial Connector Setup Guide

Release Notes - March 2019

The New Tealium Product Interface Design is Now Li...

Introducing Concurrent User Management for UDH

Concurrent User Management

Introducing the New File Import Data Source (Omnic...

Introducing the Data Supply Chain View

Release Notes - February 2019

DialogOne Connector Setup Guide

Discord Connector Setup Guide

PushCrew Connector Setup Guide

Clickatell Connector Setup Guide

OneSignal Connector Setup Guide

Kiip Connector Setup Guide

Sendlane Connector Setup Guide

Singular Events Connector Setup Guide

SendX Connector Setup Guide

Madvertise Connector Setup Guide

Pipedrive Connector Setup Guide

TVSquared Connector Setup Guide

Introducing "Experiments" - Access to Beta Feature...

Re: Release Notes - December 2018

Release Notes - January 2019

Enabling Experiments

Re: How can I take the value of a cookie set by on...

Products

Company