Tealium Learning Center

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

This article describes how to set up the Maxymiser (Async) tag in your Tealium iQ Tag Management account. Maxymiser empowers brands to transform every digital interaction into seamless, relevant and engaging customer experiences with its cloud-based testing, personalization and cross-channel optimization solutions. In this article: Tag Tips Contact Maxymiser before using this tag to confirm that your Maxymiser library is set up to be loaded asynchronously. If you need to load Maxymiser synchronously, paste the Maxymiser code into utag.sync.js or use the Maxymiser (Sync) tag instead of this one. For best performance: Advanced Settings: Set Tag Timing to Prioritized. Move this tag to the top of your list of tags (so that it loads first). Publish Settings: Enable Bundling Move utag.js to the top of the body Use mapping to: Disable the tag on a page-by-page basis. Pass additional data to Maxymiser (must be enabled on your Maxymiser account). Tag Configuration First, go to the tag marketplace and add the Maxymiser (Async) tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Library URL: The mmcore.js library URL provided by Maxymiser. Example:   //service.maxymiser.net/cdn/tealium/js/mmcore.js This should start with "//". Do not include "http:" or "https:". 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 Library URL (library_url) Disable Maxymiser (mm_disable) Load Test Content Asynchronously (mm_async) (Overrides default of "true") Custom (custom.myvar) ... View more

