Tealium Learning Center

This article describes how to set up the DoubleClick for Publishers (DFP) 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 ✓ ✓ 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. 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 screen. 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. 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 DoubleClick for Ad Exchange 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 ✓ ✓ 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 target product, either DoubleClick AdExhchange - Buyer or DoubleClick AdExchange - Publisher. 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 screen. 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. 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

Using DataXu Audience Ingestion APIs are designed send audience data into the DataXu platform. This article describes how to set up the DataXu Audiences connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add User to Segment(s) ✓ ✓ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Add User to Segment(s) Parameters Parameter Description Endpoint URL Optional When provided it will override the default endpoint Default endpoint is http://s2s-v2.w55c.net/s2s-servlet Segment(s) List/Array/Set of segment ids to which the user should be added. These segment ids can be either DataXu’s segment identifier (i.e. pixel id or segment uid) or the data partner’s segment identifier. Only Customer Data Hub Array/List/Set types are supported for all attributes configured in this section. i.e. only pick such data type as the value. Alias Type Represents kind of alias (API key of "alias_type") DataXu accepts the following alias types: DX GOOGLE_AD_ID SHA1_GOOGLE_AD_ID MD5_GOOGLE_AD_ID IDFA SHA1_IDFA MD5_IDFA ANDROID_ID SHA1_ANDROID_ID MD5_ANDROID_ID Alias ID Represents the actual identifier for the user (API key of "alias_id") and the specified "Alias Type" Timestamp Represents the time of the user’s addition to the audience (API key of "timestamp") Optional and preferably in UTC. example: 2016-12-01T15:16:33Z    ... View more

The Tealium Xamarin integration provides a set of cross-platform interfaces and configuration classes that interface with the native Tealium iOS and Android SDKs to simplify Tealium tracking Xamarin developers. In this article: Table of Contents Placeholder Overview The Tealium Xamarin integration provides a set of cross-platform interfaces and configuration classes that interface with our native iOS and Android SDKs to make Tealium tracking more straightforward for Xamarin developers. DLLs and Lifecycle Modules Dynamic-Link Libraries (DLLs)  described in this article are available at: https://github.com/Tealium/tealium-xamarin. Available DLLs Several DLLs are available for the Xamarin integration: Tealium.Common.dll This DLL contains cross-platform code, interfaces, and common code to be used in all projects within your Xamarin application. Add this DLL as a reference in both shared project and platform-specific projects. Abstraction DLLs Abstraction DLLS are included to create an easy-to-use C# API wrapper for the native Tealium SDKs and should only be referenced in platform-specific projects. These libraries contain platform-specific, concrete class implementations for the interfaces and abstract classes provided by the Tealium common library. You can code all of your cross-platform logic against the common library. Tealium.Droid.dll –  for Android mobile platforms Tealium.iOS.dll  –  for Apple mobile platforms There are DLLs specific to each mobile platform which are referenced by the abstraction DLLs. The platform DLLs are binding libraries and therefore embed our the native SDKs - they provide auto-generated wrapper code that would allow you to interact with our native SDKs directly and as a result they can be used standalone if desired. Tealium.Platform.Droid.dll Tealium.Platform.iOS.dll Binding libraries can be used by themselves. The fact that they are automatically generated results in vastly different namespaces for each platform, which adds an extra complication to development efforts. It is advised to make use of the Common and platform-specific abstraction libraries  instead. Lifecycle Modules An optional lifecycle module is available by referencing the relevant DLL for the platform. These are binding libraries for the native equivalent SDKs: Tealium.Platform.Lifecycle.Droid.dll Tealium.Platform.Lifecycle.iOS.dll Android Shared Project Example The following example illustrates the Shared project and Android platform-specific project from a typical Xamarin based app: As shown in the example, the Shared Project references only the Tealium.Common.dll library, whereas the Android-specific project references all of the following: Tealium.Common.dll Tealium.Droid.dll Tealium.Platform.Droid.dll Tealium.Platform.Lifecycle.Droid.dll Basic Configuration The first step for initialization is to ensure that your projects reference the appropriate libraries as described in the Overview. Though not required, Tealium recommends using the TealiumInstanceManager classes provided as they provide out-of-the-box, thread-safe Tealium instance management. Android Example The following example applies to an Android project: using Tealium.Droid; //... ITealiumInstanceManager instanceManager = new TealiumInstanceManager(new TealiumInstanceFactoryDroid(<myAndroidApplication>)); //Optional Lifecycle Module enablement - ensure to reference Tealium.Platform.Lifecycle.Droid.dll TealiumLifecycleManager.SetLifecycleAutoTracking = TealiumDroid.Lifecycle.TealiumLifecycleControlDelegation.SetLifecycleAutoTracking; iOS Example The following example applies to an Apple project: using Tealium.iOS; //... ITealiumInstanceManager instanceManager = new TealiumInstanceManager(new TealiumInstanceFactoryIOS()); //Optional Lifecycle Module enablement - ensure to reference Tealium.Platform.Lifecycle.iOS.dll TealiumLifecycleManager.SetLifecycleAutoTracking = TealiumIOS.Lifecycle.TealiumLifecycleControlDelegation.SetLifecycleAutoTracking; Creating Instances Once the TealiumInstanceManager is created, you can begin creating Tealium instances as with the native SDKs. The TealiumInstanceManager is a multiton pattern that provides access to multiple named instances if you need to track data on more than a Tealium profile. Use the following steps to create a new instance: Create a TealiumConfig object to hold various required and optional configuration items, as shown in the following example: TealiumConfig tealConfig = new TealiumConfig("TEALIUM_INSTANCE",//Instance Name "tealiummobile",//Tealium Account Name "demo",//Tealium Profile Name "dev",//Tealium Envrionment true);//Optional Auto Lifecycle AutoTracking (default: true) When complete, you can then can use your TealiumInstanceManager to create a Tealium instance which can be used to track your events, as shown in the following example: ITealium tealium = instanceManager . CreateInstance (tealC onfig ); Advanced Configuration The TealiumConfig class has constructor options that allow you to specify optional parameters to enable or disable the more advanced aspects of the Tealium Mobile SDKs. These parameters are optional as not all customers require these features. Remote Commands An object containing RemoteCommand blocks if you need to work with the features provided by the TagBridge tag. Similarly, you can supply code for the delegated methods that you can use in the native versions of the SDKs as well, such as Remote Commands. While the majority of the events within mobile are either sent to our data collection servers to be actioned through connectors, or processed in the tag management web view to trigger vendor tags. Remote Commands provide additional flexibility in that events used for tag management can pass data back to your native code through the IRemoteCommand interface. The following sample code prints out the CommandId (set to TealiumConsts.REMOTE_COMMAND_ID ). Using this example, you will also have access to a full payload of data, as configured in the associated TagBridge Custom Command tag required to set this up: static List<IRemoteCommand> SetupRemoteCommands() { var command = new DelegateRemoteCommand(TealiumConsts.REMOTE_COMMAND_ID, "Test command " + TealiumConsts.REMOTE_COMMAND_ID) { HandleResponseDelegate = (DelegateRemoteCommand cmd, IRemoteCommandResponse resp) => { System.Diagnostics.Debug.WriteLine($"Handling command {cmd.CommandId}..."); } }; return new List<IRemoteCommand>() { command }; } Delegate Methods There are five delegated methods that allow you to inject code into the processing logic within the Tealium SDK: DelegateDispatchValidator Provides two delegate methods  where the Boolean return value determines whether or not an existing dispatch should be dropped or queued. This is useful if you have steps within your app where you know that the user may be offline or you specifically want to write your own batching logic for example. ShouldDropDispatchDelegate ShouldQueueDispatchDelegate DispatchSentDelegateEventListener Called whenever a dispatch has been sent. DispatchQueuedDelegateEventListener Called whenever a dispatch has been queued. WebViewReadyDelegateEventListener Called when the WebView is fully loaded and ready, if you are using the Tag Management module. SettingsPublishedDelegateEventListener Executed when there has been an updated set of publish settings retrieved. The following example illustrates the usage of the delegate method: static TealiumAdvancedConfig SetupAdvancedConfig() { DelegateDispatchValidator validator = new DelegateDispatchValidator() { ShouldDropDispatchDelegate = (ITealium arg1, IDispatch arg2) => { System.Diagnostics.Debug.WriteLine("Inside ShouldDropDispatchDelegate!"); return false; }, ShouldQueueDispatchDelegate = (ITealium arg1, IDispatch arg2, bool shouldQueue) => { System.Diagnostics.Debug.WriteLine("Inside ShouldQueueDispatchDelegate!"); return shouldQueue; } }; DispatchSentDelegateEventListener sendingListener = new DispatchSentDelegateEventListener() { DispatchSent = (tealium, dispatch) => { System.Diagnostics.Debug.WriteLine("Inside DispatchSent!"); dispatch.PutString("KeyAddedBySendListener", "Value added by sending listener."); } }; DispatchQueuedDelegateEventListener queuingListener = new DispatchQueuedDelegateEventListener() { DispatchQueued = (tealium, dispatch) => { System.Diagnostics.Debug.WriteLine("Inside DispatchQueued!"); dispatch.PutString("KeyAddedByQueuedListener", "Value added by queuing listener."); } }; WebViewReadyDelegateEventListener webViewListener = new WebViewReadyDelegateEventListener() { WebViewReady = (tealium, webView) => { System.Diagnostics.Debug.WriteLine("Inside WebViewReady!"); } }; SettingsPublishedDelegateEventListener settingsListener = new SettingsPublishedDelegateEventListener() { SettingsPublished = (tealium) => { System.Diagnostics.Debug.WriteLine("Inside SettingsPublished!"); } }; TealiumAdvancedConfig advConfig = new TealiumAdvancedConfig(validator, sendingListener, queuingListener, webViewListener, settingsListener); return advConfig; } Tracking To trigger specific events within your app, use the appropriate method for the type of event that you want to track, as shown in the following sections. Screen View Tracking The following example uses screen view tracking: // Get ITealium instance ITealium tealium = instanceManager . GetExistingInstance ( TealiumConsts . INSTANCE_ID ); // Track a Page View event with the title "View Name" but no extra event data. tealium . TrackView ( " View Name " ); // Track a Page View event with the title "View Name" along with the "page_type" event daata. tealium . TrackView ( " View Name " , new Dictionary < String , object >( 1 ){ { " page_type " , " product detail page " } }); // Track a Page View event with the title "View Name" along with a single piece of event data. // This an equivalent way to the track call directly above. tealium . TrackView ( " View Name " , " page_type " , " product detail page " ); Event Tracking The following example uses event tracking: // Get ITealium instance ITealium tealium = instanceManager.GetExistingInstance(TealiumConsts.INSTANCE_ID); // The TrackEvent method has the same overloads as TrackView, so only one additional example is provided. // Track an Event with three pieces of specific Event Data. tealium.TrackEvent("Event Name", new Dictionary<String, object>(3){ {"event_category", "Menu"}, {"event_action", "Button Click"}, {"event_label", "Logo"} }); Adding Event Data As with the native SDKs, there are two additional types of variables that you can set to be added to each of your events. Persistent Data Persistent data will be merged into your event-specific data dictionary on every event that you trigger, as well as persist between launches, as shown in the following example: //Get ITealium instance ITealium tealium = instanceManager.GetExistingInstance(TealiumConsts.INSTANCE_ID); tealium.AddPersistentDataSources(new Dictionary<string, object>(1) { //Data will be merged into every event. { "PersistentDataTest", "Example persistent value." } }); Volatile Data Volatile data will be merged into your event-specific data dictionary on every event, just like persistent data. The key difference is that once the application is closed, volatile data is lost and will not be present on the next launch. //Get ITealium instance ITealium tealium = instanceManager.GetExistingInstance(TealiumConsts.INSTANCE_ID); tealium . AddVolatileDataSources ( new Dictionary < string , object >( 1 ) { //Data will be merged into every event. { " VolatileDataTest " , " Example volatile value. " } }); Consent Management The Consent Management feature comes from the two native SDKs embedded into the DLLs named Tealium.Platform.*.dlls . The Tealium.Common.dll provides the following category and status enums to use: Tealium.ConsentManager.ConsentStatus Tealium.ConsentManager.ConsentCategory Enabling Consent Management To enable Consent Management, simply pass the optional parameter in the constructor of TealiumConfig or set it as a property, as shown in the following example: TealiumConfig tealC onfig = new TealiumConfig ( TealiumConsts . INSTANCE_ID , TealiumConsts . ACCOUNT_NAME , TealiumConsts . PROFILE_NAME , TealiumConsts . ENVIRONMENT , true , commands , advConfig , false ); //optional Consent Manager Enablement. //or subsequently enable it: tealConfig . IsConsentManagerEnabled = true ; //then initialise your Tealium Instance: var tealium = instanceManager . CreateInstance (tealC onfig ); Overriding Initial Consent Status As with the native SDKs for both Android and iOS, when Consent Management is enabled, new users are assumed to be in an Unknown state. Tracking requests are queued up until the consent status has been opted-in or out, at which point events will be sent or purged, respectively. You can override the initial status through properties on the TealiumConfig object, as shown in the following example: // enable Consent Manager: tealConfig . IsConsentManagerEnabled = true ; // Set Users to be Consented by default: tealConfig. InitialUserConsentStatus = ConsentManager . ConsentStatus . Consented ; // Or set Users to be Not Consented by default: tealConfig. InitialUserConsentStatus = ConsentManager . ConsentStatus . NotConsented ; // Opt users into All Categories tealConfig. InitialUserConsentCategories = ConsentManager . AllCategories ; // or none: tealConfig. InitialUserConsentCategories = ConsentManager . NoCategories ; // or partial opt-in, only to Analytics and Mobile categories. tealConfig. InitialUserConsentCategories = new ConsentCategory []{ ConsentManager . ConsentCategory . Analytics , ConsentManager . ConsentCategory . Mobile }; Updating the User Consent Selection The ConsentManager can be interacted with directly from the Tealium instance, through the ConsentManager property. If you need to update a user's consent selection, simply pass the relevant values. Only the enum values available in the ConsentManager.ConsentCategory and ConsentManager.ConsentStatus should be used, as shown in the following example: // if the user is in an Unknown state, then the following code would trigger any queued events would be sent after this: ITealium tealium = instanceManager . GetExistingInstance ( TealiumConsts . INSTANCE_ID ); tealium . ConsentManager . UserConsentStatus = ConsentManager . ConsentStatus . Consented ; // The above will inherently opt the user into all categories as none have been provide. // To grant consent and opt into a subset of categories you can use the overload: tealium . ConsentManager . UserConsentStatusWithCategories ( ConsentManager . ConsentStatus . Consented , new ConsentCategory []{ ConsentManager . ConsentCategory . Analytics }); Resetting Consent Preferences Additional options area available to reset the currently selected consent preferences. This will revert the user back to an Unknown status so that subsequent events will begin being queued again. To completely disable, disable it on the TealiumConfig object, as shown in the following example: ITealium tealium = instanceManager . GetExistingInstance ( TealiumConsts . INSTANCE_ID ); tealium . ConsentManager . ResetUserConsentPreferences (); Resources The following sections provide links to Tealium and Xamarin resources that contain detailed information about Tealium for iOS and Android Tealium Documentation The following resources provide links to Tealium documentation for Android and iOS. If you are building a mobile application in Xamarin, you will use bindings to our iOS and Android libraries. Tealium for iOS Tealium for Android Alternatively, if only using UDH services (AudienceStream, EventStream, DataAccess), the Tealium  C#  library may be used as the native code in a Xamarin project. Vendor Documentation The following resources provide links to Xamarin's extensive documentation for adding Tealium's Android and iOS libraries: Xamarin Binding a Java Library Xamarin - Binding an iOS Objective-C Library Walkthrough: Binding an iOS Objective-C Library ... View more

