Tealium Learning Center

View the Release Notes summary to learn about updated product features, enhancements, and fixes. To view details about how to use a new feature, click the Learn More link next to the description. Universal Data Hub (Cool Stuff) Resolved bug preventing the UDH user interface from accurately depicting badges being assigned at end of visit. (Fix) Fixed an issue that incorrectly allowed individual badges to be selected as a view perspective in Audience Discovery. (Fix) Resolved a bug causing double counting of Omnichannel enrichments. (Fix) Corrected an issue that prevented you from deleting attributes. Tags (Cool Stuff) Updated our Movable Ink tag to the vendor's latest requirements. (Cool Stuff) Updated the Google Analytics tag to use gtag.js. (Cool Stuff) Updated the DoubleClick Floodlight tag to use gtag.js. (Cool Stuff) Updated text and logos for rebranding SOASTA mPulse to Akamai mPulse. (Learn more) (Fix) Fixed our Adobe Marketing Cloud ID Service tag to include the tracking server configuration object to ensure that the Analytics ID is preserved. iQ Tag Management (Fix) Fixed an issue in the Channels Extension that caused incorrect channels to be matched after deleting a channel from the configuration. (Fix) Corrected an issue with load rules assigned to tags in a library not remaining assigned after library is inherited into a profile. (Fix) Corrected a different manifestation of a previously-resolved issue in the Lookup Table extension where output values containing a single-quote would cause a syntax error in the generated utag file. (New Stuff) Update allows concurrent users to perform multiple merges before saving the profile. In addition, concurrent users with unsaved changes will be prompted to merge when new versions of the profile have been created. (Learn more) Connectors (Cool Stuff) New Marketplace Connector: Close.io (New Stuff) New Marketplace Connector: Swrve (New Stuff) New Marketplace Connector: Sendloop (New Stuff) New Marketplace Connector: GoSquared (New Stuff) New Marketplace Connector: Express Pigeon (New Stuff) New Marketplace Connector: ClickSend (New Stuff) New Marketplace Connector: Keen IO Installations (Cool Stuff) Firebase Analytics integration with mobile libraries (Android and iOS/Swift) (Learn more) (Fix) Bug fixed in release 5.3.1 for iOS. Lifecycle 'isfirstlaunch' was set to true on relaunch. (Fix) Release 5.3.1 has multiple bugs fixed for crash issues reported in github by end users of Tealium iOS SDK (New Stuff) Added the Tealium Crash Reporter module for the Tealium Android library to provide application crash tracking capability for implementations using the Tealium Android Framework. (Learn more) ... View more

This article is an introduction to Tealium EventStream, a data collection and API hub that sits at the center of your data supply chain. This article covers the following topics: Table of Contents Placeholder How It Works EventStream handles the entire data supply chain: from the setup and installation of data sources where activity is tracked, to identifying and validating incoming data to the Customer Data Hub, to enhancing that data with enrichments, to taking real-time action with event feeds and connectors. EventStream supports this entire data orchestration workflow with the following features: Data Sources (Installation and Data Collection) Live Events (Real-time Data Inspection) Event Specifications and Attributes (Data Layer Requirements and Validation) Event Feeds (Filtered Event Types) Event Connectors (API Hub Actions) EventStream is a streaming product that does not save data to disk. EventStream only keeps data in memory until it is sent to its next destination. Data Sources Data sources represent the platforms where you install Tealium to collect data. The first step to start using EventStream is to add a data source. When you add a data source, you will receive installation instructions for the platform you chose. Each data source has a unique key that must be used in the installation code to identify the data coming from that installation. Data sources can be linked to event specifications to provide more detailed code samples showing how to track your defined events on the given platform. With data sources you can easily filter incoming events in Live Events to verify that your installation is working and to inspect data quality. Learn more about Data Sources. Event Specifications and Attributes Establish a solid data foundation by creating event specifications. Specifications define your data layer by identifying the event types you want to track and their associated event attributes. Specifications will ensure you maintain a high quality of data for EventStream to process. Specs and attributes help you establish a universal data strategy across all of your digital properties. Learn more about Event Specifications. Learn more about Attributes. Live Events Live Events is a real-time chart showing incoming data from your data sources. Once your data source is installed and sending data, live events will show that data as it arrives in the Customer Data Hub. In the live events chart, click a bar to see the details of the event received. From there you can define event attributes, see data validation of events, or define new specifications based on incoming events. In addition, if you have specifications activated, the data quality of the incoming events will be reflected in the bar chart so you can quickly see if there are invalid events that need to be fixed. Learn more about Live Events. Event Feeds Event Feeds are groups of events that match specific conditions based on their attributes. Feeds are a subset of all events that can be targeted to vendor connectors. Working with feeds makes it easier to inspect incoming events in the Live Events chart and to see activity volume over time. Event Connectors Event connectors are API integrations with your vendors that send data from an event feed in real-time. Connectors are configured with your vendor account credentials and data mappings to send event attributes to the corresponding parameters expected by your vendor. Learn more about Event Connectors. ... View more

