Cloaking setup

Cloaking is turned on separately in each campaign, on the Cloaking («Клоака») tab. A visitor who doesn't pass the checks gets “white” — a stream of the Final («Замыкающий») type instead of the target one. Anyone who can edit the campaign can change the settings: with view-only access, the tab is visible but has no save button.

How cloaking processes a click

1. The tracker determines the visitor's country, connection type and device and checks whether it's a bot.
2. Cloaking runs the server checks in order: bot, data center or proxy, platform click-id, country, device. The first failed check sends the visitor to “white”.
3. A visitor who passed the checks gets into a stream by the regular rules.
4. If the JS challenge is on, the visitor first gets an intermediate page with a browser check. Those who don't pass it go to “white”.

What always applies and what is configured:

Without cloaking, bots aren't filtered out. Such a click is marked in the statistics and goes through the streams as a regular one, unless the stream has the Bot («Бот») = false condition — see Protecting a stream without cloaking.

Where filtered traffic goes

There is no separate “white” selection in the cloaking settings. A filtered visitor gets the topmost stream of the Final type in the list that is enabled and matches its own filters, schedule and click cap. Target streams are never given to them. If there is no matching final stream, the response is 404.

How to build a pair of streams with the + Black («+ Чёрная») and + White («+ Белая») buttons is covered on the Cloaking streams: “white” and target page.

Turning on cloaking

1. Open the campaign in the Campaigns («Кампании») section.
2. Go to the Cloaking tab.
3. Turn on the switch in the Cloaking card. The settings appear below it.
4. Set up the checks as described in the sections below.
5. Click Save campaign («Сохранить кампанию»).

You can also turn cloaking on and off in two other places:

• in the campaign list — with the switch in the Cloaking column. The change is saved immediately; the check settings stay the same. For a campaign available for viewing only, the switch is inactive;
• in the Create campaign («Создать кампанию») window — with the Cloaking checkbox.

Until the checks are set up on the Cloaking tab, only bot filtering and the country check apply.

Ad platform and click-id

This is the Ad platform — only let through with its click-id block. An ad network adds its own click parameter to the link. Cloaking lets the visitor through only if such a parameter arrived with a non-empty value. Macro text in place of the value that the network didn't replace — for example {fbclid}, {{ad.id}}, [CLICK_ID], __CLICKID__ or ##X## — doesn't count as a received parameter.

• Click the button of your network: + Facebook (fbclid), + Google (gclid), + TikTok (ttclid) or + Microsoft (msclkid).
• For another network, type the parameter name in the “custom parameter + Enter” («свой параметр + Enter») field and press Enter.
• To remove a parameter, click ✕ on its tag.

If several parameters are selected, any one of them is enough. The check also passes without the parameter in the link if a default value is set for it in the campaign. A default value that holds macro text doesn't pass the check.

While the list is empty, there is no check: a visitor who opens the campaign link directly passes it. Below the field there is a warning about this: “without a required parameter, a direct visit (competitors/moderation) will get to money” («без обязательного параметра прямой заход (конкуренты/модерация) попадёт на money»).

Browser, connection and device checks

JS challenge (behavior + headless detection)

Select the checkbox to check the visitor's browser before the offer is served. The visitor sees an empty page for about a second, then gets the offer or “white”. A browser without JavaScript stays on the empty page. Signals, points and the threshold are covered on the JS challenge and scoring page.

Device fingerprint (anti-moderation)

The checkbox is available only when the JS challenge is on. The tracker remembers the country from which a device visited for the first time. If the same device comes from another country, it gets “white” even when the other checks are passed. The device memory is shared by all campaigns and stored for 30 days.

Block proxy / VPN / Tor

Select the checkbox to filter out connections through proxies, VPN and Tor. Only the IP2Proxy database provides the connection type — connect it following IP2Proxy: proxy, VPN and data center database. Without the database, the checkbox has no effect.

When the database is loaded, data center addresses are treated as bots and filtered out by cloaking even without this checkbox. The checkbox adds proxies, VPN and Tor to them.

Allow devices

Select the device types that are allowed into the target stream: Mobile («Моб.»), Desktop («Десктоп»), Tablet («Планшет»). You can select several. The caption below the buttons reads “empty = any” («пусто = любые»): if nothing is selected, there is no check. If at least one type is selected, a visitor whose device couldn't be determined goes to “white”.

Where cloaking gets the countries

There is no country field on the tab. The caption in the card reads “Cloaking takes GEO from the GEO filters of the money streams — you don't need to set countries separately.” («Гео клоака берёт из гео-фильтров денежных потоков — настраивать страны отдельно не нужно.»)

• Enabled streams of the Regular («Обычный») and Intercepting («Перехватывающий») types are taken into account.
• From each of them, the countries of GEO conditions with the in list («в списке») and = operators are taken. The lists of all streams are combined.
• If at least one such stream accepts any country, there is no country check. This happens when a stream has no GEO condition, the condition is set as not in list («не в списке») or ≠, or it's in an OR group together with a condition on another field.

The tracker's geo databases determine the country by IP. If the visitor's country couldn't be determined and the country check applies, the visitor goes to “white”.

Saving and checking the result

The Save campaign button is active when there are unsaved changes — “● unsaved changes” («● есть изменения») is shown next to it. After saving, “✓ Campaign saved” («✓ Кампания сохранена») appears. Only the cloaking settings are saved; the other campaign fields don't change. New rules start applying to traffic in about 15 seconds — check after this pause.

1. If a parameter is selected in the ad platform block, open the campaign link without it. “White” should open.
2. Open the link with this parameter, for example https://track.example.com/abc1234?fbclid=test, from an allowed device and from an allowed country. The offer or landing page of the target stream should open.
3. Open the campaign and click Statistics («Статистика»).
4. Go to the Click log («Лог кликов») tab and click the row of the click.
5. Find the Cloaking section in the window. The Result («Результат») row shows “passed to money” («прошёл на money»), “sent to white” («завёрнут на whitepage») or “sent to JS check” («отправлен на JS-проверку»), and the Reasons («Причины») row shows which check failed.

The reasons are explained on the Diagnostics: why a click went to “white” page.

Frequently asked questions

Real visitors go to “white”

Open the click in the click log and look at the Reasons row. Possible causes:

• the ad link doesn't have the parameter selected in the ad platform block, or the network didn't replace the macro in it with a value;
• the visitor's country isn't in the GEO conditions of the target streams;
• not all the needed types are selected in the Allow devices block;
• the visitor uses a VPN, and the Block proxy / VPN / Tor checkbox is on.

Filtered visitors get 404

The campaign has no enabled stream of the Final type, or that stream doesn't match by its filters, schedule or click cap. Add a stream with the + White button on the Streams («Потоки») tab.