Learn about first-party domains and how to configure your own domains and SSL/TLS certificates for data collection and delivery solutions in the Tealium Customer Data Hub. To use first-party domains, you must have access to update your DNS database entries. You will need to work with your Production Operations team or the person responsible for your domain registration and SSL/TLS certificates. In this article: About First-Party Domains By default, the services offered in the Tealium Customer Data Hub are hosted on Tealium domains. When domain names don't match the domain of your brand's website, they are considered third-party domains. For example, the JavaScript files for Tealium iQ Tag Management are served from the domain tags.tiqcdn.com and the data collection endpoint for Tealium EventStream API Hub uses the domain collect.tealiumiq.com .  As new privacy regulations come out and as browsers begin limiting third-party capabilities, you might want to use your own domain to ensure that Tealium services are treated as first-party. First-party domains benefit from improved tracking and better compliance with browser privacy and cookie settings. Currently, only one first-party domain can be configured for an account. Contact the Tealium Support Desk to enable first-party domains for your account. How It Works To use your own domain name for tags.tiqcdn.com , you must create a CNAME entry in your DNS database. A CNAME record is an alias that maps one domain name to another. For example, for the website www.example.com , you would create a CNAME for tags.example.com that points to Tealium's CDN to serve the files for iQ Tag Management. For collect.tealiumiq.com , you add A records to your DNS configuration. An A record maps a domain name to the IP address for the domain. A critical part of this configuration is the management of the SSL/TLS certificates, which are the public key certificates that verify the encryption of your website over HTTPS. The Tealium first-party domain feature helps you manage which domains you want to use with Tealium services and validates the SSL/TLS certificates for those domains. When using first-party domains, make sure you are using the latest version of the Tealium Collect tag. Managed and Imported Certificates You configure first-party domains by either importing your own certificates or by requesting certificates to be managed by Tealium. Imported certificates work the same as managed certificates, but with one important exception: imported certificates are not automatically renewed. To use your own certificates, you must have access to the following SSL/TLS certificate files: PEM-encoded certificate PEM-encoded, unencrypted private key PEM-encoded certificate chain To request certificates managed by Tealium, you must have access to edit your DNS entries or have access to receive email messages sent to the domain administrator. Limits on Domains per Certificate The maximum number of domains per certificate is determined when you sign up for first-party domains. The first-party domains overview screen shows the maximum number of domains per certificate. In the following example, no domains have been mapped and the maximum number of domains is 10. Validating Domain Ownership Before Tealium can issue a certificate for your site, you must prove that you own or control all the domains in your request. You can prove ownership using either DNS validation or email validation. We recommend DNS validation because it is usually a quicker process and because sometimes it can be difficult to track down who in your organization has access to the administrative emails. However, if you don't have access to edit your domain's DNS database, then you must use email validation. DNS Validation To use the DNS validation method, you must have access to edit your DNS configuration. After you enter your domains, you are provided with temporary CNAME records for each domain requested, which you must add to your DNS configuration.  After the DNS update for the temporary CNAME records propagates (which may take several hours), the ownership is confirmed and permanent DNS records are provided in the DNS Confirmation screen. Update your DNS configuration with these permanent records. For  tags.tiqcdn.com , one CNAME record is provided for each domain. For  collect.tealiumiq.com , two A records are provided for each domain, which allows load balancing for servers. Add both A records to your DNS configuration. Email Validation To use email validation, you must be able to receive email messages at one of the contact addresses listed in the WHOIS database for each of your requested domains. The email addresses that will receive a message include: administrator@your_domain hostmaster@your_domain hostmaster@your_domain postmaster@your_domain webmaster@your_domain admin@your_domain You will receive an email message (one for each domain) from Amazon Web Services containing a validation token that expires in 72 hours. If you do not receive the email or the token has expired, return to the main screen and click Resend Email. Data Collection Domains Use first-party domains with Tealium EventStream API Hub and Tealium AudienceStream CDP for first-party data collection.  The following data collection services and domains can be mapped to your first-party domain: Tealium Service Third-Party Domain First-Party Example Tealium Collect collect.tealiumiq.com collect.example.com   To use first-party domains with other services, such as the View-Through Extension, contact the Tealium Support Desk. Tag Management Delivery Domains Use first-party domains with Tealium iQ Tag Management to maintain core functionality as browsers adopt stricter privacy policies such as ITP and ad blockers. The following tag management services and domains can be mapped to your first-party domain: Tealium Service Third-Party Domain First-Party Example iQ Tag Management Files (utag.js, utag.sync.js, utag.#.js) tags.tiqcdn.com tags.example.com Configuring Domains and Certificates To configure first-party domains for your account, you must have the Manage Account permission.  To get started, navigate to iQ Tag Management > User Menu > First-Party Domains. Selecting a Service to Configure Determine which of the following services to configure: Server-Side Data Collection/DLE Map one or more of your domains to Tealium to allow first-party data collection for EventStream and AudienceStream. Client-Side Delivery Map one or more of your domains to Tealium to allow first-party file delivery. Domains and certificates for Collection and Delivery are managed separately. Next, click Configure Certificate and select one of the following: Generate Certificate Tealium generates and manages the SSL/TLS certificate. Provide Certificate Upload your own certificate files. If you use your own certificate, Tealium cannot automatically renew it. Configuring a Certificate Generated by Tealium Select a Region To configure a domain and certificate for data collection, select the region in which your primary account operates: Germany Hong Kong Ireland Sydney Tokyo US East The certificates are stored and configured on the Tealium endpoint in the region selected for the first-party domain. If the region for the first party domain is set to a different region than the region for the profile, the event and visitor data is collected in the first-party domain region and forwarded to the region configured for the profile. Select the Type of Validation DNS Validation To validate using DNS, you will be provided temporary DNS records to add to your DNS database. After these records are propagated and validated, you will be provided permanent records to replace the temporary records. You must have access to edit your DNS configuration and update the configuration with the permanent records. Email Validation To validate using email, an email message will be sent to the administrator email address associated with the requested domains. You must be able to receive these email messages to validate your ownership of the domains. You will receive one email message for each domain containing a validation token that expires in 72 hours. If you do not receive the email or the token has expired, return to the main screen and click Resend Email. Adding Domains The first-party domains you specify are typically subdomains of your customer-facing website. For example, the website located at www.example.com would use a subdomain named  tags.example.com as a first-party domain for tag management services. Enter the first-party domain you want to use, omitting https:// and the ending slash. First-party domains apply to all profiles in your account. Enter a subdomain for each site managed by this account. View Domain Contact Info After you enter a domain, click View Contact Info to view the WHOIS database information for that domain. If the WHOIS database contains contact information for the domain, such as a name, mailing address, email address, or phone number, the contact information is displayed. Verify that the information is correct. Click + Add Another Domain to add additional domains. When the maximum number of domains for the account is reached, + Add Domain is grayed out. Click Next when you have finished entering domains. Accept the Agreement To continue, accept the agreement to allow Tealium to manage certificates for the provided domains. DNS Validation If you chose DNS validation, the following messages are displayed: When you first request the certificate, temporary DNS records (CNAME records or A records) are displayed for validation purposes, after which the permanent records are displayed. The temporary DNS records are also used for auto-renewal of the certificate. Do not delete the temporary DNS records. When the validation process is completed, one or more permanent DNS records are displayed. Each record contains a Name and Value that you must enter into your DNS provider's web interface to update the records. The record name appears in the format _X.sub.example.com. where X is a generated alpha-numeric string and sub.example.com is the first-party domain you entered. Example record name: _4c71ce829d13dacf824b18af1067d273.tags.example.com. DNS providers are inconsistent in their handling of the record name (or name) field. In some cases, you are expected to provide the entire value as shown above, while other providers automatically append the domain name to the value you enter. The record value is similar and appears in the format _X.Y.acm-validations.aws. where X.Y is a generated alpha-numeric string. Example record value: _6e23f25da49d05e43a419ea7c5f4162d.zzxlnyslwt.acm-validations.aws. Email Validation If you chose email validation, the following message is displayed: When the validation process is completed, your permanent DNS records are displayed, as follows: Configuring Your Own Certificate If you provide your own certificate, you are responsible for renewing the certificate before it expires. Your certificates must meet the AWS requirements for importing certificates. For more information, see AWS Prerequisites for importing certificates. To configure your own certificate, select a region. The certificates are stored and configured on the Tealium endpoint in the region selected for the first-party domain. If the region for the first party domain is set to a different region than the region for the profile, the event and visitor data is collected in the first-party domain region and forwarded to the region configured for the profile. Upload the following PEM-encoded files: Certificate Certificate Chain Private Key The Private Key must match the Public Key in the certificate and must not be encrypted with a password. The domains for the certificate are displayed. Verify that the list of domains is correct and click Save. The following message is displayed when your certificate files have been uploaded: When the domain status is changed to Issued, your domains are ready to use. Confirmation The following message is displayed while your domain information is being validated:   Please wait while domain information is validated. This won't take long.    Domain Statuses During the setup and validation process the domain certificate could appear with one of the following statuses: Issued: All domains are validated and the certificate is not expired nor about to expire. Expired: The certificate is expired. Pending Validation: One or more domains attached to the certificate are not validated. The domain validation must occur within 72 hours.  If the validation period expires, request a new certificate for the same domain. The DNS validation records are the same for subsequent requests of the same domain. Managing Domains After you have configured your domains, you can view contact information and add or remove a domain for a certificate. View Contact Information for a Domain To view the contact information for a domain, navigate to First-Party Domains, click on a domain, then click View Contact Info. Add a Domain to a Certificate To add domains to a certificate, use the following steps: Navigate to First-Party Domains and click on a domain. Click Manage Domains, then click Edit Domains. Click + Add Domain. An empty row is added to the list of domains. When the maximum number of domains for the account is reached, + Add Domain is grayed out. Enter the URL for the new domain and click Save. When the certificate has been updated, the response varies depending on the validation method. DNS Validation: Email Validation: When the domain status is changed to Issued, your domains are ready to use. Remove a Domain Use the following steps to remove a domain: Navigate to First-Party Domains and click on a domain. Click Manage Domains, then click Edit Domains. Click the remove icon for the domain.        Using First-Party Domains After your domains are configured and the certificates are validated you can begin using your first-party domains with the following services: Tag Management Tealium Collect First-Party Domains and Environment Switcher Environment switcher is a browser plugin that can be used to change the Tealium files (utag.js and utag.sync.js) that are loaded on a page, which is useful during testing. Environment switcher does not work properly when first-party domains is used for the tags.tiqcdn.com domain. In this case, you can setup a URL redirect for tags.tiqcdn.com in environment switcher. For more information, see Tealium Tools: Environment Switcher.  Tag Management To use your first-party domain with iQ Tag Management you must also make the following changes: Update the Universal Tag (utag.js) code snippet wherever it is installed. Set the publishing URLs. Edit the template for utag.js to adjust the location of utag.v.js. Update Universal Tag Loading Script To update the Universal Tag code snippet: Navigate to User Admin Menu > Code Center. Under Choose Domain, select your first-party domain. The example code snippet is updated to use your first-party domain. The new URL only uses the profile name and environment in the path. The account name and /utag/ portions are omitted. The URL to the Universal Tag on a first-party domain is: https://sub.your_domain.com/PROFILE/ENV/utag.js For example, the code snippet for tags.tealiumecommerce.com would be: <!-- Loading script asynchronously --> <script type="text/javascript"> (function(a,b,c,d){ a='https://tags.tealiumecommerce.com/ecomm/prod/utag.js'; b=document;c='script';d=b.createElement(c);d.src=a;d.type='text/java'+c;d.async=true; a=b.getElementsByTagName(c)[0];a.parentNode.insertBefore(d,a); })(); </script> Set Publishing URLs The publishing URLs determine where to load the additional utag.#.js files for each default environment. If you forget this step, then the vendor tag files loaded after utag.js will not originate from your domain. To set the publishing URLs: Click Save/Publish, then click Configure Publish Settings.... Under Publishing URLs, enter a URL for each environment that uses your first-party domain. Dev: //sub.your_domain.com/your_profile/dev/ QA: //sub.your_domain.com/your_profile/qa/ Prod: //sub.your_domain.com/your_profile/prod/ Click Save. After all of these changes, save and publish to apply the changes to your site. Tealium Collect To use your first-party domain with Tealium EventStream or Tealium AudienceStream you need to update the data collection URL in your installation of Tealium Collect. For websites, this requires setting the Tealium Collect Endpoint field for the Tealium Collect tag.  To update the Tealium Collect tag: Go to iQ Tag Management > Tags and expand the Tealium Collect tag. In the Tealium Collect Endpoint field, enter your first-party domain endpoint. Example: sub.your_domain.com/your_account/your_profile/2/i.gif Click Apply. Collect for Mobile For mobile apps, you must override the dispatch URL in the Collect module. For more information on setting your first-party domain endpoint, see the following: Tealium for Swift: config.overrideCollectURL Tealium for Android: config.overrideCollectUrl ... View more

