Standard tracking consists of the following tracking options:
|Allow ClickID Pixel Postbacks||
ClickID Pixel Post is created by adding the click ID to the tracking URL. This method is considered very secure, because a transaction can be generated on by using a click ID. A click ID can only be used once and within the time frame of the configured cookie life. This helps prevent fraud. The following is an example of a pixel URL with the added click ID:
|Allow AFID Pixel Postbacks||
An affiliate ID pixel post is created be adding the affiliate ID (AFID) to the tracking URL. This method is not considered secure, because a transaction can be generated simply by knowing the campaign and affiliate ID leaving the affiliate ID pixel post method open to fraud. The following is an example of a pixel URL with the added affiliate ID:
|Enable Pay-Per-Call Integration||
The LinkTrust pay-per-call service allows you to create, track, and manage call-based campaigns.
|Allow Cookie Tracking||
A cookie is a simple piece of data that is unable to perform any operation by themselves. Cookies allow users to be tracked when they visit various sites.
|Allows Cookieless Tracking (IP Backup)||
Cookieless tracking is a feature that can increase your tracking accuracy by approximately 5-10%. By default, this feature is enabled. If this feature is disabled, a merchant might report higher sales conversions then what appears in LinkTrust and consequently to an affiliate.
|Restrict Postbacks to White Listed IPs||
Restrict Postbacks to White Listed IPs is a security feature that locks down the ability to post transactions into your account unless they originate from the IP addresses you listed in the IP White List. In order for this feature to use the white list functionality, you must add the known IP addresses, posting in the transaction, to the While List field on the Domains / IPs page. This feature works for all ServerSide Postbacks (ClickID and AFID) and Mobile Tracking. .
To restrict postbacks to white list IP addresses, do the following:
To create a white list of IP addresses, do the following:
|Allow Custom Conversion Parameters||
Custom conversion parameters are parameters that allow the merchant to dynamically send the affiliate payout, merchant payout, and transaction approval information to LinkTrust on the confirmation pixel.
These parameters allow you to add specific values to a confirmation pixel that modify the transaction and allow for customized conversions. Below are the parameters and values that can be added to the confirmation pixel of a flat rate (non-percent) based campaign.
You can set the affiliate payout by putting &AP=0.00 on the query string in a confirmation pixel. The affiliate payment parameter is not case sensitive and should not contain a dollar sign ($); for example, &AP=4.99 or &AP=4.99. You must use a decimal for cents; for example, &AP=4.25 would be interpreted as $4.25 while &AP=425 would be $425.00.
You can set the merchant revenue by putting &mp=0.00 on the query string in a confirmation pixel. The merchant payment parameter is not case sensitive and should not contain a dollar sign ($); for example, &MP=4.99 or &MP=4.99. You must use a decimal for cents; for example, &MP=4.25 would be interpreted as $4.25 while &MP=425 would be $425.00.
You can set whether or not the transaction is approved by putting &A=Y or &A=N on the query string in a confirmation pixel. Since LinkTrust only looks at the first letter of this parameter, you can cloak the value in the confirmation pixel by adding additional letters, as shown below.
To approve a transaction, all of the following can be used:
To unapprove a transaction, all of the following can be used:
To enable any of the custom conversion parameters for a campaign, do the following:
If Allow Custom Conversions Parameters is not marked, LinkTrust does not recognize any of the parameters on the confirmation pixel.