How it works¶

Cloakerly inspects each visitor against the campaign you configured, then returns one of three outcomes to your integration:

Response	What your site should do
A URL	Send the visitor to that affiliate / money page
`true`	Keep the visitor on the current (safe) page
Anything else	Treat as blocked — stop, show a blocked page, or stay on the safe page

You do not need to parse extra fields. The SCRIPT snippets handle this for you.

Safe page and affiliate pages¶

Every campaign has:

Safe URL — the page that should look normal to reviewers, bots, and traffic that fails your rules. With PHP/WordPress on-page integration, this is usually the page the visitor already loaded; the script simply does not redirect.
Affiliate pages — offer URLs for qualified visitors. You can add several and split them by traffic %. Optional per-device URLs: Mobile, Tablet, Mac.

Money clicks in the dashboard are visitors who received an affiliate URL. Blocked hits are visitors who did not.

Real users stay on page¶

The switch Real users stay on page (blocked traffic goes to affiliate) inverts the default:

Off (default): allowed visitors go to the affiliate URL; blocked visitors stay on / see the safe page.
On: allowed visitors stay on the current page; blocked traffic is sent to the affiliate URL.

Use the default unless you intentionally want the landing page itself to be the money page.

Traffic decision¶

On each hit Cloakerly typically looks at:

Campaign status (Active / In-Active / Allow All / In Review)
Frequency cap (same IP too often in a time window)
Device (mobile / desktop) and operating system
Browser (user-agent filter)
IP version (IPv4 / IPv6)
Country and language
Network type (VPN, hosting, business, wireless, residential)
VPN and datacenter allow/block switches
Your IP blacklist / whitelist
Required click IDs (GCLID / FBCLID) and UTM rules
Then it picks an affiliate URL (including device-specific URLs and traffic %)

Checks that can decide locally run first so obvious mismatches do not wait on extra lookups.

Campaign statuses¶

Status	Behaviour
In-Active	Filtering is off. Visitors see the landing / safe page as a normal site.
Active	Filters run. Qualified traffic can be redirected to an affiliate page.
Allow All	Filters are skipped. Everyone is sent to an affiliate page.
In Review	Hits are still logged, but everyone stays on the safe page. Useful while an ad account is looking at the site.

Change status from the campaign form or by clicking the status badge on the dashboard.

Start In Review or In-Active, confirm logs, then switch to Active.

Filtering layers¶

Blacklist and whitelist¶

IP Listing stores IP ranges you own:

Blacklist — always treat as blocked (safe page).
Whitelist — always treat as allowed (affiliate page), subject to campaign status.

Use this for office IPs, known bot ranges, or partners you always want through. See IP listing.

Visitor fingerprint¶

Each request includes IP, user agent, language, current URL, and (unless you hide it) the referrer. Cloakerly uses that plus network intelligence (proxy, VPN, hosting, scraper, Tor, and similar flags) to classify the hit. Those flags appear on the Click Log so you can see why a visitor was allowed or blocked.

Quality scoring¶

Cloakerly combines rule filters with automated quality signals (datacenter, VPN, anonymous, scraper, and similar). You control the outcome with:

Allow VPN
Allow Datacenters
Network Type (allow only selected types)
Country, language, OS, browser, and UTM rules

You do not configure third-party services. All of this is inside the campaign form.

What gets logged¶

Every evaluated hit can appear in Click Logs with:

Campaign, IP, allow/block status, reason
Country, city, timezone, currency
ISP / network
Proxy, VPN, scraper, Tor, hosting, anonymous flags
Client (browser / OS icons from the user agent)
Response time and timestamp (in your profile timezone)

Use the reason column when a campaign “does nothing” or sends the wrong page — it usually names the failing rule.