3 steps to a Tealium Queue to avoid lost data on Single-Page Applications

How to enhance Tealium with a “utagQueue” to avoid losing data if users start clicking around before the Tealium library has loaded.

  1. If your website is a Single-Page Application (SPA), you likely use the utag_cfg_ovrd.noview flag to avoid sending the “automatic” utag.view call to execute the initial Pageview and have your application send that call (to avoid a duplicate pageview on the initial pageload). But how does your application know that Tealium is ready?
  2. On slow mobile connections, loading can take a long time. But until then, a lot can happen: People start clicking around because they already see the page. Your developer’s code captures these interactions and wants to execute a utag.link or utag.view call (e.g. to register the next “virtual Pageview” on a SPA), but they can’t because Tealium has not loaded completely yet. The data is lost.

Step 1:

Step 2:

Note that I am using nested Object notation (page.title instead of Tealium’s usual “flat” format (page_title)). You will need Tealium’s “Data Layer Converter” to make this work, so if you can, go for flat notation.

Step 3:

Another Option

But…

--

--

Digital Analytics Expert. Owner of dim28.ch. Creator of the Adobe Analytics Component Manager for Google Sheets: https://bit.ly/component-manager

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Lukas Oldenburg

Digital Analytics Expert. Owner of dim28.ch. Creator of the Adobe Analytics Component Manager for Google Sheets: https://bit.ly/component-manager