Tealium Learning Center

As part of our continued effort to prepare you for GDPR, we have released the AudienceStream Visitor Lookup Tool! This tool makes it easy to search for visitor records based on any of your Visitor ID attributes, and even satisfy GDPR data subject requests by deleting those records from the system. Read on to learn more. What's New? Located in the Tools section of the Universal Data Hub (UDH), the Visitor Lookup Tool offers two ways to access the powerful new visitor search API. The Search tab offers the ability to search for individual visitor records based on a known value of a Visitor ID attribute and the REST API tab gives you an overview of the behind-the-scenes API calls that make it all work. How Does It Work? The new Visitor Lookup tool is based on the Visitor ID attributes you've defined in your account. These are the values that uniquely identify your visitors. Simply choose the desired attribute and enter a value to search for. When a visitor profile is found the full JSON object of the record is displayed in the main viewing panel. The side panel offers a more user-friendly view of all the attributes assigned to that visitor profile. The REST API tab provides a useful guide for working with the API directly. The API can be used to implement your own GDPR compliance features. Learn more about the new features: Visitor Lookup Tool Visitor Lookup API   ... View more

This article describes how to set up the Silverpop Engage Connector in your Customer Data Hub account. Table of Contents Placeholder Supported Actions Action Name AudienceStream EventStream Insert/Upsert Visitor in Database ✓ ✗ Update Visitor in Database ✓ ✗ Insert Visitor into Contact List ✓ ✗ Insert/Upsert Visitor in Database and Add to Program ✓ ✗ Insert Visitor into Program ✓ ✗ Send Email using Custom Triggered Autoresponder ✓ ✗ Upsert Visitor in Relational Table ✓ ✗ 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 API Password Server Host: e.g. "api5.silverrpop.com" where "api5" is your pod number (do not include "http(s)://" protocol)  Action Settings - Parameters and Options Click Next or go to the Actions tab. It's where you'll set up Actions and trigger them. This section describes how to set up Parameters and Options for each Action. Action - Insert/Upsert Visitor in Database Parameters Parameter Description Database Name This is the target Database (not Contact List), it can be found by Logging into your Silverpop account Browsing to Data -> Databases Data Column(s) to Set Primary Key field(s) is required. "VISITOR_KEY" (Optional): when provided, allows specifying a visitor key to associate a contact to a previously unknown visitor when using the Web Tracking feature. "CONTACT_LIST_ID" (Optional): when provided, allows adding the new contact to the provided Contact List Id . Recipient Primary Key Column(s) to Lookup Required only if "Enable Recipient Database Column Update Criteria" is enabled. Also, to prevent errors, you need to have "Enable Upsert" option enabled. Either "RECIPIENT_ID" or Primary Key field(s) is required. "Email": As an API requirement, if Email column is set make sure to set OLD_EMAIL column also. Recipient Database Column(s) Criteria to Match Required only if "Enable Recipient Database Column Update Criteria" is enabled. All the specified criteria will be evaluated i.e. logical "AND" operation. Note: Using this option enforces an extra API call for database recipient lookup, use only when necessary. Action - Update Visitor in Database Parameters Parameter Description Database Name This is the target Database (not Contact List), it can be found by Logging into your Silverpop account Browsing to Data -> Databases Primary Key Column(s) to Lookup Either "RECIPIENT_ID" or Primary Key field(s) is required. "Email": As an API requirement, if Email column is set make sure to set OLD_EMAIL column also. Data Column(s) to Update Only fields that have the keyword "_tealium_as" in the custom field name are updatable. Ensure you have appended your custom column names with the keyword "_tealium_as" Recipient Database Column(s) Criteria to Match Required only if "Enable Recipient Database Column Update Criteria" is enabled. All the specified criteria will be evaluated i.e. logical "AND" operation. Note: Using this option enforces an extra API call for database recipient lookup, use only when necessary. Action - Insert Visitor into Contact List Parameters Parameter Description Contact List Name This is the Contact List (not Database), it can be found by Logging into your Silverpop account Browsing to Data -> Contact Lists Contact List's Corresponding Database This is the Corresponding Contact List"s Database, it can be found by Logging into your Silverpop account Browsing to Data -> Databases Primary Key Column(s) to Lookup Either Recipient ID or Primary Key field(s) is required. Please ensure, the contact to be added already exists in the Target Contact List's Corresponding Database. Action - Insert/Upsert Visitor in Database and Add to Program Parameters Parameter Description Database Name This is the target Database (not Contact List), it can be found by Logging into your Silverpop account Browsing to Data -> Databases Data Column(s) to Set Primary Key field(s) is required. "VISITOR_KEY" (Optional): when provided, allows specifying a visitor key to associate a contact to a previously unknown visitor when using the Web Tracking feature. "CONTACT_LIST_ID" (Optional): when provided, allows adding the new contact to the provided Contact List Id . Program Id Unique ID of the Program. Recipient Primary Key Column(s) to Lookup Required only if "Enable Recipient Database Column Update Criteria" is enabled. Also, to prevent errors, you need to have "Enable Upsert" option enabled. Either "RECIPIENT_ID" or Primary Key field(s) is required. "Email": As an API requirement, if Email column is set make sure to set OLD_EMAIL column also. Recipient Database Column(s) Criteria to Match Required only if "Enable Recipient Database Column Update Criteria" is enabled. All the specified criteria will be evaluated i.e. logical "AND" operation. Note: Using this option enforces an extra API call for database recipient lookup, use only when necessary. Action - Insert Visitor into Program Parameters Parameter Description Contact Id Unique ID of the Contact being added to the Program. Program Id Unique ID of the Program. Action - Send Email using Custom Triggered Autoresponder Parameters Parameter Description Autoresponder Mailing Send Id Required: This is the Autoresponder Id (not name). For this operation to work the autoresponder has to be custom triggered i.e. choose "Custom" option when creating the Automated Mailing Send and also use a Database as its "Contact Source" You can find the Autoresponder Id by going to your Silverpop account Autoresponder list"s page Opening the Autoresponder, and copying the value of the browser URL query string for "mailingId" e.g. https://engage5.silverpop.com/mailingsSummary.do?action=mailingSummary&mailingId=XXXXXXX Autoresponder's Corresponding Database This is the Database that was used when creating the selected Autoresponder. Corresponding Primary Key Column(s) to Lookup "RECIPIENT_EMAIL": is required. Also required (if the the database has a key other than "Email") is the Primary Key Column(s) of the Database used for this Automated Mailing. Action - Upsert Visitor in Relational Table Parameters Parameter Description Target Relational Table Required Upsert Data to Set Map column values to keys. Primary Key field(s) is required. Natively, if Silverpop can match the Primary Key, it will update the existing record, otherwise a new record is inserted. Note: this action supports multiple relational table insertions in One API Call. If you want to use this feature, configure the target column(s) to an AudienceStream List. Note: If the relational table column that is being configured is of Silverpop Column Type of "DATE" or "TIMESTAMP" and a value of AudienceStream Type of Date is assigned to it, this connector will automatically convert the date variable to the appropriate GMT dates, shown below. If any other AudienceStream Types are configured, please make sure to pass formatted data accordingly to prevent the API call failure. Silverpop Engage Relational Table API Expected Date Format: MM/dd/yyyy e.g. 06/18/2015 Silverpop Engage Relational Table API Expected Timestamp Format: MM/dd/yyyy hh:mm:ss e.g. 06/18/2015 10:57:06 ... View more

