Offer or White Page: who sees what

For every visit, ArtisanClo checks the conditions in order, from top to bottom. The first one that matches decides, and the visit is not checked any further. You can see the reason for each decision in the click log.

Order of checks

#	Condition	What the visitor sees	Reason in the log
1	No active plan, or the trial clicks have run out	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 has already been identified with certainty as a bot or a platform reviewer — in your account or another customer’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, without checks	“In your blacklist”
7	Warm-up is in progress: the flow has fewer than N clicks so far	White Page, without 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 already been caught as a bot, or it is an obvious automated browser	White Page	“Previously flagged address”, “Headless browser detected”
11	An ad verification service, a program instead of a browser, a platform’s link preview robot	White Page — always, whatever the settings	“Ad verification or spy service”, “A program, not a browser”, “Search or platform crawler”
12	Audiences: country, device, OS, browser, language, time zone, city, region, network, provider, referring site, schedule	White Page, if the visitor does not match	“Country not allowed”, “Outside campaign hours”, etc.
13	The shield is up and the link has no ad click ID	White Page	“Shield: no paid click id”
14	A minimum time on page is set	A waiting page, then a repeat check	—
15	Trust score: VPN, data center, IPv6, no provider, no referring site, no JavaScript and other signals	White Page, if too many suspicious signals add up	“Trust score too low”, “High-risk network”, etc.
16	Extra guard finds the visit similar to your bots	White Page	“Second opinion: looks like your bots”
17	All checks passed	Offer (picked by branches and weights)	“Allowed”

If an offer was picked but its page did not load (“Loading” mode), the visitor sees the White Page and the log shows “Offer did not load”.
If the flow has no enabled offer at all — White Page and “The flow has no offer to send to”.
If a visitor did not pass the script check and did not come back from the waiting page, the click appears in the log later with the reason “JavaScript required”.
The “Known bot address” check works only when the flow filters: it does not apply under review, in shadow mode, in “Tracker” mode or with cloaking off. It does not stop an address on your IP whitelist.

Shield

For a few hours, the shield lets through to the offer only visitors who came from an ad click. Turn it on when the platform is actively reviewing your campaign: moderators and reviewers usually arrive without an ad click ID.

What the shield counts as an ad click — the link contains the platform’s click ID parameter:

Platform	Parameter in the link
Facebook	`fbclid`
Google	`gclid`, `wbraid`, `gbraid`, `gad_source`
TikTok	`ttclid`
Microsoft	`msclkid`
X	`twclid`
Snapchat	`sc_click_id`
Pinterest	`epik`
Reddit	`rdt_cid`
Taboola	`tblci`
Outbrain	`ob_click_id`, `obOrigUrl`
Amazon	`aaaid`

A referring site (referrer) alone is not enough — the parameter itself is required. On platforms without a click ID (Telegram, for example), nobody gets through while the shield is up.

What changes while the shield is up:

A visitor without a click ID sees the White Page.
A visitor with a click ID moves on but is checked more strictly: VPNs and proxies are always blocked; data center, automated browser and IP blacklist blocking are turned on; on the JS tag and 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 is not allowed sees the White Page even with a click ID.
Shadow mode and “Tracker” mode are switched off while the shield is up.
A “Shield is up” banner with the end time is shown throughout the dashboard.

What the shield costs

Some real visitors without a click ID — direct visits, forwarded links, bookmarks — will also see the White Page while the shield is up. Keep the shield on only as long as the review lasts.

How to turn it on manually Professional and above: Diagnostics → the Ban risk tab → Raise for 6h. The block heading shows how much time is left. To lower it early, click Lower the shield. The shield lowers itself when time is up; raising it again does not shorten a longer shield that is already up.

Shared bot list

When an ad verification service, a platform robot or a program instead of a browser is identified with certainty at any customer, the address is remembered for the whole service. Its next visit to any of your flows gets the White Page right away — without checks and without delay, with “Known bot address” in the log. Real visitors with a doubtful network, a VPN or no JavaScript are never added to this list. Data center and hosting addresses stay on it practically indefinitely, home and mobile ones for 14 days.

Auto-shield

Professional and above The Raise the shield automatically as soon as a review is detected checkbox on the Ban risk tab. When the box is checked and the shield is down, the block heading says “Shield armed”.

