Tealium Learning Center

The new Tealium Docs site brings all product guides, developer documentation, and API docs into one site. We are excited to announce the relaunch of Tealium Docs, a milestone release that makes it easier than ever for Tealium customers to access quick start guides, platform installation guides, and product feature documentation in one site. Prior to this release, the product user guides, API docs, and developer docs were available on two different sites, each with their own site structure and search, making it difficult to know exactly where to find information.  Key features of the new Tealium Docs portal: A single and central location for all documentation for the Tealium Customer Data Hub. Improved navigation to reduce time spent finding what you need. Expandable navigation allows you to explore each section. What’s changing? The product documentation from TLC has been migrated to the new Tealium Docs  portal and can be accessed from this URL:  https://docs.tealium.com In the coming weeks, all TLC product guide pages will be redirected to their new locations in the Tealium Docs portal. TLC is still the primary destination to engage with the Tealium user community and to read the latest announcements. ... View more

Learn about the new features and fixes released in March 2022. Tealium iQ Tag Management Fixed an issue in the consent manager that caused raw HTML to appear on the configuration screen. Client-Side Tags Updated the SchemaApp tag to the vendor's latest version. Updated the Bloomreach tag to support Content Search, Content Page View, Widget View, Widget Click, and Widget Add-to-Cart events. Tealium EventStream and Tealium AudienceStream Added a new incoming webhook data source for Airship. Updated tally attributes to use integer values by default, instead of decimal values. Updated the attribute list screen to display the last modified time stamp, instead of the relative time frame (e.g. 2 years ago). Added a search feature to the attribute list screens, making it easier to find and navigate long lists of attributes. Added the ability to use RegEx in rules and audience conditions. (Learn More) Fixed an issue in the Set Date enrichment that caused attributes to not appear in the drop-down list. Server-Side Connectors New/Cool Stuff New marketplace connector: MediaMath New marketplace connector: Google Analytics 4 Measurement Protocol, with support for page view events, events, and Firebase events. Fixes Updated the Facebook Audiences connector to support hashing options for the external_id parameter. Merged two similar connectors, Salesforce DMP and Salesforce DMP (Krux), into one connector configuration, and updated the parameters to the latest API specification. Updated the AWS Kinesis Streams (Tealium-Provided Credentials) connector to support additional authentication methods via AWS Management Console: Cross-Account Access. Updated the AppNexus connector to the new branding Xandr Instant Audience Service connector. Added a connector insight to the Facebook Custom Audiences connector to show information about the custom audience, including audience size. (Learn More) Fixed an issue with the Google Ad Manager 360 connector where actions would fail if the Android Ad Id parameter was missing. Fixed an issue with connector reports where the browser time was used instead of the configured server time. Updated the Google Analytics 4 connector to support overriding the API secret using a data mapping. Installations Mobile Tealium for iOS (Swift) version 2.6.3 Fixed bugs related to publish settings and the expiration of data layer variables. Updated the Location module with public getter methods.   ... View more

Learn about the new features and fixes released in February 2022. iQ Tag Management Fixed an issue that caused modified tag templates to get reverted to the default template when being copied. Tags Updated the Heap tag to support events tracked with utag.link() . Updated the True Fit tag to the vendor's latest version with better support for user ID creation. New marketplace tag: Salsify. Updated the Vidora tag to load the latest version of the Vidora JavaScript SDK. Updated the Lotame Lighting tag to the latest version with support for event data collection, audience extraction, and handling consent. Updated the Adobe Target tag to support library versions 1.83 and 2.8. Customer Data Hub Fixed an issue where deleting a label that was applied to an event specification would prevent the event specifications screen from loading. Fixed an issue where the expanded attribute selection modal could not be closed. Fixed an issue on the AudienceStore DataAccess console screen that caused the file list to appear empty. Connectors New/Cool Stuff New marketplace connector: ROKT Events, with support for conversion tracking. New marketplace connector: TikTok Events Updated the Marketo connector to support adding a lead to a list if it does not already exist. Fixes Upgraded the Google Ads Conversions and Customer Match connectors to use Google API v9 and added braid and wbraid as mappable fields for Google Ads Conversions. Fixed an issue in the Facebook App Events connector where optional extended device parameters were incorrectly marked as required and where event names were incorrectly capitalized. Installations Mobile React Native Added support for the Location module. ... View more