Google Analytics lets you do more than measure sales and conversions. It also gives insights into how visitors find and use your site, and how to keep them coming back. Learn more about your customers by bringing all of your data together so everyone in your organization can explore, gain intelligence, and inform strategies to increase business performance. This article describes how to set up the Google Analytics Connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Supported Actions Action Name AudienceStream EventStream Send Analytics Event Data ✓ ✓ Send Analytics Event Data (Mobile Optimized) ✓ ✓ Send Analytics Transaction Data ✓ ✓ Send Analytics Transaction Data (Mobile Optimized) ✓ ✓ Send Analytics Social Data ✓ ✓ Send Analytics Social Data (Mobile Optimized) ✓ ✓ Send Analytics Page View Data ✓ ✓ Send Analytics Screen View Data (Mobile Optimized) ✓ ✓ Send Analytics Timing Data ✓ ✓ Send Analytics Timing Data (Mobile Optimized) ✓ ✓ 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: Google Tracking Id: Required: The format is UA-XXXX-Y Action Settings - Parameters and Options Click Next or go to the Actions tab. It's where you'll set up Actions and trigger them. This section describes how to set up Parameters and Options for each Action. Action - Send Analytics Event Data Parameters Parameter Description Google Tracking Id Required if not configured in the Configuration Tab This will overwrite the value defined in the Configuration Tab if the value resolves to not empty The format is UA-XXXX-Y Measurement Parameters Map values to measurement parameters (see: Measurement Parameter Reference) Required: Client ID or User ID must be set Empty values are skipped and not included Following parameters are automatically set (if applicable): Hit Type, Client ID Custom Dimensions Map values to dimension indices between 1 and 20 ( 200 for Premium accounts) Custom Metrics Map values to metric indices between 1 and 20 ( 200 for Premium accounts) Event Tracking Data Required: map values to event parameters Enhanced E-Commerce: Product Action Specify action type of included products Required for all Enhanced E-Commerce sections Must be set to value of detail , click , add , remove , checkout , checkout_option , purchase or refund Enhanced E-Commerce: Action Data Map values to action transaction parameters (see: Enhanced E-Commerce Parameters) Transaction ID parameter is required if action type is purchase or refund Enhanced E-Commerce: Products Data Required: Either Product SKU or Name must be set if this section is configured Only Array type attributes are supported and must contain same number of elements productIndex corresponds to "Product Impression SKU or Name" array index Enhanced E-Commerce: Products Custom Dimensions Map values to product dimension indices between 1 and 20 ( 200 for Premium accounts) Only Array type attributes are supported and must contain same number of elements Enhanced E-Commerce: Products Custom Metrics Map values to product metric indices between 1 and 20 ( 200 for Premium accounts) Only Array type attributes are supported and must contain same number of elements Impressions Data Product Impressions represent information about a product that has been viewed Required: Either Product SKU or Name must be set if this section is configured listIndex corresponds to "Product Impression List Name" array index and defaults to 1 if empty Only Array type attributes are supported and must contain same number of elements Impressions Custom Dimensions Map values to dimension indices between 1 and 20 ( 200 for Premium accounts) Only Array type attributes are supported and must contain same number of elements Impressions Custom Metrics Map values to metric indices between 1 and 20 ( 200 for Premium accounts) Only Array type attributes are supported and must contain same number of elements Enhanced E-Commerce: Promotion Action Specify action type of included promotions Must be set to value of view or promo_click If not specified, default promotion action of view is assumed Enhanced E-Commerce: Promotions Data Map values to promotion parameters (see: Promotion Parameters) Only Array type attributes are supported and must contain same number of elements Action - Send Analytics Event Data (Mobile Optimized) Parameters Parameter Description Google Tracking Id Required if not configured in the Configuration Tab This will overwrite the value defined in the Configuration Tab if the value resolves to not empty The format is UA-XXXX-Y Mobile Measurement Parameters Map values to measurement parameters (see: Measurement Parameter Reference) Empty values are skipped and not included Following parameters are automatically set from Tealium Mobile UDO: Hit Type, Client ID, Application ID, Application Name, Application Version, Device Resolution, Device Language, Data Source Origin, Viewport Size, Screen Color, User Agent If a non Mobile Event or an Audience is the Source for this action, the above parameters will not be set and Client ID (cid) or User ID (uid) is required Custom Dimensions Map values to dimension indices between 1 and 20 ( 200 for Premium accounts) Custom Metrics Map values to metric indices between 1 and 20 ( 200 for Premium accounts) Event Tracking Data Required: map values to event parameters Enhanced E-Commerce: Product Action Specify action type of included products Required for all Enhanced E-Commerce sections Must be set to value of detail , click , add , remove , checkout , checkout_option , purchase or refund Enhanced E-Commerce: Action Data Map values to action transaction parameters (see: Enhanced E-Commerce Parameters) Transaction ID parameter is required if action type is purchase or refund Enhanced E-Commerce: Products Data Required: Either Product SKU or Name must be set if this section is configured Only Array type attributes are supported and must contain same number of elements productIndex corresponds to "Product Impression SKU or Name" array index Enhanced E-Commerce: Products Custom Dimensions Map values to product dimension indices between 1 and 20 ( 200 for Premium accounts) Only Array type attributes are supported and must contain same number of elements Enhanced E-Commerce: Products Custom Metrics Map values to product metric indices between 1 and 20 ( 200 for Premium accounts) Only Array type attributes are supported and must contain same number of elements Impressions Data Product Impressions represent information about a product that has been viewed Required: Either Product SKU or Name must be set if this section is configured listIndex corresponds to "Product Impression List Name" array index and defaults to 1 if empty Only Array type attributes are supported and must contain same number of elements Impressions Custom Dimensions Map values to dimension indices between 1 and 20 ( 200 for Premium accounts) Only Array type attributes are supported and must contain same number of elements Impressions Custom Metrics Map values to metric indices between 1 and 20 ( 200 for Premium accounts) Only Array type attributes are supported and must contain same number of elements Enhanced E-Commerce: Promotion Action Specify action type of included promotions Must be set to value of view or promo_click If not specified, default promotion action of view is assumed Enhanced E-Commerce: Promotions Data Map values to promotion parameters (see: Promotion Parameters) Only Array type attributes are supported and must contain same number of elements Action - Send Analytics Transaction Data Parameters Parameter Description Google Tracking Id Required if not configured in the Configuration Tab This will overwrite the value defined in the Configuration Tab if the value resolves to not empty The format is UA-XXXX-Y Measurement Parameters Map values to measurement parameters (see: Measurement Parameter Reference) Required: Client ID or User ID must be set Empty values are skipped and not included Following parameters are automatically set (if applicable): Hit Type, Client ID Custom Dimensions Map values to dimension indices between 1 and 20 ( 200 for Premium accounts) Custom Metrics Map values to metric indices between 1 and 20 ( 200 for Premium accounts) E-Commerce: Transaction Details Required: map values to transaction parameters (see: E-Commerce Parameters) E-Commerce: Item Details Item specific information for the transaction. Action - Send Analytics Transaction Data (Mobile Optimized) Parameters Parameter Description Google Tracking Id Required if not configured in the Configuration Tab This will overwrite the value defined in the Configuration Tab if the value resolves to not empty The format is UA-XXXX-Y Mobile Measurement Parameters Map values to measurement parameters (see: Measurement Parameter Reference) Empty values are skipped and not included Following parameters are automatically set from Tealium Mobile UDO: Hit Type, Client ID, Application ID, Application Name, Application Version, Device Resolution, Device Language, Data Source Origin, Viewport Size, Screen Color, User Agent If a non Mobile Event or an Audience is the Source for this action, the above parameters will not be set and Client ID (cid) or User ID (uid) is required Custom Dimensions Map values to dimension indices between 1 and 20 ( 200 for Premium accounts) Custom Metrics Map values to metric indices between 1 and 20 ( 200 for Premium accounts) E-Commerce: Transaction Details Required: map values to transaction parameters (see: E-Commerce Parameters) E-Commerce: Item Details Item specific information for the transaction. Action - Send Analytics Social Data Parameters Parameter Description Google Tracking Id Required if not configured in the Configuration Tab This will overwrite the value defined in the Configuration Tab if the value resolves to not empty The format is UA-XXXX-Y Measurement Parameters Map values to measurement parameters (see: Measurement Parameter Reference) Required: Client ID or User ID must be set Empty values are skipped and not included Following parameters are automatically set (if applicable): Hit Type, Client ID Custom Dimensions Map values to dimension indices between 1 and 20 ( 200 Premium accounts) Custom Metrics Map values to metric indices between 1 and 20 ( 200 Premium accounts) Social Interactions Required: map values to social parameters Action - Send Analytics Social Data (Mobile Optimized) Parameters Parameter Description Google Tracking Id Required if not configured in the Configuration Tab This will overwrite the value defined in the Configuration Tab if the value resolves to not empty The format is UA-XXXX-Y Mobile Measurement Parameters Map values to measurement parameters (see: Measurement Parameter Reference) Empty values are skipped and not included Following parameters are automatically set from Tealium Mobile UDO: Hit Type, Client ID, Application ID, Application Name, Application Version, Device Resolution, Device Language, Data Source Origin, Viewport Size, Screen Color, User Agent If a non Mobile Event or an Audience is the Source for this action, the above parameters will not be set and Client ID (cid) or User ID (uid) is required Custom Dimensions Map values to dimension indices between 1 and 20 ( 200 Premium accounts) Custom Metrics Map values to metric indices between 1 and 20 ( 200 Premium accounts) Social Interactions Required: map values to social parameters Action - Send Analytics Page View Data Parameters Parameter Description Google Tracking Id Required if not configured in the Configuration Tab This will overwrite the value defined in the Configuration Tab if the value resolves to not empty The format is UA-XXXX-Y Measurement Parameters Map values to measurement parameters (see: Measurement Parameter Reference) Required: Client ID or User ID must be set Empty values are skipped and not included Following parameters are automatically set (if applicable): Hit Type, Client ID Custom Dimensions Map values to dimension indices between 1 and 20 ( 200 Premium accounts) Custom Metrics Map values to metric indices between 1 and 20 ( 200 Premium accounts) Content Information Required: map values to page view document parameters Document Location URL or Document Host Name and Document Path must be specified Following parameters are automatically set: Document Location URL, Document Title, Document Referrer Enhanced E-Commerce: Product Action Specify action type of included products Required for all Enhanced E-Commerce sections Must be set to value of detail, click, add, remove, checkout, checkout_option, purchase or refund Enhanced E-Commerce: Action Data Map values to action transaction parameters (see: Enhanced E-Commerce Parameters) Transaction ID parameter is required if action type is purchase or refund Enhanced E-Commerce: Products Data Required: Either Product SKU or Name must be set if this section is configured Only Array type attributes are supported and must contain same number of elements productIndex corresponds to "Product Impression SKU or Name" array index Enhanced E-Commerce: Products Custom Dimensions Map values to product dimension indices between 1 and 20 ( 200 Premium accounts) Only Array type attributes are supported and must contain same number of elements Enhanced E-Commerce: Products Custom Metrics Map values to product metric indices between 1 and 20 ( 200 Premium accounts) Only Array type attributes are supported and must contain same number of elements Impressions Data Product Impressions represent information about a product that has been viewed Required: Either Product SKU or Name must be set if this section is configured "listIndex" corresponds to "Product Impression List Name" array index and defaults to "1" if empty Only Array type attributes are supported and must contain same number of elements Impressions Custom Dimensions Map values to dimension indices between 1 and 20 ( 200 Premium accounts) Only Array type attributes are supported and must contain same number of elements Impressions Custom Metrics Map values to metric indices between 1 and 20 ( 200 Premium accounts) Only Array type attributes are supported and must contain same number of elements Enhanced E-Commerce: Promotion Action Specify action type of included promotions Must be set to value of view or promo_click If not specified, default promotion action of view is assumed Enhanced E-Commerce: Promotions Data Map values to promotion parameters (see: Promotion Parameters) Only Array type attributes are supported and must contain same number of elements Action - Send Analytics Screen View Data (Mobile Optimized) Parameters Parameter Description Google Tracking Id Required if not configured in the Configuration Tab This will overwrite the value defined in the Configuration Tab if the value resolves to not empty The format is UA-XXXX-Y Mobile Measurement Parameters Map values to measurement parameters (see: Measurement Parameter Reference) Empty values are skipped and not included Following parameters are automatically set from Tealium Mobile UDO: Hit Type, Client ID, Application ID, Application Name, Application Version, Device Resolution, Device Language, Data Source Origin, Viewport Size, Screen Color, User Agent If a non Mobile Event or an Audience is the Source for this action, the above parameters will not be set and Client ID (cid) or User ID (uid) is required Custom Dimensions Map values to dimension indices between 1 and 20 ( 200 Premium accounts) Custom Metrics Map values to metric indices between 1 and 20 ( 200 Premium accounts) Content Information Required: map values to screen view parameters Screen Name must be specified Following parameters are automatically set: Screen Name Enhanced E-Commerce: Product Action Specify action type of included products Required for all Enhanced E-Commerce sections Must be set to value of detail , click , add , remove , checkout , checkout_option , purchase , or refund Enhanced E-Commerce: Action Data Map values to action transaction parameters (see: Enhanced E-Commerce Parameters) Transaction ID parameter is required if action type is purchase or refund Enhanced E-Commerce: Products Data Required: Either Product SKU or Name must be set if this section is configured Only Array type attributes are supported and must contain same number of elements "productIndex" corresponds to "Product Impression SKU or Name" array index Enhanced E-Commerce: Products Custom Dimensions Map values to product dimension indices between 1 and 20 ( 200 Premium accounts) Only Array type attributes are supported and must contain same number of elements Enhanced E-Commerce: Products Custom Metrics Map values to product metric indices between 1 and 20 ( 200 Premium accounts) Only Array type attributes are supported and must contain same number of elements Impressions Data Product Impressions represent information about a product that has been viewed Required: Either Product SKU or Name must be set if this section is configured "listIndex" corresponds to "Product Impression List Name" array index and defaults to "1" if empty Only Array type attributes are supported and must contain same number of elements Impressions Custom Dimensions Map values to dimension indices between 1 and 20 ( 200 Premium accounts) Only Array type attributes are supported and must contain same number of elements Impressions Custom Metrics Map values to metric indices between 1 and 20 ( 200 Premium accounts) Only Array type attributes are supported and must contain same number of elements Enhanced E-Commerce: Promotion Action Specify action type of included promotions Must be set to value of view or promo_click If not specified, default promotion action of view is assumed Enhanced E-Commerce: Promotions Data Map values to promotion parameters (see: Promotion Parameters) Only Array type attributes are supported and must contain same number of elements Action - Send Analytics Timing Data Parameters Parameter Description Google Tracking Id Required if not configured in the Configuration Tab This will overwrite the value defined in the Configuration Tab if the value resolves to not empty The format is UA-XXXX-Y Measurement Parameters Map values to measurement parameters (see: Measurement Parameter Reference) Required: Client ID or User ID must be set Empty values are skipped and not included Following parameters are automatically set (if applicable): Hit Type, Client ID Custom Dimensions Map values to dimension indices between 1 and 20 ( 200 Premium accounts) Custom Metrics Map values to metric indices between 1 and 20 ( 200 Premium accounts) Timing Map values to timing parameters Action - Send Analytics Timing Data (Mobile Optimized) Parameters Parameter Description Google Tracking Id Required if not configured in the Configuration Tab This will overwrite the value defined in the Configuration Tab if the value resolves to not empty The format is UA-XXXX-Y Mobile Measurement Parameters Map values to measurement parameters (see: Measurement Parameter Reference) Empty values are skipped and not included Following parameters are automatically set from Tealium Mobile UDO: Hit Type, Client ID, Application ID, Application Name, Application Version, Device Resolution, Device Language, Data Source Origin, Viewport Size, Screen Color, User Agent If a non Mobile Event or an Audience is the Source for this action, the above parameters will not be set and Client ID (cid) or User ID (uid) is required Custom Dimensions Map values to dimension indices between 1 and 20 ( 200 Premium accounts) Custom Metrics Map values to metric indices between 1 and 20 ( 200 for Premium accounts) Timing Map values to timing parameters ... 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. Connectors Fixes API calls for the Twilio connector now correctly pass data as query parameters instead of body parameters. Updated endpoint action for Twilio connector. New/Cool Stuff Added new marketplace connector, Braze to replace previous version of Braze connector. DCM Floodlight was originally released with only typed string attributes. This update adds support for any UDO attribute. New marketplace connector: ActiveCampaign New marketplace connector: CleverTap Updated Webhook connector to add additional helper functions, including SHA2. Tags New/Cool Stuff Added campaign tracking parameters to Google Analytics gtag.js mappings. Updated Bazaarvoice Pixel tag to vendor's latest version. Updated SMARTASSISTANT tag to vendor's latest version. New marketplace tag: Media IQ New marketplace tag: Outbrain New marketplace tag: Segment New marketplace tag: iSpot.tv New marketplace tag: Bidtellect New marketplace tag: Drawbridge New marketplace tag: FullStory Updated Adobe Analytics marketplace tag to allow mapping and combining of linkTrackVars and linkTrackEvents. (Learn more) Updated Cxense tag to support custom mappings. Updated method for creating the "s" object for the Adobe Analytics AppMeasurement tag. Updated OtherLevels tag library call to include appKey. Updated TVSquared tag to the vendor's latest version. Updated Zaius tag to the vendor's latest version. Fixes Corrected issue with Zanox (Awin) .ppl template to use current patterns and match the requested parameters. Resolved bug with Google Tag Manager and utag.js that involves GTags from sources other than Tealium. Updated Demandbase template to use correct API call. Updated Affilinet tag to adjust Product ID generation and query parameter mapping. Updated Content Square | UX tag to send custom variables to the correct mapped index. Updated Adform tag so that order tracking is no longer dependent on product IDs. Updated Monetate tag and related article to remove debug, and update logic and configuration options. iQ Tag Management New/Cool Stuff Created a new category for "Cookie Match" tags in the Tealium iQ Tag Marketplace. Preview release of the Consent Preferences Manager for your customers to control their tracking preferences (part of our GDPR compliance offering). Preview release of the Global Consent Preferences to help manage the deployment of our consent management features (part of our GDPR compliance offering). (Learn more) Fixes Added additional security on API calls that edit tag templates. Corrected an issue preventing proper update of Tag Marketplace Policy when new tags are added. Universal Data Hub New/Cool Stuff A pre-release of the event specifications for consent management in accordance with GDPR compliance (Learn more). Continued improvements to the navigation in Universal Data Hub. Corrected issue affecting the ability to retain labels when duplicating a rule. Updated AudienceStream dashboard to allow audiences to be clickable. Added new visit/visitor attribute types: Array of Strings, Array of Numbers, and Array of Booleans (Learn more). Fixes Corrected console error: "Uncaught TypeError: Cannot read property 'selectAll' of undefined." Fix links that jump from one area to another to correctly expand and scroll the item into view. ... View more