This article describes how to set up the The Trade Desk In-App Events connector in your Customer Data Hub account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send In-App 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: Advertiser ID (adv) Represents your Advertiser ID on The Trade Desk. 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 In-App Event Parameters Parameter Description TTD Event Tracker ID ( upid ) TTD Event Tracker ID ( upid ) Mobile App Event ( ref ) This should be the same as the name of the event. Same as the value that you have configured on The Trade Desk configuration page for this specific event ( ref ) Mobile Client IP Address ( client_ip ) Mobile Client IP Address ( client_ip ) Mobile IDFA for iOS ( idfa ) IDFA is the iOS ID for Advertisers ( idfa ) Mobile GPS ADID for Android ( gps_adid ) ADID is the Google Play Advertiser ID ( gps_adid ) Mobile NAID for Windows ( win_naid ) Windows NAID is the Windows Phone Device ID ( win_naid ) Revenue Tracking Value ( v ) Revenue tracking parameters v and vf are only sent if the UI is enabled. ISO 4217 currency codes are used for vf field Floating point numbers are expected for the v field. Example: 0.99 , 3.99 Revenue Tracking Currency ( vf ) Revenue tracking parameters v and vf are only sent if the UI is enabled Note that ISO 4217 currency codes are used for vf field Floating point numbers are expected for the v field. Example: 0.99 , 3.99 Additional Query Data Provide any additional url query parameter data if needed   ... View more

This article describes how to set up the The Trade Desk (theTradeDesk) connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send First Party Advertiser Data ✓ ✓ 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: Agency Secret Key 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 First Party Advertiser Data Parameters Parameter Description Data Center Region Required Select data center geographically closest to where user data comes from. Advertiser ID Required Advertiser ID Trade Desk ID (TDID) Trade Desk ID ( TDID ) Device Advertising ID (DAID) Device Advertising ID ( DAID ) Override TTL in Minutes Override time to live ( ttl ), in minutes Override Timestamp Override timestamp Data Name Required Data Name ... View more

This article describes how to set up the dotdigital connector in your Customer Data Hub account. Table of Contents Placeholder How it Works The dotdigital connector provides digital marketing professionals with SaaS technology solutions and tools, and offers an email marketing platform. Connector Actions Action Name AudienceStream EventStream Trigger Campaign ✓ ✓ Send Email Using a Triggered Campaign ✓ ✓ Send SMS ✓ ✓ Create or Update Contact ✓ ✗ Add Contact to Address Book ✓ ✗ Delete Contact from Address Book ✓ ✗ 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 Username Username for your API user. To get started using the API, you must first create an API user. These API user credentials (username/password) are required to authenticate each operation/method call and to ensure that you are connected to the correct account. For setup information, see the following vendor documentation: Getting Started with the API API Password Password for your API user. Region ID Region ID to be included in every API endpoint. You can find your API endpoint under Settings > Access > API users. 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 - Trigger Campaign Parameters Parameter Description Campaign ID The ID of the campaign, which needs to be included within the request body. Address Book ID The Address Book ID the campaign is to be sent to. You must specify either an Address Book ID or a Contact ID. Contact ID The Contact ID the campaign is to be sent to. You must specify either an Address Book ID or a Contact ID. Send Date The date and time at which you want the campaign to be sent. Action - Send Email Using a Triggered Campaign Parameters Parameter Description To Address The email address of the recipient. Campaign ID The ID of the triggered campaign. For more information on this endpoint, see the following vendor documentation: Send transactional email using a triggered campaign. Personalization Values Each personalization value is a key-value pair. Action - Send SMS Parameters Parameter Description Telephone Number The mobile number of the contact. Message The SMS message to be sent to your contact's mobile phone. Action - Create or Update Contact Parameters Parameter Description Email The email address of the contact. For more information on this endpoint, see the following vendor documentation: Create contact. Data Fields Each contact data field is a key-value pair. Opt-In Type The opt-in type of the contact. Email Type The email type of the contact. Contact Id The ID of the contact. This must be set to update a contact. Action - Add Contact to Address Book Parameters Parameter Description Address Book ID The ID of the Address Book. For more information on this endpoint, see the following vendor documentation: Add contact to address book. Email The email address of the contact. For more information on this endpoint, see the following vendor documentation: Create contact. Data Fields Each contact data field is a key/value pair. Opt-In Type The opt-in type of the contact. Email Type The email type of the contact. Action - Delete Contact from Address Book Parameters Parameter Description Address Book ID The ID of the Address Book. For more information on this endpoint, see the following vendor documentation: Delete contact from address book. Contact ID The ID of the contact to be deleted. ... View more

