Overview¶

What is Cloakerly¶

Cloakerly is a traffic filtering platform for performance marketers. You attach a short integration snippet (or a cloaking link) to a landing page. Cloakerly inspects each visitor and decides whether they should:

• stay on (or be shown) your safe page, or
• be sent to an affiliate / money page.

The dashboard at https://ai.cloakerly.com is where you create campaigns, copy integration code, review click logs, and manage billing.

Typical uses:

• Keep review traffic, bots, and unwanted geos on a compliant safe page.
• Send qualified visitors to the offer that should convert.
• Split traffic across several affiliate URLs.
• Pass click IDs and UTM values through to the offer.

Cloakerly does not replace your ads account, tracker, or hosting. It sits in front of the page the visitor actually loads.

Traffic sources¶

When you create a campaign, you pick a traffic source. That label is used for reporting and for source-specific click-ID checks:

Choose the source that matches where you buy traffic so reports stay clean and click-ID rules apply correctly.

Integration¶

You do not write credentials by hand. After a campaign is saved, open SCRIPT. Cloakerly fills in the campaign ID and your account token.

Supported methods:

• PHP — server-side redirect (recommended for most PHP sites)
• PHP cURL (no redirect) — embed the destination in an iframe
• WordPress — plugin plus a campaign snippet
• JavaScript — client-side check
• React / Angular / Python — snippets for those stacks
• Reverse proxy — one PHP entry point that filters traffic, then streams the origin page
• Link cloaking — a ready-made Cloakerly URL you can paste into ads or a tracker

See Integration for placement rules and Getting started for the first install.

Hosting and domains¶

Use a domain and host you control. The integration runs on your site; Cloakerly only receives the visitor details needed to make a decision.

Recommendations:

• Prefer a dedicated landing domain, not a shared “link farm” domain.
• PHP integrations need cURL enabled.
• WordPress needs WordPress 5.0+ and PHP 7.4+.
• If you use a CDN or reverse proxy, pass the real visitor IP through (for example Cloudflare’s connecting IP header). Otherwise geo and VPN checks will see the proxy, not the user.
• Avoid stacking several redirects before Cloakerly. Extra hops lose referrers, click IDs, and UTM values.

Workflow¶

A typical campaign lifecycle:

1. Create account and pick a plan
2. Create a campaign (safe URL + affiliate URL + filters)
3. Copy the SCRIPT (or Link Cloaking URL)
4. Install it on the landing page / tracker
5. Leave status as In Review or In-Active while you test
6. Confirm hits in Click Log
7. Switch status to Active
8. Watch Dashboard, Performance, and Click Log

In Review still logs every hit but always shows the safe page. Use it while an ad account is checking the site. Switch to Active when you want filters to send qualified traffic to the affiliate page.

Allow All skips filters and sends everyone to the affiliate page. Use it only for short tests.