Consent events are used to collect user responses to tracking and data privacy prompts. In this article: Table of Contents Placeholder Overview Data privacy and tracking are important to consider when collecting visitor activity. These consent events identify how a visitor has interacted with the features offered in Tealium Consent Management.  These events can be found as event specifications under the category "Privacy". Consent events are used for auditing purposes and to enforce which connectors can run server-side. Learn more here: Consent Preferences: Server-Side Categories CCPA Consent Manager Consent Management: Event Logging Consent Change Events The following consent events use these parameters: Name Description Example policy The context of the consent, usually specific to the terms presented to the visitor upon gaining consent. Values: "gdpr" (opt-in), "ccpa"(opt-out) "gdpr" consent_categories The category names of approved types of tracking and data collection. ["affiliates", "social"] do_not_sell The list of tag IDs to be blocked from selling personal information. [1, 42, 51] grant_full_consent The grant_full_consent event indicates that the visitor has granted full consent to tracking and data collection. Opt-In Example { "tealium_event" : "grant_full_consent", "policy" : "gdpr", "consent_categories" : [ "analytics", "affiliates", "display_ads", "search", "email", "personalization", "social", "big_data", "misc", "cookiematch", "cdp", "mobile", "engagement", "monitoring", "crm" ], "tealium_visitor_id": "0184a9cef4ce000c9173745530e705075007706d00fb8" } Opt-Out Example (Explicit OK to Sell decision)   { "tealium_event" : "grant_full_consent", "policy" : "ccpa", "consent_categories" : [], "tealium_visitor_id": "0184a9cef4ce000c9173745530e705075007706d00fb8" }   grant_partial_consent The  grant_partial_consent event indicates that the visitor has only granted partial consent. For consent granted from the Consent Preferences, the event is accompanied by a list of category names that the user has consented to. For the consent granted from the CCPA Consent Manager, the event is accompanied by a list of IDs of the tags to be blocked from selling personal information. Opt-In Example { "tealium_event" : "grant_partial_consent", "policy" : "gdpr", "consent_categories" : ["affiliates", "social"], "tealium_visitor_id": "0184a9cef4ce000c9173745530e705075007706d00fb8" } Opt-Out Example (Do Not Sell decision) { "tealium_event" : "decline_consent", "policy" : "gdpr", "consent_categories" : [], "tealium_visitor_id": "0184a9cef4ce000c9173745530e705075007706d00fb8" } decline_consent This decline_consent event indicates that the visitor has declined consent to tracking and data collection. Opt-In Example { "tealium_event" : "decline_consent", "policy" : "gdpr", "consent_categories" : [], "tealium_visitor_id": "0184a9cef4ce000c9173745530e705075007706d00fb8" }   ... View more

Consent parameters are the variables used in the code that generates the consent prompt and preferences pop-ups. These parameters can be set at the account level to your profiles to inherit the same configuration. In this article: Table of Contents Placeholder How It Works The Consent Prompt Manager and the Consent Preferences Manager use parameters to represent translatable text that displays in the prompts. The prompts are generated using CSS, HTML, and JavaScript where these parameters are referenced using the syntax {{parameter_name}} . When the code is generated, each {{parameter}} is replaced by its configured value. These parameters and values can then be defined at the account level or in each profile. Additional languages can also be configured at the account level. This makes it easy to create translations of your parameters at the account level and make them available to all profiles within your account. Parameters are set separately for the Explicit Consent Prompt Manager and the Consent Preferences Manager. Managing Global Consent Resources The global consent resources are accessed from the user menu at the top-right of the screen. Only users with the Manage Account permission have access to this feature. Use the following steps to access the global consent resources: Click your user icon on the top right and select Global Consent Customization from the drop-down menu. The Global Consent Customization dialog displays. Select the tab for the feature you want to manage, Explicit Consent Prompt or Consent Preferences Dialog. Setting Parameter Values The consent features use the following built-in parameters: Title {{title}} The main heading of the prompt. Message {{message}} Your message to customers to inform them about your tracking intentions and links to other resources such as a privacy policy or contact form. Opt-in/Opt-out {{opt_in}} / {{opt_out}} The two options available: opt-in - grant consent opt-out - deny consent Confirmation Button {{confirmation_button}} The label on the submission button. Enter a value for any of these parameters and click Apply. Adding Custom Parameters Custom parameters can be added to further customize your prompts. These parameters can be referenced within the built-in parameters or within the CSS/HTML/JavaScript code. As a best practice, avoid putting translatable text directly in the HTML or JavaScript. Instead, customize the code with {{parameters}} and define that content using custom parameters. Use the following steps to add a custom parameter: Scroll down to the Custom Parameters section and click + Add Parameter. The Custom Parameter dialog displays. Enter a name for the parameter. Click Apply. The new custom parameter displays in the list. Enter a value for the new parameter. This value will be substituted where the parameter is referenced. Click Finish. Adding a Language The consent features are built with automatic language detection. The language setting is detected in the browser, for example, the two-character language code "de" for German. If the language detected is configured, this code presents the corresponding version of the prompt. The prompts are configured in English ("en") as the default. Use the following steps to add a language: To the right of Language in the side panel, click + Add. The Add Language dialog displays. Select the desired language from the drop-down list and click Apply. The new language displays under English (en) in the Language side panel. Click the new language to configure the content for that language. Enter the translated values in the parameter fields. If the new language will be the default language, check the Make Default Language checkbox. Click Finish. Save/Publish Workflow The global consent parameters are saved at the account level, therefore you do not need to save and publish to save your changes. To save the changes so that they are reflected at the profile level, you must save and publish the profile. The following steps describe the workflow for updating and publishing global consent parameters: In any profile, open the Global Consent Customization from the user menu. Make changes to the parameters and click Apply. It is not necessary to do a save/publish. Switch to the profile that you want to update. When the profile loads, the latest global consent parameters will be imported and the Save/Publish button will display in orange to indicate that unsaved changes are present. To preview the latest global changes, go to the Consent Management screen and click Preview. Verify the updates and close the preview window. Click Save/Publish and follow your normal release process for publishing to Dev/QA/Prod. Steps 3 – 5 must be performed for each profile that inherits the global consent parameters. ... View more