A Dynamic Customer Profile (DCP) is a single, actionable view of your customer built from a combination of first and third-party customer data. It enables you to deliver consistent, personalized web and mobile experiences for your most valuable customers, and measure the impact of those experiences. In this article: Table of Contents Placeholder This article describes how to set up the Optimizely Dynamic Customer Profiles connector in your Customer Data Hub account. Connector Actions Action Name AudienceStream EventStream Update Customer Profile ✓ ✓ 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: Visit http://app.optimizely.com/tokens to generate an API token, or http://developers.optimizely.com/classic/token for more information. 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 - Update Customer Profile Parameters Parameter Description DCP Service ID For more information on where to find your DCP Service ID, visit: Create Audiences with Dynamic Customer Profiles. Datasource ID For more information on where to find your Datasource ID, visit: Create Audiences with Dynamic Customer Profiles. Customer ID in Datasource For more information on where to find your Customer ID, visit: Create Audiences with Dynamic Customer Profiles. Tealium recommends using the Optimizely end user ID found in the first party cookie. Customer Profile Attributes A Profile Attribute describes one aspect of a customer's profile within a data source. The specified attribute value overwrites any existing value specified earlier. If a key does not correspond to a registered attribute name, the write will fail, and if a value does not respect the attribute's datatype/format, the write will fail. ... View more

The most advanced analytics for mobile in the world. This article describes how to set up the Mixpanel connector in your Customer Data Hub account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Track Event ✓ ✓ Update Profile - Set ✓ ✓ Update Profile - Add ✓ ✓ Update Profile - Append ✓ ✓ Update Profile - Union ✓ ✓ Update Profile - Unset ✓ ✓ Update Profile - Delete ✓ ✓ Update Profile - Track Revenue ✓ ✓ Create Alias ✓ ✓ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: API Project Token: A project token is required to send profile and events data to Mixpanel. See: Where can I find my project token? 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 Parameters Parameter Description User ID   IP Address   Override Event Time   Event Name (Required) Event Data Custom properties to add to your event Date type properties are converted to Mixpanel date format 'YYYY-MM-DDThh:mm:ss' Properties with empty values are skipped and not included Action - Update Profile - Set Parameters Parameter Description Ignore Last Seen Update   User ID (Required) IP Address   Override Update Time   Created   Phone Number   Last Name   Email   First Name   Full Name   Do Not Overwrite Existing Property Values (Set Once)   Action - Update Profile - Add Parameters Parameter Description Ignore Last Seen Update   User ID (Required) IP Address   Override Update Time   Add Data Specify properties to add a numerical amount to their existing value It is possible to decrement values by providing a negative amount Properties with empty values are skipped and not included Action - Update Profile - Append Parameters Parameter Description Ignore Last Seen Update   User ID (Required) IP Address   Override Update Time   Append Data Specify properties to append a value to their existing list of values Appending to a property that doesn't exist produces a new list with one element Properties with empty values are skipped and not included Action - Update Profile - Union Parameters Parameter Description Ignore Last Seen Update   User ID (Required) IP Address   Override Update Time   Union Data Specify properties to merge their values with the existing list on the user profile Properties must be of Array type in Data Layer Properties with empty values are skipped and not included Duplicate values are ignored Action - Update Profile - Unset Parameters Parameter Description Ignore Last Seen Update   User ID (Required) IP Address   Override Update Time   Unset Data Specify properties to permanently remove them and their values from a user profile Supports Array type in Data Layer Action - Update Profile - Delete Parameters Parameter Description Ignore Last Seen Update   User ID (Required) IP Address   Override Update Time   Action - Update Profile - Track Revenue Parameters Parameter Description Ignore Last Seen Update   User ID (Required) IP Address   Override Update Time   Transaction Amount (Required) Transaction Time (Required) Action - Create Alias Parameters Parameter Description Original User ID Previously set identifier for a user Typically a temporary generated ID before a better user ID becomes available (example: user's email after sign up) New Alias User ID New ID to map to original ID Typically an alias is set immediately after user signs up and all subsequent events & updates utilize the new alias ID For more info see: Using Mixpanel Alias ... 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: Affirm New marketplace tag: AudienceOne Discovery (Cookie Matching) New marketplace tag: RTB House Retargeting New marketplace tag: Snapchat New marketplace tag: Wunderman Segment Broadcasting Updated Adjuggler tag to reflect name branding change to Nui Media. Updated Adobe AppMeasurement tag to version 2.10.0 and VAPI to 3.3.0. Updated AT Internet tag tooltips and code to Version 5.12.0. Updated Amplitude tag to the latest library version and updated the set user property event order. Updated AudienceOne Discovery tag to rename aone_home_work parameter to aone_work_zip. Updated Baidu tag to include events, custom variables, and eCommerce tracking. Updated BrightRoll Conversion tag to OATH Ad Platforms Conversion due to rebranding. Updated CJ Affiliate tag to save cjevent in a cookie and make the configuration of a referral period optional. Updated default Google Ads pageview to a Conversion ID. Updated Fullstory tag snippet and added event to fire on links. Updated Google AdWords tag to   support multiple Google Ads Conversion IDs and Labels and multiple Google Analytics Tracker IDs. Updated Logicad tag to newest version. Updated new Taboola tag to include new events and deprecated older version of the tag. Updated Norton Guarantee Seal to set hash code as a configuration item. Fixes Corrected issue with ContentSquare UX Analytics tag to add validation for required parameters. Corrected issue with Mopinion tag that prevented proper initialization. Connectors New/Cool Stuff New marketplace connector: BlueKai (Learn more) New marketplace connector: Facebook Ads, Customer-Provided Credentials (Learn more) Updated Emarsys connector to support all editable field types available in Emarsys. (Learn more) Updated Selligent connector to include new actions: Add to Action List and Trigger Campaign. (Learn more) Fixes Added support for merge-fields date-formatting and product arrays. Corrected Experian CheetahMail connector issues with CB and REQ parameters and enforced validation for the existence of the associated email. Corrected volume issue related to missing Adobe event parameters in the Salesforce Email Studio (formerly ExactTarget) connector drop-down menu. Universal Data Hub New/Cool Stuff Updated Profile Settings field to "EventDB Retention Time" and the description to read "This determines how long EventDB data will be retained." Updated user interface to ensure that the Chrome tab displays the account name in the tab title when one or more instances of UDH are open in the Chrome browser. Updated user interface to set the default order of enrichments for a profile to match the order displayed in the interface. Fixes Corrected issue causing rules to be removed automatically when an associated enrichment is removed. iQ Tag Management Fixes Corrected display issue for variables in the user interface for the Data Layer tab. Corrected draft promotion process permissions issue with the JavaScript extension. Removed ES6 code in TiQ to prevent blocking for users of Internet Explorer (IE). Installations Fixes Added millisecond-precise timestamp to all hits from iOS Objective-C SDK. Applied minor bug fixes for Swift SDK. Applied minor fix to make RemoteCommand subclassable when using dependency managers, such as CocoaPods. Corrected WatchOS Objective-C issue causing tracking failure when completion handler is not specified. Updated Android device library to support POST data to event endpoint to allow the use of complex nested objects as data layers. Updated Android, Swift, and Objective-C SDKs to use a default 30 minute time out for teal_session_id. (Configurable)   ... View more

