Firefox & Safari manual link tracking

[Jahangir147]

Recent changes to Firefox and Safari have caused us some major issues when trying to manually track links. Typically, this was done using the s.tl() method: you could call this on anything clickable, and it would send a payload of information to Omniture in the form of an image request. Newer versions of these two browsers however are silently failing to do this. So what’s going on? And more importantly, how does one fix it?

The problem
The short version of this story is that these browsers are basically ignoring any scripts that slow down a user’s experience when moving from one page to the next, including your s.tl() script calls.

The official solution
Adobe provides the following solution for tracking links that leave the page. Please note this uganda email list 439482 contact leads example will only work for A tag links, I’ll get to other situations later.

[javascript]Click here[/javascript]

The standard s.tl() parameters are all still there:

type – use this for A tags, and true for other types of HTML elements,
type of link – ‘o’ for custom links, ‘d’ for downloadable files and ‘e’ for exit links,
label – a human readable description of the link for reporting labels
There are also two new parameters, one for overriding certain variables and one that indicates the action to be taken after the s.tl() has completed its recording activities. Here, a pre-built function called ‘navigate’ reads and actions the HREF attribute.

But what of elements that aren’t A tags, that don’t have a HREF attribute? For example, forms that result in a new page? In these cases, the navigate method won’t work (remember it’s expecting a HREF attribute to follow) so we need to use some custom code: