The fastest path from sign-up to a protected landing page takes five short steps. Each one maps to a screen in the dashboard, so you can follow along with the app open in another tab.

1. Open the dashboard. Head to the app and create your account. The dashboard is where every campaign, filter, and report lives.
2. Create a campaign with the wizard. Give it a name and set the single approved destination that all valid visitors will reach. This is the same page for everyone — there is no separate reviewer version.
3. Choose your filters. Start with the recommended traffic quality filters. Enable proxy, VPN, datacenter, and frequency checks, then decide whether risky visits are blocked, challenged, or only logged.
4. Install the snippet. Add the Cloak4U snippet to your landing page using PHP, WordPress, or JavaScript. From that point on, every visit is scored before your page is served.
5. Watch your reports. Open Reports and the click log to see what was allowed, what was blocked, and why. Tune sensitivity from there.

That is the whole loop: evaluate, decide, log. Once traffic is flowing you can add custom rules, adjust retention, and export data as your needs grow.

Campaigns and the approved destination

A campaign is a protected landing page plus the rules that guard it. Every campaign has one approved destination. Valid visitors — including anyone an ad platform sends to review where your ad points — all resolve to that same page. Cloak4U decides whether a visit is valid; it does not decide who sees a different page.

Filters and custom rules

Built-in filters score each visit against signals like datacenter IP ranges, proxy and VPN origins, automation user-agents, timezone mismatches, and click frequency. On top of those, you can layer custom allow/block rules using country, device, referrer, language, user-agent, and URL parameters with AND/OR logic. Signals are weighted and combined, so one soft signal will not block a visitor on its own.

Outcomes and the click log

Each evaluated visit ends in one of four outcomes — allow, block, challenge, or log-only — and every outcome is written to the click log with the rule that triggered it, a human-readable reason code, a risk score, and a request ID. Your reports summarize this so you can audit exactly why traffic was handled the way it was.

Integrations

The snippet is how Cloak4U sees traffic in the first place. Choose the integration that matches your stack. Server-side options like PHP and WordPress evaluate the request before your page renders; the JavaScript option runs client-side. All of them feed the same evaluation and logging pipeline.

Privacy and retention

Cloak4U is built around data minimization. It collects only the signals needed to score a visit, masks or hashes IP addresses in the UI, and lets you control how long records are kept. See the privacy policy for the full list of what is and is not collected.