Documentation sections
Flow setup
Offer or White Page: who sees what
For every visit, ArtisanClo checks conditions in order, top to bottom. The first match wins, and no further checks run. Why a visit ended up where it did is shown in the click log.
On this page
Order of checks
| # | Condition | What the visitor sees | Reason in the log |
|---|---|---|---|
| 1 | No active plan, or the trial clicks are used up | White Page | “No active plan”, “Click limit reached” |
| 2 | The flow is paused or a draft | White Page | “Flow is not running” |
| 3 | The address is already definitely known as a bot or platform reviewer, on your account or another client's | White Page, no checks | “Known bot address” |
| 4 | The flow is under review | White Page, no checks | “Flow under review” |
| 5 | Cloaking is off | White Page | “Cloaking switched off” |
| 6 | The address is on your IP blacklist | White Page, no checks | “In your blacklist” |
| 7 | Warm-up in progress: the flow hasn't reached N clicks yet | White Page, no checks | “Before filtering” |
| 8 | The address is on the IP whitelist | Offer | “Allowed by whitelist” |
| 9 | The daily clicks per IP limit is exceeded | White Page | “Too many clicks from one IP” |
| 10 | The address has been seen as a bot before (if “IP blacklists” is on), or it's an obvious headless browser (if “Headless browsers” is on) | White Page | “Previously flagged address”, “Headless browser detected” |
| 11 | An ad verification service, a program instead of a browser, a platform preview robot, a browser with proven traces of automation | White Page, always, with any settings | “Ad verification or spy service”, “A program, not a browser”, “Search or platform crawler”, “Automated browser traffic” |
| 12 | A visit from a datacenter address with no regular ISP behind it, which also comes over a VPN or without JavaScript; the browser isn't verified yet | A waiting page with a browser check, then another check | “Unverified browser” |
| 13 | Audience: country, device, OS, browser, language, time zone, city, region, network, ISP, referring site, schedule | White Page, if it doesn't match | “Country not allowed”, “Outside campaign hours” and so on |
| 14 | The shield is up and the link has no ad click tag | White Page | “Shield: no paid click id” |
| 15 | A minimum time on page is set | A waiting page, then another check | — |
| 16 | Trust score: VPN, datacenter, IPv6, no ISP, no referring site, no JavaScript and other signals | White Page, if there are too many suspicious signals | “Trust score too low”, “High-risk network” and so on |
| 17 | Smart protection thinks the visit looks like your bots | White Page | “Second opinion: looks like your bots” |
| 18 | All checks passed | Offer (chosen by branches and weights) | “Allowed” |
- If an offer was chosen but its page didn't open (“Loading” mode), the visitor sees the White Page, and the log shows “Offer did not load”.
- If the flow has no enabled offers, it's the White Page and “The flow has no offer to send to”.
- With “Require JS” on, a visitor who didn't pass the script check and didn't come back from the waiting page shows up in the log later with the reason “JavaScript required”. If the toggle is off, or the visitor landed on the waiting page for another reason, a visit that doesn't come back won't get into the log.
- The “Known bot address” check works only when the flow is filtering. Under review, in shadow mode, in “Tracker” mode and with cloaking off, it doesn't run. It doesn't stop an address from your IP whitelist.
Shield
While the shield is up (for a few hours), only visitors who came from an ad click reach the offer. Turn it on when the platform is actively reviewing the campaign: moderators and reviewers usually come in without an ad click tag.
The shield counts a visit as coming from an ad when its link carries the platform's click tag:
| Platform | Parameter in the link |
|---|---|
fbclid | |
gclid, wbraid, gbraid, gad_source | |
| TikTok | ttclid |
| Microsoft | msclkid |
| X | twclid |
| Snapchat | sc_click_id |
epik | |
rdt_cid | |
| Taboola | tblci |
| Outbrain | ob_click_id, obOrigUrl |
| Amazon | aaaid |
A referring site (referrer) alone isn't enough; it has to be the parameter. If a platform doesn't add a click tag (Telegram, for example), nobody reaches the offer while the shield is up.
What changes while the shield is up:
- A visitor without a click tag sees the White Page.
- A visitor with a click tag moves on, but the check is stricter: VPNs and proxies are always blocked; blocking of datacenters, headless browsers and addresses from IP blacklists turns on by itself. When you connect with the JS tag or the PHP file, JavaScript and at least 2 seconds on the waiting page are required (Keitaro and Binom have no waiting page).
- Audience rules apply as usual: a visitor from a country that isn't allowed sees the White Page even with a click tag.
- Shadow mode and “Tracker” mode are switched off while the shield is up.
- Every dashboard page shows a “Shield is up” banner and the time it will come down.
Some real visitors without a click tag (direct visits, forwarded links, bookmarks) will also see the White Page while the shield is up. Keep the shield up only as long as the review lasts.
How to turn it on manually from Professional: Diagnostics → the Ban risk tab → Raise for 6h. The block header shows how much time is left. To take it down early, click Lower the shield. The shield comes down on its own when time runs out; if it's already up for longer, turning it on again won't shorten it.

Shared bot list
When we definitely recognize an ad verification service, a platform robot or a program posing as a browser, its address is remembered for all ArtisanClo clients. The next visit from that address to any of your flows gets the White Page right away, with no checks and no delay, and the log shows “Known bot address”.
- Datacenter and hosting addresses go on the list the first time and stay there almost forever.
- Home and mobile addresses are used by many real people, so once isn't enough. Such an address goes on the list only when a bot from it has been caught at three different clients, within an hour of the third case. It stays there for 14 days.
- Hits on trial accounts don't put an address on the list right away, but in the hourly recount they count the same as everyone else's.
- Real people with a suspicious network, a VPN or no JavaScript are never put on this list.
Auto-shield

