Conversion Tracking

Trackhouse supports conversion* tracking via client (aka pixel tracking) and server-side notifications (aka postbacks aka callbacks).

This support extends to also notifying the traffic source (if appropriate) via a client or server side request.

Notification flow Fig.1 Full Size

Server Side Notification

Server side notification of conversion is the most secure method of conversion tracking. The following URL should be called by the Destination's server on conversion:

This URL should be provided to destinations who will be providing you with server side conversion postbacks.

trfk_id is the unique value that is passed to the destination link. The value of this parameter should replace the 'REPLACE' text in the URL above. Server side notification can be further secured by using some additional security options:

  1. Private Postback URL (unique to Destination)
  2. IP Whitelist
  3. Posback signature (using private key)

Client Side Notification

Client side notification is supported through the following fixed URL:

This URL should be called from the client's browser when the conversion occurs, e.g in an image pixel:

<img src="" width="1" height="1" border="0" />

Note that in this case, when Trackhouse receives the client side notificaiton, it will notify the traffic source of the conversion event (if appropriate) via server to server call.

If you wish to notify traffic source via client side then the following snippet should be used:

<img src="" width="1" height="1" border="0" />

You may alternatively use an iframe snippet (in cases where the traffic source notification page contains javascript):

<iframe src="" scrolling="no" frameborder="0" width="1" height="1"></iframe>

We have built-in support for custom multi-event tracking. Contact us for more details on this.