You can now select to use the decimal or integer type for number attributes. This feature applies to number attributes in Tealium EventStream and AudienceStream. There are no changes to preloaded attributes. About Number Attributes Previously, number attributes were stored as decimals, with no ability to change the type. This meant that connector actions would automatically receive a value with a decimal, even if the vendor expected an integer in their API. For example, a vendor that collects product purchase data might expect whole number values for product quantities, but if you mapped the product_quantity attribute with a value of [2, 1, 1] in a connector action, the value would be sent to the vendor's API as [2.00, 1.00, 1.00] . This could cause unexpected results. What's New Number attributes now have a type property: decimal (default) or integer. This setting determines how the value is stored and transmitted. All existing number attributes will have the default type of decimal. The number type option can be changed after the attribute is created, so you can adjust existing attributes as needed. To specify the number type, simply select an option from the Type drop-down list. The available options are: Decimal (default) Decimal values can have zero (0) or more decimal digits. This type is recommended for attributes that represent monetary values. Examples: 12, 12.0, 12.345  Integer Integer values are stored as whole numbers. This type is useful for attributes that represent quantities, counters, or scores. Examples: 12, -4, 3214 This feature is available for the following attributes: Number Array of Numbers Tally ... View more

This article describes how to use the data types array of strings, array of numbers, and array of booleans. In this article: How it Works Before you begin, familiarize yourself with the following: Using Attributes Using Enrichments Arrays are used to store a list of values. Whereas a string or number attribute can only contain a single value, such as "Home Page" or 12.95 , an array can contain multiple values, such as  ["Pants", "Shirts"] or [5.99, 12.95] . Arrays are available for the number, string, and boolean attribute data types. In this article, arrays are represented in JSON format in all examples. ["Pants", "Shirts", "Shoes"] [2, 4, 6] [true, false, false] [] Arrays can contain duplicate values. There are no storage capacity limits for arrays, but these attributes are still limited by the maximum size of the profile after encryption and compression. Array of Strings Enrichments The array of strings attribute stores a list of text values. The array of strings is available in the following scopes: Event, Visit, Visitor. Add a String This enrichment adds the value of a string attribute to the array. The added attribute can only be a string, iQ variable, or omnichannel attribute. Attribute Name: product_name STARTING VALUE ["Pants"] ENRICHED WITH "Shirts" RESULTING VALUE ["Pants", "Shirts"] Add an Array of Strings This enrichment adds all the values from another array to the array. The added attribute can only be an array of strings or an iQ variable. Attribute Name: product_name STARTING VALUE ["Pants"] ENRICHED WITH ["Shirts", "Shoes"] RESULTING VALUE ["Pants", "Shirts", "Shoes"] Difference Between Two Arrays This enrichment takes two arrays as input, and returns a new array containing all values found in the first array but not the second. In this example, values from Wishlist Products that do not also occur in Purchased Products are added to the resulting array.   Attribute Name: Unpurchased Products STARTING VALUE [] ENRICHED WITH Difference between: Wishlist Products ["Pants", "Shirt", "Shoes", "Belt"] and Purchased Products ["Pants", "Shirt"] RESULTING VALUE ["Shoes", "Belt"] This example shows that the resulting attribute value is replaced, not appended to and that repeated values in the first array are removed. STARTING VALUE [7, 8, 9] ENRICHED WITH Difference between: Some Numbers [1, 3, 1, 2, 3] and Some Other Numbers [3] RESULTING VALUE [1, 1, 2] Reset This enrichment removes all values from the array. Attribute Name: product_name STARTING VALUE ["Shoes", "Belt"] ENRICHED WITH   RESULTING VALUE [] Lowercase This enrichment lowercases every value in the array. Attribute Name: product_name STARTING VALUE ["Shoes", "BELT"] ENRICHED WITH   RESULTING VALUE ["shoes", "belt"] Set to Set of Strings Sets an array of strings to a set of strings. This enrichment replaces all values in the array. Attribute Name: Active Browser Types STARTING VALUE ["IE"] ENRICHED WITH ["Chrome" "FireFox", "Opera"] RESULTING VALUE ["Chrome" "FireFox", "Opera"] Add a Set of Strings Adds a set of strings to a string array. This enrichment preserves the existing values in the array, therefore there can be duplicate items in the resulting value. Attribute Name: product_name STARTING VALUE ["Pants"] ENRICHED WITH ["Pants", "Shoes", "Ties"] RESULTING VALUE ["Pants", "Pants", "Shoes", "Ties"] Remove a String from the Array Specify a first, last, or all instances of a string to remove. This enrichment removes from an array every instance of the item selected for removal. Attribute Name: product_name STARTING VALUE ["Pants", "Pants", "Shoes", "Ties"] ENRICHED WITH "Pants" RESULTING VALUE ["Shoes", "Ties"] Array of Numbers Enrichments The array of numbers attribute stores a list of numeric values for browsing metrics such as visits, page views, and purchase events. Numeric values are stored as decimals or integers. Choose the type that matches your needs: Decimal (default) Decimal values can have zero (0) or more decimal digits. Example: 12, 12.0, 12.345 Recommended for attributes that represent monetary values. Integer Only whole number values are stored. Example: 12, -4, 3214 Useful for number attributes that represent quantities, counters, or scores. The array of numbers is available in the following scopes: Event, Visit, Visitor. String representations of numbers ("0", "123", "12.95") are converted to their numeric values. All other non-numeric values are ignored. Add a Number This enrichment adds a number value to the array. The added attribute can only be a number, iQ variable, or omnichannel attribute. For example, you may wish to add the last purchase value to the rolling purchase_total_history value array. Attribute Name: purchase_total_history Starting Value [12.95] Enriched With 5.99 Resulting Value [12.95, 5.99] Add an Array of Numbers This enrichment adds all the values from another array to the array. The added attribute type can only be an array of numbers or iQ variable. For example, you may wish to add the array of purchased product prices to an array of all purchased product prices. Attribute Name:  purchased_products_history Starting Value [24.99, 12.95] Enriched With [5.99, 10.00] Resulting Value [24.99, 12.95, 5.99, 10.00] Reset This enrichment removes all values from the array. For example, you may wish to remove the last purchase items from the array of last purchases. Attribute Name:  purchase_total_history Starting Value [12.95, 5.99] Resulting Value [] Set Array of Numbers to be the Difference of Two Arrays This enrichment takes two arrays as input, looks for values that occur in one and not the other, and inserts them into the array. In this example, values from Gift Card Amounts that do not also occur in Gift Cards Purchased are added to the resulting array. Attribute Name: gift_card_not_purchased Starting Value [] Enriched With Difference between:   Gift Card Amounts [5.00, 10.00, 25.00, 50.00, 100.00, 250.00] and   Gift Cards Purchased [25.00, 50.00] Resulting Value [5.00, 10.00, 100.00, 250.00] Array of Booleans Enrichments The array of booleans attribute stores a list of true/false values. The array of booleans is available in the following scopes: Event, Visit, Visitor. The strings "true" and "false" (any mix of upper/lowercase) are converted to their respective boolean values. All other non-boolean values are ignored. Add a Boolean This enrichment adds a value to the array. The added attribute can only be a boolean, iQ variable, or omnichannel attribute. For example, you may wish to add a boolean to the array to represent that the customer purchased on their last visit. Attribute Name: did_purchase_on_visit Starting Value [true] Enriched With false Resulting Value [true, false] Add an Array of Booleans This enrichment adds all the values from another array to the array. The added attribute type can only be an array of booleans or iQ variables. Attribute Name: my_booleans Starting Value [true] Enriched With [false, true] Resulting Value [true, false, true] Reset This enrichment removes all values from the boolean array. Attribute Name: did_purchase_on_visit Starting Value [true, false, true] Resulting Value [] ... View more