This article describes how to use Visitor Lookup in AudienceStream. Use this interface to find and delete active visitor profiles within the Customer Data Hub. In this article: Table of Contents Placeholder Overview Visitor Lookup is a graphical interface of the Visitor Lookup API. A visitor lookup uses a visitor ID attribute and a search value to locate a visitor record in the system. When a record is located, all the known attributes for that visitor are displayed for review. Visitor records can then be deleted. The interface also offers a REST API screen for demonstrating how the API works. Search Searching for a Visitor Record To find a visitor record, you will need a known value for one of the visitor ID attributes defined in your account. Use the following steps to perform a visitor lookup: Go to Server-Side Tools > Visitor Lookup. Select an attribute from the drop-down list. Enter a known value for the selected attribute. Click Search. If the visitor record exists, the results will display. Viewing a Visitor Record When a visitor record is located, the information is displayed in two panels: the attribute filter panel on the left and the main JSON object panel. JSON Object The main panel displays the raw JSON object of the visitor record. Each attribute data type is represented as keys in the object. Learn more about the fields available in the visitor object. Attribute Filter The left panel provides an attribute filter to adjust the list of attributes that are displayed. Use the Filter by menu to choose between displaying All Attributes or Assigned attributes. When choosing Assigned, only attributes that have an assigned value for the currently located visitor profile will be displayed. Click the heading for each attribute type to expand its list of attributes. Filter by All Attributes Filter by Assigned Attributes Deleting a Visitor When a visitor record is located, you have the option to delete it. This process can take up to 24 hours to complete and the action cannot be undone. Deleting a visitor record will permanently remove its data from all components of the Customer Data Hub. When you click Delete Visitor, a request is logged to our system to delete the visitor record and a transaction ID is returned to log the request. The delete request enters a queue and will be processed over the next 24 hours. If you search for the same visitor again and the record is not found, you will know the delete process has completed. The transaction ID can be used in the Visitor Lookup API to check the status of the request. REST API The REST API tab provides an interface to the Visitor Lookup API. The API calls are pre-formatted for you as examples of how to implement the same functionality in your application. Select the API call you want to make and adjust the placeholder values in the request URL. Each API call is available in the Request Types drop-down list. Select a request type to view the details of that API call. ... View more

This article describes the built-in variables that are part of the Universal Data Object generated by utag.js. In this article: Table of Contents Placeholder Overview The Universal Data Object (UDO) contains built-in variables that collect basic information about the page where it is loaded. These variables include cookies created by utag.js, standard DOM variables from the page, and Tealium-specific variables about the loaded configuration. Learn more about the types of data layer variables available. Built-In Variables Standard Page Data The following variables are generated from the standard JavaScript properties available in the web page. These variables appear automatically within the iQ interface for use with load rules, extensions, data mappings, and conditions. These values assume the URL of the page: http://www.example.com/path/file.html?param1=value1#hash=fragment Variable Description Example dom.domain The full domain of the URL. Source: location.hostname www.example.com dom.hash The hash fragment of the URL (excluding the # character). Source: location.hash hash=fragment dom.pathname The path of the URL, excludes the query parameters and domain. Source: location.pathname /path/file.html dom.query_string The full query string of the URL. Source: location.search  param1=value1 dom.referrer URL of previous page. Source: document.referrer   dom.title Text contained between the <title> tags. Source: document.title Test Page Name dom.url The full URL of the page. Source: document.URL http://www.example.com/path/file.html?param1=value1#hash=fragment dom.viewport_height The height of the browser view port. Source: window.innerHeight or document.documentElement.clientHeight 1320 dom.viewport_width The width of the browser view port. Source: window.innerWidth or document.documentElement.clientWidth 1278 Cookies The following variables are stored and maintained in a single cookie named utag_main .  They appear in the data object as separate variables, all prefixed with cp.utag_main_ . To add these variables to your iQ configuration, use the data bundle named Tealium Built-in Data from the Data Layer tab. Variable Description Example cp.utag_main__pn Session Page View Count The number of pages viewed in the current session. 2 cp.utag_main__se Session Event Count The number of events tracked in the current session. 2 cp.utag_main__sn Session Count The number of sessions for this unique visitor. 1 cp.utag_main__ss Is Start of Session A flag that indicates whether or not a page view is the start of a session. A value of 1 means yes and 0 means no. 0 cp.utag_main__st Timestamp The Unix/Epoch time stamp in milliseconds. 1522968400449 cp.utag_main_ses_id Session ID A unique identifier for the session. 1522965346545 cp.utag_main_v_id Visitor ID A unique identifier for each visitor. 016297481... (45 characters) Tealium Data The following variables contain information about the utag.js loaded in the page, along with other values used internally. The ut.* variables can be added to your iQ configuration using the data bundle named  Tealium Built-in Data  from the Data Layer tab. Variable Name Example tealium_account Account Name sandbox tealium_datasource Data Source Key   tealium_environment Publish Environment prod tealium_event Tealium Event Name Defaults to "view" or "link" if not set directly. view tealium_library_name Library Name utag.js tealium_library_version Library Version 4.44.0 tealium_profile Account Profile main tealium_random Random Number 7782219635308327 tealium_session_id Copy of utag_main_ses_id 1522965346545 tealium_timestamp_epoch Current Unix timestamp in seconds 1522956509 tealium_timestamp_local Local Timestamp 2018-04-05T12:28:29.019 tealium_timestamp_utc UTC Timestamp  2018-04-05T19:28:29.019Z tealium_visitor_id Copy of utag_main_v_id 016297481... (45 characters) ut.account Copy of tealium_account sandbox ut.domain The top level domain used for setting cookies. example.com ut.env Copy of tealium_environment prod ut.event Copy of tealium_event view ut.profile Copy of tealium_profile main ut.session_id Copy of tealium_session_id 1522956509018 ut.version The publish version (utag.js version + timestamp) ut4.44.201710171745 ut.visitor_id Copy of tealium_visitor_id 016297481... (45 characters) Sample The following is a sample of the built-in data found within utag.data. { "cp.utag_main_v_id": "015da2e1daf10020914ce74dfaf00207900780700093c", "cp.utag_main__sn": "389", "cp.utag_main__ss": "0", "cp.utag_main__st": "1522970376944", "cp.utag_main__se": "2", "cp.utag_main_ses_id": "1522915346545", "cp.utag_main__pn": "8", "qp.param1": "value1", "qp.hash1": "val1", "dom.referrer": "", "dom.title": "Test Page", "dom.domain": "www.example.com", "dom.query_string": "param1=value1", "dom.hash": "hash=fragment", "dom.url": "http://www.example.com/path/file.html?param1=value1#hash=fragment", "dom.pathname": "/path/file.html", "dom.viewport_height": 780, "dom.viewport_width": 1436, "ut.domain": "example.com", "ut.version": "ut4.44.201710171745", "ut.event": "view", "ut.visitor_id": "015da2e1daf10020914ce74dfaf00207900780700093c", "ut.session_id": "1522965346545", "ut.account": "sandbox", "ut.profile": "main", "ut.env": "prod", "tealium_event": "view", "tealium_visitor_id": "015da2e1daf10020914ce74dfaf00207900780700093c", "tealium_session_id": "1522915346545", "tealium_datasource": "abc123", "tealium_account": "sandbox", "tealium_profile": "main", "tealium_environment": "prod", "tealium_random": "7421526627003796", "tealium_library_name": "utag.js", "tealium_library_version": "4.44.0", "tealium_timestamp_epoch": 1522968576, "tealium_timestamp_utc": "2018-04-05T22:49:36.945Z", "tealium_timestamp_local": "2018-04-05T15:49:36.945" }   ... 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 (Cool Stuff) Changed branding of Appboy to Braze. (Learn more) (Cool Stuff) Updated the BloomReach tag to accommodate event mapping and the vendor's latest library. (Cool Stuff) Updated the Doubleclick tag to show sample of conversion ID format. (Cool Stuff) Updated Demandware logo to Salesforce Commerce Cloud logo. (Cool Stuff) New marketplace tag: Piano. (Cool Stuff) Updated our Movable Ink tag to the vendor's latest requirements. (Cool Stuff) New marketplace tag: Google Analytics (gtag.js). (Fix) Updated the etracker tag to the latest version. (Fix) Fixed an issue with Data Layer Enrichment in the Tealium Collect tag when used on a mobile app with third-party cookies disabled where returned visitor profiles were empty. Installations (Cool Stuff) Added support for using tealium.js in Node.js as an npm module called 'tealium-collect'. (Learn more) iQ Tag Management (Cool Stuff) Introduced the Tealium v2 API with managed API keys for stricter account control. (Learn more) (Fix) Fixed an issue with the profile switcher in Internet Explorer 11 where a new selection was not persisted. Universal Data Hub (Cool Stuff) Updated Trace to display event specification information about received events. (Cool Stuff) Updated EventDB to include query string attributes in the table schema. (Fix) Corrected an issue with the Google AdWords Customer Match connector where the UI would not provide success/failure feedback when creating a list. (Fix) Applied context-aware escaping to increase protection against Cross-Site Scripting (XXS) injection attempts. (Fix) Fixed an issue that caused UDH to reload when clicking the icon for a connector while editing it. (Fix) Applied escaping to label names to protect against Cross-Site Scripting (XXS) injection attempts. (Fix) Corrected an issue with UDH not properly respecting MFA enforced accounts. (Fix) Fixed an issue in Audience Discovery that incorrectly allowed individual badges to be selected as a view perspective. (Fix) Fixed an issue with Audience Discovery where cross-tab reports would not load. (Fix) Fixed an issue in Trace where an enriched timeline attribute was not displaying correctly. Connectors (Cool Stuff) Upgraded the Iterable connector to support more actions. (Cool Stuff) Updated the Adobe Analytics connector to support merchandising eVars. (Cool Stuff) Updated the Facebook Ads connector to use version v2.12 of the Marketing API. (Fix) Fixed an issue with the Webhook connector where actions no longer supported the multipart/form-data content type. (Fix) Fixed an issue with the Facebook Connector where the UDH could not authenticate with Facebook. (New Stuff) Updated the Bronto eCommerce connector to use their eCommerce REST API. (New Stuff) New marketplace connector: Heap (New Stuff) New marketplace connector: Elastic Email (New Stuff) New marketplace connector: Braze (formerly Appboy) (New Stuff) New marketplace connector: Drift (New Stuff) New marketplace connector: Vero (New Stuff) New marketplace connector: Swrve (New Stuff) New marketplace connector: Sendloop ... 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. Connectors New/Cool Stuff New Connector: Facebook Send API New Connector: WebEngage New Connector: dotmailer New Connector: Kochava New Connector: Zendesk New Connector: AppCues New Connector: Experian Marketing Suite (CCMP) New Connector: Listrak (ESP) New Connector: Google DCM Floodlight New Connector: Klaviyo Updated our Eloqua connector to support Upsert Custom Object Record by Contact action. Upgraded our Adwords Customer Match connector to the latest vendor API. Updated the Adobe Campaign connector to support self-hosted endpoints. Updated the Twitter connectors to the latest API version (v3). Updated ExactTarget connector branding to Salesforce Marketing Cloud, added IP whitelisting requirement, and added the ability to add and update multi-line records in Data Extensions. Fixes Corrected issues with our Adobe Analytics connector related to UTF-8 encoding of outgoing values. Fixed an issue in our Adobe Analytics connector related to merchandising eVars being transmitted as blank/empty. Universal Data Hub New/Cool Stuff User Management is now available in Early Access. The new Universal Data Hub UI is now the default interface, with the older UI only available for a limited time. Fixes Upgraded security protection related to cross-site scripting (XSS) on various components. Improved a warning message regarding invalid characters found in attribute names that gets displayed in the Save/Publish and DataAccess settings dialog. Fixed a display issue in the new UI where the "Save" dialog (no publish) was not visible. Corrected the sample code generated for the iQ Tag Management data source. Fixed a UI issue where HTML was incorrectly displayed in the name of an element. Implemented Cross-Site Scripting (XSS) protection in Add Enrichment > Enrich/Attributes. Tags New/Cool Stuff New Tag: Namogoo New Tag: Eyeview Digital New Tag: Adobe Analytics Cookie Matching New Tag: Userneeds New Tag: Mopinion New Tag: Google Analytics Cookie Matching for customers moving their GUA implementation off the page and into EventStream. New Tag: Nielsen Digital Content Ratings (DCR) Fixed an issue in our A8 tag related to the parsing of Yen amounts. Fixed an issue in our Google Universal Analytics (gtag.js) tag where the user_id parameter was not getting mapped properly. Fixed an issue in our LivePerson LiveEngage tag that prevented data from being sent to the vendor properly. Updated the YellowHammer with new data mappings for ecommerce and tracking ID. Updated Google Analytics tag to support nonInteraction exception events. Updated our Adobe Heartbeat tag to the latest vendor version (v2.0.2). (Learn more) Updated our AffiliateTraction tag to support the 'options' parameter. Updated our Conversion Logic tag to include offer code and customer type. Updated our Adobe AppMeasurement tag to version 2.7 and Visitor Service to 3.0. Updated the Tealium Collect tag to support additional regions. Updated VisiStat branding to KickFire LIVE Leads. Updated our Google Translate tag to prevent initialization of multiple Google Translate drop-downs. Updated our ClickTale tag to match vendor requirements. Updated tag names to differentiate "Yahoo!" and "Yahoo! Japan". Updated our Performance Horizon Event Tracker tag to version 1.0.0. Fixes Fixed an issue in our Google Universal Analytics (gtag.js) tag that preventing existing instances from being detected in some cases. Fixed an issue in our Adobe Marketing Cloud ID Service tag related to checking the DemDex cookie and prematurely triggering callbacks. Updated our Google Universal Analytics (gtag.js) tag to optimize for multiple instances of gtag.js. Fixed an issue in our Facebook Pixel tag related to failed tracking if the fbq object already exists in the page. (Learn more) iQ Tag Management New/Cool Stuff Released the Visitor API endpoint stubs in preparation for GDPR (Learn more). Released a preview screen for new Privacy Management tools. Fixes Fixed incorrect links to the API key documentation in the product and generated emails. Corrected an issue with tag-scoped extensions in a library not being inherited into profiles. Upgraded security protection related to cross-site scripting (XSS) on various components. Installations New/Cool Stuff Cordova 1.1.1: various fixes and enhancements. (Learn more) Fixes Corrected Android Library StrictMode policy violation error. Updated Tealium for Android with additional checks when opening a database connection in order to better handle errors. ... View more

