Ad Traffic is a module inside Botlord Platform. Install and activate the platform first, then configure the engines available to your plan.

Initial configuration

License, runtime mode, credentials, and saving a baseline config before you run any volume.

1 min read

License and install

Install Botlord Platform from Software in your dashboard or from the public download page. One installer covers all engines — there is no separate Google Ads Clicker installer anymore.

Paste your platform license key on first launch. Ad Traffic appears as an unlocked module when your plan includes it. Manage device seats from your dashboard under Licenses.

If security software blocks an installer or update, stop and verify the download source, publisher signature and available checksum. Preserve the exact warning and contact support or the security vendor about a suspected false positive. A signature alone does not prove a file is safe; do not disable protection or add a blanket folder exclusion to bypass a warning.

Runtime mode and credentials

Browser Runtime Mode controls how the bot launches browsers. Auto uses the built-in Chromium runtime — no extra accounts needed and the easiest way to start.

Use AdsPower or MultiLogin when you need isolated fingerprints across many parallel workers. Those modes require the provider's desktop app running alongside Botlord Platform, plus credentials entered in the Configuration tab.

CapMonster Cloud and 2captcha API keys are optional but keep workers from stalling when Google serves a CAPTCHA. Add $5–10 USD balance before a long run.

Antidetect runs need real RAM for Electron, the MLX/AdsPower agent, and a browser profile. See System requirements before using a small VPS or Windows Server box.

Core fields before first run

Set your target keyword, ad click target (Google / Yahoo), proxy source, and wait times. Keep concurrency at 1–2 workers while validating that proxies and captcha solve correctly.

Click Save Configuration after every change. Stop the bot before switching runtime mode or proxy file — mixing old and new settings mid-session causes inconsistent behaviour.

Run a single test session with Logs visible before leaving anything unattended.

← All topics for Ad Traffic