This article shows how to troubleshoot a mobile implementation of iQ Tag Management via the published file mobile.html.

In this article:

Table of Contents Placeholder


When you activate a mobile profile in Tealium iQ a file named mobile.html is published to the following path on the CDN:{account}/{profile}/{environment}/mobile.html

This file is used by the native mobile library to receive mobile publish settings and to facilitate the Tag Management module. This file can be useful to perform some basic troubleshooting of your mobile implementation. 

Inspecting mobile.html 

The behavior of utag.js on the mobile.html page will be similar to that of a standard desktop website page. The utag.js file is loaded and subsequent vendor tags are executed.

To inspect the mobile.html page:

  1. Load the mobile.html URL for your iQ profile in a new browser window.
  2. Open the developer tools or web console of the browser to inspect the page source:mobile-html-developer-tools.jpg

From here you can now perform many of the same troubleshooting techniques that you would use for a website witih Tealium's utag.js installed.

Verifying the Publish Timestamp

The first thing to verify is that your most recently published changes are being loaded in mobile.html. This is done by matching the timestamp from the HTML source to the timestamp from the iQ Versions screen.

To verify the publish timestamp:

  1. At the top of the page source of mobile.html, look for the published timestamp on the first line. The timestamp in mobile.html has the following pattern: ut.4.0.YYYYMMDDHHMM. (Time is always in GMT.)
  2. In your iQ profile, go the Versions screen and find the most recently published version of the same environment. The timestamp of this publish should match the timestamp found inside mobile.html.

Inspecting Mobile Publish Settings JavaScript Object

The mobile.html page uses a JavaScript object named mps to store the values of the mobile publish settings. You can inspect this object to verify your settings.

To inspect the mps object:

  1. Type "mps" into the web console and hit enter.
  2. The properties marked "4" and "5" correspond to versions 4.x and 5.x of your mobile library respectively. 

Mobile_MPS_4_and_5.pngSimulating Tracking Calls

The behavior of utag.js on this page will be similar to that of a standard desktop website page. This means you can watch the network activity to see which utag.*.js files are loaded and you can trigger tracking calls from the browser console to verify that your tags are working as expected.

To simulate tracking calls in mobile.html:

  1. From the browser console, type utag.view({screen_title : "Test Page"}) and hit enter.
  2. Go to the network activity screen to inspect the outgoing vendor tracking activity.