The Consent Preferences Manager makes it easy to deploy a tracking preferences option to your website. Customers are able to specify which categories of tags they want to allow. This tools offers full access to customize the code that generates the preferences pop-up and the ability to translate content for your global customers. In this article: How It Works The Consent Preferences Manager works together with the Consent Prompt Manager to present tracking options to your customers and replaces the functionality previously offered by the Privacy Manager extension. The consent preferences manager groups tags in categories based on their function and purpose, such as "Analytics", "Display Ads", or "Email Marketing". These categories are presented to the customer and displayed as toggle buttons to allow or disallow that tracking to occur. For example, if a user opts out of the “Marketing” category, tags categorized in the marketing category are suppressed. If needed, customers can still access their preference selections about the types of tracking they allow by using the consent preferences pop-up. The Consent Preferences Manager automatically suppresses tags in opted-out categories from loading. Preferences pop-up example: The iQ Tag Management Consent Preferences Manager simplifies the creation and deployment of a tracking preferences prompt to your website using your existing installation. After published, add a simple JavaScript function call to your page code to trigger the pop-up. EventStream Consent Categories Changes in consent preferences are also honored by Tealium EventStream connectors. The consent category of a connector action is displayed on the action configuration screen: When a customer sets consent category preferences, they are included in subsequent server-side requests. Only connector actions in the categories that the customer has opted into are triggered. Example You have two connectors configured, one for "Analytics" and one for "Personalization". A customer grants partial consent in the preference form by allowing "Analytics" tracking but not allowing "Personalization". Only connector actions in the "Analytics" category are triggered. Any connector action categorized as "Personalization" is suppressed. AudienceStream Consent Category Tealium AudienceStream is categorized in the CDP consent category. In order for attributes and connectors to be processed in AudienceStream, the visitor must be opted into the CDP category. DataAccess Consent Category EventDB is categorized in the Big Data consent category. In order for event data to be stored in EventDB, the visitor must be opted into the Big Data category. AudienceDB is categorized in the CDP consent category. In order for audience data to be stored in AudienceDB, the visitor must be opted into the CDP category. Features The Consent Preferences Manager offers the following features: Display Templates Customizable Style and Layout Multi-Language Support Tag Categories All of the configuration is bundled with your existing installation of the JavaScript library (utag.js). After you activate and configure the preferences prompt, the changes are released in your next publish. JavaScript Code After enabled and published, the consent preferences pop-up introduces a JavaScript function into the utag namespace to allow you to integrate additional functionality. Use the following function to launch the consent preference dialog: utag.gdpr.showConsentPreferences() Displays the consent preferences pop-up. This function should be integrated into your site to provide visitors a way to change their consent preferences. Example: <a href="#" onClick="utag.gdpr.showConsentPreferences()">Consent Preferences</a> To set the language dynamically, pass a language code value to the function. This overrides both the window.utag_cfg_ovrd.gdprDLRef configuration and the browser detection logic. Examples: utag.gdpr.showConsentPreferences('de-DE'); // German/Germany utag.gdpr.showConsentPreferences('fr'); // French Setting up the Consent Preferences Manager The Consent Preferences Manager is configured using the following tabs: Content This tab is used to enter the message displayed to your customers, add multiple language translations, and provide your company's logo URL and privacy policy link. Customization From this tab, customize the design and layout of your prompt by editing the CSS, HTML, and JavaScript used to display the pop-up. Categories In this tab, group your tags into categories based on their purpose or function. Options This tab allows you to adjust additional options, such as logging consent changes using DataAccess or marking non-tracking tags that are not governed by consent management, for example, a chat widget. Global Settings The Consent Preferences Manager is configurable for multiple profiles simultaneously when using global settings. This allows you to configure the preferences pop-up at the account level and have each profile inherit the global configuration. Learn more about global consent content. Getting Started Use the following steps to begin setting up the Consent Preferences Manager: In the left sidebar, go to Client-Side Tools > Consent Management.In the Consent Preferences Dialog section, click Get Started to launch the configuration modal. If your prompt is already set up, toggle it on or off from this screen. Content Use the Content screen to customize the message displayed in the preferences pop-up, add languages for translated content, define custom parameters, and see a preview of the pop-up. The pop-up is templatized so that the content is separated from the code. The code uses parameters to substitute content using placeholder parameters. Parameters are referenced using the format: {{parameter_name}} . The standard built-in content parameters are: Title {{title}} The main heading of the consent prompt. Message {{message}} Your message to customers to inform them about your tracking intentions and links to other resources such as a privacy policy or contact form. Opt-in/Opt-out {{opt_in}} / {{opt_out}} The two options available: opt-in - grant consent, opt-out - deny consent. Confirmation Button {{confirmation_button}} The label on the submission button. To edit the content of the standard parameters, modify the text fields and click Finish. Sample HTML code with parameters: <div class="example_body"> <div class="privacy_prompt"> <div class="privacy_prompt_content"> <h1>{{title}}</h1> <p>{{message}}</p> </div> <div class="privacy_prompt_footer"> <div class="button right">{{confirmation_button}}</div> </div> <div class="close_btn_thick"></div> </div> </div> Custom Parameters Add custom parameters to further customize the pop-up. Custom parameters are referenced within the standard parameters or in the CSS/HTML/JavaScript code. Best Practice: Avoid putting translatable text directly in the HTML or JavaScript. Instead, construct the code with {{parameters}} and define the values using custom parameters. To add a custom parameter: Click + Add Parameter. The Custom Parameter dialog displays. Enter a name for the parameter. Click Apply. The new custom parameter displays in the list. Enter a value for the new parameter. This value is substituted any place that the parameter is referenced. Click Finish. Languages The preferences pop-up is built with automatic language detection. The browser's language setting of the browser is detected (two-character language code, for example 'de' for German) and the pop-up presents the corresponding version of the content (if that language has been configured). The preferences pop-up is configured in English (en) as the default. You are able to override the language with a value provided in the data layer (provided it is in the ISO format). Add this code as a preloader extension. This tells the Consent which variable to use to switch the language. This affects the language shown for both explicit and preferences manager. window.utag_cfg_ovrd = window.utag_cfg_ovrd || {}; window.utag_cfg_ovrd.gdprDLRef = "<some data layer var e.g. meta.lang/page_lang>"; Use the following steps to add a language: In the Language side panel, click + Add. The Add Language dialog displays. Select the desired language and click Apply. The new language displays in the Language side panel. Click the new language to configure its content. Enter the translated values in the standard parameter boxes (Title, Message, and Confirmation button). Click Finish. Set a default language by checking the box named Make Default Language located in the language title bar. The default language is used to display the preferences pop-up when the customer's detected browser language does not have a matching language configured in the consent prompt manager. Preview Preview your configuration by clicking Preview from the language title bar. Customization (CSS, HTML, JavaScript) On the Customization screen, the code appears behind the consent prompt – the CSS, HTML, and JavaScript that runs the prompt. This code is editable to adjust the look and design of the pop-up to match your website. Categories When a user opts out of a category, tags in that category are suppressed automatically by the consent preferences manager. Customers can access their preference selections by clicking a link that you provide using the consent preferences JavaScript. On the Categories screen, you can adjust the categories that tags are grouped into. Use the following steps to adjust a tag category: Select a category from the sidebar. The list of tags displays in the main panel. Click the drop-down list and select a new category for the tag. Click Finish. To omit a category from displaying in the pop-up list that displays to the customer, toggle the switch to Off. To display a category in the customer's pop-up display, toggle the switch to On. Options On the Options screen, configure the Tealium cookie behavior and tags to omit. Cookie Preferences Select whether or not to retain the Tealium cookie. This setting overrides any other preferences that disable tracking. The Tealium cookie is used for visitor, session and timestamp information. It addition, it is used with the Persist Data Values extension to store custom values. Default State for Categories This setting applies to two (2) scenarios where a default state for the categories is needed: Explicit consent prompt is active but the customer ignores it When the consent preferences modal is shown the default state for categories is used. On Categories are enabled by default in the preferences modal until the customer makes changes, but tracking follows the consent prompt policy until the customer gives consent. Off Categories are disabled by default in the preferences modal until the customer makes changes, but tracking follows the consent prompt policy until the customer gives consent. Explicit consent prompt is inactive and the customer has not set preferences The default state for categories determines if tags should fire. On Tracking occurs until preference categories are disabled Off Tracking is suppressed until preference categories are enabled Tag to Omit Not all tags deployed via iQ Tag Management are for tracking or data collection. Tags and extensions are also used to serve site functionality, such as pop-up modals, product feedback, site support, or chat clients. Use the Tags to Omit setting to create a list of tags to be exempted from the consent preferences pop-up. ... View more

