Tealium Learning Center

This articles describes the installation options for Tealium AudienceStream CDP. This article is for customers that want to install Tealium AudienceStream but do not already use Tealium iQ Tag Management or Tealium EventStream API Hub. In this article: Option 1: Tealium Universal Tag + Tealium Collect If you are not already using a tag manager, we recommend using a basic setup of Tealium iQ Tag Management and the Tealium Collect tag to send data to AudienceStream. Tealium iQ requires a simple installation of the Universal Tag (utag.js) on all pages of your site and the Tealium Collect tag, which is easily added with a few clicks from the tag marketplace. Additional benefits of this option include access to the extension marketplace, for preparing and transforming your data before it's sent to AudienceStream, and the use of Web Companion and Tealium Tools to validate and extend your installation. Installation Components: Tealium iQ Tag Management Tealium Universal Tag (utag.js) Tealium Collect Tag Option 2: Google Tag Manager + Tealium Collect If you are using Google Tag Manager and are satisfied with your data layer and event tracking, we recommend deploying the Tealium Collect tag for Google Tag Manager. The Tealium Collect tag sends all data processed by Google Tag Manager, including the complete dataLayer object, directly to AudienceStream. Installation Components: Tealium Collect for Google Tag Manager Option 3: Google Tag Manager + Tealium Universal Tag If you prefer (or are required) to deploy vendors using Google Tag Manager, we recommend deploying the Tealium Universal Tag as a Custom HTML Tag in Google Tag Manager. This approach is also recommended if your Google Tag Manager implementation is not tracking behaviors and data points that are critical to your business, such as conversion funnel activity or ecommerce checkout steps. By deploying the Tealium Universal Tag you can take advantage of the full benefits of iQ Tag Management to fully implement advanced event tracking and supplemental data layer variables. This approach provides the advantages of deploying iQ Tag Management, as well as the ability to utilize existing event tracking in Google Tag Manager to expedite the installation. Installation Components: Tealium iQ Tag Management Tealium Universal Tag in Google Tag Manager Custom HTML Tag in Google Tag Manager Learn More The following resources are available to help continue your implementation experience: Live Events Regardless of the installation option, you will validate the data flowing into AudienceStream using Tealium Live Events. Live Events shows incoming data in real-time so that you can evaluate your tracked events and collected data attributes. Tealium Education Explore Tealium’s robust on-demand learning at education.tealium.com to take advantage of courses to increase your Tealium knowledge and skills, including the AudienceStream Basic eLearning course. ... View more

This article shows how to install Tealium in your Magento® 2 system using the Tealium iQ Tag Management extension from the Magento Marketplace. Table of Contents Placeholder Requirements The following items are required: An active Tealium iQ Tag Management account Your Tealium account ID Your Tealium profile name The Tealium environment to use (prod, qa, dev, or custom) How it Works In its current state, Tealium for Magento 2 is an implementation of some minimal boiler plate code for implementing and extending universal data objects (UDOs) for various page types. It relies heavily on Magento's prescribed dependency injection system and layout systems. Included is a simple script that will scaffold out boiler plate code when creating a new UDO. It allows you to specify any UDOs that it may extend, and which pages of the site the new UDO should appear on. When finished, you're left with a scaffolded template that just needs to be filled in with any data specific logic for your particular use case. To learn more, see the Introduction to the Data Layer. Learn more in the Magento Documentation. Install Install Magento 2.x by copying the Tealium folder from Github to the app/code within your Magento folder as follows:   sudo php bin/magento setup:upgrade sudo php -d set_time_limit=3600 -d memory_limit=1024M bin/magento setup:di:compile Configure  In the admin panel under store configuration, set the options for the extension: Stores > Configuration > Tealium > Tag Management. Enable the extension and provide your iQ account, profile, and environment. Release Notes 3.1.0 Update for support of Magento 2.4 Add tracking for user-submitted product reviews Bug fixes 3.0.2 Add support for Magento 2.3.3 3.0.1 Add support for Magento 2.2.8, 2.3.0, and 2.3.1-2 2.0.0 Updated composer.JSON Updated readme Releasing all previous commits 1.0.1 Default UDO (utag_data JSON object in page source) deployed via Magento Extension to match Tealium iQ TMS Data Layer bundle Configure account info in admin panel Extend and customize UDOs ... View more