Learn about the new features and fixes released in January 2022. Connectors New/Cool Stuff New Iterable connector, with support for SMS notifications, sending emails, batch events, updating a shopping cart, batch user upserts, and triggering a workflow. Learn More New Airship connector with support for tracking custom events. Learn More Fixes Updated the Google Ads Conversion connector to display more helpful error messages in the sample errors file. Fixed an issue in the Google Ads Customer Match connector where the addressInfo object was incorrectly sent in some scenarios. Installations Mobile Minor fixes to inaccuracies in the documentation. ... View more

This article describes how to set up the Acoustic Campaign connector. This connector is currently available as an experiment. Learn how to enable an experiment. In this article: Connector Actions Action Name AudienceStream EventStream Upsert Contact in Database ✓ ✗ Insert Contact into Contact List ✓ ✗ Upsert Contact in Database and Add to Program ✓ ✗ Send Email using Custom Triggered Autoresponder ✓ ✗ Upsert Contact in Relational Table ✓ ✗ Configure Settings Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see the About Connectors article. After adding the connector, configure the following settings: OAuth2 Client ID Required: OAuth2 Client ID. Please, contact Acoustic for assistance. OAuth2 Client Secret Required: OAuth2 Client Secret. Please, contact Acoustic for assistance. OAuth2 Refresh Token Required: OAuth2 Refresh Token. Please, contact Acoustic for assistance. Server Host Please provide your host. Hint: api-campaign-ZZ-X.goacoustic.com . Replace X with your pod number and replace ZZ with your region. Do not include HTTP(S) protocol. Example: api-campaign-us-5.goacoustic.com . Click Done when you are finished configuring the connector. Action Settings — Parameters and Options Click Continue to configure the connector actions. Enter in a name for the action and then select the action type from the drop-down menu. The following section describes how to set up parameters and options for each action. Action — Upsert Contact in Database Parameters Parameter Description Database Name Select the database name to upsert the contact in. It can be found by logging into your Acoustic account and havigating to Data > Databases. Database Type The type of database. Enable Auto Reply (If AutoResponder is defined for database)   Contact Identifier(s) If your database has a key other than Email, you must include all unique key columns with their corresponding name/value pairs. If adding and/or updating contacts in a flexible database, one or more Sync Fields must be specified in order to look up the contact. Enable Contact Database Column Update Criteria   Action — Insert Contact into Contact List Parameters Parameter Description Contact List Name Select the contact list name to add the contact to. It can be found by logging into your Acoustic account and navigating to Data > Contact Lists. Contact List's Corresponding Database Select the corresponding contact list's database name to add the contact to. It can be found by logging into your Acoustic account and navigating to Data > Databases. Action — Upsert Contact in Database and Add to Program Parameters Parameter Description Database Name Select the database name to upsert contact in. It can be found by logging into your Acoustic account and navigating to Data > Databases. Database Type The type of database. Enable Auto Reply (If AutoResponder is defined for database)   Contact Identifier(s) If your database has a key other than Email, you must include all unique key columns with their corresponding name/value pairs. If adding and/or updating contacts in a flexible database, one or more Sync Fields must be specified in order to look up the contact. Program ID Unique ID of the Program. Enable Contact Database Column Update Criteria   Action — Send Email using Custom Triggered Autoresponder Parameters Parameter Description Autoresponder Mailing Send ID For this operation to work, the autoresponder has to be custom triggered. Choose "Custom" option when creating the Automated Mailing Send and use a Database as its "Contact Source". You can find the Autoresponder ID by logging into your Acoustic Campaign account Autoresponder listing page and hovering your mouse over the mailing name. Autoresponder's Corresponding Database Provide the database name that was used when creating the selected Autoresponder. Action — Upsert Contact in Relational Table Parameters Parameter Description Target Relational Table Select the relational table name to upsert contact in. ... View more

