Conversion Tracking

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

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

Notification flow Fig.1 Full Size

Trackhouse Tokens

Trackhouse supports dynamic parameter replacement in notifications using {tokens}.

Token usage

{token} can be used in:

  1. Destination Links - tokens will be replaced by an appropriate value (either from the click or a reserved parameter). More on this below..
  2. Traffic Source Notification URL (including Campaign specific override) - tokens will be replaced by an appropriate value (either from the click or a reserved parameter). More on this below..

External (Traffic Source) Tokens

Traffic source specific tokens can be included in the "Source Parameters" querystring (which is included in all campaign links for that traffic source, for easy insertion into the traffic source's system).

Note that these tokens are not replaced by Trackhouse but by the Traffic Source at click time. See more info on Traffic Source Parameters

Source Params

Reserved tokens

There are some tokens reserved by the Trackhouse platform for replacement with specific values, as follows:

TokenDescription
{trfk_id}replaced with Trackhouse’s unique event id, by default this is added to the destination link and should be passed back in conversion notifications
{trfk_payout}the payout value specified in the Campaign settings
{trfk_payout_currency}the payout currency specified in the Campaign settings
{trfk_referrer}used as a test override for request referrer
{trfk_ua}used in test requests as an override for the user agent
{trfk_ip}used in test requests as an override for the user IP Address
{trfk_timestamp}used as a test override for event timestamp
{trfk_event}Event type, e.g trfk_custom1, 1, etc.. Custom Event
{trfk_cref}Campaign reference
{trfk_tsref}Traffic Source Reference

Request Parameters

Values sent in the click/event request. The value of any parameter that is included in the click request (i.e in the campaign link) can be used in:

  • a) Destination Links and
  • b) Traffic Source notifications

This is achieved using the following token format: {parameterName}

Example Campaign link:

https://link.trf.kr/C38WE/TNR0K?tid=559348&subid=32

{tid} in Destination Link or Traffic Source Notification Url would be replaced with 559348
{subid} in Destination Link or Traffic Source Notification Url would be replaced with 32

Note on Traffic Source Notification URL:

  • Tokens in the notification URL will be replaced as described above from the click parameters. However, they can also be replaced by corresponding parameters in the destination conversion callback (destination → trackhouse_)
  • Priority (in the case of conflicts) is given to the click parameter. To avoid this (i.e to choose a callback parameter over a click parameter of the same name) you can prefix the token as follows: {callback_parameterName}

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

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:

https://s2s.trf.kr/?trfk_s2s&trfk_id=REPLACE

trfk_id is the unique value that is passed to the destination link Server side notification can be further secured by using some additional security options:

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

Client Side Notification

Client side notification is supported through the following fixed URL:

https://link.trf.kr/?trfk_c2s

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

<img src="https://link.trf.kr/?trfk_c2s" 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="https://link.trf.kr/?trfk_c2sb" 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="https://link.trf.kr?trfk_c2sb" scrolling="no" frameborder="0" width="1" height="1"></iframe>