Every 15 minutes, ArtisanClo looks at active flows with traffic and counts traces of reviews over the last 3 hours: ad verification services and platform preview robots, including repeat visits from those the service already recognizes by address. The count is compared with the flow’s usual level over the past week.
Risk levels:
- Calm — everything is as usual;
- Watching — noticeably more traces than usual (or a new flow that a reviewer has already visited). You get a bell notification; the shield is not raised;
- Reviewing — a sharp spike: for example, 8 or more traces in 3 hours against an almost zero usual level. With auto-shield on, the shield is raised for 6 hours; without the checkbox you only get a notification.
A raised shield is reported in the bell and in Telegram: “The platform is reviewing your campaign”.

A network-wide review wave. Once an hour, ArtisanClo looks at all accounts at once. If a country shows many review traces across several customers within 3 hours, three times above the usual level, a wave is declared. Flows with auto-shield that accept that country get a shield for 3 hours. Everyone else gets a “The platform is sweeping the network” notification suggesting to raise the shield manually.

Under review

While it is on, every visitor sees the White Page with no filtering. Turn it on while the platform reviews your ad: moderators see only the safe page. Nothing is written to your blacklist. But reviewers and platform bots that the service identifies with certainty during this time are remembered: their next visits to any flow get the White Page right away.

How to turn it on Professional and above: Diagnostics → Ban risk tab → Turn on review mode. There is no time limit, you switch it off yourself. While it is on, every dashboard page shows a “Flow under review” banner. Live traffic also goes to the White Page during these hours and does not reach the offer — switch it off as soon as the ad is approved.

Auto-tuning

Professional and above The Auto-tuning tab in Diagnostics. Once an hour, auto-tuning looks at the flow and makes at most one change at a time, no more often than once every 6 hours, once the flow has at least 300 visits in the past week.

Shield: the “Careful” policy raises the shield already at the “Watching” level; “Balanced” and “More traffic” raise it at the “Reviewing” level. This works regardless of the auto-shield checkbox.
Protection: turns on data center, automated browser, VPN, IP blacklist or no-referrer blocking if it would catch enough bots without touching a single paying visitor. Or removes a rule that was cutting off visitors who paid.
Weights: shifts 10% of the traffic toward the offer with the best revenue.
Auto-tuning never touches geo, devices or the schedule. While the risk is not calm or the shield is up, it changes nothing. It does not work in shadow mode: there is nothing to optimize there.
Every change appears in the auto-tuning log with an explanation, and you can undo it. After you undo a change, auto-tuning leaves that setting alone from then on.

Extra guard

Professional and above The Extra guard tab in Diagnostics. The model learns from your account’s history: who paid and who turned out to be a bot. It only checks visitors that all other rules have already let through, and sends visits that look like your bots to the White Page. While you do not have enough data of your own, a shared model is used. It retrains every night and turns itself off if it starts cutting a noticeable share of conversions.

Shadow mode and “Tracker” mode

Shadow mode — when connected with the PHP file, the Keitaro filter or the Binom gate, all visitors go to the offer, and the log shows whom the filter would have cut (“Watched, not cut”). Clicks in shadow mode do not count toward the trial limit. On the JS tag and the flow link, the flow filters as usual.
“Tracker” mode — when connected with the PHP file, the Keitaro filter or the Binom gate, everyone goes to the offer (“Tracked, not filtered”), and bots are only flagged in reports. On the JS tag and the flow link, the flow filters like a cloak.
Neither shadow mode nor the tracker overrides a paused flow or an unpaid plan: in that case everyone sees the White Page. When the shield is up, both modes are switched off.

Examples

Situation	What they see	In the log
A Facebook moderator in a regular browser without `fbclid`, shield is 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 is up	2 seconds of waiting (on the tag and the PHP file), then the offer	“Allowed”
The same person on a VPN, shield is up	White Page	“High-risk network” or “Trust score too low”
A person opened a forwarded link without a click ID, shield is up	White Page	“Shield: no paid click id”
The first click of a flow with a warm-up of 50	White Page without checks — the same goes for 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 time zone	White Page	“Outside campaign hours”
Your address is whitelisted, the “1 click per IP” limit is already used up, shield is up	Offer — the whitelist is checked before the limit and the shield	“Allowed by whitelist”
The flow is paused, “Tracker” mode on the PHP file	White Page	“Flow is not running”
Cloaking is off, the site is connected with the tag	White Page	“Cloaking switched off”
Shadow mode, a data center bot, PHP file	Offer	“Watched, not cut”
The visitor passed the checks, but the offer (“Loading” mode) did not respond	White Page	“Offer did not load”
Auto-shield is on, 9 reviewers arrived within 3 hours against a usual level of zero	Within 15 minutes the shield goes up for 6 hours; after that, everyone without a click ID sees the White Page	“Shield: no paid click id”

ArtisanClo · Dashboard documentation. Questions — info@artisanclo.com or @artisanclo_support on Telegram.