Required settings

API key
Your secret API key. You can find it in the welcome email.
WhitePage
The page that will be shown to bots, spyservices and other unwanted visitors. As a whitepage, you can specify a path on the local server (for example, whitePage.html) or a link to a external source (https://amazon.com/). We strongly recommend using the local page as a whitepage. You can get more detailed recommendations on white pages from our support.
OfferPage
The page that will be shown to targeted visitors. As an offer page, you can specify a path on the local server (for example offerPage.html) or a link (https://google.com/).
Allowed GEO
Two-letter country codes of visitors from which will get to offerpage. For example, if you enter RU, UA system will only allow users from Russia and Ukraine. A list of 2 letter codes can be found here.

Optional settings

Two-letter country codes of visitors from which will get to whitepage. For example, if you enter RU, UA system will block users from Russia and Ukraine. A list of 2 letter codes can be found here.


This option allows you to enable traffic from IP owned VPN/Hosting/Data Centers. Bots also use IP owned by datacenters (including VPN). If your audience has a large percentage of VPN users, then you can enable this option.
Please note that this will reduce the filtering quality.


This option allows you to forward UTM tags or other request parameters. That is, transmit request parameters to offerpage. We recommend enabling this option if you use additional TDS or use UTM to evaluate the effectiveness of advertising campaigns.



These options allow you to filter your traffic based on the UTM tags contained in the request.
If the line specified here is missing in the request, the user will be redirected to the whitepage.
Exact match required!

If none of the tags specified here is contained in the request, then the user will be redirected to the whitepage.
Tags must be separated by commas!

If the line specified here is present in the request, the user will be redirected to the whitepage.
Exact match required!

⚠️ To reduce the possibility of ban recommend using local WHITE_PAGE, place it directly on your hosting!

Curl - uses a server request to show third-party whitepage on your domain. Important: if you have a domain with HTTPS, and the white page (or its components) is not, then perhaps the whitepage will not display correctly. In this case, it is better to find another whitepage.

302 - uses a 302 redirect to redirect the request to a third-party domain. Usually this method requires a trust advertising account.

Choosing the most suitable blackpage display method depends on your server settings, type of advertising campaign and its goals.

meta - User redirect through meta refresh. The default method due to maximum compatibility with different affiliates, hosting and applications. For a few milliseconds slower than the 302nd redirect.

302 - User redirect through 302 redirect. Recommended method if the goal is maximum transitions. InApp browser can track that redirects.

iframe - Uploads content without redirecting user through iframe. The most hidden, but at the same time the slowest method. Attention: if you have a domain with HTTPS and domain blackpage does not have a valid SSL certificate, then this method will not work! If blackpage or him components contain an X-Frame-Options header - this method will not work!

This option allows you to block requests without a referrer. Conversions on advertising in search engines (Yandex, google, bing) and social networks (VK, FB) usually contain a referrer. Enabling this option can lead to loss of traffic from bookmarks and some applications (but this is inaccurate).


If you want to allow requests only if the transition was from certain domains (referrers), you can write them in this field. Only part of the domain can be specified. For example, "google" will allow requests from any Google domains: google.com, google.ru, googleusercontent.com and others. Warning: wrong use of this option can lead to large traffic losses. If you have multi-page landing page, be sure to add your domain. We do not recommend using this option.


Some users want to block certain devices, browsers, or operating systems. This can be done using the following options. But we consider it superfluous.






A delayed start allows you to block the first X unique IP addresses. This is usually not required. But for accounts with a low trust in ad networks with manual moderation, this can be useful.



Paranoia mode uses the most rigid filters. Checks out some additional features inherent in spуservices. But at the same time, in some geos, it can block a significant part of real users. It is recommended to use only in difficult situations.