This article describes how to import CSV files as a data source, allowing offline data to become enriched and actionable within the Customer Data Hub. Before you begin: Preparing a CSV File for Import This guide has the following sections: How It Works Learn about the process of setting up a file import data source, uploading files, and the final results within the Customer Data Hub. Using the File Import Data Source Step by step instructions for setting up a file import data source. Import Status See how to check on the status of your file imports, including details metrics for number of rows processed and errors. In this article: Table of Contents Placeholder Prerequisites Your account must be enabled for AudienceStream How It Works The File Import feature provides the ability to import a CSV file to supplement online visitor profiles with valuable offline data. Using this feature, you can import a CSV file using a file transfer service, such as an Amazon S3 Bucket. The Tealium server connects to the file service, reads the file and ingests the data. Each imported row is processed as an event. Once ingested, the data can then be enriched, stitched to existing visitor profiles, and sent to other vendors. There are two components used in setting up a file import: a column mapping configuration and a file transfer service. CSV Column Mapping The column mapping configuration determines the event attributes that correspond to each column in the CSV file. The column names are often different from the attribute names in the Customer Data Hub, so this mapping ensures that the data is imported properly. For example, a CSV file might have a column named postalCode , but the matching event attribute is named customer_zip , so a column mapping is needed to associate the two. Mappings can be configured based on an existing event specification or as a custom event. Event Spec Mapping When a file import uses an event specification mapping, the event attributes are preselected and you specify the CSV column name that corresponds to each attribute. Each row is processed as an event of the selected specification, for example tealium_event = "purchase" Custom Mapping When a file import uses a custom event mapping, you specify the event attribute that corresponds to each CSV column. Each row is processed as an event with the following event identifier: tealium_event = "imported" File Transfer Service The file transfer service is a secure location where you upload the files to be imported. The following file transfer services are supported: Amazon S3 (Tealium bucket or your own bucket) Tealium uses VPC endpoints to access S3 buckets directly through the AWS network. Use IAM credentials to allow Tealium to access to your own bucket. Microsoft Azure File/Blob Storage FTP/SFTP If using your own file transfer service, be sure to have the connection details ready before proceeding. Workflow The order of operations for importing a file as a data source is as follows: Step 1 - Create a File Import data source Create a CSV file to import. (Learn more). Choose a file name related to the type of data to import, such as store_purchases . Upload a sample file to automatically detect the column names. Map the columns to event attributes. Configure a new file transfer service or assign an existing file transfer service to your file import data source. Step 2 - Upload a CSV file Manual Upload Drop a file into the upload area of the file import data source. File Transfer Service Upload files to the configured file transfer service. The system checks for new files every 10 minutes. File Import Process Once a file transfer service is assigned to a file import data source you will upload files to the service. The system then uses the following order of operations: Check for New Files The system checks the file transfer service for new files every 10 minutes. Copy New Files When a new file is detected, it is copied from the file transfer location and processed in the Customer Data Hub. Match Filename Prefix to File Import Data Source The prefix of the filename is used to identify which file import data source to use when importing the data in the file. Process Files The header line is read to identify the attributes being ingested. From there, the following processing is performed: Visitor Lookup The visitor ID is used for a lookup of the visitor record in AudienceStream. If an existing visitor record is not found a new one is created. Grouping rows with the same visitor ID will increase the speed of the import. Attribute Enrichment The visitor record will be enriched according to the attributes imported and the existing enrichments in your account. Using the File Import Data Source Setting up a file import data source requires that you prepare a CSV file, configure column mappings, and assign a file transfer service. Before you begin, create a sample CSV file (less than 1,000 rows) to use during the setup process. It will be used to automatically detect the column mappings. Use the following steps to begin setting up a file import: In the sidebar, select Sources > Data Sources. Click + Add Data Source. Add a File Import Data Source Upload a Sample File Configure Column Mappings Configure a File Service Adding a File Import Data Source Use the following steps to add a file import data source: In the sidebar, select Sources > Data Sources. Click + Add Data Source. Under Categories, click File Import and select the File Import platform. In the Name field, enter a unique name related to the file type and click Continue. Upload a Sample File The first step in setting up a file import is to upload sample CSV file. This will automatically detect the columns names in the file and pre-configure them on the column mappings screen. This step is optional and can be skipped by clicking Continue to go directly to the column mappings screen. Use the following steps to upload a sample file: Select a file. Click [Choose a file...] and select the file and click Open, or Drag and Drop a file directly onto the upload area. The Sample Preview displays the file contents in table format. Scroll through the sample file to verify that the columns and data look correct. The detected column names are listed in CSV format below the table and are pre-populated on the column mapping screen. If there are problems with the sample file, click Remove next to the uploaded file name and try another file. Click Continue to go to the Mapping screen. Configure Column Mappings The Mapping screen is used to indicate the type of data being imported and how to map the CSV columns to event attributes. Event Specification Each row of the CSV file is processed as an event. Use the drop-down menu to select which specification matches the data in the file, otherwise select Custom. This selection determines the value of the tealium_event attribute during the import process. If Custom is selected, tealium_event is set to "imported", otherwise it is set to the corresponding specification name e.g. "purchase". Changing the selected specification will reset the column mapping table. Column Mapping Table The column mapping table contains the following columns: Column Label from CSV The columns names from the CSV (pre-populated from the sample file) Date Formatter A date formatter for columns that contain date/time values. Event Attribute The event attribute to receive the data from that column. Sample 1 – Sample 3 Values from the sample file. Use the following steps to map each column to an event attribute: Enter or select a column name from the file (if not already pre-selected). Click the drop-down list in each Event Attribute column and select the event attribute you want that column to map to. Note each CSV column heading must be unique. Columns with date/time values must have a matching date format setting. Click the checkbox in the date column next to any column for which you need to customize the timestamp format. The default value is yyyy-MM-dd . An interactive menu displays that allows you customize the timestamp format for that column. Repeat the column mapping and date formatting steps for each column. Click the red "X" to left of any column you do not want to map to remove that column from the list. (Optional) Click the Enable Visitor ID Mapping in AudienceStream checkbox. Click Continue to advance to the Service Configuration tab. Configure a File Service The file transfer service is a secure location used you upload your files for Tealium to retrieve them. If you are using your own file transfer service, ensure that you have the connection details ready before proceeding. Tealium supports the following file transfer services: Amazon S3 (Tealium bucket or your own bucket) Microsoft Azure File/Blob Storage FTP/SFTP Use the following steps to add and configure your file transfer service: Select a service from the Choose File Service drop-down list. (Optional) If you do not have a file service set up or want to add a new service, click + Add New File Service. The Configure File Service dialog displays. Enter the File Service Name. From the Service drop-down list, select a supported file service from the list. Enter the credentials necessary to access the service you selected. If you selected Tealium S3 Bucket, the necessary credentials are generated for you automatically. Click Save to save this service for future use. Enter the File Name Prefix, such as ordercompleted. The prefix of the filename is used to identify which file import data source to use when importing the data in the file. In this example, the prefix is used to create a CSV file titled ordercompleted_VERSION.csv. Use the slider to Enable or Disable Service Processing for File Import. When set to ON, the file service is checked and files are processed every 10 minutes. Set to OFF if you are not ready to start processing files. You can enable the service later. Click Continue to advance to the Summary tab. Summary In this final step, you will view the summary, make any needed corrections, and then save and publish. View the Event Attribute Mappings. To make changes, click Previous twice to return to the Mapping tab to update. Click Finish to exit the configuration dialog. Your new data source now displays in the list of data sources. Click Save/Publish to save and publish your changes. Upload a File to a File Service The final step is to upload your CSV files, which is done outside of the product interface. To upload a file to a file service, a third-party application is required to initiate the upload. Though you may use any client for this purpose, Tealium recommends Cyberduck because it’s free and supports FTP and Amazon S3. When multiple files are uploaded at the same time using SFTP or S3, the files are processed in the order of the upload timestamp. Use the following steps to upload a file via FTP or Amazon S3 using Cyberduck: Install (or launch) Cyberduck. Create a new connection and give it a title. From the first drop-down list, select the file transfer service used in your File Transfer Service configuration. Enter the credentials (username and password) for your service. My FTP Connection and My SFTP Connection Tealium S3 Bucket – the credentials are pre-populated as an Access Key (username) and Secret Key (password). Provide other details, such as the server, path, port, etc, required by your service. Learn more about accessing third-party S3 buckets using Cyberduck. Save the connection. You are now ready to upload files by dragging and dropping your CSV files into Cyberduck. If you try to access an S3 bucket that is empty, the message "Listing directory / failed." may be displayed. The workaround is to add ".s3.amazonaws.com" to the end of the information in the "Path" field and then cut and paste everything from the "Path" field into the "Server" field instead (leaving the "Path" field empty). This is an issue only for when the bucket is empty; after that the normal set-up will work. When using SFTP, the file must be located in the root folder. Files cannot be located in the sub-folders of an SFTP connection. Check Import Status Once the file import data source is set up and has begun importing files, you can view the import activity from the Status tab. A rolling month report will display, with details about how many rows were processed, with and without errors, in graphical format. A tabular view displays directly underneath the graph. You can also see events imported from files on the Live Events screen by navigating to Live Events and selecting the File Import data source you want to view from the drop-down list. If an error occurs, hovering over the red area of a bar in the graphical display displays a breakdown of the errors. Tooltips will show common errors with a link to detailed report of all errors hosted in S3. Hover over any bar in the display to view details about the number of rows processed. FAQ This section addresses frequently asked questions (FAQs) about the feature described in this article. What if the file transfer service fails? If AudienceStream fails to copy a file using the file transfer service, it will retry in 10 minutes. What if the file fails to be processed? When a file process failure occurs, the file is ignored. The system will not attempt to process the file again. The most common reasons for failure are: The CSV file is improperly formatted and is therefore not a valid CSV file. The CSV file must be in UTF-8 format with no BOM encoding. Column names used in the file definition do not exist in the file A column name is used more than once in the File Service configuration Can files be encrypted with PGP/GPG? File import does not support PGP or GPG key encryption. Unencrypted or decrypted files prior to transfer in order for them to be uploaded successfully. Files are secured with native SFTP in transit, or native S3 in transit and at rest. Can files be compressed? File import does not support compressed (zipped) files. Extract (unzip) files prior to transfer in order for them to be uploaded successfully. ... View more

