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:
- From the Campaign Settings page, under Conversion Tracking Options, select Restrict Postbacks to White Listed IPs.
- Select Update.
To create a white list of IP addresses, do the following:
- From the top menu, select Account.
- From the left menu, select Domains / IPs.
- Scroll down to the bottom of the page.
- In the IP Address White List field, enter the IP addresses you wish to allow.
- Note: Enter each IP address on a separate line.
- Select Update Lists.
|
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:
- The first letter is Y or y (e.g., &a=y, &A=Y, &A=Yes, &a=yahoo)
- The first letter is T or t (e.g., &a=t, &A=T, &a=true, &A=Telephone)
- The first value is 1 (e.g., &a=1, &A=1, &a=1234, &A=1abc)
To unapprove a transaction, all of the following can be used:
- The first letter is N or n (e.g., &a=n, &A=N, &a=night)
- The first letter is F or f (e.g., &a=f, &A=F, a=false, A=False, A=Feather)
- The first value is 0 (e.g., &a=0, &A=0, a=0123, A=0abc)
To enable any of the custom conversion parameters for a campaign, do the following:
-
In LinkTrust, go to your campaign.
-
Open Campaign Details.
-
Open Campaign Settings.
-
Under Additional Tracking Options, mark Allow Custom Conversion Parameters.
If Allow Custom Conversions Parameters is not marked, LinkTrust does not recognize any of the parameters on the confirmation pixel.
|