The Explicit Consent Prompt Manager makes it easy to deploy a prompt to your website to allow users to opt-in or opt-out of tracking. This tool offers full access to customize the code behind the scenes as well as offers translated content to global customers. This feature replaces the functionality previously offered by the Privacy Manager extension and is part of our consent management features designed to help you stay compliant with GDPR. In this article: How It Works The Explicit Consent Prompt Manager works together with the Consent Preferences Manager to present tracking options to your customers. A consent prompt notifies your customers about your desire to track their activity on your digital property and to acquire their consent. Explicit consent is a proactive approach in encouraging your customers to opt-in or opt-out by forcing a pop-up prompt until a selection is made. If a customer opts-out, the website suppresses all tracking activity and cookie storage that is not directly relevant to the digital experience. If the customer opts-in, the website can track the user behavior (commonly using third-party services). Explicit Consent Prompt example: The Explicit Consent Prompt Manager in iQ Tag Management makes it easy to create and deploy a consent prompt to your website using your existing installation. This feature can be used with the Consent Preferences Manager to offer your customers more granular control over how they are tracked. The Explicit Consent Prompt satisfies a requirement of the General Data Protection Regulation that a data subject (EU residents) must give explicit consent before activity can be tracked. Visitor Experience After you deploy to your website using the standard iQ JavaScript container ( utag.js ), the consent prompt operates automatically – no additional coding is needed for the consent prompt to function. The prompt behavior is based on the configured load rule and the presence of a consent cookie. The prompt is triggered automatically on pages matching the load rule if that cookie is not detected. After a response to the prompt is submitted (for example, the visitor selects "Opt-in" or "Opt-out"), the consent cookie is created and subsequent page views do not trigger the consent prompt. The consent prompt can be displayed programmatically using the JavaScript helper functions. Features The Explicit Consent Prompt in Tealium iQ offers the following features: Display Templates Customizable Style and Layout Multi-Language Support Configurable Display Condition Global Settings for Enterprise Rollout Consent Logging (requires DataAccess or EventStream) This feature does not require additional code on your site. All of the configuration is bundled with your existing installation of our JavaScript library (utag.js). After you configure and activate the consent prompt, the changes are released in your next publish. Steps The Explicit Consent Prompt is set up using the following screens: Content Use this screen to enter the message displayed to your customers, add multiple language translations, and provide your company's logo URL and privacy policy link. Customization Customize the design and layout of your prompt by editing the CSS, HTML, and JavaScript used to display your prompt. Display Rule Use your data layer to create a load rule that determines when to display the consent prompt. Options Adjust additional options, such as logging consent changes using DataAccess or marking non-tracking tags that are not governed by consent management, such as chat widget. Default Consent Categories (JavaScript Code Extension) (when Consent Preferences is disabled) If you do not use the Consent Preferences Dialog and have a server-side product enabled (EventStream, AudienceStream, or DataAccess), then this JavaScript Code extension is required to set the default consent categories. If you skip this step, incoming events might be ignored. Global Settings The Explicit Consent Prompt can be configured for multiple profiles simultaneously when using the global parameters setting. This allows you to configure your consent prompt at the account level and have each profile inherit that configuration. To learn more, see Managing Global Consent Content. Getting Started Use the following steps to begin setting up the explicit consent prompt: In the left sidebar, go to Client-Side Tools > Consent Management. In the Explicit Consent Prompt section, click Get Started to launch the configuration. If the Explicit Consent Prompt is already set up, you can toggle it on or off from this screen. Content On the Content screen, customize the message displayed in the consent prompt, add languages for translated content, define custom parameters, and view a preview of the prompt you created. Content Parameters The Explicit Consent Prompt uses parameters to construct the final prompt that displays on your site. The prompt is templatized so that the values of the parameters can be easily substituted. Parameters are referenced using the format: {{parameter_name}} . The standard built-in content parameters are: Title {{title}} The main heading of the consent prompt. Message {{message}} Your message to customers to inform them about your tracking intentions and links to other resources such as a privacy policy or contact form. Opt-in/Opt-out {{opt_in}} / {{opt_out}} The two options available: opt-in - grant consent opt-out - deny consent Confirmation Button {{confirmation_button}} The label on the submission button. To edit the content of the standard parameters, modify the text fields and click Finish. Sample HTML code with parameters: <div class="example_body"> <div class="privacy_prompt"> <div class="privacy_prompt_content"> <h1>{{title}}</h1> <p>{{message}}</p> </div> <div class="privacy_prompt_footer"> <div class="button right">{{confirmation_button}}</div> </div> <div class="close_btn_thick"></div> </div> </div> Custom Parameters Custom parameters can be added to further customize the prompt. These parameters can be referenced within the standard parameters or in the CSS/HTML/JavaScript code. Best Practice: Avoid putting translatable text directly in the HTML or JavaScript. Instead, construct the code with {{parameters}} and define the values using custom parameters. Use the following steps to add a custom parameter: Scroll down to the Custom Parameters section and click + Add Parameter. The Custom Parameter dialog displays. Enter a name for the parameter. Click Apply. The new custom parameter displays in the list. Enter a value for the new parameter. This value are substituted where the parameter is referenced. Click Finish. Languages The consent prompt can be displayed in multiple languages. For each language you add you must provide the translations for each content parameter and custom parameter. The consent prompt detects the language setting in the visitor's browser (two-character language code) and displays the corresponding version. If the detected language is not configured, the default language is displayed. Add a Language To add a language: In the Language side panel, click + Add. Select the desired language and click Apply. The new language displays in the side panel. Click the new language to enter translated text for all content parameters and custom parameters. Set the Default Language The default language is used to display the consent prompt when the user's detected browser language is not configured. To set a default language: Check the Make Default Language box located in the language title bar. Click Preview to view your language configuration. Override the Language You can override the consent manager language setting with a data layer variable by using the Universal Tag settings override object. Specify the name of the data layer variable which stores the language to be used in the consent manager. For example, if your data layer contains a variable named site_language : window.utag_cfg_ovrd = window.utag_cfg_ovrd || {} window.utag_cfg_ovrd.gdprDLRef = "site_language"; Do not set the two-character language code directly. This override setting expects a variable name, not a language code value. Customization (CSS, HTML, JavaScript) On the Customization screen, the code is behind the consent prompt – the CSS, HTML, and the JavaScript that runs the prompt. This code can be edited to adjust the look and design of the prompt to match your website. The JavaScript code is minified before it is published into the utag.js file. If the minification process fails for any reason (such as a syntax error), the publish process halt and return a warning message in iQ. Upon successful publish, when utag.js executes on the page, the consent prompt JavaScript code is injected into the <head> of the page. Display Rule On the Display Rule screen, select the load rule to determine when to load the consent prompt and display it to customers. To comply with GDPR regulation, the consent prompt must be presented to data subjects residing in the European Union (EU). You can select an existing load rule or create one to satisfy that criteria. If you are unsure, a guide is offered to generate a load rule for you. GDPR Load Rule Creation Guide The GDPR load rule creation guide is a series of questions about your website, domain, and data layer that generates the best load rule for the consent prompt. The questions are designed to determine the easiest way to identify your EU visitors using the data available in the data layer. The guide has pre-built the list of EU country names and generates the conditions needed to detect them all in one load rule. Identifying EU data subjects can be accomplished the following ways: Domain, Subdomain, or Pathname If your iQ profile is loaded on a website that is dedicated to EU citizens or your business only operates within the EU, then the domain, subdomain, or pathname of the URL likely contains a country code that can be used in a load rule. Examples: de.example.com , www.example.de , www.example.com/de Data Layer Country Variable If your iQ profile is loaded on a website that allows visitors to choose their country or language, then this information can be represented in the data layer and used to create a load rule. Examples: utag_data.country_code = "de" If you skip the load rule creation guide, you can create your own load rule or, if your iQ profile is loaded on a site entirely dedicated to serving EU citizens, you can use the default load rule, "All Pages". Options From the Options screen, you can enable event logging and tags to omit. Event Logging The event logging option requires DataAccess (EventStore or EventDB) or EventStream and logs every consent action taken by your visitors. These consent actions can then be logged to EventStore, EventDB, or EventStream. Each time a visitor grants or revokes consent using the consent prompt, the action is logged for auditing purposes. This option is offered to help you comply with Recital 42 of the GDPR, which requires that proof of consent be available for auditing purposes. In addition, the event logging option provides you with the data needed to enable you to analyze the volumes and percentages of visitors that opt in or opt out of consent and the types of cookies each visitor is opting in or out of as a result of your efforts. Learn more about Event Logging for Consent Management. Tags to Omit Not all tags deployed via iQ Tag Management are for tracking or data collection. Tags and extensions can also be used to serve site functionality, such as pop-up modals, product feedback, site support, or chat clients. Use the Tags to Omit setting to create a list of tags to be exempted from the tracking restrictions. Consent Cookie The consent prompt uses a cookie named CONSENTMGR . The presence of this cookie and the values it contains determines the behavior of the prompt and reflect the state of the visitor's consent. The key/value pairs are delimited by the " | " character. The CONSENTMGR cookie stores the following key/value pairs related to the consent and preferences prompts: c1..N – integer value 1 or 0 indicating the tag category consent status where 1..N is the category number. 1=allowed, 0=not allowed (for use with the Consent Preferences prompt) consent – a Boolean value that reflects the consent state of the visitor: true – consent was given using the opt-in option false – consent was declined using the opt-out option ts – the timestamp of the last consent state change Example value of the CONSENTMGR cookie: ts:1525369619|consent:true|c1:0|c2:0|c3:0|c4:0|c5:0|c6:0|c7:1|c8:0|c9:1|c10:0|c11:0|c12:1|c13:0|c14:0|c15:0 Default Consent Categories (JavaScript Code Extension) This step is only needed if the Consent Preferences Dialog is disabled and if you have a server-side product (EventStream, AudienceStream, DataAccess) enabled. This step uses the JavaScript Code extension to add the default consent categories to the data layer to ensure that server-side events continue to be processed. To add the default consent categories: Add a JavaScript Code extension. Add this line of code to set the default list of consent categories: b["consent_categories"] = ["analytics", "affiliates", "display_ads", "search", "email", "personalization", "social", "big_data", "misc", "cookiematch", "cdp", "mobile", "engagement", "monitoring", "crm"]; Scope the extension to the Tealium Collect tag. JavaScript Helper Functions After enabled and published, the consent prompt introduces JavaScript utility functions into the utag namespace to allow you to integrate additional functionality. The namespace utag.gdpr contains all of the consent management utility functions. utag.gdpr.showExplicitConsent() Displays the explicit consent prompt. Integrate this function into your site to provide visitors a way to change their consent setting. To set the language dynamically, you can send the language as a parameter when calling the function. This overrides both the window.utag_cfg_ovrd.gdprDLRef defined above and the browser detection logic. Example: <a href="javascript&colon;utag.gdpr.showExplicitConsent('EN')">Change Consent</a> utag.gdpr.getCookieValues() Returns an object of key/value pairs from the CONSENTMGR cookie (mentioned above). The values are retrieved from utag.data['cp.CONSENTMGR'] . Example of consent declined: > utag.gdpr.getCookieValues() { ts: "1525369619", consent: "false" } Example of partial consent has been given for categories 7, 9, and 12: > utag.gdpr.getCookieValues() { ts: "1525369619", consent: "true", c1: 0, c2: 0, c3: 0, c4: 0, c5: 0, c6: 0, c7: 1, c8: 0, c9: 1, c10: 0, c11: 0, c12: 1, c13: 0, c14: 0, c15: 0 } ... View more