This article provides the data layer definition for basic video tracking. Table of Contents Placeholder Data Layer Attributes Variable Description Example Type tealium_event Tealium event name eg. video_pause. "video_pause" String video_playhead The playhead position (in seconds) of the video at the time of the event. 75 Number video_id A unique identifier for the video. "xWlEk2i9r5Q" String video_length The total length (in seconds) of the video. 300 Number video_milestone The percentage of video played eg. 25, 50, 75 25 Number video_name The display name of the video. "How to track videos in Tealium" String video_platform The name of the platform serving the video eg. "YouTube". "YouTube" String Event Tracking Video Load Identifier tealium_event="video_load" Description The video was loaded and made available to the viewer.. Sample { "tealium_event" : "video_load", "video_id" : "xWlEk2i9r5Q", "video_length" : 300, "video_name" : "How to track videos in Tealium", "video_platform" : "YouTube", } Video Start Identifier tealium_event="video_start" Description The video began playing for the first time (either via auto-play or user click).. Sample { "tealium_event" : "video_start", "video_id" : "xWlEk2i9r5Q", "video_length" : 300, "video_name" : "How to track videos in Tealium", "video_platform" : "YouTube", } Video Play Identifier tealium_event="video_play" Description The video playback changed from not playing to playing.. Sample { "tealium_event" : "video_play", "video_playhead" : "75", "video_id" : "xWlEk2i9r5Q", "video_length" : "300", "video_name" : "How to track videos in Tealium", "video_platform" : "YouTube", } Video Pause Identifier tealium_event="video_pause" Description The video playback changed to paused. Sample { "tealium_event" : "video_pause", "video_playhead" : 75, "video_id" : "xWlEk2i9r5Q", "video_length" : 300, "video_name" : "How to track videos in Tealium", "video_platform" : "YouTube", } Video Seek Identifier tealium_event="video_seek" Description Video playback was advanced forward or backward to a new playhead. Sample { "tealium_event" : "video_seek", "video_playhead" : 75, "video_id" : "xWlEk2i9r5Q", "video_length" : 300, "video_name" : "How to track videos in Tealium", "video_platform" : "YouTube", } Video Complete Identifier tealium_event="video_complete" Description Video playback has completed. Sample { "tealium_event" : "video_complete", "video_id" : "xWlEk2i9r5Q", "video_length" : 300, "video_name" : "How to track videos in Tealium", "video_platform" : "YouTube", } Video Milestone Identifier tealium_event="video_milestone" Description The video playback reached a specific percentage milestone. Sample { "tealium_event" : "video_milestone", "video_playhead" : 75, "video_id" : "xWlEk2i9r5Q", "video_length" : 300, "video_milestone" : 25, "video_name" : "How to track videos in Tealium", "video_platform" : "YouTube", } ... View more

The Customer Data Hub can send data to external systems via connector actions. Those external systems might restrict access to only an approved list of IP addresses, also called a whitelist. To allow the Customer Data Hub to send data to your network, add all of the following IP addresses to your whitelist:  IP Address Region 50.18.192.141 US-West-1  -  San Jose, California 52.36.206.227 44.238.18.189 US-West-2 - Oregon 107.23.142.239 3.210.6.72 3.210.238.60 US-East-1  -  Ashburn, Virginia 54.229.215.104 EU-West-1  -  Dublin, Ireland 52.29.185.253 EU-Central-1  -  Frankfurt, Germany 18.166.4.167 AP-East-1  - Asia Pacific, Hong Kong 13.112.219.50 AP-Northeast-1  -  Tokyo, Japan 52.62.159.75 AP-Southeast-2  -  Sydney, Australia   ... View more

