Quick start

This guide gets you through the smallest working loop: visitors go to the landing or safe page per your rules, verified with Rule Preview before going live. Menu names follow the console UI.

What you need

• A console account (trial via Free trial or Contact us)
• A domain pointed to the platform (HTTPS required)
• Landing and safe page assets (lightweight static HTML recommended; you can also export a ZIP from the built-in editor)

Recommended order

1. Check your account and permissions

Make sure you are operating under the right account. Admins manage shared account resources (e.g. rule templates); members usually manage only what they create.

2. Add your domain

Add the domain in Domain management and finish DNS and certificate setup. Without a usable domain, ads have no stable entry.

3. Prepare landing and safe pages

• Landing page: your real conversion page (product intro, checkout redirect, etc.)
• Safe / fallback page: shown to non-target or high-risk traffic. Use a complete brand, policy, or maintenance page consistent with the domain - not a placeholder, fake 404, or unrelated page

When uploading a ZIP, prefer small static pages; page quality and size directly affect loading experience.

4. Create an ad

Create a new ad, fill in the path and an ad code, and attach the domain and pages. You enter the ad code yourself (usually unchangeable after creation) — you’ll use it later in conversion tracking.

5. Configure filtering rules

Open the rules page of the ad and configure Country, Language, Device, Network, Bot, Ad Verification, IP / ASN, Referer, etc. for your target market. Platform presets seed the Ad Verification list; clear that dimension and save if you do not want it.

Tips:

1. Make sure the target market can reach the landing page first
2. Then gradually tighten proxy / datacenter / VPN / Bot
3. Always self-test before scaling traffic

Parameter meanings for every dimension: Ad rules basics. The overall model: Traffic quality filtering basics.

6. Self-test with Rule Preview before going live

Open Rule Preview for the ad:

• Pick a preset profile (Meta / TikTok / Google) or customize visitor fields and rerun
• See whether the result is landing or safe, plus which dimension matched
• Rule Preview only simulates; it never changes live rules

You can also open a single access log entry in Rule Preview to re-test a real sample.

7. (Optional) Enable conversion tracking

If conversion tracking is enabled for your account, configure tracking link parameters and the payment postback to write payment results back into reports. See Conversion tracking and postback.

8. (Optional) Bind ops notify

Admins can open System → Notifications to bind this account’s Telegram and/or Webhook for license-expiring and domain-unhealthy alerts. Steps: Notify & Telegram setup and Notify & Webhook setup.

9. (Optional) Use IP Lookup

If operations has enabled it for your tenant, open IP Lookup in the console to check a single IP’s context: single-query lookup, structured results, one-click JSON copy. See IP Lookup.

10. (Optional) Edge decision

If operations has enabled it, open Edge Decision, configure rules, then download the official PHP pack (PHP 8.3) or Cloudflare pack (Worker or Pages middleware) for your environment and deploy it. Visitors to that site get a page or a redirect from the platform decision. You do not need to move the domain onto our servers. See Edge decision & official scripts.

Every page, explained

The main flow above is the shortest path. For every field, button, and action on every console page — in sidebar order (Advertising, Pages, Analytics, Ops Tracking, System & Account) — see the Console guide.

After going live

Common pitfalls

• No rules = fully open: the UI will tell you; that’s “filter not yet set”, not a broken Rule Preview
• Edited the form but didn’t save: rules and templates both require Save to take effect
• Poor fallback page quality: use a complete brand, policy, or maintenance page; do not show reviewers content different from ordinary visitors