This article describes how to manage templates and how to update to the latest version of a template. In this article: Requirements To manage templates you need the Manage Tag Templates permission. How it Works A template contains the JavaScript code for the core logic of a vendor tag or a component of the consent manager. Each marketplace vendor tag has its own template that converts the tag configuration, data mappings, and extensions from the iQ Tag Management interface into the JavaScript code that runs on your site. And each component of the consent manager has a template that controls its behavior on your site. There are a number of scenarios where you might need to edit a template, including: Updating to the latest release of a vendor tag. Updating to the newest features of the consent manager. Changing the core logic of a tag. Customizing components of the consent manager. Fixing a bug in a tag. Some customizations and fixes can be achieved using an extension scoped to the tag rather than editing the template. This approach should be considered first because it is easier to maintain over time. Template Types Templates are used for vendor tags, Tealium tags, and the consent manager. When you view a list of templates, each type can be identified by the following names: Tealium Tags uTag Loader The template for utag.js. uTag Sync The template for utag.sync.js. uTag Footer (deprecated) The template for utag.footer.js Consent Manager Dom Ready (cmDomready) General (cmGeneral) Show Explicit (cmShowexplicit) Show Preferences (cmShowpreferences) Marketplace Tags All marketplace templates are identified by their vendor name (as it appears in the marketplace), tag name (as entered in the tag configuration), and the tag UID. For example: Twitter Conversions: Twitter Conversions (Retargeting): Tag UID: 2042 Workflow When you edit or update a template you must apply your changes and then save the profile. If a marketplace tag template is changed, the tag will be marked as Updated. If you change a template and don't save the profile, the changes are discarded. Accessing Templates The following methods are available for accessing templates: User Menu From the the user menu, click Manage Templates. This method allows you to browse all templates in the profile and quickly access them from a drop-down list. Tag Configuration From the tag configuration screen, expand the Advanced Settings area and click Edit Templates. This method takes you directly to the template for that tag. Template Status Checker From the user menu, click Template Status Checker then click a template in the report. This method displays a status report of your templates, including the consent manager templates and the Tealium uTag templates. Learn more about the template status checker. Updating a Template Updating a template replaces the current template with the latest system version. If a template has been customized, this action will overwrite those changes. To update a template: Use a method to access the template. Click Update. A confirmation dialog appears. Click Update to confirm and replace the template with the latest system version of the template. Click Apply. You must save the profile to preserve the changes to the template.  Reverting a Template Reverting a template discards any changes that have been made since the last time the profile was saved. If a template has been updated or edited, this action will undo those changes. To revert a template: Use a method to access the template. Click Revert. A confirmation dialog appears. Click Revert to confirm and revert to the last saved version of the template. Click Apply. ... View more

