Page Tracking

Learn how to track page view using utag.view().

This guide explains how to track page views using utag.view() . Page view tracking gathers information about the navigation path a visitor takes. Each time a web page is loaded or the main content of the screen is changed, a page view should be tracked.

The default installation of utag.js will automatically track page views on the DOM-ready event.

Single Page Applications

On single page applications where the page loads utag.js only once per visit, you will suppress the automatic page view tracking call to allow your application to make these calls directly.

To override the automatic page tracking add this line to your page prior to loading utag.js:

window.utag_cfg_ovrd = {noview :true};

Once your application is loaded (and utag.js is loaded) you can trigger utag.view() tracking calls in your page code. These calls would typically be triggered at the DOM-ready event or any event that causes a content view refresh.

Important Notes

The utag_data object declared on initial page landing is not re-purposed with these calls. If data from the initial page landing needs to be used it will need to be re-declared and passed again in the method call.

As of utag.js version 4.26, load rules are re-evaluated for both utag.view and utag.link calls. Note: a utag.link call will not bring in a new tag (one that isn’t already loaded from initial page load), whereas a utag.view call will.

For utag.js versions prior to 4.26, load rules are not executed again during manual utag.view() or utag.link() calls. This means only the tags loaded on the initial page landing are available to be executed. For example, if SiteCatalyst and DoubleClick are the only two tags to run on page landing, these will be the only two tags available to respond to the utag tracking calls.

Global and Tag-scoped Extensions are executed during these calls. Pre-loader and DOM Ready extensions will not executed during these calls.