This article describes how to set up the AppsFlyer Smart Banner SDK tag in your Tealium iQ Tag Management account. The Web-S2S API for People-Based Attribution complements the Web SDK allowing marketers to report events occurring on their websites but outside the scope of the Web SDK In this article: Tag Tips Use AppsFlyer Web SDK or AppsFlyer Smart Banner SDK but not both. To get your Web Dev Key, In AppsFlyer, go to the My Apps tab, click View brand bundles. To get Your Banner Key, In AppsFlyer, go to Engagement & Deep Linking > Smart Banners Use mappings to: Dynamically override the E-Commerce extension values Setup event triggers Supports the following E-Commerce extension values: Order Subtotal (_csubtotal) Order Currency (_ccurrency) Tag Configuration First, go to the tag marketplace and add the AppsFlyer Smart Banner SDK tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Web Dev Key Your Banner Key Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Tag Configuration Variable Description Web Dev Key (web_dev_key) [String] Your Banner Key (your_banner_key) [String] E-Commerce Variable Description Sub Total (order_subtotal) (Overrides _csubtotal) [String] Currency (order_currency) (Overrides _ccurrency) [String] Events Variable Description Search search AddToCart addToCart RemoveFromCart removeFromCart Purchase purchase Download download Signup signup Subscriptions subscriptions Custom Custom Event-specific Parameters Variable Description Search search AddToCart addToCart RemoveFromCart removeFromCart Purchase purchase Download download Signup signup Subscriptions subscriptions Custom Event Custom_Event ... View more

This article describes how to set up the AppsFlyer Web SDK tag in your Tealium iQ Tag Management account. The Web-S2S API for People-Based Attribution complements the Web SDK allowing marketers to report events occurring on their websites but outside the scope of the Web SDK In this article: Tag Tips To get your Web Dev Key go to AppsFlyer > My Apps > View brand bundles. Use mappings to: Dynamically override the E-Commerce extension values Setup event triggers Supports the following E-Commerce extension values: Order Subtotal (_csubtotal) Order Currency (_ccurrency) Tag Configuration First, go to the tag marketplace and add the AppsFlyer Web SDK tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Web Dev Key Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Tag Configuration Variable Description Web Dev Key (web_dev_key) [String] E-Commerce Variable Description Sub Total (order_subtotal) (Overrides _csubtotal) [String] Currency (order_currency) (Overrides _ccurrency) [String] Events Variable Description Search search AddToCart addToCart RemoveFromCart removeFromCart Purchase purchase Download download Signup signup Subscriptions subscriptions Custom Custom Event-specific Parameters Variable Description Search search AddToCart addToCart RemoveFromCart removeFromCart Purchase purchase Download download Signup signup Subscriptions subscriptions Custom Event Custom_Event ... View more

Insights brings additional connector data from the vendor into your Tealium account to help you evaluate its performance. The Facebook Event Match quality insight is an integration with the Facebook Conversions connector that brings event match quality data from Facebook into your account. This article shows you how to access the feature, explore the data, and evaluate your event match quality. In this article: Overview of Connector Insights The insight for the Facebook Conversions connector provides a summary of the conversion event types received by Facebook and details about the customer information parameters received for each event type. These insights are presented in a summary of the event types received by Facebook and the event match percentage of the customer parameters included with those events. Event Type Summary The event type summary shows the event types received by Facebook from the connector. The event types displayed are based on the Pixel ID in the connector configuration and the events configured in the connector actions.  The Pixel ID is automatically detected from the connector configuration. If the Pixel ID is set dynamically as a mapped parameter in the connector action then the event type summary data cannot be retrieved from Facebook and the EMQ scores will not appear. Each event type has an event match quality score ranging from 1 to 10. The score indicates how well the customer information in those events matches up to existing Facebook accounts. Customer Information Summary The customer information summary shows the details for an event type. The summary table displays all customer information parameters received for the event type along with the percentage of events receiving each parameter. The higher percentage of events that contain customer information, the more likely the EMQ score will improve. Using Connector Insights To access Connector Insights: Go to EventStream > Connectors, find the Facebook Conversions connector, and click Insights. The event type summary displays. Event Type Summary The event type summary displays the following: The Pixel ID of the configured connector Each event type collected by Facebook The event match quality for each event type. Use the search, filter, and sorting options to find an event to review. Click an event to see the details of the event match quality. Customer Information Summary The customer information summary displays each customer parameter received for the selected event type and the percentage of events containing the parameter. Evaluating Event Match Quality What is Facebook Event Match Quality (EMQ)? Facebook Event Match Quality is a score that indicates how well your server events are matching customer accounts in Facebook. Events are matched based on the customer information parameters that are sent with the events. The EMQ score is calculated from the configured Pixel ID, but scores from Pixel ID override variables are not supported at this time. The scores range from 1 to 10. A higher score results in more optimized conversions and better ad attribution. What is a good EMQ score? Facebook recommends aiming for a score of 6.0 or higher. Learn more about event match quality from Facebook for Business: Best Practices for Conversions API. How do I improve the EMQ score? Facebook lists several best practices to improve EMQ scoring. As a general rule, the more customer information parameters that you can include in your events, the higher the EMQ score will be. It can also help to prioritize the parameters that are most likely to result in a customer match in Facebook. The most effective parameters are: Hashed email address Client IP address / Client user agent Hashed phone number Add data mappings for these parameters and more in the Facebook Conversions connector. Additional Resources Facebook for Business: View Server Event Details Facebook for Business: Best Practices for Conversions API Tealium EventStream: Facebook Conversions Connector Tealium iQ: Facebook Pixel Tag ... View more

This article describes how to get the most out of Tealium and Google Ads Enhanced Conversion by setting up the Google Ads Conversion Tracking & Remarketing (gtag.js) tag in iQ Tag Management and the Google Ads Enhanced Conversions for Web connector in EventStream API Hub. In this guide: Overview What to expect The combination of Tealium and Google Ads Enhanced Conversions for Web preserves and improves advertising conversion by helping you leverage consented first-party data to: Adapt to browser restrictions. Avoid ad-blockers. Adhere to privacy and consent requirements. Successful implementations of this solution have benefited from the following positive impact on conversion rates: Search: 3.5% avg. increase in conversion rates (range: 1-5%) YouTube: 12% avg. increase in ad conversion rates (range: 7-25%)   How it works This hybrid solution uses both the client-side tag and server-side API to customer data and send conversion events, such as subscriptions, sign ups, and purchases, to Google. The customer data is matched to a signed-in Google user and the conversion event is attributed to ad clicks or views. The customer data is protected using a one-way hashing algorithm called SHA256, which keeps it secure and private. Enhanced conversions only work when one or more of the following customer attributes is available: Email address (recommended) Full name and home address Phone number (must be combined with one of the others) Customer Data The following customer parameters are expected.  The client-side tag will normalize these values for you, but you should normalize these values using extensions in iQ or enrichments in EventStream. Data Field Description Email address Lower-case and, for Gmail addresses, remove all periods. Example: janedoe@gmail.com<.code> Phone number Remove symbols and dashes, but keep the country code. Example: 14155551212 First name User first name. Example: Jane Last Name User last name. Example: Doe Street address User street address. Example: 123 Main St City User city name. Example: San Diego Region User region, state, or province. Example: CA or California Postal Code User postal code (5-, 6- or 7- digit version). Example: 92121 or S099 9XX Country User country code, in ISO-3155-1 standard. Example: US or UK Conversion Data The following Google conversion parameters are expected by the tag and the connector: Data Field Description Conversion Tracking ID Unique tracking ID for your advertiser account. Conversion Label Encoded conversion tracking ID and conversion type. Conversion Type Type of conversion event. Only used if conversion label is not available. Transaction ID Unique identifier for the event, generated by you the advertiser. See more at Google Ads Help: Use a transaction ID to minimize duplicate conversions. Conversion Value A transaction-specific value or the value used for this conversion type. See more at Google Ads Help: About conversion values. Currency Code Currency code for the conversion value. User Agent User agent from the browser where the conversion event occurred. Prerequisites Tealium iQ Tag Management Google Ads Conversion and Remarketing (gtag.js) tag EventStream Google Ads Enhanced Conversions for Web connector Google Google Ads account with an Enhanced Conversions enabled conversion Website Tracking Tag To configure the Google Ads Conversion and Remarketing tag in iQ Tag Management, you need the following: A load rule to identify the conversion event to track. Your Google Ads conversion settings, specifically your conversion tracking ID and conversion label. The following steps are available in more detail in the Google Ads Conversion Tracking & Remarketing (gtag.js) Tag Setup Guide. Tag Configuration Go to the Tealium tag marketplace and add the Google Ads Conversion & Remarketing (gtag.js) tag. Load Rule Set a load rule that matches your conversion event. This could be the page where the conversion occurs or the event that represents the conversion. Example load rules include: Purchase - tealium_event EQUALS "purchase" Sign up - tealium_event EQUALS "newsletter_signup" Data Mappings After adding the tag, go to the Data Mappings section to configure any additional mappings. With the E-Commerce extension in use, the following mappings are automatic: Order Subtotal/Conversion Value Order Currency/Conversion Currency Order ID/Transaction ID Server-Side Connector To configure the Google Ads Enhanced Conversions for Web connector in EventStream, you need the following: An event feed to identify the conversion events to track. Your Google Ads conversion settings. The following steps are available in more detail in the Google Ads Enhanced Conversions for Web Connector Setup Guide. Add the Connector Go to the connector marketplace and add the EventStream action for the Google Ads Enhanced Conversions for Web connector. To set up this connector, you will establish a connection between Tealium Customer Data Hub and your Google Ads account, so it is helpful to log into your Google account prior to configuring the connector. Then configure the following: Data Source - select the data source that represents the website where the conversion events occur. Event Feed - select the feed containing only the conversion events to track. Proceed to establish a connection with your Google account, then select the Send Conversion action type. Data Mappings The Send Conversion action sends the conversion event to the Google server-side API for enhanced conversions. The following data mapping is required in the enhanced conversion API call: Transaction ID - the ID the unique identifies the conversion event, generated by you as the advertiser. For purchase events this is the order ID. At least one of the following customer data mappings are required: Email address - user email address at the point of conversion. OR Full name and address (first name, last name, street address, city, region, postal code, country) All fields must be provided. Phone number is an optional value that can be provided with either option. The EventStream connector allows for plain-text mapping, and SHA-256 hashing will be applied. Google Enhanced Conversions The following considerations should be noted regarding Google Enhanced Conversions: Gclid Gclid is optional and will not be used for attribution, reporting, or bidding. User agent User agent is required for web conversions and allows you to report same device and cross-device conversions separately. The following conversion events are not in scope at this time: Mobile app conversions (installs, in-app actions, etc.) Phone conversions Import/offline conversions Additional Resources Better Together: Tealium + Google Overview of Tealium + Google Enhanced Conversions Setup (video) Google Ads Help: About enhanced conversions (beta) ... View more