An improved workflow is now available for managing templates. About Templates A template is the underlying JavaScript code that runs various parts of your iQ Tag Management configuration. Templates are used for marketplace tags, Tealium tags, and the consent manager. Previously, templates were edited, updated, and saved separately from the account publish workflow, which often led to confusion about which template was active.  This goal of this release is to address the following shortcomings of the previous way that templates were managed: Eliminate the confusing options of "Save Profile Template" and "Save Version Template". Provide intuitive steps for updating a template to the latest system version. Include templates in the version history notes. What's New This release brings the following improvements to managing templates: Standard Publish Workflow Previously, to edit or update a template, you would save the changes immediately without needing to save the profile. In this release, after you edit a template and apply your changes, you must save your profile to preserve those changes to the profile. Version History Previously, after editing and saving a template, the change would not be displayed in the version history. Now, since you must save your profile to preserve changes to a template, the version history displays a note whenever a template is edited. You may notice this message for templates edited prior to this release, it is recommended that you validate these before publishing to production. Update and Revert Options Previously, to update to the latest system version of a template you would click the trash icon. Now, when you view a template there are two clear options: Update Click this button to replace the current template with the latest system version of the template. Revert Click this button to revert the template back to the most recently saved version in the profile. This action discards any unsaved changes to the current template.   Learn more Managing Templates Template Status Checker ... View more

