Custom Conversion Events

Tezify conversions are similar to Google Analytics goals. A tracking setup can have one or more conversions. Examples of conversion events are : a visitor subscribing to a mailing list, performing a certain search, watching a certain video, etc.

Setting up Custom Conversions

Custom conversions can be configured within your Tezify tracking setup via any of the following two approaches:

Destination URLs

By specifying a destination URL, a session is marked converted if a visitor accesses the specified URL. For example, if a user registration leads the user to a URL such as ‘/signup.php’, you can specify this URL pattern within your Tezify tracking snippet. Whenever the Tezify tracking will encounter this URL, it will mark the session as converted.




window.wto.conversions = {}
window.wto.conversions.UserRegistered = ‘/signedup.html’

You can specify more than one conversions within a tracking setup:


window.wto.conversions = {}
window.wto.conversions.UserRegistered = ‘/signedup.html’
window.wto.conversions.UserSubcribed = ‘/subscriptionconfirmed.html’

The benefit of specifying conversions through destination URLs is that no code change outside tracking snippet is needed. Also, you can specify only part of the URL. However, please ensure to make sure the URL is unique enough to not occur when conversion has not happened.


Javascript call

Some conversion events may not lead to change in the destination URL. Or the destination URL may not be trackable. For example, if a user clicking to view a video clip is a conversion event, it cannot be tracked through destination conversions because the page URL would not change. Such conversion events can be tracked through a Javascript call. This javascript call will have to be added on occurance of that event (and not to the tracking code snippet):



wto(‘conversion’, ‘<Conversion event name>’)

The above stated Javascript call may fail to track conversion events in certain situations. This would happen if the tracked page gets unloaded before the Javascript call finishes to process. Here’s an example of such a scenario - Lets say you are tracking a website on Mediterranean cooking. Your webpages have links to your Facebook posts. And you are interested in tracking the % of sessions that open your Facebook posts. So, you add the above Javascript call to track such clicks. But, the problem is that your page may get unloaded before the tracking call gets processed. To overcome this, you need to make a tracking call as following:



wto(‘conversion’, ‘<Conversion event name>’, ‘beacon’)

The ‘beacon’ parameter in the above call will ensure the request is processed before your page is unloaded (without blocking your visitor or slowing down your page).


Note : Please avoid using special characters in conversion event names. Please use aphanumerics and spaces.