This article provides best practices for writing queries on EventDB and AudienceDB. In this article: Table of Contents Placeholder Query Best Practices This section provides an example of a "bad" query and describes how the query impacts results, and then provides best practice suggestions on how to create a "good" query with more efficient, meaningful results. Example of a "Bad" Query The following example shows a "bad" query, wherein the results are not as useful as they could be: SELECT * FROM events_view__all_events__all_events This query can impact your results in the following ways: Inefficient – This query does not include a where clause filter which will result in the entire table being scanned and returning much more data than is needed. Performance – Selecting all of the columns in a schema is an expensive operation, especially when using columnar databases such as Redshift. This query will take longer than necessary since, in most cases, all columns are not needed in the result set. Best Practices for a "Good" Query The following list suggests best practices for meaningful query results and provides code examples for each: Select Specific Columns Only select the columns that contain the data you are interested in analyzing: SELECT   "event - udo - referrer" FROM events_view__all_events__all_events Predicate Filter (WHERE Clause) Wherever possible, use predicate column filters to reduce the subset of data to be queried. SELECT   "event - udo - referrer" FROM events_view__all_events__all_events WHERE "event - udo - referrer" = 'google.com' AND "event - udo - page_name" = ‘Home’ Specify a Date Range Filter on date columns to limit the amount of data scanned. SELECT   "event - udo - referrer" FROM events_view__all_events__all_events WHERE "event - udo - referrer" = 'google.com' AND "event - time" BETWEEN ‘2018-07-01’ and ‘2018-07-31’ About Redshift Spectrum EventDB and AudienceDB are hosted on Amazon Redshift and Amazon Redshift Spectrum. This section describes issues that pertain only to Redshift Spectrum  databases . How do I know if I am on Redshift Spectrum or standard Redshift? Redshift Spectrum users have this additional schema, in addition to the standard account__profile schema.  account__profile__spectrum How does using Redshift Spectrum impact my data and query performance? Redshift Spectrum users connect to their Spectrum database in the same way that standard Redshift users connect to their databases. The differences are as follows: Redshift Spectrum user data is stored in S3 instead of within a physical Redshift cluster disk. Redshift Spectrum allows the customer to store and query large amounts of data in comparison to traditional Redshift database user storage. Some users, depending on their data size and query requirements, are hosted on Redshift Spectrum as opposed to standard Redshift. Redshift Spectrum table schemas have additional columns that are referred to as partition columns. How do I use partition column predicate filters? Partition columns, when queried appropriately, can vastly accelerate query performance when performing large scans on Redshift Spectrum databases. The following table provides query examples with partition column predicate filters for AudienceDB and EventDB: Environment Example AudienceDB SELECT col1, col2 FROM account__profile.visitors_view WHERE "visit - day" >= ‘2018-01-01’ SELECT col1, col2 FROM account__profile.visits_view WHERE "visit - day" >= ‘2018-01-01’ EventDB SELECT col1, col2 FROM account__profile.events_view__all_events__all_events WHERE "event - day" >= ‘2018-01-01’ Additional Vendor Information For additional vendor information about query best practices, see the following AWS documentation: Amazon Redshift Best Practices for Designing Queries Improving Amazon Redshift Spectrum Query Performance ... View more

The data supply chain dashboard provides a high level overview of your configuration, summary metrics of your usage, and status alerts that need attention. This article describes the information available in the dashboard and how to change the views. In this article: Table of Contents Placeholder How it Works The overview dashboard provides a comprehensive summary of the data supply chain of the Customer Data Hub. The dashboard uses three interactive panels to represent your data flow: Filters - adjust the dashboard view by product and by time period. Data Flow Summary - see summary metrics of your data flow and important status alerts. Data Flow Details - inspect specific components to see data connections and health status. Data Supply Chain Views The Data Supply Chain dashboard view changes depending on the product view and time period selected. To view, click to select a product and then use the drop-down list to select a time period. Most views contain the following information, with differences described in the product-specific sections below. Data Sources – quick link to data sources Events Received – quick link to live events Events Inspected – quick link to event specifications and summary metrics for event types All Products From the All Products summary view, select from the standard information listed in the overview or one of the following views: Actions Triggered – view the number of successful and failed connector actions Connectors – quick link to EventStream and AudienceStream connectors  EventStream From the EventStream summary view, select from the standard information listed in the overview or one of the following views: Enrichments Applied – quick link to attributes Active Feeds – quick link to feeds EventStream Actions Triggered – view the number of successful or failed EventStream actions EventStream Connectors – quick link to EventStream connectors AudienceStream From the AudienceStream summary view, select from the standard information listed in the overview or one of the following views: Visit Count – view the number of visitors in the time period selected Active Audiences – quick link to audiences AudienceStream Actions Triggered – view the number of successful or failed AudienceStream actions AudienceStream Connectors – quick link to AudienceStream connectors EventStore From the EventStore summary view, select from the standard information listed in the overview or one of the following views: EventStore Feeds – quick link to feeds Events Sent to S3 – view the number of events sent to your S3 bucket EventDB From the EventDB summary view, select from the standard information listed in the overview or one of the following views: EventDB Feeds – quick link to feeds Events Sent to Redshift – view the number of events sent to Redshift AudienceStore From the AudienceStore summary, select Data Sources or one of the following views: Active Audiences – quick link to audiences Visitors Sent to S3 – view the number of visitors sent to your S3 bucket AudienceDB From the AudienceDB summary, select Data Sources or one of the following views: Active Audiences – quick link to audiences Visitors Sent to RedShift – view the number of visitors sent to Redshift Additional Views and Navigation This section describes additional views and the interactions available within with the body of the interface. View Data Flow and Relationships Data relationships and data flow clearly displays in the lower portion of your screen. You can quickly view these relationships and the flow and drill down into the details of related items to edit. Expand and Collapse Expand or collapse the details for an item. Sort Results Use the up (▲) or down (▼) arrows to sort results by volume or whether an action fired successfully or failed to fire. View More Options Click on the More Options vertical ellipses (︙) to go directly to a data source, connector, or event feed to edit. View Errors and Warnings Hover over the warning icon to view error or warning messages and click an available Learn More link to read about how to solve the issue. ... 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 Added support for the Goal Currency mapping parameter for the Bing UET tag. New marketplace tag: Conversant New marketplace tag: Delacon Call Tracking New marketplace tag: GroupBy New marketplace tag: Holimetrix New marketplace tag: iAdvize New marketplace tag: SchemaApp Updated branding for Adobe ID Service and terminology (Marketing Cloud to Enterprise Cloud). (Learn more) Updated eCommerce default values for the LiveIntent tag and updated configuration parameters to allow mapping override for "name" for the purchase event. Updated Google Ads Cookie Matching Tag to support treating additional mappings as query string parameters. Updated Google Analytics tag to add support for Google AMP Client ID. Updated Google Marketing platform tag branding for Google AdWords, Analytics, and DoubleClick. Updated Pepperjam tag with track click ID query parameters, save in cookie, and send with pixel. Updated Rakuten Marketing conversion code for Safari Tracking Prevention. Updated SellPoints tag to current tag template patterns, updated base_url, and added a cache-busting query string parameter. Updated Sophus3 tag to newest version. Updated the AT Internet Smart Tag integration to allow alphanumeric Visitor IDs. Updated the IBM Digital Analytics tag to support the error tag (cmCreateErrorTag). Updated the script URL for the LightningBolt tag. Fixes Corrected issue with duplicate loading of Google Analytics, DoubleClick, and AdWords (gtag.js). Combined Google Analytics mapping labels for Event and Timing value. Updated Tealium Collect tag to address issue handling pipe-delimited lists of server endpoints. Updated the ClickTrack for AdForm tag call to only use the order data. Connectors New/Cool Stuff New   marketplace   connector:   AWS   Firehose   (Learn more) New   marketplace   connector:   Centro   DSP (Learn more) New   marketplace   connector:   Freshdesk (Learn more) New   marketplace   connector:   PersistIQ (Learn more) Fixes Corrected issue causing   SmartFocus   connector to send dynamic content without   MemberSync. Corrected the   sfdmp.json   file for the   Salesforce   DMP   (Krux) connector to make the connector available in EventStream. Deprecated EventStream non-mobile actions with default mappings for Google Analytics and Adobe Analytics and created actions with default mappings removed. Made AudienceStream connector visitor's current visit checks null safe due to delayed actions and Audience Sizing job actions having null current visits. Placed a temporary hold on the availability of the Zoho Mail connector from the marketplace until OAUTH2 is implemented. Temporarily hid the Floodlight   connector from the connector marketplace pending resolution of API limit issues and the ability to offer API batching. Universal Data Hub New/Cool Stuff Applied updates to ensure visitors using Trace do not skip end of visit processing due to early eviction. Fixes Corrected issue to not allow attributes to be added to event specifications when the values are generated by a data source. Corrected Trace-related browser console error when logging into   UDH. iQ Tag Management New/Cool Stuff Added static mapping support for marketplace tags. (Learn more) Built-in DOM variables now display in the UI on the Data Layer tab. (Learn more) Replaced in-product code editors with new, more flexible ace.c9.io editor. The Javascript extension now offers draft mode, scheduled promotion, a robust editor, and is integrated with the publish engine and permissions. (Learn more) Fixes Corrected duplicate JavaScript draft mode extension issue. Corrected issue in Consent Manager related to content definitions that disabled the ability to override user language selection. Corrected issue in which a JavaScript Code extension scoped to tag did not update utag.js timestamp for cache busting. Corrected issue with ES6 function inside utui.core.js to prevent blocking login for users logging in from older browsers. Installations New/Cool Stuff Added Mobile SDK support for Crash Data collect in iOS in preparation for UDH Connector support for end-to-end integration with New Relic. (Learn more) Updated iOS (Objective C) SDK to use HTTP Collect API (/event) in place of legacy vdata. ... View more