Overview When implementing the Firebase Tag in Tealium IQ, there are three components to be implemented that will require both edits in the native code and within Tealium. First, the Firebase SDK needs to be included in the app. Second, there are remote commands that need to be added to your native code through the Tealium SDK. Lastly, the Firebase Tag will be added to Tealium IQ. All three parts need to be implemented or Firebase will not receive data. Native Code Configuration Step 1 – Add the Firebase SDK to the Native App Step 2 – Add the Tealium SDK to the Native App Step 3 – Include the Remote Command Classes in the Native App For all libraries, you will need to register the Firebase Analytics Remote Command before it can be used. This should be done when you initialize the library. Follow the guide to implement the remote command based on the mobile platform being used. Tealium IQ Configuration Step 1 – Add the Firebase Tag The Firebase Tag is a special tag that contains an implementation of the API required to trigger custom native code blocks you have registered with the Tealium mobile libraries. This tag is available in the tag marketplace and communicates with “Step 3” of the native app configuration. How It Works The Tealium event (view or event) is triggered by the native code, which is then ingested by utag.js in the webview. The Firebase tag and associated extensions review the event and send a Firebase event to the remote command that was added to the native code. The remote command takes the request from the tag and formats and sends the event so that it can be collected by the Firebase. Step 2 – Set the Tag Configuration The only option for configuration is whether to enabled debug mode. This is up to your developers whether they need this option enabled. The default setting is "False". Step 3 – Add Mappings Set-Up Certain mappings need to be present for the tag to work. These are the general settings that need to be applied. Session Timeout (seconds) Session Minimum (seconds) Firebase Log Level Screen Name Command Name Firebase Event These can be set as static values or can be set dynamically using extensions. Variable Description firebase_session_timeout_seconds Integer as String firebase_session_minimum_seconds Integer as String firebase_analytics_enabled Boolean as String firebase_log_level String td> firebase_event_name String firebase_event_params JSON firebase_screen_name String firebase_screen_class String firebase_property_name String firebase_property_value String firebase_user_id String command_name String Automatic Events Some of the events that will be used are automatically collected by the Firebase SDK and do not need to be set up using the Tealium Firebase Tag. For a list of these events, click here. Standard Events The event name is the event occurring in the app that needs to be captured (cart events, search events, payment events, etc.) Below is a list of standard events available through the Firebase SDK. If your event is not available in the list, it can be sent using a logEvent custom event. Variables   config event_level_end setScreenName event_login setUserProperty event_post_score setUserId event_present_offer logEvent event_purchase_refund resetData event_remove_cart event_add_payment_info event_search event_add_to_cart event_select_content event_add_to_wishlist event_set_checkout_option event_app_open event_share event_begin_checkout event_signup event_campaign_details event_spend_virtual_currency event_checkout_progress event_tutorial_begin event_earn_virtual_currency event_tutorial_complete event_ecommerce_purchase event_unlock_achievement event_generate_lead event_view_item event_join_group event_view_item_list event_level_up event_view_search_results event_level_start Firebase events are mapped as they would be in any other tag. Values can come in either from the data layer or set through an extension and then mapped to the tag in the following manner: Custom Events If the event you want to send is not included in the list of default events, you’ll need to send a logEvent event with a custom value attached for the event name. Map your variable value to the logEvent event. Add a parameter to send the event name with your logEvent event. Standard Parameters Event parameters are sent along with the event and can be mapped to the parameters in the list below. Params can be mapped in two ways: As a standard param sent with any event As an event param sent only with specified events Variable Description param_achievement_id String param_ad_network_click_id String param_affiliation String param_cp1 String param_campaign String param_character String param_checkout_option String param_checkout_step Integer param_content String param_content_type String param_coupon String param_creative_name String param_creative_slot String param_currency String param_destination String param_end_date String param_flight_number String param_group_id String param_index String param_item_brand String param_item_category String param_item_id String param_item_list String param_item_location_id String param_item_name String param_item_variant String param_level Integer param_location Integer param_medium String param_number_nights Integer param_number_pax Integer param_number_rooms Integer param_origin String param_price Double param_quantity Integer param_score Integer param_search_term String param_shipping Double param_method String param_source String param_travel_class String param_virtual_currency_name String param_start_date String param_term String param_tax Double param_transaction_id String param_value Integer or Double param_level_name String param_success String E-Commerce order_id String Overrides _corder order_total Integer or Double Overrides _ctotal order_shipping Double Overrides _cship order_tax Double Overrides _ctax order_currency String Overrides _ccurrency order_coupon_code String Overrides _cpromo product_id Array Overrides _cprod product_name Array Overrides _cprodname product_brand Array Overrides _cbrand product_category Array Overrides _ccat product_quantity Array Overrides _cquan product_unit_price Array Overrides _cprice param_item_list Array param_item_variant Array param_index Array Custom Parameters If your param is not available in the list above, a custom param will need to be sent with the event. When adding custom parameters to any event, note that they are sent along with the event (either standard or custom) and must be in a JSON format. The value of the mapped variable must be set up in a JavaScript code extension. Multiple events can be formatted as shown. The mapping to send custom params would be configured as shown. Tips Below are some items to keep in mind when setting up the Firebase Remote Command Tag. The config command is automatically sent on the first load if it is not found in the event list. If the appropriate data is provided (variable mapped to user ID), the event_login and event_signup events will automatically send setUserId and setUserProperty events. If the appropriate data is provided (variable mapped to screen name), the event_view_item_list , event_view_item , event_ecommerce_purchase , and event_begin_checkout can automatically send a setScreenName event. Use only the singular parameters or the e-commerce arrays, not both. Notes About Firebase Firebase is not the same as Google Analytics and has different terminology and a completely different setup. The variables/mappings do not translate one for one, therefore, custom dimensions are not included in Firebase. Params take the place of custom dimensions and should be used accordingly. If you need a custom param, they can be configured within Firebase. A/B testing parameters are stored in Firebase and are not accessible to Tealium. If the A/B testing data needs to be used within Tealium, the data can be exported from Firebase for FREE using BigQuery. The data can then be imported into Tealium server-side products for use in connectors/audiences. Resources Tealium Firebase Remote Command Integration Firebase Remote Command Example – iOS (Github) Firebase Remote Command Example – Android (Github) Google Firebase Guide Automatically Collected Events – Firebase ... View more