What is changing? The JSON files in DataAccess will be changed from having a .gzip extension to a .gz extension. Only new files generated after the release will have the new .gz extension. Any files that existed prior to the release will retain their original .gzip extension. The change does not alter the format of the file contents or the compression method used, nor does it impact CSV files. Why is this changing? The current filename extension of .gzip is not the standard for files compressed with the gzip application. Switching to the industry standard extension .gz will improve our compatibility with third-party software used to ingest these files. When is this changing? The potential release date is August 4, 2017. What do I need to do? You must update any integrations that reference the filename extension explicitly eg. "*.gzip". For example, when using the AWS s3api command line interface to fetch a single JSON file the .gzip extension is used in the command: aws s3api get-object --bucket uconnect.tealiumiq.com \ --key {account}/{profile}/events/{stream}/{filename}.gzip ./   This would need to be updated to: aws s3api get-object --bucket uconnect.tealiumiq.com \ --key {account}/{profile}/events/{stream}/{filename}.gz ./ If your integration uses a wildcard filename specifier that does not reference .gzip (eg. "*.*") then it's possible no change is necessary. However, this is potentially a breaking change so we strongly recommend that all integrations with EventStore/AudienceStore be reviewed prior to the release to ensure uninterrupted service. FAQ Q: ​When is the changing happening? ​A: The release is tentatively scheduled for August 4, 2017.   Q: Do I have to update my integrations to use the new filename extension? A: Yes. After the release, all new files will use the .gz extension and any integrations looking for the older .gzip files will not detect the new files. That is, all previous files with the .gzip file extension will retain their file extension, but all files created after the release will have the new .gz extension.   Q: Can I update my integrations now in anticipation of the release? A: New files with the .gz extension will not appear until the release date. We recommend that your integrations be prepared now to accommodate both extensions, .gz and .gzip, to ensure a seamless transition.   ... View more

