When do I use different JavaScript tracking methods?

ConversionRuler offers three ways of tracking actions using JavaScript on your web site, they are:

• cr_track - For tracking landings and actions on page loads
• cr_link - For tracking when visitors click on links
• cr_submit - For tracking form submissions

Why different forms of tracking?

cr_link and cr_submit were added solve some specific issues with certain browsers and downloading non-web content (like installers, PDFs and other binary content).

The issue was, unfortunately, that tracking wouldn't work due to issues with those browsers.

What's the problem?

The issue is that for binary content, the page loads to a new URL and some browsers do not call our tracking code at all before the new content loads.

As a general rule, if a link or form opens a new window, or performs an AJAX call, you can use cr_track instead of cr_link or cr_submit.

When in doubt

When to use cr_link

cr_link was added in order to solve a particular bug in browsers when downloading binary files, like installers, PDFs or executables.

When a user clicks on a link which is cr_link-enabled, it:

1. Tracks the action with ConversionRuler ...
2. Waits 300 microsectods
3. Follows the link

This solves the bug in all browsers. (The bug is present in FireFox and Safari.)

In prior versions of the tracking, you could use cr_track:

<a href="/page.html" onclick="return cr_track(2)">Track link with action 2</a>

or

<a href="/page.html" onclick="return cr_link(this, 2)">Track link with action 2</a>

Both tracking forms are still acceptable, but it is generally recommended to use cr_link as it handles all cases accurately for all kinds of links.

When to use cr_submit

cr_submit was added in order to solve a bug in browsers when submitting a form which results in a binary file download (such as installers, PDFs or executables.)

It works similarly to how [[