This article describes the Environment Switcher, which is available as a Tealium Tools browser extension. In this article: How it Works The Environment Switcher is a powerful testing tool used to change the Tealium files (utag.js, utag.sync.js) that are loaded on a page by specifying a specific environment (Dev, QA, or Prod) and/or a specific account/profile. Use the Environment Switcher in Google Chrome or Mozilla Firefox by adding the Tealium Tools extension. Learn more about the Tealium Tools Browser Extension. Using the Environment Switcher When you launch the Environment Switcher, the current account and profile detected on the page displays, along with configuration tabs that allow you to adjust the switcher according to your input. Once you have the Environment Switcher available in Tealium Tools, use the following steps to launch it: Click the Tealium Tools icon in the upper right of the screen. Click the Home tab. Click Environment Switcher. The Environment Switcher configuration screen displays a set of configuration tabs. Basic Configuration The options on the Basic tab allows you to load utag.js and utag.sync.js from different environments. Use the following steps to switch environments: Click the Basic tab. Click the environment you want to switch to. When you select a new environment, the environment detected on the page is outlined in orange and the active environment on the page (the one you switched to) is highlighted in blue. Click the Start button to apply your changes. This action refreshes the current page. Advanced Configuration The options on the Advanced tab provide the following features Advanced redirects to load the Tealium files from a different account, profile, and environment. This is helpful if you use profile libraries or custom publish environments. URL redirects to load the Tealium files from a custom URL location. Separate settings for each Tealium file and your browsing session.. Advanced Redirects To redirect the Account, Profile, or Environment, click Advanced Redirect to expand. Type the source name for each in the Source column and the destination name for each in the Destination column. URL Redirects To redirect to a custom URL, click URL Redirect to expand. Type the source URL in the Source column and the destination URL in the Destination column. Advanced Options Click Advanced Options to select or deselect how your redirects are applied. Select or deselect one or more of the the following: Current Domain Only - only apply the redirects to the current domain. If you navigate to a different subdomain, the redirects are not applied. Current Tab Only - only apply the redirects to the current browser tab. Other browser tabs, even if viewing the same page, will not be affected. Apply to utag.js - apply the redirect to utag.js. Apply to utag.sync.js - apply the redirect to utag.sync.js. Set utag_cfg_ovrd.path - set a custom cookie path. Click Start to apply all changes made. Active Redirects After making any changes using the Environment Switcher, the Active Redirects tab is the default tab that displays the next time you initiate the switcher. This tab displays environments that are currently being switched. Disable an Active Redirect To disable an active redirect, click Stop in the Action column. The page is automatically refreshed and the Tealium files load normally, as coded in the page. In subseqent visits to this tab, you can select Refresh or Stop in the Action column. Recent Redirects The Recent Redirects tab provides a history of recently used configurations, which makes it simple to reactivate a switcher that was previously configured. To reactivate a previously configured switcher: Click the Recent Redirects tab. A list of recently configured switchers displays. Click the Start button next to the switcher that you want to reactivate. The page refreshes automatically and the changes are applied. Troubleshooting The Help tab provides troubleshooting options to force stop all active redirects or completely reset the Environment Switcher. Force Stop All Active Redirects To force stop all active redirects: Click the Help tab. Click Force Stop all Active Redirects. The Active Redirects tab is now empty and all active redirects are stopped. Reset Environment Switcher to the Default State Resetting the Environment Switcher to the default state and stop all current redirects, remove all information saved in the UI setting, remove recent redirects, stop the backend service, and close the Tealium Tools window. Use the following steps to reset the Environment Switcher: Click the Help tab. Click Force Reset to expand. Click Reset Environment Switcher. The Active Redirects and Recent Redirects tabs are now empty. All active redirects are stopped and recent redirects are purged. Additional Information Tealium Tools Browser Extension An overview of the Tealium Tools browser extension and how to install in on Google Chrome or Mozilla Firefox. List of Custom Tealium Tools Detailed information about available custom tools. Creating Custom Tealium Tools Detailed developer information and migration steps for existing utilities. ... View more

