Documentation sections
Flow setup
Step 2. Filtering
Who gets through to the offer. In “Tracker” mode this step is called “Traffic assessment”: the filter does not cut anyone, it only flags bots, and the report shows what share of the traffic you paid for was bots.
Check strictness
The Soft / Balanced / Strict switch. Below the heading you can see which platform the protection is tuned for: “source: …”, “platform: …” or “no source chosen — profile not applied”. Below that, badges list what has been turned on.
| Level | What it cuts |
|---|---|
| Soft | Obviously untargeted traffic: addresses on IP blacklists and automated bots. Minimal risk of losing real people, no per-IP limits. |
| Balanced | Adds VPNs, proxies and data centers, plus a daily clicks-per-IP limit. Suits most campaigns. |
| Strict | Adds IPv6 blocking, required JS check, a minimum time on page and a tight per-IP limit. May cut some of your target traffic. |
The platform comes from the source chosen in step 1. Each platform has preset values:
| Platform | Without ISP | Warm-up | Required JS | Clicks per IP (Balanced) | Why |
|---|---|---|---|---|---|
| Facebook Ads | on | 50 | no | 3 | Facebook’s in-app browser often drops the referrer, so the referrer check is off. The first moderation checks go to the White Page. |
| Google Ads | on | 30 | yes | 2 | Google passes a click ID (gclid), so JS can be required. |
| TikTok Ads | off | 50 | no | 3 | ISP-based blocking is off. |
| Native and push | on | 100 | yes | 5 | More clicks per IP and a longer warm-up. |
| Another source | on | 0 | yes | 3 | Standard checks with no platform-specific rules. |
What the strictness level changes:
| Level | VPN and proxy | Datacenter ASN | Live interaction | IPv6 | Min. time | Required JS | Clicks per IP per day |
|---|---|---|---|---|---|---|---|
| Soft | off | off | off | off | 0 | per platform | no limit |
| Balanced | on | on | off | off | 0 | per platform | per platform |
| Strict | on | on | on | on | 1500 ms | always | 2 |
- At every level, cloaking, IP blacklist blocking and automated browser blocking are on, and the referrer check is off.
- A new flow starts with “Another source + Balanced”.
- Features not included in your plan are switched off after applying: for example, on Starter the clicks-per-IP limit and warm-up are reset to zero.
- If you have already changed the toggles manually, changing the strictness or source opens a “Replace your protection settings?” dialog with a “before → after” list. Apply replaces the settings, Keep my settings changes only the selection itself. If nothing would change, or you have not touched the form yet, the dialog does not appear.
How the decision is made
Some checks cut a visit immediately (IP blacklists, an obvious automated browser, an audience rule). The rest add up to a trust score: each suspicious signal adds a penalty, and if the total exceeds the threshold, the visitor sees the White Page. The protection toggles decide how much each signal weighs.
Protection
Each option is a card with a checkbox and a description. The block heading shows a summary: “cloaking on · checks: N of 9”.
| Toggle | What it does | When to turn it on |
|---|---|---|
| Shadow mode | Buttons “Off”, “6 h”, “12 h”, “24 h”, “48 h”. The filter cuts no one and only flags whom it would have blocked; “Diagnostics” shows whom it would have cut. It turns off on its own when time is up, and clicks in shadow mode do not count toward the trial limit. Works with cloaking on and the connection via the PHP file, the Keitaro filter or the Binom gate; on the JS tag and the link the filter cuts as usual. The White Page is still shown to visitors of a paused or unpaid flow, to addresses from your IP blacklist and to every visit in “Under review” mode. While the shield is up, shadow mode does not apply. | When you suspect you are losing conversions, or before tightening the rules. Keep it short: while it is on, the offer is open to everyone. |
| Cloaking | The main switch. On — every visit is checked and unwanted visitors go to the White Page. Off — all visitors see the White Page. | Always on, except when you need to close a campaign temporarily. |
| Block by IP blacklists | Immediately cuts addresses already seen in automation — by you or by other customers. The shared list of addresses where bots and platform reviewers have already been caught with certainty always applies, even with the checkbox off; only the flow’s IP whitelist bypasses it. | Always. |
| Block VPN/Proxy | Sharply lowers trust in visits through VPNs and proxies, which are used to fake the country. | When the visitor’s real country matters. |
| Block IPv6 | Sharply lowers trust in visits from IPv6 addresses. | Only if your offer and tracker work over IPv4 — otherwise you will lose real people. |
| Block without ISP Professional and above | Lowers trust in visits with no visible provider — usually servers. | For most platforms; usually turned off for TikTok. |
| Block without Referrer Professional and above | Lowers trust in visits with no referring site. | Only if traffic always comes through links on the platform. Do not turn it on for Facebook. |
| Block datacenter ASN | Cuts hosting and cloud networks that scanners and bots come from. | “Balanced” and “Strict” levels. |
| Block headless | Catches bots and auto-clickers pretending to be a browser. Cuts immediately when there are clear traces of automation. | Always. |
| Live interaction check | Looks at how the mouse or finger moves: people behave naturally, bots do not. Adds up to half a second of waiting. With the PHP file connection, you need its latest version. | For strict platforms; the “Strict” level. |
| Require JS | A visitor without JavaScript gets a heavy penalty and is sent to a check. Simple bots and scrapers trip over this. | When the platform passes a click ID and almost all traffic comes from regular browsers. |
Audience
The block is collapsed, and its heading shows “rules: N” or “no restrictions”. Each list has Allowed and Denied buttons:
- Allowed — let through only what is listed;
- Denied — let everyone through except what is listed;
- an empty list restricts nothing.
A visitor who fails a list sees the White Page with a reason such as “Country not allowed”.
| List | How to fill it in |
|---|---|
| Countries | Pick from a searchable list; buttons “All”, “Clear”, “Done”. |
| Devices | Mobile, Desktop, Tablet, Smart TV, Game console, Wearable, Bot / crawler, Unknown. |
| Operating Systems, Browsers | Pick from a searchable list. |
| Languages, Timezones | Pick from a searchable list. The old and new names of one time zone count as the same zone: Europe/Kiev and Europe/Kyiv, Asia/Calcutta and Asia/Kolkata, Asia/Saigon and Asia/Ho_Chi_Minh — browsers often send the old one. |
| Cities | Enter names as they appear in the click log, for example “Berlin”. A value is added with Enter or a comma. |
| Regions | The region name or ISO code, for example “Bavaria” or “BY”. |
| Networks (ASN) Professional and above | The network number: “AS15169” or “15169”. |
| Providers Professional and above | The name as it appears in the click log, for example “Deutsche Telekom AG”. |
| Referrers Professional and above | The referring site’s domain, for example “facebook.com”. Subdomains are included automatically. |
Campaign schedule Professional and above
- An On / Off switch (off by default). When you turn it on, weekdays from 09:00 to 18:00 in your time zone are filled in right away.
- Campaign timezone — time is counted in this zone, not in the visitor’s.
- For each day: the day is on or off, with an Around the clock checkbox or “from” and “to” times.
- Outside the schedule, all visitors see the White Page.
Limits
| Field | What it does | Values |
|---|---|---|
| Clicks from one IP per day Professional and above | After N clicks from one address within a day, the next ones see the White Page. Every visit counts, including reloads that the log merges into one click. Addresses on the IP whitelist skip this check. | 0 — no limit, up to 1,000,000 |
| Clicks before filtering (warm-up) Professional and above | The first N clicks of the flow see the White Page without any check — this is where the first moderation checks land. | 0 — no warm-up, up to 1,000,000 |
| Min time on page (ms) | A visitor who stays for less is sent to a waiting check and checked again. | 0 — no waiting; we recommend 1500–2500 |
ArtisanClo · Dashboard documentation. Questions — info@artisanclo.com or @artisanclo_support on Telegram.