This article describes how to customize your Shipify theme to use Tealim with the Tealium Shopify integration.  In this article: Table of Contents Placeholder Summary Customize your Shopify theme to use Tealium with the Tealium Shopify integration. This code provides a Universal Data Object (UDO) and loads the necessary Tealium assets on each page of your site. This integration takes the form of a theme customization. The code snippet for the order status page also appears on the "Thank you" page of the checkout. It provides the UDO for conversion tracking. Since the order status page may be revisited after the order is placed, it is recommended to configure logic in Tealium iQ Tag Management in order not to track conversions twice. Only Shopify Plus customers have access to the checkout.liquid file, which loads  utag.js throughout the checkout funnel. This integration does not currently support the checkout funnel, however you may implement your own checkout.liquid following the patterns used on other pages. Setup Instructions Settings Copy the following JSON object into the JSON array contained in the Config/settings_schema.json file of your Shopify theme. This enables the Tealium-specific settings for your theme. { "name": "Tealium", "settings": [ { "type": "text", "id": "tealium_account", "label": "Account", "info": "Name of your acount" }, { "type": "text", "id": "tealium_profile", "label": "Profile", "default": "main", "info": "Which profile to load your tags from", "placeholder": "main" }, { "type": "text", "id": "tealium_environment", "label": "Environment", "default": "prod", "info": "Which environment to load your tags from", "placeholder": "prod" }, { "type": "checkbox", "id": "tealium_enabled", "label": "Enable", "default": false, "info": "Check to enable Tealium" } ] } Edit your Tealium-specific settings in the General Settings tab when customizing your theme. Snippets Drop the files from the Snippets folder of this GitHub repository into the Snippets folder of your Shopify theme. These files contain the UDO implementations for the various page types. Learn more about theme snippets.  Templates On each page, include the correct snippet corresponding to the data layer of that page. Go to the page's template, or the section for specific pages such as the index (home) page, and insert the relevant snippet. For example, the product.liquid template file in the default Debut theme that Shopify provides looks like the following, where the product_udo snippet has been added at the beginning of the file. {% include 'product_udo' %} {% comment %} The contents of the product.liquid template can be found in /sections/product-template.liquid {% endcomment %} {% section 'product-template' %} <script> // Override default values of shop.strings for each template. // Alternate product templates can change values of // add to cart button, sold out, and unavailable states here. theme.productStrings = { addToCart: {{ 'products.product.add_to_cart' | t | json }}, soldOut: {{ 'products.product.sold_out' | t | json }}, unavailable: {{ 'products.product.unavailable' | t | json }} } </script> Order Status Unlike other pages, the order status page doesn't have access to the admin Settings, so you must reconfigure your Tealium account information. Define the settings in the Additional scripts box of the Order processing section, as described in the Shopify documentation: From your Shopify admin, click Settings and then click Checkout. Near the bottom of the Order processing section, find Additional content & scripts. And then add the following code. Before you begin,  set  tealium_enabled  to  true , and to set the  tealium_account ,  tealium_profile , and  tealium_environment  variables to match what you configured in the settings.    "product_price": [ {% for line_item in checkout.line_items %} "{{ line_item.price | money_without_currency }}"{% unless forloop.last %},{% endunless %} {% endfor %} ], "product_name": [ {% for line_item in checkout.line_items %} "{{ line_item.title }}"{% unless forloop.last %},{% endunless %} {% endfor %} ], "product_sku": [ {% for line_item in checkout.line_items %} "{{ line_item.sku }}"{% unless forloop.last %},{% endunless %} {% endfor %} ], "page_name": "{{ page_title }}", "language_code": "{{ shop.locale }}", {% if customer %} "customer_logged_in": "true", "customer_id": "{{ customer.id }}", "customer_email": "{{ customer.email }}", "customer_first_name": "{{ customer.first_name }}", "customer_last_name": "{{ customer.last_name }}", {% if customer.default_address %} "country_code": "{{ customer.default_address.country_code }}", {% endif %} {% else %} "customer_loggedin": "false", {% endif %} {% if cart %} "cart_total_items": "{{ cart.item_count }}", "cart_total_value": "{{ cart.total_price | money_without_currency }}", {% endif %} "page_type": "order" } </script> <!-- Loading script asynchronously --> <script type="text/javascript"> (function(a,b,c,d){ a='//tags.tiqcdn.com/utag/{{ settings.tealium_account }}/{{ settings.tealium_profile }}/{{ settings.tealium_environment }}/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> {% else %} <!-- Please configure your Tealium account information for the order confirmation page. --> {% endif %} Release Notes 1.0.2 Updated README to more clearly reflect the capabilities of the integration Updated order_status snippet to include more data and better variable names Renamed checkout.liquid to order_status.liquid to better reflect its functionality 1.0.1 Fixed misspelled variable name in the global_udo_vars snippet. customer_loggedin  was replaced with customer_logged_in . 1.0.0 Initial Release All snippets and configuration required to customize a Shopify theme to integrate Tealium Instructions for customizing a theme License Use of this software is subject to the terms and conditions of the license agreement contained in the file titled LICENSE.txt . Please read the license before downloading or using any of the files contained in this repository. By downloading or using any of these files, you are agreeing to be bound by and comply with the license agreement. ... View more

This article describes how to use the Tealium Tools version of Mobile QR Trace Table of Contents Placeholder  How it Works The Mobile Trace Tool enhances the Trace feature by providing a QR code that is scannable by your device, enabling you to quickly view events coming from the Tealium Mobile SDKs.  After clicking Start Trace in the tool, once per Customer Data Hub session, a QR code is automatically injected into the main browser window each time you start a new trace. QR codes are generated for each platform (Android or iOS).  After you scan the appropriate QR code with the appropriate mobile device's camera, click the link from the QR code to start the app and pass trace parameters to the Tealium SDK.  The Tealium SDK recevies the trace ID (along with other parameters) and inserts the trace ID into the data layer for the current session All subsequent events are recorded in the trace session until you end the session or leave the trace.  The following diagram illustrates how it works:  Install To use this tool, you must first add it your Chrome browser using the Tealium Tools extension. To install this extension on Chrome or Firefox, see Tealium Tools Browser Extension. In the Add by URL textfield, paste the URL: https://solutions.tealium.net/hosted/tealiumTools/mobile-trace/tool.json When installation has completed, launch the Mobile Trace Tool icon from the Tealium Tools extension. URL Schemes In order to use the Mobile Trace tool, determine which URLs are handled by your Android and iOS apps in order to configure the URL schemes.  The QR code trace feature launches your app from a URL and listens for a specific query parameter. In order to launch your app directly from a URL, your app must have registered itself to handle specific domains. Typically, most apps already handle specific URLs. For example, if your website domain is https://mycompany.com , your app registers itself as a handler for this domain and, if your app is installed on a user's device, the user is prompted to launch the link in your app instead of within a browser.  Some apps register custom URL schemes instead of `http` or `https`, for example `mycompanyapp://`. These also work with the Mobile Trace Tool. Once you have established which URL schemes launch your app, enter these into the input fields in the Mobile Trace Tool. The tool supports different schemes for Android and iOS if necessary, but in general, these are the same for both platforms. Click Save next to each URL scheme to store the setting in the browser's localStorage. Click the blue pencil icon to edit the URL schemes as needed.  Trace The following describes how to start and leave a trace using the Mobile Trace Tool. Start Trace Before starting a trace, verify that you are in the server-side Customer Data Hub. Click Start Trace in the Mobile Trace Tool, which starts a new trace and adds the Mobile Trace QR codes into the trace window.  After you have started a trace once from the Tealium Tools UI, close the Tealium Tools UI and you don't need to use it for the rest of your session. Subsequent traces are started directly from Customer Data Hub, and the QR code automatically refreshes each time a new trace starts. Scan the QR code with your device's camera, click the link to launch your app and automatically begin tracing. Any Tealium events generated by your app after joining the trace are recorded in your trace session. Leave Trace If you leave a trace session without ending it, you are able to rejoin the same trace from a different device without losing the history of that trace session. To leave a trace: Select the Leave Trace checkbox in the trace UI Scan the QR code again with your device's camera Click the link for your device to no longer participate in the trace session End of Visit (AudienceStream) Testing "End of Visit" actions in Tealium AudienceStream requires a signal to immediately end the visitor's session, otherwise it is necessary to wait for the session to expire normally. In the Mobile Trace Tool, end the session immediately by selecting the Kill Visitor Session checkbox, which adds a parameter to the QR code that makes the SDK send a  kill_visitor_session event. ... View more

If you are a customer integrating Tealium services into your site, but have a strict Content Security Policy (CSP), use a whitelist to accept resources from trusted domains.  Table of Contents Placeholder Domains For each Tealium product or service you are using, add their data center domains to your CSP whitelist. Also, add domains of any vendors loaded through Tealium iQ Tag Management. Each list is a full list, including all data center domains that may be used in the future. Tealium iQ Tag Management Add the following iQ Tag Management data center domains to your CSP whitelist: tags.tiqcdn.com tags.tiqcdn.cn tags-eu.tiqcdn.com Tealium Collect Tag, AudienceStream and EventStream Add the following Tealium Collect Tag, Tealium AudienceStream and Tealium EventStream data center domains to your CSP whitelist: collect-ap-northeast-1.tealiumiq.com collect-ap-northeast-2.tealiumiq.com collect-ap-northeast-3.tealiumiq.com collect-ap-southeast-1.tealiumiq.com collect-ap-southeast-2.tealiumiq.com collect-ap-south-1.tealiumiq.com collect-ca-central-1.tealiumiq.com collect-eu-central-1.tealiumiq.com collect-eu-west-1.tealiumiq.com collect-eu-west-2.tealiumiq.com collect-eu-west-3.tealiumiq.com collect-sa-east-1.tealiumiq.com collect-us-east-1.tealiumiq.com collect-us-east-2.tealiumiq.com collect-us-west-1.tealiumiq.com collect-us-west-2.tealiumiq.com collect.tealiumiq.com Data Layer Enrichment Add the following Tealium Data Layer Enrichment data center domains to your CSP whitelist: visitor-service-ap-northeast-1.tealiumiq.com visitor-service-ap-northeast-2.tealiumiq.com visitor-service-ap-northeast-3.tealiumiq.com visitor-service-ap-southeast-1.tealiumiq.com visitor-service-ap-southeast-2.tealiumiq.com visitor-service-ap-south-1.tealiumiq.com visitor-service-ca-central-1.tealiumiq.com visitor-service-eu-central-1.tealiumiq.com visitor-service-eu-west-1.tealiumiq.com visitor-service-eu-west-2.tealiumiq.com visitor-service-eu-west-3.tealiumiq.com visitor-service-sa-east-1.tealiumiq.com visitor-service-us-east-1.tealiumiq.com visitor-service-us-east-2.tealiumiq.com visitor-service-us-west-1.tealiumiq.com visitor-service-us-west-2.tealiumiq.com visitor-service.tealiumiq.com Tealium API Add the following Tealium API data center domain to your CSP whitelist: api.tealiumiq.com ... View more

The following is a list of Tealium integrations for Facebook products: Facebook Ads Connector Facebook App Analytics Tag Facebook App Events Connector Facebook Audiences Connector Facebook Conversions Connector Facebook Messenger Connector Facebook Offline Conversions Connector Facebook Pixel   ... View more

This article describes how to set up the Facebook App Analytics tag in your Tealium iQ Tag Management account. App Events allow you to measure the performance of your app using Facebook Analytics for Apps, measure conversions associated with Facebook ads, and build audiences to acquire new users as well as re-engage your existing users. In this article: Table of Contents Placeholder Tag Tips Facebook Developer documentation API v2.12 Application Activities Tag Configuration These can be found on your dashboard API Version APP ID APP Token (APP Secret) Tag Configuration First, go to Tealium's tag marketplace and add the Facebook App Analytics tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Application Id: An integer value (e.g., 123456) Access Token (App Secret): An integer value (e.g., 123456) Event Name 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 Description Parameter App Id app_id Access Token access_token Event Name event_name Advertiser Id advertiser_id Attribution attribution Advertiser Tracking Enabled advertiser_tracking_enabled Application Tracking Enabled application_tracking_enabled Custom Events (custom_events)   custom_events [Array of Objects] Event List (event_list)   event_list [Array of Objects] Mobile Variable Description Bundle ID Overrides app_rdns   Bundle Version   Bundle Short Version Overrides app_version   Events Parameter Description    fb_mobile_level_achieved Level achieved   fb_mobile_activate_app Active app   fb_mobile_add_payment_info Add payment info   fb_mobile_add_to_cart Add to cart   fb_mobile_add_to_wishlist Add to wishlist   fb_mobile_complete_registration Complete registration   fb_mobile_tutorial_completion Tutorial completion   fb_mobile_initiated_checkout Initiated checkout   fb_mobile_purchase Purchase   fb_mobile_rate Rate   fb_mobile_search Ssearch   fb_mobile_spent_credits Spent credits   fb_mobile_achievement_unlocked Achievement unlocked   fb_mobile_content_view Content view Custom Custom Parameters Description Parameter Log Time ( int ) _logTime App Version  _appVersion Value to Sum ( float ) _valueToSum Content ID ( string ) fb_content_id Content Type ( string ) fb_content_type Currency ( string ) fb_currency Description ( string ) fb_description Level ( string ) fb_level Max Rating Value ( int ) fb_max_rating_value Number of Items ( int ) fb_num_items Payment Info Available ( 1 or 0 ) fb_payment_info_available Registration Method ( string ) fb_registration_method Search String ( string ) fb_search_string Success( 1 or 0 ) fb_success Custom Custom Limited Data Use Variable Description   lmt_data.use_ldu (Use LDU) If true , use Facebook’s Limited Data Use option If false , do not use Facebook’s Limited Data Use option lmt_data.ldu_types.geolocate  (LDU should Geolocate) If true , the LDU geolocates the user. If false , the LDU doe snot geolocate the user. If “Use LDU” is enabled, then “LDU should Geolocate” is also enabled by default. lmt_data.ldu_types.california  (LDU is California) If true , sets the state and country California-specific values inside the template. Only enable this option if the user is located in California and needs to be processed with Limited Data Use. If false , does not set the user’s state and country California-specific values inside the template. ... View more

Mobile remote commands are a feature of the Tealium iOS and Android libraries that allows native code to be triggered using Tealium iQ Tag Management.  Remote commands works in conjunction with the TagBridge Custom Command tag and the third-party vendor SDK you wish to integrate into your app. Learn about Remote Commands: How it Works. Tealium supports the following remote command integrations: AppsFlyer Braze Contentsquare Facebook Firebase Usabilla   ... View more

Tealium for Mobile just released the Location and Geofencing module which provides user location tracking and the ability to add geofences around points of interest. This module is now available in the latest releases of Tealium for Android and Tealium for iOS (Swift). In this announcement:  Table of Contents Placeholder What is Location Tracking and Geofencing? Location tracking is the process of receiving geographic location (latitude and longitude) from a user’s device. A geofence is a virtual perimeter surrounding an area of interest, specified by latitude and longitude coordinates and a radius. Geofencing is a location tracking service that combines awareness of the user’s location with the user’s proximity to a geofence. A geofence is a virtual perimeter surrounding an area of interest, specified by latitude, longitude, and a radius. Want to learn more? On March 12, 2020, Kyle Brierley, Director of Product and Jake Spencer, Product Marketing Manager will be hosting a live customer webinar to cover everything you need to know about Event Batch as well as Geofencing and Location Tracking for Tealium Mobile. Register below to attend you’ll walk away with new use case ideas, ask live questions, and see demos: US/EMEA Webinar Asia Pacific/Japan Webinar How it Works Include the Location module in your Tealium for Mobile installation and, with permissions granted, your app continuously tracks user location and automatically adds latitude and longitude to the data layer. During geofencing, a tracking call containing location data is sent when the transition state of the user changes. Transition state changes include: Entering a geofence Exiting a geofence Dwelling inside a geofence for a period of time Benefits The benefits of the Location module include: Track continuous location events of users. Provides opportunities to conduct location-based marketing. High accuracy monitoring for real-time applications Links Developer Docs > Getting Started > Location Tracking and Geofencing Developer Docs > Android > Location Module Devleoper Docs > iOS > Location Module     ... View more

Tealium for Mobile just got an upgrade that will optimize performance for Android and iOS installations. A new feature called event batching is now available in the latest releases of Tealium for Android and Tealium for iOS (Swift). In this announcement: Table of Contents Placeholder What is Event Batching? Event batching is a new optimization to the way data is sent from a mobile device to the Tealium Collect service.  It sends multiple events in a single HTTP request to eliminate repetitive data layer variables and to minimize the size of the payloads. How it Works Previously, each event tracked on a device would trigger an HTTP request to transmit that data to the Tealium Collect service. With event batching, tracked events are stored temporarily in an event queue until they are combined into one payload and sent as a single HTTP request.  The batch payload is compressed with gzip to minimize the amount of data transmitted and the batch data is optimized to only include repeated data layer variables once. Benefits The benefits of event batching include: Reduced size of total transmitted data. Fewer network requests for the same number of events. Improved battery performance on the device. Overall, you'll gain a further increase in performance, especially if you use Tealium Collect and EventStream for SDK reduction. Links Developer Docs > Getting Started > Event Batching   ... View more

This article describes an example of a Firebase Mobile Remote Command order event. In this article: Table of Contents Placeholder Install Learn more about the Tealium remote command integration for Firebase on Android and Swift/iOS Tag Setup The Custom Command 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. Learn more about setting up the Firebase Mobile Remote Command Tag in your Tealium iQ Tag Management (TiQ) account. Extensions may be needed to update the data coming from the app via a tracking call. For example, you might be tracking a screen view using the Tealium SDK on the "Order Confirmation" screen, which you want to also log in the Firebase SDK. The following is an example of the tracking call in Tealium for iOS (Swift): tealium?.trackView("order_confirmation", ["order_id":"A123456", "user_id": "john.doe@someprovider.com", "user_loyalty_status":"vip", "travel_class" : "first"]) In the Firebase SDK, you may wish to log this as an event using the logEvent API call, and also set a user property called user_id . In Tealium iQ, this is done in several different ways. The value for the command_name variable is set to a comma-separated string of commands to execute. The 5 possible values that it may contains are: config setUserId setScreenName setUserProperty logEvent . For this example, it is important to understand the order of operations in Tealium iQ. Extensions with the same "scope" are guaranteed to execute in order, from top to bottom as you see them in the Extensions tab. Therefore, logic is easily split into different extensions, but keep writing to a variable that was defined in an earlier extension. Create a new data layer variable called firebase_command_name in your Tealium iQ profile. Create a Set Data Values extension, select the new variable firebase_command_name from the dropdown list, and leave the data entry field blank. This initializes the variable to an empty string. Create the following list of Set Data Values extensions, with the settings listed in the tables below: config Execute this configuration only once per session. The following lists the Tealium iQ configuration variables: TiQ Variable Name Type Example Notes command_name Text config Required, case-sensitive firebase_minimum_session_length Text 10 Optional firebase_session_timeout Text 3600 Optional firebase_analytics_enabled Text true Optional, case-sensitive, default = true firebase_log_level Text error Optional, case-sensitive This produces the following call in the native Firebase API: Android: mFirebaseAnalytics = FirebaseAnalytics.getInstance(mCurrentActivity.getApplicationContext()); mFirebaseAnalytics.setSessionTimeoutDuration(3600); mFirebaseAnalytics.setMinimumSessionDuration(10); mFirebaseAnalytics.setAnalyticsCollectionEnabled(true); Swift: let firConfig = FirebaseConfiguration.shared let firAnalyticsConfig = AnalyticsConfiguration.shared() firAnalyticsConfig.setSessionTimeoutInterval(3600) firAnalyticsConfig.setMinimumSessionInterval(10) firAnalyticsConfig.setAnalyticsCollectionEnabled(true) firAnalyticsConfig.setLoggerLevel(FirebaseLoggerLevel.error) firConfig.analyticsConfiguration = firAnalyticsConfig FirebaseApp.configure() setUserId The following user ID variables are available: TiQ Variable Name Type Example Notes firebase_command_name JS Code b.firebase\_command\_name + ",setUserId" Case-sensitive, comma-separated, no spaces firebase_user_id Text john.doe@someprovider.com Required. Any valid string This produces the following call in the native Firebase API: Android: FirebaseAnalytics.setUserId("john.doe@someprovider.com"); Swift: Analytics.setUserID("john.doe@someprovider.com") setScreenName The following screen name variables are available: TiQ Variable Name Type Example Notes firebase_command_name JS Code b.firebase_command_name + ",setScreenName" Case-sensitive, comma-separated, no spaces firebase_screen_name Text Order Confirmation Required. Any valid string firebase_screen_class Text Order Optional. Any valid string This produces the following call in the native Firebase API: Android: FirebaseAnalytics.setCurrentScreen(<current activity reference>, "Order Confirmation", "Order"); Swift: Analytics.setScreenName("Order Confirmation", screenClass: "Order) setUserProperty The following user property variables are available: TiQ Variable Name Type Example Notes firebase_command_name JS Code b.firebase_command_name + ",setUserProperty" Case-sensitive, comma-separated, no spaces firebase_property_name Text user_loyalty_status Required. Any valid string firebase_property_value Text vip Required. Any valid string. Set to empty string to clear previously-set value. This produces the following call in the native Firebase API: Android: FirebaseAnalytics.setUserProperty("user_loyalty_status", "vip"); Swift: Analytics.setUserProperty("vip", forName: "user_loyalty_status") logEvent The following log event variables are available: TiQ Variable Name Variable Example Notes firebase_command_name JS Code b.firebase_command_name + ",logEvent" Case-sensitive, comma-separated, no spaces firebase_event_name Text   event_ecommerce_purchase Required. Any valid string. Use one of the recommended event types listed above for best results. firebase_event_params JS Code {"param_travel_class" : b.travel_class, "param_transaction_id": b.order_id}; Optional. Any valid JSON object. Use one of the recommended default parameters listed above for best results. Custom parameters must be defined in the Firebase console before they show in reports. This produces the following call in the native Firebase API: Android: Bundle b = new Bundle(); b.putString("param_travel_class", "first"); b.putString("param_transaction_id", "A123456") FirebaseAnalytics.logEvent(FirebaseAnalytics.Event.ECOMMERCE_PURCHASE, b); Swift: Analytics.logEvent(AnalyticsEventEcommercePurchase, parameters: [AnalyticsParameterTravelClass: "first", AnalyticsParameterTransactionID: "A123456"])   ... View more

The following article describes all Customer Data Hub Profile settings. In this article: How it Works To view your profile settings, log into Customer Data Hub and click your initials on the upper-right corner of the screen and then select Settings from the drop-down list. After changing editable settings, you must click Save, and then click Save/Publish for the changes to take effect. Read-only (non-editable) settings can only be changed by Tealium support or the account manager. All settings are read-only except Enable Rule Dependency Checking and Enrichment Order Respects UI Order. General Settings Activate AudienceStream (Read Only) Enable/disable all AudienceStream features for the current profile. AudienceStream Event Filter (Read Only) Enter the event attribute name and value (case insensitive). Enter the Event Attribute name and value (case insensitive). Only events matching this condition are sent to AudienceStream. Leaving these fields empty sends all events to AudienceStream. While the filter only accepts a single attribute name and value, the event filter is applied after server-side enrichments are applied, which allows for more complex filtering based on a custom attribute using enrichments and rules. Visitor Stitching (Read Only) Enable Visitor Stitching to merge visitor profiles across platforms, devices, and browsers when they originate from the same visitor. With this insight, you can apply your marketing efforts with greater precision and efficiency. Default value is ON. Profile Retention Time (Read Only) A visitor's last event determines the retention start time, in days. Display/UI Time Zone (Read Only) Select the time zone for your Customer Data Hub dashboard display. Selections are Greenwich Mean Time (GMT) or Local Time. Selecting Local displays the browser time for the user currently logged in. Enable Rule Dependency Checking (Editable) Enabling rule dependency checking ensures that attribute dependencies on rules are captured and executed in the correct order. Default value is ON. It is recommended that this setting is always set to On. If this setting is set to Off, rules are not taken into consideration when calculating execution order and, if there are rule dependencies, enrichments are not guaranteed to execute in the correct order. Enable Visitor IP Attribute (Read Only) When enabled, the visitor’s IP address is available as an attribute named Client IP. This attribute can be mapped in connectors and used in enrichments and rules. The Client IP attribute is not visible in Live Events or Trace. To see the values of this attribute in Live Events or Trace, enrich a separate attribute with the Client IP attribute. Data layer enrichment key: client_ip . Available in AudienceStore as current_visit.last_event.client_ip . Default value is OFF. Enrichment Order Respects UI Order (Editable) Enabling this updates the way enrichments are ordered to respect the order that they appear in the user interface. Default value is ON. Usage Report Start Date (Read Only) Set the date to use as the default start date for usage reports. DataAccess Event Data Storage (Read Only) A signed contract is required before enabling Event Data Storage. Audience Data Storage (Read Only) A signed contract is required before enabling Audience Data Storage Enable Spectrum (Read Only) Before enabling Spectrum for existing customers who have been using DataAccess, a data migration is needed to ensure all existing and new data are written to the correct location. Open a ticket with Support Desk to request this feature. Default value is OFF. EventStore Retention Time (Read Only) Determines how long EventStore data is retained. Default value is 390 days (13 months). EventDB Retention Time (Read Only) Determines how long EventDB data is retained. Default value is 90 Days. EventStream Connectors Activate EventStream Connectors (Read Only) Enable/disable EventStream Connectors for Events features for the current profile. Default value is ON. Region Region (Read Only) The Region above is the authority storage location for your data. Typically, you should choose a geographic location closest to a high percentage of your customers. One exception is that some clients have legal restrictions that require their data be stored in a specific geographic location. If you are unsure which is the best region for this profile, select US East and request an “Optimal Authority Region” report from Customer Success Leadership. They will provide the region recommendation after collecting a few days of data. Any data collected in an incorrect region may be discarded. Daily Visitor Query Cap Sample Size of Daily Visitors to Process (Read Only) Determines the sample size of visitors used to project results in Audience Sizing and Audience Discovery queries. Audience Sizing Jobs run on total visitors matched, not just those from the sample. Learn more. Default value is 100000. Predict Enable Predict Premium (Read Only) Enable Predict Premium plan for the profile. When enabling or disabling this feature, Max Number of Model Trainings and Max Number of Concurrently Deployed Models should be adjusted to reflect the current contract. ... View more

This article describes how to view and manage your Customer Data Hub server-side version history. Table of Contents Placeholder How it Works In the sidebar, click Server-Side Versions to view an easy-to-understand display of Customer Data Hub version history. Dashboard Filters The colored box in the Showing list shows the latest version on the chart (default).  The All Revisions list on the right of the screen displays all recent revisions (default). You can modify the list by selecting a specific date range in the start and end date textfield boxes above and clicking Update Date Range.  Version Options Clicking on a version in the Showing list allows you to change to it a different version. Alternatively, you can click on Add Another Version to show additional versions onto the chart. The following chart shows two versions selected.  You can close a version at any time by clicking on the X icon on the right side of the colored box.  Each version on the chart is shown by a different (random color) line, and each point on the line refers to a different revision.  The All Revisions list on the right of the screen will update with all revisions related to these two versions selected. You can click on any of the revisions in the chart or from the All Revisions list to get a pop-up that displays the following information: Whether or not the revision has been published. The email address of the publisher. The revision date. Revision comments. Clicking on Switch to This Revision will take you to an overview page for that revision in Customer Data Hub.  Using the Diff Tool Select two or more revisions from the All Revisions list, then click Show Diff to see differences between the two revisions. You will be taken to a new screen showing the differences between the two revisions (if any). The Added column shows what rule or attribute has been added. The Changed column shows what rule or attribute has been modified The Removed column shows what rule or attribute has been removed. The diff screen is a read-only screen, and no changes can be made here. When clicking the  < Back link to return to the previous screen, you will lose any changes you made on the server-side versions chart. Alternatively, clicking the Back button on the browser will just take you to the Customer Data Hub Overview page, and you will still lose your changes on the server-side versions chart.     ... View more