This article describes the Tealium Predict ML product and how it is used to create, train, and deploy machine learning models to make predictions about visitor behavior. In this article: How it Works Tealium Predict is a built-in machine learning technology product used with the Tealium AudienceStream CDP product that takes a complicated discipline (machine learning) and distills it down to a fully-managed feature. Tealium Predict works with Tealium AudienceStream to build and create more intelligent audiences and activate trustworthy machine learning insights. Using Tealium Predict, you can create, optimize, and deploy data models that make meaningful predictions about visitor behavior allowing you to determine: The driving factors that influence your key performance indicators (KPIs). For example, which types of customers are likely to make online purchases. Which marketing channels within your website drive purchases. Categories of online visitor segmentation to apply successful customer personalization. Deployed models are managed by Tealium in real-time using a predictive output attribute that is made available to you after your model is trained and deployed. In just a few clicks, you can create audiences by categorizing visitors based model scores and target them with personalized experiences to drive ROI. Key Benefits Key benefits of Tealium Predict include the following: Leverage Machine Learning Intelligence Across your Entire Implementation Automatically activate predictive insights in any of Tealium's over 1,200 integrations. Simplification Tealium Predict technology simplifies the implementation of machine learning for you without the need for a data scientist or dedicated team. You can create a model, deploy it, and immediately activate the value in AudienceStream without writing a single line of code. Predict Customer Actions Automatically draw conclusions about what actions customers are likely to take in the future and design tailored programs that directly address their needs. Personalization The Tealium Customer Data Hub allows you to pinpoint meaningful visitor personalization data. Reduce Time Spent on Machine Learning Projects that Involve User Data Data collection and analysis are natively integrated with machine learning intelligence, greatly reducing time spent on data preparation and activation. Score Customers with Predictive Potential Technology built into the model produces a score for visitors with the likelihood to return or complete a specific behavior. You can then leverage the scores to generate audiences for further proactive action, such as re-engagement campaigns. Customer Use Cases To learn more about the real ways that machine learning and customer data can drive revenue through improved customer experiences, see Tealium Predict ML: Top 5 Emerging Machine Learning Use Cases with Customer Data. These customer use cases cover perspectives from marketing, customer experience strategists, and data scientists including: Proactive Marketing: Machine Learning-Powered Segmentation Marketing Efficiency: Improve Purchase or Conversion Rate Customer Retention: Reduce Churn Customer Experience: Funnel Optimization Predictive Analytics: Get Customer Insights and Validate Assumptions Learn More About the Technology To learn more about machine learning technology, see Machine Learning Concepts and Technology. ... View more