This article describes how to set up the Google Consent Mode tag in your Tealium iQ Tag Management account. Consent mode (beta) allows you to adjust how your Google tags behave based on the consent status of your users. You can indicate whether consent has been granted for Analytics and Ads cookies. Google's tags will dynamically adapt, only utilizing measurement tools for the specified purposes when consent has been given by the user. In this article: Vendor Documentation About Google Consent Mode Google Developers: Adjust tag behavior based on consent Tag Configuration First, go to the tag marketplace and add the Google Consent Mode tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Automatically read from Tealium Consent Cookie If set to true, Google consent will be set based on the Tealium Consent Manager. See the other configuration descriptions for the exact behavior. Ad Storage If the integration with Tealium Consent Manager is enabled and partial consent is given, this sets ad_storage_consent value to granted . When full consent is given, granted is set. Analytics Storage If the integration with Tealium Consent Manager is enabled and partial is given, this sets analytics_storage_consent value to granted . When full consent is given, granted will be set. Ads Data Redaction Mapping When ads_data_redaction is true and ad_storage is denied , ad click identifiers sent in network requests by Google Ads and Floodlight tags are redacted. URL Passthrough You can optionally elect to pass information through URL parameters across pages in order to improve measurement quality. Wait For Update If your consent tool loads asynchronously, it might not always run before your Google tags. To account for this, specify wait_for_update along with a millisecond value to control how long to wait before sending data. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Variable Description Read From Tealium Consent Cookie [Boolean] Ad Storage Consent (ad_storage_consent) [String] Analytics Storage Consent (analytics_storage_consent) [String] Ads Data Redaction Mapping (ads_data_redaction) [Boolean] URL Passthrough (url_passthrough) [Boolean] Wait For Update (wait_for_update) [Number] ... View more

TLS (Transport Layer Security) is the protocol for establishing secure communication over HTTPS. Due to evolving internet standards, support for the older TLS 1.0 and TLS 1.1 has been deprecated across the major web browsers and TLS 1.2 is now the recommended minimum.  What is changing? Update Planned for June 1st, 2021 Tealium has security standards that require our endpoints to use TLS 1.2 and to end support for TLS 1.0/1.1. This also includes ending support for non-secure connections over HTTP. This update affects the following Tealium Collect endpoints: datacloud.tealiumiq.com collect.tealiumiq.com uconnect.tealiumiq.com While these endpoints already support TLS 1.2 as a security best practice, they also support TLS 1.0/1.1 for backwards compatibility. This update will end that support for TLS 1.0/1.1. After June 1, 2021, Tealium Collect will no longer support TLS 1.0/1.1 encryption. What is the impact? The impact to users will be minimal since modern browsers already default to using TLS 1.2. According to the Google Security Blog, "only 0.5% of HTTPS connections made by Chrome use TLS 1.0 or 1.1." We estimate the impact to Tealium Collect to be less than 0.1% of all events collected. Starting June 1, 2021, Tealium Collect endpoints will no longer accept requests from older web browsers and devices that do not support TLS 1.2 (or newer). Similarly, requests to Tealium Collect endpoints using HTTP (non-secure) will result in the response  301 Moved Permanently . What do I need to do? In most cases, you won't need to take any action. The default behavior of the Tealium Collect tag and mobile library is not affected. Visitors to your brand site or mobile app that use the default Tealium Collect installation will not be affected. However, if you have a customized implementation of Tealium Collect that uses a hard-coded HTTP endpoint, then you are affected. Update any HTTP Tealium Collect endpoints to use HTTPS or the default endpoint. The most common example would be a Tealium Collect tag with the Server field set to a custom URL using http:// , as seen here: Simply update the URL to use https:// and publish the changes. For mobile apps, if you override the default Tealium Collect endpoint with a custom URL using http:// , then change the URL to use https:// . Additional Resources Tealium Collect Tag Setup Guide Managing Templates Tealium for Swift: config. overrideCollectURL Tealium for Android: config.overrideCollectUrl   ... View more