Use CTRL + F (CMD + F) for quick search.
- Is this functionality provided for tests?
The Free plan provides 1 Website Protection campaign for 14 days from the date of registration for tests. Full access to the Website Protection functionality is available on the Basic+ plan and higher.
- Can Facebook API be used to track conversions?
If you're using the Facebook conversion tracking by API, Facebook will automatically get the data about the page you want to hide from Facebook. Accordingly, using Facebook API is prohibited, as it contradicts using the Website Protection campaign goals.
- How to set up a postback for a Website Protection campaign?
- For a Website Protection campaign with a redirect, setting up a redirect link (black page) is similar to setting up a postback for a standard campaign offer link - steps 3 and 9 of this article. http://help-center.peerclick.com/en/articles/4238148-offer-general-settings
- For a Website Protection campaign without a redirect, you need to extract the cid value from the script to pass it to the affiliate network to register the conversion and postback to the tracker using the following script:
$res = \BotDetecter::getResponce();
$cid = isset($res['cid']) ? $res['cid'] : null;
This script is inserted into a block with a white or black page. Further use of cid is implemented in the page code.
Cid is passed to the required place on the side of the affiliate network and then sent to the tracker with a postback. The implementation of the passing the cid value is up to the user.
- Why is the website protection campaign not working?
1. Try installing PHP version 7.0.
2. The logic of work - a redirect to a black offer occurs if no matches are found according to the rules for determining the bot. Make sure that your test visit does not match one of the selected bot definition rules, standard or custom.
To determine if a visit belongs to bots or users, you can view detailed information by visits in the click log, including the rule that determined the visit as a bot.
3. If the logic is correct, check what returns if you embed the line
<?php print_r(\BotDetecter::getResponce());die(); ?>
- for redirect mode - put before or after the line with the redirect.
- without redirect mode - put before the code with a condition.
This line interrupts the rendering of the page and displays the response from our server.
Server response example:
Array ( [token] => 1 [ip] => 18.104.22.168 [cookie] => Array ( ) [useragent] => Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36 [utm] => +03:00 [is_bot] => [expires] => Array ( [flow] => 1607440178 [cid] => 1607440178 ) [cid] => 81275f105bd03cbc57f7b1444a825061-22030-1207 [redirect_to] => https://biz.example.store/? )
Where https://biz.example.store/ is the URL where the user visit goes.
If it displays a response from our server, the script is most likely installed correctly.
! If the campaign is paused, displays the following response:
! There is an option that the hoster can interfere with the script by overwriting the redirect headers.
! There is also a variant of a specific implementation of the page (where a script is installed) that blocks the transfer of headers.