This article is an introduction to page performance and how it relates to tagging. It covers the basics of the browser load process, defines important terms, and summarizes the available performance options in iQ Tag Management. In this article: Table of Contents Placeholder What is Page Performance? Page performance is the measure of how quickly a web page loads and renders in the browser. The primary interest in page performance is to optimize the user experience. It's no secret that a slow loading page is a good way to lose visitors from your site, so maximizing page performance is generally considered a worthwhile endeavor. As you begin to evaluate page performance, one thing becomes clear: there are a wide variety of factors that affect the speed of a loading page. Everything from network latency, file compression, and browser caching to CSS, fonts, and inline JavaScript have an impact on performance. Tagging (loading JavaScript files) is just one of the factors of this complex process and will be the focus of this article. More specifically, we will explore the contributing factors to perceived page performance and what controls can be used within the iQ Tag Management console. Specifically, the focus is on two concepts that are most relevant to tagging and performance: Asynchronous JavaScript DOM-Ready Event Perceived Load Time vs. Actual Load Time Before we begin it's worth mentioning the difference between perceived load time and actual load time. The actual load time is traditionally a measurement from the browser that indicates when all of the assets of a web page have been processed. The perceived load time, arguably the more important of the two, is a measurement of when the web page is visually rendered and available to the user. This topic of what to measure is quite technical and can be researched via industry experts such as WebPagetest, Google's PageSpeed Tools, and Yahoo's YSlow. The iQ Tag Management JavaScript library (utag.js) is designed to have little or no impact on the perceived load time of a page. Tealium Files vs. Third-Party Files At the foundation of the Tealium solution is our file serving framework, the Multi-CDN. This global and real-time solution ensures that Tealium's files are delivered to your visitors' browser at the quickest speed possible. The JavaScript loader (or wrapper) files contain the logic and configuration from your iQ Tag Management account and can be identified in your browser's network console by the names "utag.js" and "utag.#.js". These are the files served by Tealium from the "tags.tiqcdn.com" domain. Example browser network log of Tealium files: As the browser loads these Tealium files there might be additional requests for files that are required by your tag vendors. These files can be identified as coming from a domain other than "tags.tiqcdn.com" and with names other than "utag". Tealium does not host nor control the performance of third-party files. Browser File Cache Browsers have their own methods of optimizing page performance, the most widely known is file caching. The browser will save a copy of a file so that it doesn't request the same content over the network repeatedly. This reduces network traffic and allows site pages to load more quickly once the initial assets are cached in the browser. Learn more about how Universal Tag (utag.js) files are cached in the browser. Asynchronous JavaScript Asynchronous JavaScript is a method for delaying the loading of non-essential elements to prioritize page rendering to the user. You can think of asynchronous requests in a page like a "To Do" list for the browser: when the browser doesn't have other, higher priority elements to render, it will process the items in its asynchronous "To Do" list. The opposite effect is achieved when using synchronous JavaScript, which behaves like a "Must Do" list for the browser: the browser must block the rendering of the page in order to process items in its synchronous "Must Do" list. All modern tag vendors have switched to the asynchronous method, which is one of the most common ways to improve page load speed. What does iQ Tag Management do? The utag.js loader file and all subsequently loaded tag files use the asynchronous method. Additional reading: Synchronous vs. Asynchronous JavaScript Optimize JavaScript Use (PageSpeed Recommendations) | Google Developers DOM-Ready Event The DOM-ready event, also known as "DOMContentLoaded", is the browser's way of indicating when it has completed the loading of the main content in the page. This event is commonly used as the trigger for loading non-essential elements of the page to ensure that the page renders as quickly as possible (i.e. percieved load time). What does iQ Tag Management do? Vendor tracking is delayed until the DOM-Ready event to minimize the impact on page rendering. Additional reading: Understanding Order of Operations (utag.js) DOMContentLoaded - Event reference | Mozilla Developer Network iQ Tag Management Settings and Best Practices There are several options in iQ Tag Management to help you control how JavaScript is loaded on your pages. Every website is different so there isn't a single optimal solution for everyone. The default settings in iQ are balanced to have minimal impact on perceived load time and provide the greatest compatibility with the largest number of vendor tags. Code Placement Code placement refers to where in the HTML document the utag.js code snippet appears. There are two main locations where you might load JavaScript in your HTML: inside the <head> tag or inside the <body> tag. The Tealium utag.js file must be loaded inside the <body> tag. Base HTML structure: <html> <head> <!-- Script Files here --> </head> <body> <!-- Tealium utag.js asynchronous script here --> .... </body> </html> The best practice is to place the utag.js code snippet at the top of the <body> . This position allows your tag management configuration to load asynchronously while the page continues to render so that your tags are ready to fire at the DOM-Ready event. The utag.js file can be placed lower in the <body> if needed. In general this will result in delayed loading of tags and/or a slightly faster perceived load time. Read more about utag.js code placement. Ready Wait Flag The Ready Wait Flag found in the Publish Configuration area controls when utag.js will begin executing. By default, this flag is "Off" and utag.js begins executing as soon as it's loaded into the page. When this flag is set to "On", utag.js will wait for the DOM-Ready event before executing. You can deprioritize your tags in favor of possible gains in page load time by turning this flag on. Setting Ready Wait Flag to "On" could lead to lost tracking due to visitors navigating away from the page before the tags have loaded. Always perform thorough testing before releasing new settings to your live site. File Compression and Minification The files delivered from the Mult-CDN are compressed using the GZip industry standard. This ensures the JavaScript files (text files) are as small as possible upon delivery to the browser. This behavior cannot be changed. The code within those JavaScript files is also minified by default. Minification adds another step of compressing the code files to only their essential text by removing comment lines and white space. You can turn this setting off if needed (eg. for debugging purposes). Read more about the Minify Tag Templates setting. Bundling Bundling allows vendor tag code to be included in the main utag.js file to eliminate additional HTTP requests from the page. By default, the vendor tags configured in iQ Tag Management are loaded as separate files (eg. utag.4.js) into the page. This is done to minimize the risk of introducing a code error into the main utag.js file i.e. an error in one file will not affect the others. However, using separate files increases the number of HTTP requests the page makes to load your tags. And while the delivery of these files is optimized via the Multi-CDN and browser caching, if you need to optimize further then bundling is an option to consider. Here is a simple example where bundling tags resulted in an 80% improvement in load time for the files coming from Tealium. Two vendor tags unbundled Number of files: 3 (utag.js, utag.1.js, utag.21.js) Total Size: 18.2 KB (9.1 + 5.0 + 4.1) Total Time: 100 ms (54 + 23 + 23) Two vendor tags bundled Number of files: 1 (utag.js) Total Size: 17 KB Total Time: 19 ms Read more about bundling individual tags or bundling any tag using the "All Pages" load rule. Tag Timing (Tags) As mentioned, the default behavior in utag.js is to wait for the DOM-Ready event before firing the vendor tags. The Tag Timing setting is a tag-level setting that controls this logic for individual tags. The default setting is "DOM Ready (default)", which means "wait for DOM-Ready". When this flag is set to "Prioritized", the individual tag will run as soon as possible (usually prior to DOM-Ready). Read more about the Tag Timing for tags. Tag Ordering Your configured tags are loaded into the page in the same order as they appear in the iQ Tag Management console. You can drag and drop tags into the desired order of loading. The Tealium best practice is to put your analytics tag(s) and other high priority tags at the top of the list to ensure they are the first ones loaded. Read more about Tag Ordering. ... View more