If you haven't already noticed, the Universal Data Hub has a great new look. The layout and navigation are improved to optimize the workflows within each product.  You can still access the old layout by clicking View older version in the top banner, but the old layout will only be available for a limited time. What's New? Feedback Form Look in the bottom right of any screen to find the new feedback button. Click the button to expand the form and share your feedback. This feedback goes straight to our product team for review. All feedback is helpful -- the raves and the rants -- so don't hesitate to pop open the form and tell us about your experience in the new layout. Note: Bug reports or requests for support should still be submitted through Tealium Support Desk. Sidebar Navigation The new layout of Universal Data Hub now has a convenient sidebar to give you easy access to any other screen. The sidebar can be expanded or collapsed by clicking the Tealium logo at the top or the arrow at the bottom. The sidebar is organized by product for a more intuitive workflow.  One thing you'll notice right away is that event-based and visitor-based components are now separated into the their own screens. Specifically, this means that event attributes and visit/visitor attributes are now located within their respective product areas. Same goes for event-based connectors and audience-based connectors. The new sidebar contains the following areas: Home A new landing screen for all of your high-level information, such as summary usage, viewing data trends, and exploring past versions of your account. Included screens: Overview Usage Report Versions Sources The starting point for setting up your account, with access to create new data sources and create new omnichannel file definitions. Included screens: Data Sources Omnichannel iQ Tag Management A quick link to access your iQ account. EventStream Everything you need to manage your event data and API hub. Included screens: Live Events (Feeds) Event Specs (Specifications) Attributes (Event) Connectors (Event-based) My Connectors Connector Marketplace AudienceStream Everything you need to manage your visitor data. Included screens: Dashboard Discover Audience Discovery Audience  Sizing Attributes (Visit/Visitor) Audiences Connectors (Visitor-based) My Connectors Marketplace Audience Sizing Jobs DataAccess Get credentials and configure all of your data storage solutions. Included screens: EventStore AudienceStore EventDB AudienceDB Tools Tools and screens that apply to the entire account. Included screens: Trace Rules Visitor Profile Sampler Learning Community A quick link to access the community and documentation.   ... View more

This article shows how to connect your Microsoft Power BI Desktop application to EventDB and AudienceDB in Tealium DataAccess. In this article: Table of Contents Placeholder Create ODBC Data Source To connect Power BI to DataAccess, an ODBC Data Source connection is required. To create an ODBC data source in Power BI: Install the Amazon Redshift Driver for Windows Create a system DSN entry for an ODBC connection Be sure to use System DSN Your configurations should resemble the following: After the ODBC Data Source has been configured, click Test. If the client computer can connect to the Amazon Redshift database, you will see the following message: Connection successful. Close the ODBC configurations. Connect Microsoft Power BI to Tealium DataAccess Within Power BI, select the Home tab then Get Data (click the icon, not the drop-down) Select Other, then ODBC, then click Connect. Select your Data source name from the drop-down. If you retrieve the entire database, you may not be able to successfully run queries after you are connected. We recommend that you click Advanced options and enter a limiting statement in the SQL statement (optional) field so that you retrieve only the data you need. It should resemble the following: Click OK. A data Navigator will appear. Expand the directory structure and select the table you wish to query then click Load. Power BI will connect to the data, load the data for modeling, and populate the columns with your attributes. Now you are ready to build reports using Microsoft Power BI on top of Tealium DataAccess. Troubleshooting "Server certificate for <cluster name> does not match host name." First, try to use the full cluster name in the connection settings. If that does not resolve the error, try changing the sslmode setting to verify-ca rather than verify-full . Learn more about Redshift SSL Support.   ... View more

