Documentation sections
Reference
If something doesn't work
Almost any problem is explained by the decision reason in the click log. Start with three steps, then find your case in the table.
Open your click in the log
Follow the ad link yourself and find the visit in the Click log; clicking the row opens a card with the reason and the step at which the visit was cut.

Click card: 1 decision reason, 2 the visit: where it was sent and how it was shown. Check the connection
Flow menu → Connect → Check my page. Details in Connecting your site.
Look at the flow analysis
Diagnostics shows which rule cuts the most and how many real people it catches.
| What you see | Why it happens | What to do |
|---|---|---|
| All visitors see the White Page | No active plan or the trial clicks are used up; the flow is paused or a draft; cloaking is off; warm-up is in progress; the shield is up and the link has no click tag. | Check the reason in the click log: “Flow under review”, “No active plan”, “Click limit reached”, “Flow is not running”, “Cloaking switched off”, “Before filtering”, “Shield: …”. The order of checks is in Offer or White Page. |
| All visits in the log have the same IP, your server's or host's address | A hosting proxy sits in front of the site, and the PHP file sees its address instead of the visitor's. The file accepts the visitor's real address from headers only when they come from Cloudflare. | Proxy the domain through Cloudflare (orange cloud) or ask your host to pass the visitor's real address to the server (the real IP / mod_remoteip setting). |
| The PHP file responds with a 503 error or the page loads slowly | Your server can't connect to ArtisanClo: outgoing connections are blocked, the curl extension is missing and allow_url_fopen is off, or the host's firewall blocks the requests. The file waits up to 4 seconds for a response via curl; if curl fails and allow_url_fopen is on, a second attempt waits up to 4 more seconds, up to 8 in total. | Check that the hosting runs PHP 7.2 or newer with the json and filter extensions and allows outgoing HTTPS requests. What the file does when the connection fails. For a day, it decides based on the last response: visitors with an ad click tag go to the offer, everyone else to the White Page, shown the same way the flow shows it (for example, via “Loading” under your ad address). A flow under review sends everyone to the White Page during an outage. If ArtisanClo is unavailable for more than a day, the file goes back to answering 503 to every visit. A visit that arrives before the first response also gets a 503. Older files behave differently: those downloaded between September 17 and October 17, 2026, during an outage, redirect a visitor with a click tag to the offer and everyone else to the White Page's own domain, which platforms treat as cloaking; files older than September 17 answer everyone with a 503. Download such a file again. |
| The host responds with 403 to requests to the landing | The host's protective filter (WAF, ModSecurity) mistakes the waiting page's requests for an attack. | Add the landing address to the filter's exceptions or ask your host's support to turn it off for this site. |
| Everyone sees the page, even bots; or decisions don't change right away | A WordPress caching plugin, the host's cache or a CDN serves a saved copy of the page instead of asking for a decision for each visitor. | Exclude the landing from caching or turn off page caching. After the change, clear the cache and check in an incognito window. |
| The tag is installed, but the page shows before the decision | The code is loaded through Google Tag Manager, with async or defer, or isn't the first line in <head>. | Paste the code as the first line in the <head> of every page, without a tag manager. Check with the Check my page button. |
| Connected via Cloudflare, but there's no tag on the page | A gray cloud, Deploy not clicked after the variable, a route on the wrong host or a path in the skipped list. | Go through the table in Connecting via Cloudflare → Checking and troubleshooting. |
| The integration check says the page couldn't be opened | Some sites and hosts don't let automated checks in, for example a Cloudflare challenge. The reason is given in the response. | That doesn't mean the connection isn't working. Open the landing yourself: after the first visit, the method gets the “Installed” mark in the connection window, and “Connected” appears in the flow list. |
| My test visits don't show up in the log | If you visit again from the same address and browser within the same clock minute and get the same decision, no new click is recorded: it's merged with the previous one. With the PHP file, a repeat visit within a minute doesn't reach us at all: the decision is kept in the browser. A visit that didn't wait for the waiting page to finish doesn't get into the log unless “Require JS” is on in the flow. | Wait a minute or test from another device or network; on the waiting page, wait for the redirect. |
| The flow settings changed, but the visitor sees the old result | With the PHP file, the decision for one visitor is kept in the browser for up to a minute. | Test in a new incognito window. You don't need to re-upload the PHP file after editing the flow: settings aren't stored in the file. Download the file again only if the connection window says “You're running an older file”. |
| The offer in a frame doesn't open, or its links take over the whole tab | The offer site forbids being shown in a frame. With the JS tag, such an offer is shown through our server, and its links open in the full tab; with the PHP file, the frame stays empty. | Choose “Loading” or “Redirect” mode. In “Iframe” mode, the dashboard warns about this below the offer address: “This site refuses to be shown in a frame”. |
| People on a VPN or from another country don't get through | That's by design. A visit from a country that isn't in the flow's geo is cut by the geo rule; the VPN toggle doesn't affect this. With “Block VPN/Proxy” on, VPNs and proxies are rejected as “High-risk network”; if it's off, a VPN still lowers the trust score a little and, together with other signals, can lead to “Trust score too low”. | If you need a VPN audience, turn off “Block VPN/Proxy” and check the loss in Diagnostics before turning it off. Need other countries? Add them to the flow's geo. |
Didn't find your problem? Contact support and include an example of a wrong decision.
ArtisanClo · Dashboard documentation. Questions — info@artisanclo.com or @artisanclo_support on Telegram.