We recently identified some issues with how the Explicit Consent Prompt was handling tracking calls under certain conditions. This led to scenarios where extra tracking calls were being made or tracking calls were being permitted prior to consent. The latest release of this feature has addressed these issues. Who Is Affected Pages Using noview Option If you are using the utag override option, noview , then you might have experienced extra tracking calls. The explicit consent prompt was ignoring the noview option and triggering tracking calls based on the consent status. Since a page that uses the noview option typically triggers a tracking call based on other criteria, this often led to duplicate tracking calls. Event Tracking Prior to Consent If your page tracks additional events to the initial page load, then these might have been allowed even prior to acquiring consent. If the explicit consent prompt was actively displayed to the visitor, tracking calls that occurred at the same time were incorrectly allowed. How It Works Now The latest updates to the Explicit Consent Prompt include the following fixes: Explicit Consent Prompt will not trigger a tracking call if the noview option is enabled. If you previously implemented a work-around for this scenario, you should test the new behavior and make adjustments as needed. Tracking calls that occur while the consent prompt is active will be queued and handled appropriately after consent is received. These changes will be reflected upon your next publish. We always recommend that you publish to Dev or QA first to test your changes before promoting to Prod. ... 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 Added support for item-level basket reporting on the "Purchase" event when using the Google AdWords Conversion Tracking tag. New marketplace tag: Adobe Audience Manager New marketplace tag: Impact Universal Tracking New marketplace tag: SnapChat New marketplace tag: Teavaro New marketplace tags: Google Customer Reviews (Badge and Survey) Updated AT Internet tag to allow XTO parameter mappings for multiple categories. Updated Pinterest tag to include enhanced match. Updated the TRUSTe tag to TrustArc and added new GTM and CDN parameters. Fixes Corrected issues bundling multiple Doubleclick Floodlight (gtag.js) tags. Corrected link to Help Docs in the UI for the Currency Converter tag. Updated Google AdSense tag to address error when attempting to add advertisements. Updated Google gtag.js tags to resolve issues when bundling. Connectors New/Cool Stuff Implemented Mailchimp and Sendgrid as the first two push-based input connectors in UDH. (Learn more) New marketplace connector: Adobe Target New marketplace connector: CallRail New marketplace connector: CO-SENDER New marketplace connector: Krux (Salesforce DMP) New marketplace connector: Postways New marketplace connector: Square New marketplace connector: Streak New marketplace connector: Taplytics New marketplace connector: XiTi Analytics (AT Internet) The Centro connector is now hidden and not available from the connector marketplace due to the deprecation of the Centro s2s endpoint. The MediaMath connector is now deprecated and no longer available from the connector marketplace. Existing actions will remain functional with the addition of an informational message regarding deprecation. Updated Amazon Kinesis Data Streams (KDS) and Amazon Simple Queue Service (AWS SQS) connectors to enable TiQ data-sources. Updated DCM Floodlight Connector Setup Guide inline and TLC documentation. (Learn more) Updated Facebook connector API to current version. Updated Selligent connector to add support for linked lists.  ( Learn more ) Updated the Google DoubleClick Campaign Manager (DCM) Floodlight connector to add "api@tealium.com" as a user in their FL account and, as a result, no longer require user login. Fixes Corrected Adobe connector context data (XML) to be passed in the correct format. Universal Data Hub New/Cool Stuff Added button to UDH UI to allow user to scroll back to the top on the attributes tab. Added the ability to support persistent cookie-sync data for EventStream. (Learn more) Applied updates to optimize API Sampler performance. Made Universal data attributes available in the drop-down lists for the "Join Attributes" enrichment. Provided the ability to store DataCloud profiles in Amazon Aurora to aid in profile migration. Updated Audience Sizing language in UI to match new UDH user interface. Updated messaging in UDH to clarify configuration requirements for Visitor ID attributes in regard to visitor stitching. Updated ON/OFF toggle button colors in user interface to more easily discern toggle position. Updated the order of enrichments in the UI to honor the calculated sort order. Updated the UDH UI to allow easier selection of ADB attributes. Updated UDH UI to display secondary Visitor IDs in the Visitor API to assist users in determining the reason that a look up may not return the expected visitor. Fixes Corrected console error in UDH when clicking on duplicate icon for custom UDH attribute. Corrected issue in UDH to allow for the selection of more than one event specification. Corrected issue to allow Tealium Cookie Sync (TCS) cookie to insert values into events for PUT/POST collect calls. Removed whitespace from the end of attribute names and applied checks to ensure there is no additional whitespace prior to saving. Updated audience-level retention values to no longer require correction of visitorRetentionDays for existing profiles. Updated Product Feedback dialog to consistently render correctly on all screens. iQ Tag Management New/Cool Stuff Added Single Sign-On (SSO) support to FreshDesk from TLC. Applied post-deployment update to Cascading Style Sheet (CSS) for the new TiQ interface to correct minor cosmetic issues. Applied changes to mobile profiles to ensure that the Tealium Collect and the Tag Management modules cannot both be enabled at the same time. (Learn more) Installations New/Cool Stuff Integrated Privacy Manager for Android mobile library to streamline GDPR compliance for customer. ... View more