from Professional The Raise the shield automatically as soon as a review is detected checkbox on the Ban risk tab. If it's ticked and the shield is down, the block header reads “Shield armed”: it goes up on its own when we spot a review.
- Every 15 minutes, ArtisanClo counts how many reviews running flows got over the last 3 hours: visits from ad verification services and platform preview robots, including those we already know by address. This number is compared with the flow's usual level over the past week.
- Risk levels:
- Calm: everything as usual;
- Watching: noticeably more reviews than usual (or the flow is new and a reviewer has already been on it). You get a bell notification; the shield doesn't go up;
- Reviewing: a sharp spike, for example 8 or more reviews in 3 hours when there are usually almost none. With the auto-shield on, the shield goes up for 6 hours; without the checkbox you only get a notification.
- When the shield goes up, you get a notification in the bell and on Telegram: “A platform is reviewing a campaign”.
A review wave across the network. Once an hour, ArtisanClo looks at all accounts at once. If, within 3 hours, reviews in one country are hitting several clients at once and there are three times more of them than usual, that's a wave. Flows with the auto-shield that are open to that country get the shield for 3 hours. Everyone else gets a notification that the platform is sweeping the network, with advice to raise the shield manually.
Review mode
While this mode is on, all visitors see the White Page with no filtering. Turn it on while the platform is reviewing an ad: moderators will see only the White Page. Nothing goes into your blacklist. But platform reviewers and bots that we definitely recognize during this time go on the shared bot list under the usual rules: datacenter addresses right away, home and mobile ones once several clients have caught them.
How to turn it on from Professional: Diagnostics → the Ban risk tab → Turn on review mode. The mode won't turn itself off; switch it off by hand. While it's on, a “Flow under review” banner shows on every dashboard page. Live traffic also goes to the White Page during these hours and doesn't reach the offer, so turn it off right after approval.
Auto-tuning
from Professional The Auto-tuning tab in Diagnostics. Auto-tuning checks the flow once an hour. If the week has gathered at least 300 visits, it can change one setting, but no more often than once every 6 hours.

- Shield: the “Careful” strategy raises the shield already at the “Watching” level, while “Balanced” and “More traffic” do so only at the “Reviewing” level. This works regardless of the auto-shield checkbox.
- Protection: turns on blocking of datacenters, headless browsers, VPNs, IP blacklist addresses or visits without a referrer, if it would catch enough bots without touching a single buyer. Or turns off a rule that was cutting buyers.
- Weights: shifts weight by 10 percentage points toward the offer with the best revenue.
- Auto-tuning never touches geo, devices or the schedule. While the risk isn't calm or the shield is up, it changes nothing. It doesn't work in shadow mode: there's nothing to optimize there.
- Every change shows up in the auto-tuning log with an explanation, and you can revert it. After a revert, auto-tuning leaves that setting alone.
Smart protection
from Professional The Extra guard tab in Diagnostics. The model learns from your account's history: who bought from you and who turned out to be a bot. It only checks visitors that the other rules have already let through, and sends visits that look like your bots to the White Page. While you don't have much data of your own, a shared model is used. It retrains every night and switches itself off if it starts cutting a noticeable part of conversions.

Shadow mode and “Tracker” mode
- Shadow mode: with the PHP file, the Keitaro filter or the Binom gateway, all visitors go to the offer, and the log shows whom the filter would have cut (“Watched, not cut”). Clicks in shadow mode don't use up the trial limit. When you connect with the JS tag or the flow link, filtering works as usual.
- “Tracker” mode: with the PHP file, the Keitaro filter or the Binom gateway, everyone goes to the offer (“Tracked, not filtered”), and bots are only flagged in reports. When you connect with the JS tag or the flow link, filtering works as in “Cloaking” mode.
- Neither shadow mode nor “Tracker” overrides a paused flow or an unpaid plan: then everyone sees the White Page. Both modes are switched off while the shield is up.
Examples
| Situation | What they see | In the log |
|---|---|---|
A Facebook moderator in a regular browser without fbclid, shield up | White Page | “Shield: no paid click id” |
| Facebook's link preview robot, with or without the shield | White Page | “Search or platform crawler” |
A real person from an ad with fbclid, shield up | 2 seconds of waiting (on the tag and the PHP file), then the offer | “Allowed” |
| The same person on a VPN, shield up | White Page | “High-risk network” or “Trust score too low” |
| A person opened a forwarded link without a click tag, shield up | White Page | “Shield: no paid click id” |
| The first click of a flow with a 50-click warm-up | White Page with no checks; this applies to the first 50 clicks, including your whitelisted address | “Before filtering” |
| A visit at 23:00 with a 9:00–18:00 schedule in the campaign timezone | White Page | “Outside campaign hours” |
| Your address is whitelisted, the “1 click per IP” limit is used up, shield up | Offer: the whitelist is checked before the limit and the shield | “Allowed by whitelist” |
| Flow paused, “Tracker” mode on the PHP file | White Page | “Flow is not running” |
| Cloaking off, site connected with the tag | White Page | “Cloaking switched off” |
| Shadow mode, a datacenter bot, PHP file | Offer | “Watched, not cut” |
| The visitor passed the checks, but the offer (“Loading” mode) didn't respond | White Page | “Offer did not load” |
| Auto-shield on, 9 reviewers in 3 hours, while usually nobody comes | Within 15 minutes the shield goes up for 6 hours; after that everyone without a click tag sees the White Page | “Shield: no paid click id” |
ArtisanClo · Dashboard documentation. Questions — info@artisanclo.com or @artisanclo_support on Telegram.