The Omnichannel File Status API provides detailed status information for your Omnichannel Files. The API is available to AudienceStream-enabled accounts only. This article assumes you have already uploaded the Omnichannel Files in your AudienceStream profile. Table of Contents Placeholder File Status Fields The API returns a File Status that details when the files imported and how they were processed, including any processing errors. A File Status is represented as a JSON object containing the following keys: Name Type Description account string Name of the AudienceStream account profile string Name of the profile (in the account) where your files are uploaded and processed  created at UTC timestamp date and time when the file status was created (expressed in UTC format with the designator 'Z') file.name string Name of the file in question file.size integer File size in bytes file.source-type string Service used for uploading the file: FTP, SFTP, Tealium S3, and S3 file.source-host string Name of the service Hosting account for FTP/SFTP Bucket name for S3/Tealium S3 line_count integer Number of rows in the file status.state string Indicates the processing action on the file. Possible values are: DOWNLOADING, DOWNLOADED, PROCESSING, or PROCESSED. status.timestamp UTC timestamp date and time when the [status-state] was recorded (expressed in UTC format with the designator 'Z') lines_successfully_processed integer Number of rows parsed successfully lines_skipped integer Number of rows that could not be parsed due to missing data lines_failed_processing integer Number of rows that could not be parsed due to bad data or incorrect formatting last_failure string Error due to which the row/file could not be processed (Refer to Error Glossary and Troubleshooting link_here) Sample File Status { "account": "company_xyz", "created_at": { "$date": "2016-04-04T22:27:56.993Z" }, "file": { "name": "sales-transaction_2016feb4v50.csv", "size": 2744, "checksum": "44b12d35ea9fffdeeb69f98b03004f22", "source": { "type": "s3", "host": "companyxyz:" }, "line_count": 35 }, "node_id": "bulk_downloader_i-cd504b49", "profile": "omnichannelv2", "status": [ { "state": "DOWNLOADING", "timestamp": { "$date": "2016-04-04T22:27:57.285Z" } }, { "state": "DOWNLOADED", "timestamp": { "$date": "2016-04-04T22:27:57.722Z" } }, { "state": "PROCESSING", "timestamp": { "$date": "2016-04-04T22:27:57.780Z" }, "lines_skipped": 34 }, { "state": "PROCESSED", "timestamp": { "$date": "2016-04-04T22:27:58.797Z" } } ] } File Count Returns the count of uploaded files. Only applies to files with the same file prefix. The following query parameters are used: filePrefix - the file prefix matching the Omnichannel file definition eg. "sales_transactions" startDate - the start date of a range of files to query eg. "2017-01-01T12:34Z" endDate - the end date of a range of files to query eg. "2017-01-08T12:34Z" GET /v1/omnichannel/accounts/{account}/profiles/{profile}/files/count?utk={utk token}&filePrefix={file prefix}&startDate={start date}&endDate={end date} Curl Request curl -i -b JSESSIONID={session_id} \ https://api.tealiumiq.com/v1/omnichannel/accounts/{account}/profiles/{profile}/files/count?utk={token}&filePrefix={file prefix}&startDate={start date}&endDate={end date} If the file count exceeds 50, try narrowing the date range parameters. Example Response { "count" : 42 } Error Messages Error Type Description 400 Bad request File Definition prefix exceeds 150 chars File Definition prefix, start date, or end date not supplied Start/End date format is invalid End date is before Start date Single File Status GET /v1/omnichannel/accounts/{account}/profiles/{profile}/files/{file name}?utk={utk token} Curl Request curl -i -b JSESSIONID={session_id} \ https://api.tealiumiq.com/v1/omnichannel/accounts/{account}/profiles/{profile}/files/{filename}.csv?utk={utk token} \ -o {filename}.txt Example Response { "_id": { "$oid": "5702ea6db993f8f8cbea334c" }, "account": "acme", "created_at": { "$date": "2016-04-04T22:27:56.993Z" }, "file": { "name": "sales-transaction_2016feb4v50.csv", "size": 2744, "checksum": "44b12d35ea9fffdeeb69f98b03004f22", "source": { "type": "s3", "host": "johndoe:" }, "line_count": 35 }, "node_id": "bulk_downloader_i-cd504b49", "profile": "main", "status": [ { "state": "DOWNLOADING", "timestamp": { "$date": "2016-04-04T22:27:57.285Z" } }, { "state": "DOWNLOADED", "timestamp": { "$date": "2016-04-04T22:27:57.722Z" } }, { "state": "PROCESSING", "timestamp": { "$date": "2016-04-04T22:27:57.780Z" }, "lines_skipped": 34 }, { "state": "PROCESSED", "timestamp": { "$date": "2016-04-04T22:27:58.797Z" } } ] } Error Messages Error Type Description 404 Not Found Supplied file name not found 400 Bad request File name exceeds 150 chars Multiple File Statuses Returns an array of file statuses within the specified date range. Only applies to files with the same file prefix. GET /v1/omnichannel/accounts/{account}/profiles/{profile}/files/search?utk={utk token}&filePrefix={file prefix}&startDate={start date}&endDate={end date} Curl Request curl -i -b JSESSIONID={session_id} \ https://api.tealiumiq.com/v1/omnichannel/accounts/{account}/profiles/{profile}/files/search?utk={token}&filePrefix={file prefix}&startDate={start date}&endDate={end date} \ -o {filename}.txt   Example Response Below is a sample file status for three files that are all prefixed by "sales-transaction". Each file prefix is followed by "_" and a unique date identifier. Each file entry contains information about the file size, line count (i.e. number of rows) and number of lines processed (including any processing errors).  [ { "_id": { "$oid": "5702ea6db993f8f8cbea334c" }, "account": "acme", "created_at": { "$date": "2016-04-04T22:27:56.993Z" }, "file": { "name": "sales-transaction_2016feb4v50.csv", "size": 2744, "checksum": "44b12d35ea9fffdeeb69f98b03004f22", "source": { "type": "s3", "host": "johndoe:" }, "line_count": 35 }, "node_id": "bulk_downloader_i-cd504b49", "profile": "main", "status": [ { "state": "DOWNLOADING", "timestamp": { "$date": "2016-04-04T22:27:57.285Z" } }, { "state": "DOWNLOADED", "timestamp": { "$date": "2016-04-04T22:27:57.722Z" } }, { "state": "PROCESSING", "timestamp": { "$date": "2016-04-04T22:27:57.780Z" }, "lines_skipped": 34 }, { "state": "PROCESSED", "timestamp": { "$date": "2016-04-04T22:27:58.797Z" } } ] }, { "_id": { "$oid": "5702ea6bb993f8f8cbea334b" }, "account": "acme", "created_at": { "$date": "2016-04-04T22:27:55.562Z" }, "file": { "name": "sales-transaction_2016feb4v49.csv", "size": 2744, "checksum": "7b8f92474e220c275bf9931c0337abf3", "source": { "type": "s3", "host": "johndoe:" }, "line_count": 35 }, "node_id": "bulk_downloader_i-cd504b49", "profile": "main", "status": [ { "state": "DOWNLOADING", "timestamp": { "$date": "2016-04-04T22:27:55.601Z" } }, { "state": "DOWNLOADED", "timestamp": { "$date": "2016-04-04T22:27:55.887Z" } }, { "state": "PROCESSING", "timestamp": { "$date": "2016-04-04T22:27:56.045Z" }, "lines_skipped": 34 }, { "state": "PROCESSED", "timestamp": { "$date": "2016-04-04T22:27:56.669Z" } } ] }, { "_id": { "$oid": "5702ea69b993f8f8cbea3349" }, "account": "acme", "created_at": { "$date": "2016-04-04T22:27:53.276Z" }, "file": { "name": "sales-transaction_2016feb4v53.csv", "size": 2744, "checksum": "44b12d35ea9fffdeeb69f98b03004f22", "source": { "type": "s3", "host": "johndoe:" }, "line_count": 35 }, "node_id": "bulk_downloader_i-cd504b49", "profile": "profile", "status": [ { "state": "DOWNLOADING", "timestamp": { "$date": "2016-04-04T22:27:53.307Z" } }, { "state": "DOWNLOADED", "timestamp": { "$date": "2016-04-04T22:27:54.249Z" } }, { "state": "PROCESSING", "timestamp": { "$date": "2016-04-04T22:27:54.289Z" }, "lines_skipped": 34 }, { "state": "PROCESSED", "timestamp": { "$date": "2016-04-04T22:27:55.480Z" } } ] }, Error Messages Error Type Description 400 Bad request File Definition prefix exceeds 150 chars File Definition prefix, start date, or end date not supplied Start/End date format is invalid End date is before Start date   Omnichannel File Errors File processing can fail for many reasons: invalid service credentials, missing row data, internal server error, etc. In the File Status, these specific errors are logged in the value of the  last_failure  key. Here's a truncated sample of a file status: ... { "state": "PROCESSING", "timestamp": { "$date": "2016-10-05T18:09:54.014Z" }, "lines_failed_processing": 1, "last_failure": "Failed to find attribute for column with id" }, ...   Below listed errors are specific to Omnichannel Files; they are different from the API endpoint errors. Processing and Download Errors Error message What does it mean How to resolve Unknown file prefix, unable to parse file File for the supplied prefix (name) could not be found. Either the file doesn't exist or there is a typo in the prefix. Re-upload the file and double check the file prefix in the Omnichannel Definitions tab. If the error persists, please contact your Tealium Account Manager. DBObject of size {###} is over Max BSON size {###} File is too large to be processed Split up your file data into multiple file definitions Failed to download (FTP, SFTP, S3) file File could not be downloaded due to errors in your service credentials (see Omnichannel Configuration tab). For FTP/SFTP, double check the Host name, user name, and password For S3/Tealium S3, double check the Access/Secret keys and Bucket/prefix Invalid connection type OR  Could not find required (FTP, SFTP, S3) configuration parameters for definition Your service credentials (under Omnichannel Configuration tab) could not be authenticated. For FTP/SFTP, double check the Host name, user name, and password For S3/Tealium S3, double check the Access/Secret keys and Bucket/prefix Configuration and Definition Errors These errors are caused by incorrect column mappings in the Definitions tab. Error Message What does it mean How to resolve Failed to find attribute for column with id AudienceStream could not generate an Omnichannel Attribute for the column name you mapped. Replace the offending column header with a fresh instance and re-upload the file Exception thrown while processing file Unable to parse the value of your mapped column header into the Omnichannel Attribute Replace the offending column value and re-upload the file. Secondary visitor ID column= {column_name_here} does not exist in the file, unable to continue The column header you mapped to the Visitor ID field does not exist in your file. This could be due to a typo or the header is not defined. Make sure the column header you supplied matches what is in the file {date_format_here} could not be parsed as a Date The date format you specified for the mapped column name does not exist in your file. Make sure the date format you supplied matches what is in the file The number of columns to be processed {##} must match the number of CellProcessors {##}: check that the number of CellProcessors you have defined matches the expected number of columns being read/written The column names you mapped under Omnichannel Attributes do not exist in your file. This could be due to a typo or the header is not defined. Make sure the column header you supplied matches what is in the file Internal Server Errors These errors occur when the different servers processing your files are unable to communicate with each other. Connection is already closed due to connection error; cause: com.rabbitmq.client.MissedHeartbeatException Can't connect to new replica set master [##.#.#.###:###], err: couldn't connect to server [##.#.#.###:###], error querying server DBClientBase::findN: transport error socket exception [SEND_ERROR] Resolution: Re-upload your file(s). ... 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. Universal Data Hub (Cool Stuff) Resolved bug preventing the UDH user interface from accurately depicting badges being assigned at end of visit. (Fix) Fixed an issue that incorrectly allowed individual badges to be selected as a view perspective in Audience Discovery. (Fix) Resolved a bug causing double counting of Omnichannel enrichments. (Fix) Corrected an issue that prevented you from deleting attributes. Tags (Cool Stuff) Updated our Movable Ink tag to the vendor's latest requirements. (Cool Stuff) Updated the Google Analytics tag to use gtag.js. (Cool Stuff) Updated the DoubleClick Floodlight tag to use gtag.js. (Cool Stuff) Updated text and logos for rebranding SOASTA mPulse to Akamai mPulse. (Learn more) (Fix) Fixed our Adobe Marketing Cloud ID Service tag to include the tracking server configuration object to ensure that the Analytics ID is preserved. iQ Tag Management (Fix) Fixed an issue in the Channels Extension that caused incorrect channels to be matched after deleting a channel from the configuration. (Fix) Corrected an issue with load rules assigned to tags in a library not remaining assigned after library is inherited into a profile. (Fix) Corrected a different manifestation of a previously-resolved issue in the Lookup Table extension where output values containing a single-quote would cause a syntax error in the generated utag file. (New Stuff) Update allows concurrent users to perform multiple merges before saving the profile. In addition, concurrent users with unsaved changes will be prompted to merge when new versions of the profile have been created. (Learn more) Connectors (Cool Stuff) New Marketplace Connector: Close.io (New Stuff) New Marketplace Connector: Swrve (New Stuff) New Marketplace Connector: Sendloop (New Stuff) New Marketplace Connector: GoSquared (New Stuff) New Marketplace Connector: Express Pigeon (New Stuff) New Marketplace Connector: ClickSend (New Stuff) New Marketplace Connector: Keen IO Installations (Cool Stuff) Firebase Analytics integration with mobile libraries (Android and iOS/Swift) (Learn more) (Fix) Bug fixed in release 5.3.1 for iOS. Lifecycle 'isfirstlaunch' was set to true on relaunch. (Fix) Release 5.3.1 has multiple bugs fixed for crash issues reported in github by end users of Tealium iOS SDK (New Stuff) Added the Tealium Crash Reporter module for the Tealium Android library to provide application crash tracking capability for implementations using the Tealium Android Framework. (Learn more) ... View more