This version of the JavaScript Code extension is deprecated. Go to the new version of the JavaScript Code Extension. The JavaScript Code Extension is designed for implementing custom JavaScript code through Tealium iQ. It comes with a built-in code editor and configuration options for when and where to run the code. In this article: Table of Contents Placeholder Prerequisites Permission to Manage JS Code Extension: This permission is required to add or edit a JavaScript Code Extension in your account. utag version 4.38 or higher: This version provides support for the execution options under the All Tags scope. Upgrade to this version if you haven't already. How It Works The JavaScript Code extension give you the power to write custom code to be included in the files that load on your site. Depending on the scope of the extension the code either loads in utag.js or in a vendor utag.#.js file.  The code entered into the text box of the extension is included in the utag files just as it appears, but it's important to note that the code is run from an anonymous function wrapper,  like this: function(a, b) {     // content of JavaScript Code extension runs here } The parameters represent the following: a: indicates which tracking call was made "view" for utag.view() and "link" for utag.link(). b: a reference to the data object passed to the tracking call. While the JavaScript Code extension is very flexible and can be used for virtually anything you would want to accomplish within your tag management solution, it's important to understand the impact it could have on your account.  We strongly recommend that you try to use the other built-in extensions to accomplish your task before turning to the JavaScript Code extension. Please consider the following: Pros Fully customizable code can accomplish virtually anything that can be done in JavaScript. Faster and more familiar for developers that are used to writing front-end JavaScript. Cons Difficult for non-developers to understand and edit. More difficult to maintain over time. Prone to typos and logic errors. Variable names are hard-coded and therefore not updated if you change the name of a variable on the Data Layer tab. A changed variable name will not be propagated to the JavaScript Code extension (i.e. if you change the name of a variable you must also change all occurrences of that variable within JavaScript Code extensions.) Conditions Conditions add an extra layer of control on top of the Scope. You can apply any number of conditional statements, just like you would in the Set Data Values and Join Data Values Extensions, to control when the JavaScript Code extension will run. Execution Order and Run Once The JavaScript Code extension offers the following options for determining the timing of when the code will run (learn more order of operations in utag.js): Before Load Rules After Load Rules (default) After Tags Run Once after Load Rules Run Once before Load Rules Run Once after Tags By default, a JavaScript Code Extension runs for every tracking call, including in-page event tracking, which would potentially cause it to run more than once per page load. If you want to prevent multiple executions of your code, choose one of the Run Once options in the execution drop-down list. These options are only available in the All Tags scope and require utag v4.38 or higher. Before You Begin Here are a few things to be consider: Do not surround the code with <script> tags since the content of the text box will be included in a JavaScript file exactly as you enter it. If you are referencing a variable from the utag_data object (e.g. page_name or language), use b['VARIABLE']. (Learn more about the b object.) If you are referencing a variable defined in the tag template of the scoped tag (e.g. account_id or base_url), use u['VARIABLE'] . Configuration Steps Use the following steps to configure the JavaScript code extension: Go to the Extensions Marketplace and add the JavaScript Code Extension from the Advanced tab. Title: Enter a name for this extension. Scope: Choose from the following options: Preloader (does not support Conditions) DOM Ready All Tags Vendor Tag(s) Execution: This drop-down list is only available to the All Tags scope. Choose one of the following options: Before Load Rules After Load Rules (default) After Tags Run Once after Load Rules Run Once before Load Rules Run Once after Tags Enter your JavaScript Code in the editor. Condition (optional): Click Add Condition and create a conditional statement. The first drop-down list is populated with variables and the second drop-down list provides a list of evaluating operators. If you are running the conditional logic against a value, be sure to enter it in the text field. To apply multiple conditions, choose between the AND and OR logic. Use the + button inside the box for AND and the + button outside for OR.   Save and publish the changes.  Frequently Asked Questions (FAQ)  Why am I unable to add or edit the new JavaScript Code Extension? You do not have the Manage JS Code Extension permission in your Tealium iQ account. Contact your Tealium account administrator to obtain the permission. Why can't I select Preloader with Conditions? In the preloader state, the Data Layer is not yet populated and there is no utag data with which to evaluate the conditional logic. For this reason, the Conditions drop-down selections are greyed out when Preloader is selected. What's the difference between Preloader and Run Once Before Load Rules?  Both will cause the Extension to run once before the Data Layer is populated—except the Preloader does NOT support conditions. Be mindful of this caveat when configuring the Scope. ... 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: Krux Cookie Matching Service New marketplace tag: Nielsen DCR Video Browser SDK New marketplace tag: Norton Shopping Guarantee New marketplace tag: Radial 3DS New marketplace tag: Swaven New marketplace tag: Urban Airship Web Notify New marketplace tag: UserVoice New marketplace tag: Wiland Digital Solutions New marketplace tag : Nielsen Static Browser SDK Fixes Corrected feature and custom loop issue with Bazaarvoice tag. Corrected issue in the logic for filtering out mobile variables from the list of context data variables when using the Adobe Analytics AppMeasurement for JS tag. Corrected issue with Adform tag template to allow tracking in AJAX environments. Updated Eloqua tag template to run in AJAX environments. Updated LiveIntent tag to support custom event handling. Updated the Nanigans tag to pass data partner parameter, set a default for the value parameter if not already set, and applied general template updates. Set global variable with user consent selection for the Rakuten Marketing tag. Updated branding for Keen IO tag to Keen and added new logo. Updated Catchpoint Glimpse tag to Catchpoint RUM and matched to latest library. Updated CJ Affiliate tag to add support for capturing the CJEVENT parameter. Updated iSpot.tv Pixel tag to support cid parameter. Updated the endpoint for the Hubspot tag template. Connectors New/Cool Stuff New marketplace connector: Intercom New marketplace connector: Google Cloud Pub/Sub (to support JSON Web Token (JWT) auth for Service Accounts) Fixes Corrected character encoding issue for the Silverpop Engage connector. (Learn more) Corrected issues with Salesforce Email Studio connector related to Data Extension actions. (Learn more) Updated the Facebook "Create" tab API to accommodate the latest Facebook API changes. Updated "Keen IO" connector branding to "Keen". Updated the "Zoho CRM" connector name only to "Zoho Mail Connector". Universal Data Hub New/Cool Stuff Updated UDH UI to automatically sort labels alphabetically. Fixes Corrected issue in UDH to ensure reliable updates to the attribute type when updating a mapping drop-down field. Corrected issue with filtering by type or label in UDH. Corrected UI for pre-saved actions to allow adding new rows beside required fields. iQ Tag Management Fixes Added messaging to Collect tag in TiQ to communicate that this tag is essential to data collection and will load for any user that has not fully opted out. Corrected issue causing improper display of the Consent Manager default state in Preview mode. Corrected issue for visitors that are opted-in when the Consent Manager load rule value is false and created warning message for deleting related load rules. New/Cool Stuff User interface style updated to more closely match UDH, including the page headers, fonts, and buttons. Installations New/Cool Stuff Integrated Consent Manager for Swift SDK. (Learn more) ... 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. iQ Tag Management New/Cool Stuff Added support for returning JSON files from Hosted Data Layer. (Learn more) Extensions now offer publish location settings to control which environments they get published to. (Learn more) Updated Consent Preferences with a setting to control the default state for tag categories. (Learn more) Fixes Corrected hiding of consent category slider in TiQ. Corrected Internet Explorer (IE), Version 11 issue in opening Consent Management in TiQ. Corrected issue that caused all Tealium Generic Tags to fire, regardless of opt out settings, when multiple instances are in use and one is added to the omitted tags in Consent Manager. Corrected utag.js issue with a double line in Windows that resulted in a TiQ Consent Management error in the Preferences JavaScript. Removed tracking in Consent Manager for instances where explicit consent is not given. (Learn more) Updated hiding of consent logic modals in TiQ. Tags New/Cool Stuff New   marketplace tag: Commerce Connector New   marketplace tag:   Flashtalking Onetag New marketplace tag: IBM UBX Cookie Matching New  marketplace tag: Optimise Conversion New marketplace tag: Optimise Media Universal New   marketplace tag:   Qubit AuraNew marketplace tag: Radial Device Fingerprint New marketplace tag: Salesfloor New marketplace tag: Sprinklr Universal Pixel Updated Adobe Appmeasurement tag to support Version 2.9.0. Updated Kampyle branding to Medallia Digital and updated to new marketplace tag version. Fixes Updated the method used to pass the GTIN array to the Bizrate Insights Survey Solution tag. Added Order ID parameter and removed Tracker ID for TVPage tag. Corrected redirect URL for MIQ Capture tag. Deprecated previous Qubit tag. Corrected branding for the Perform Media marketplace tag. Corrected an issue where calls to utag.track() to fire a tag directly via UID were not honoring the OPTOUTMULTI cookie. Updated Google Analytics (gtag.js) support for product views and impressions containing either ID or Name. Connectors New/Cool Stuff New marketplace connector: AppsFlyer App Events New marketplace connector: AppNexus Audience Service (Beta) New  marketplace connector: Cordial New  marketplace connector: DialogTech New   marketplace connector: IBM Universal Behavior Exchange (UBX) Events (Learn more) New marketplace connector: Mailgun New marketplace connector: Moosend New  marketplace connector: Nexmo New  marketplace connector: PostUp New marketplace connector: Reply.ai New marketplace connector: Zoho CRM Updated Adobe Analytics connector to include automatic mapping of lifecycle and referrer. (Learn more) Updated Facebook Custom Audiences connector with additional mappings. Fixes Corrected a configuration issue with the new Twitter connector. Corrected issue with Mark IBM UBX connector when publishing events related to cart abandonment data in AudienceStream. Installations Fixes Updated the Tealium Cordova plugin to implement backward compatibility with old (Diamond Operator) Java versions. Universal Data Hub Fixes Corrected issue causing a problem in assigning universal variables to enrichments. Corrected issue in UDH where event attributes could be added to audience-based connectors. Corrected UDH attribute display issues when using the Firefox browser. Fixed bug preventing Visitor API from deleting a visitor when there is a pending delete request. New/Cool Stuff Deprecated Version 1 of the Universal Data Hub (UDH) user interface. Updated the UDH user interface for displaying the scope of  Visit, Visitor, and Event attributes. ... View more

Persistent cookie matching in EventStream is an enhancement to ensure that third-party cookie sync data is saved in a Tealium-owned third-party cookie and included in all subsequent event collection requests. In this article: Table of Contents Placeholder How It Works Persistent cookie matching works in conjunction with cookie matching tags that run in iQ. Cookie matching tags make a request to a third-party vendor to retrieve a user identifier. The third-party vendor sends the anonymous identifier back to the Customer Data Hub to be associated to the visitor. That visitor data is then returned back to the website through Data Layer Enrichment. This process allows server-side actions to tie visitors events across multiple domains. Here's how it works: In iQ, a specific vendor cookie matching tag is added. When it runs in the page, it sends a request to the vendor asking for the visitor identifier and providing a return endpoint to which it can be sent. The vendor then makes a request back to the Customer Data Hub with the requested identifier (cookie ID). In the Customer Data Hub, the cookie matching request is received and the identifiers is saved to a Tealium third-party cookie. In subsequent EventStream events collected, the third-party cookie values are made available as event attributes. This process continues until the cookie expires. The Tealium Cookie Sync (TCS) cookie is valid for one (1) year, or when reaching the storage capacity of 4093 bytes. As an example scenario, the interaction between a TiQ cookie matching tag and the vendor might translate into something like this: Tealium Cookie Matching Tag: “Hi, I’m Tealium, can you give me the visitor ID so that I can later tell you who this person is and something about them in a way you will understand?” Vendor: "Sure. Here you go, this is the Visitor ID." Tealium Cookie Matching Tag: "Thanks. I'll take the Visitor IDs you provided and persist them in the Customer Data Hub. As useful data emerges, I'll leverage the data to your benefit and return it to you to use as needed." Flow Diagram The following diagram describes the flow of data between the Tealium Customer Data Hub and the customer website. Standard Event Collection The Tealium Collect tag fires for actions that do not need cookie sync data. No third-party cookie sync data is attached at this point. Cookie Matching Requests (for each vendor) A cookie sync request is sent from the customer site to the vendor cookie matching service. Cookie Match Response The cookie sync services sends a "302" redirect to the customer site. Customer Data Hub Saves Cookie The cookie sync redirect received by the customer site is forwarded to the Customer Data Hub where the matched identifier is saved in the third-party Tealium cookie. Tealium Third-Party Cookie Updated The Customer Data Hub redirect back to the customer site sets the third-party cookie containing the synced identifier from the vendor. Event Collection with Persisted Cookies The customer site then sends Tealium Collect tag requests that contain the persisted cookie data. The collect tag waits for all (or a percentage or preset delay time) cookie sync tags to complete and then fires again with third-party cookie sync data to ensure that actions that rely on visitor identifiers can fire. Third-party cookie sync data is attached at this point. EventStream Actions In the final step, EventStream events now contain the persisted vendor identifiers as event attributes, which are then available to be mapped in connector actions. Supported Marketplace Tags The following table lists the callback method and callback formatting for Tealium marketplace tags that support the persistent cookie matching service: Callback Method Callback formatting Tag Name Calls Visitor Data (vdata) Uses a callback to make the vdata call. (u.callback, query param with callback name, takes a cookie value and sends it to vdata) Criteo Cookie Matching Service IBM UBX Cookie Matching Service intelliAd Cookie Matching Service Krux Cookie Matching Service Yahoo Cookie Matching Service (Hidden) The Trade Desk Cookie Matching Service Formatted (their url+vdata+query params) Xandr (formerly AppNexus) Cookie Matching Service Google Analytics Cookie Matching Service Krux Cookie Matching Service Sizmek Cookie Matching Service Does not call vdata Copies an ID from one cookie to another Adobe Analytics Cookie Matching Service Centro Cookie Matching Service DataXu Cookie Matching Service Google Cookie Matching Service for Doubleclick LiveRamp Realtime IdentityLink Pixel (formerly LiveRamp Cookie Matching Service) MediaMath Cookie Matching Service RadiumOne Cookie Matching Service Tapad Cookie Matching Service Add a Cookie Matching Tag Use the following steps to add a cookie matching tag: Log into iQ Tag Management (TiQ). In the left sidebar, go to the iQ Tag Managment > Tags. Click + Add Tag. In the left panel, click Cookie Match. A list of available marketplace tags supporting the cookie matching service displays. Click + Add next to the tag you want to add. Follow the onscreen instructions to configure your tag. Save and publish your changes. FAQs How do I update my tag to get the latest functionality? To verify that your tag is the latest version and contains the latest functionality, click on the tag and view the Tool Tips section in the left navigation panel. The Tips section will contain a notification if a newer version of the tag is available and instruct you to disable the current version and add the new tag from the tag marketplace. Learn more about adding and configuring tags from the tag marketplace. ... View more

Now that you have a basic understanding of how the product works, what data is required, and what to expect in terms of increased performance, you are ready to move on. Each of the articles referenced below are found in the Tealium Learning Center (TLC). These topics contain additional details about setting up and configuring various components of the system, page performance, and best practices. More Tealium iQ Tag Management Documentation Now that you know the basics about how to add tags, configure load rules and extensions, and verify your installation, it's time for more  advanced topics: Adding utag.js to your site Event Tracking An Introduction to the Data Layer Data Mappings Tag Marketplace Load Rules Master List of Extensions Saving and Publishing Managing User Permissions More Getting Started Guides Getting Started with Tealium EventStream Getting Started with Tealium AudienceStream Helpful Resources To get help, learn about new features, or view and share best practices, visit the following resources: Tealium Learning Center (TLC) A collaborative environment with participation from Tealium customers and product experts, monitored by Tealium staff and also home to our product documentation. Tealium Education The official site for on-site and on-demand learning, including various levels of certification. Tealium Support Desk The official site to submit tickets to the Tealium technical support team. ... View more

In this article: Now that you have successfully saved and published your changes, it's time to test and view the results on your site. You will learn how to install the Tealium tag and data layer and then use testing tools to verify that it's working. In this section you will: Learn about the Universal Data Object (utag_data) and Universal Tag (utag.js). Use the Code Center to get the installation code for your iQ Tag Management account. Use Web Companion to verify that the tag is loading. Install the Universal Data Object and the Universal Tag This step requires that you have access to edit the code of your website. Now that you have a basic tag configuration saved and published in your account, it's time to install the two components of the Tealium tag management solution: utag_data and utag.js . Both of these components should be installed on every page of your website. Universal Data Object (UDO) – utag_data The Universal Data Object (UDO) is a JavaScript variable named utag_data . It contains dynamic data from your web page. This object must be populated with the same variable names that you define in the Data Layer screen of the iQ Tag Management interface. Universal Tag – utag.js The Tealium Universal Tag is a JavaScript library called  utag.js . It contains the generated code necessary to load the configuration from your iQ Tag Management account on your website. Using the Code Center The Code Center in iQ Tag Management is where you get the code to install Tealium on your site. Use the following steps to get the code: Go to the user menu at the top-right of the screen and select Code Center. Find the universal data object code sample that looks like this: <!-- Tealium Universal Data Object --> <script type="text/javascript"> var utag_data = { page_name : "", page_section : "", page_category : "", page_subcategory : "", page_type : "" } </script> These variables should be populated dynamically by your web application framework. However, for this test, you can set static values. Copy this code and paste it into the HTML after the <body> tag of a test page on your site. Next, find the universal tag code that looks like this: <!-- Tealium Universal Tag --> <script type="text/javascript"> (function(a,b,c,d){ a='https://tags.tiqcdn.com/utag/your_account/main/qa/utag.js'; b=document;c='script';d=b.createElement(c);d.src=a; d.type='text/java'+c;d.async=true; a=b.getElementsByTagName(c)[0];a.parentNode.insertBefore(d,a) })(); </script> Copy the code and paste it into the HTML after the universal data object. This loads the Tealium tag asynchronously into the page. If you copy this code, you must change your_account to your actual account name. Otherwise, use the code from your Code Center that contains your account, profile, and environment. After your website code is updated, it's time to test.  Verifying with Web Companion Web Companion is a browser tool to help verify your installation. Launching this tool will show that the utag.js tag is loading properly on your site. To install and use the Web Companion bookmarklet: In iQ Tag Management, go to the user menu at the top right of the screen and select Web Companion. Click and drag the Web Companion button to your browser toolbar to create the bookmarklet. Navigate to your test page and click the Web Companion bookmarklet. If your code is working, the Web Companion window will display on the page like this, with the following information: Account – the name of your account. Profile – the name of the profile within your account  (default is "main"). Version – the name of the version of utag.js loaded on the page. Environment – the publish environment loaded. Last Published – the publish timestamp of utag.js. Tags – a list of tags loaded. If Web Companion doesn't load, double-check that you are testing a page that has the Universal Tag coded in it. Also check the browser console for any syntax errors that might be preventing the code from running. ... View more

Now that you have edited the configuration, it is important to understand how the save and publish process works and how to navigate your version history. This section explains the difference between Save and Save As, when to use publish environments, and how to view your version history. In this article: Saving When you add, edit, or delete an item in your configuration the interface displays orange visual cues to alert you of unsaved changes. If you logout or close your browser without saving, those changes are discarded. The following visual cues indicate unsaved changes: Sidebar Individual Items Save/Publish Button Save/Publish Button After you make changes the Save/Publish button becomes orange to indicate that you have unsaved changes. The drop-down displays a summary of the unsaved changes. Click an item to navigate to it. To save your changes, click the Save/Publish button to display the save dialog. Choose one of the following save methods: Save Changes are saved in the current version. You cannot revert to previous revisions of this version. Save As Creates a new version with a new title and preserves a copy of the previous version, allowing you to revert as needed. We recommend using Save As in most cases for the following reasons: You have the ability to roll back your changes to a previous version. The title gives each version a unique and descriptive name. It's a good idea to save often. If you're just making small, incremental changes, then choosing the Save option can help avoid clutter in your version history. Publishing When you save changes, you have the option to publish the changes to the Universal Tag (utag.js) by selecting a publish environment. Publish environments provide separate instances of the JavaScript file so that you can install one on your non-production environment and one on your live production site. This allows you to test changes before releasing them directly to your production site. When the publish is completed, the files in the respective publish environments are regenerated to include your new configuration. Publish Environments There are three publish environments to support a proper release cycle: Dev, QA, and Prod. Each environment uses a separate utag.js file for your different website environments. For example, use the file corresponding to the Prod environment on your production site: https://tags.tiqcdn.com/utag/your_account/main/prod/utag.js Use the file corresponding to the QA environment on your non-production sites: https://tags.tiqcdn.com/utag/your_account/main/qa/utag.js It typically takes a few minutes for the files to update on the CDN. There three default publish environments are: Dev An environment for developing new tags and features. QA An environment for testing and validation. Prod The environment of your live production site. Changes published to Prod are public-facing. Versions and Revisions View save and publish history by clicking Client-Side Versions from the sidebar. Your account history is organized into versions and revisions. Versions version is created when you use the Save As option. A version has a name and contains one or more revisions. This allows you to revert back to a previous version. Revisions A revision is created within the current version when you use the Save option. This is is typically used for minor changes. You cannot revert back to a previous revision within a version. Save and Publish To continue, return to the save dialog or relaunch it by clicking the orange Save/Publish button, then follow these steps: Select Save As. Enter a new title for the version you are creating, for example "Getting Started". Enter notes to describe your changes. Click the QA publish target. Click Save. Congrats! You just completed the first save and publish of your Tealium iQ account. This is tag management in action! The next step is to install the Tealium tag into your page code and verify that it's working. ... View more

Extensions provide a user-friendly interface to add customizations to your data layer and tags without the need for coding. Extensions are used for a variety of purposes, such as modifying data layer values, setting cookies, and even setting up click tracking. In this article: Scope The effects of extensions are either global or local, meaning they are applied to all tags globally or to individual tags. In iQ Tag Management, this setting is called Scope. Global Scope The effects of an extension apply to all tags. The scope is called "All Tags". Local Scope The effects of an extension only apply to a specific tag. The scope is called "Tag Scope". Order of Operations To get familiar with extensions, it is important to understand the order of operations of the main components of iQ Tag Management and when the "All Tags" scope occurs. The following is a simplified order of the operations that shows when the data layer is processed by each component. Page loads the following: Universal Data Object – utag_data Universal Tag – utag.js Universal Tag (utag.js) runs the following: Data Layer variables are evaluated (cookies, meta, query string, etc.) Load Rules are evaluated "All Tags" extensions run Tags run "Tag Scope" extensions run Tags fire There are two other global scopes called "Pre Loader" and "DOM Ready" that are used for more advanced scenarios. Also, within the "All Tags" scope there is an execution setting that provides more granular control for running tags before load rules or after all tags are loaded. Additional details about these settings can be found at the end of this guide. Now that you know a little about extensions, you can set up your first extension and see it in action. Add an Extension A common use for extensions is to set a default value for a data layer variable. This requires setting the value of a variable – but only if it does not already have a value. In this step you will use the Set Data Values extension to set page_name to the value of a built-in variable named document title – but only if page_name does not have a value. Use the following steps to add this extension: In the sidebar, select iQ Tag Management > Extensions. Click + Add Extension. Under the Standard Data tab, click + Add next to Set Data Values. In the Title field, enter Default Page Name to identify your extension. In the Scope field, keep the All Tags - After Load Rules (default) default value. Under Configuration, apply the following settings: Use the drop-down list in the Set field to select the Page Name variable. In the To field, select Variable. In the variables drop-down list, select document title . Under Condition, click Add Condition. Use the drop-down list to select the Page Name variable. In the next field, use the drop-down list to select is not populated. That's it! Your extension is configured. This extension ensures that if your data layer does not contain a value for the page_name variable, then the value of document title will be used instead. This is just one example of an extension. Be sure to explore the other extensions. The next step is to learn about of saving and publishing your work. ... View more