Browser History Change Event

Requirements

• utag v4.38 or later. For more information about updating the utag.js template, see our knowledge base article Best Practices for Updating to the Latest Version of utag.js.
• The page or app uses history.pushState() and history.replaceState() functions in the browser’s history API for navigation.

How it works

The browser history change event listener monitors the functions history.pushState() and history.replaceState() in the browser’s history API. These two functions are used to manage navigation in SPA without full page reloads. When the visitor navigates to a new page within the app or goes back, the tracking call is triggered.

For more information about how to add an event listener, see Manage events.

Event triggers

Event triggers are the actions the event listener tracks.

History change

This event is triggered by the browser change history.

Event trigger variables

Event trigger variables are the values the event sends with the tracking call. This event has the following default variables:

Example

{
   "tealium_event"  : "history_change",
   "iq_event_id:" : "history_change_events_1"
}