Documentation sections
Reference
Decision reasons
Every click in the log gets one of 83 reasons. They are grouped as follows:
| Group | What it means |
|---|---|
| Bot / automation | Platform crawlers, ad verification services, spy services, automated browsers, programs instead of a browser. |
| Infrastructure traffic | Data centers, hosting, proxy networks. |
| Campaign rule | A flow setting was triggered: geo, device, schedule, clicks per IP limit, VPN, script check, trust score — or the address is on your IP blacklist, or was already caught on automation before — at you or at other clients. |
| Allowed | “Allowed”, “Allowed by whitelist”, “Watched, not cut” (shadow mode), “Tracked, not filtered”. |
| Waiting page | The browser was given time to prove it is real. |
| Flow or plan state | “Flow under review”, “Cloaking switched off”, “Flow is not running”, “No active plan”, “Click limit reached”. |
| Other | Warm-up, “Offer did not load” (the White Page was shown so the click is not lost), “The flow has no offer to send to”, “Shield”, “Extra guard”. |
Where they were cut
Every refusal belongs to one of three steps — the same way ad measurement splits invalid traffic into general (GIVT) and sophisticated (SIVT):
- Network and request — the visit was cut before the browser check: by address, network, provider, headers, click id and flow rules (country, device, schedule). This step touches real people least.
- Browser check — the script ran, and its answer showed automation or did not earn enough trust. Bots pretending to be people are caught here, and this is also where the filter errs most often: if this share grows, review the strictness.
- Check never came back — the check page was served and no answer followed. That is how programs without JavaScript behave.
The shares of the three steps are shown above the list of reasons in Statistics, and the step of a single click in its details in the log.
ArtisanClo · Dashboard documentation. Questions — info@artisanclo.com or @artisanclo_support on Telegram.