Campaigns
ATB organizes all your work into campaigns. A campaign bundles everything about one traffic goal: a name and tags, the visitor volume and device mix, the connection (IP) method, one or more tasks to perform, an optional schedule, and per-campaign features like browser profiles or extensions.
You control campaigns from the Campaigns page: start, stop, clone, edit (single or bulk), archive, import/export, and inspect them.
Anatomy of a campaign
| Part | What it defines | Details |
|---|---|---|
| Settings | Name, tags, visitors, devices, delays, feature toggles | Campaign Settings |
| Connection | How the IP changes between visitors | Connection setup |
| Tasks | What each visitor actually does | Search Engine, Direct, AI |
| Flow (optional) | The whole journey as a node graph | Flow editor |
| Schedule (optional) | When and how much traffic is sent | Scheduling |
Visitors, tasks, and threads
- A visitor is counted once all tasks in the campaign have been completed by one browser session.
- Threads are the workers that process campaigns — each thread drives exactly one browser. Five threads means at most five simultaneous browsers/visitors. See Threads & AutoPilot.
- Delay between campaigns makes a thread wait after finishing a visitor before it proceeds with the next one.
Campaign types
The campaign list groups campaigns by the type of their tasks:
- Search Engine Traffic — visitors arrive through a search engine (best for CTR/SEO).
- Direct Traffic — visitors open your URL directly, optionally with a referrer.
- AI Traffic — an AI model performs the visit based on your prompt.
A campaign can also be Archived to get it out of the way without deleting it — see Housekeeping.
Statuses you'll see
In the campaign list, the Status column tells you what the campaign (or its last session) is doing — for example Sleeping (waiting for its turn or delay), sent (visitor completed), skipped – Because of CTR % settings (the dice said not to click this time — expected when CTR < 100%), or error states like Browser launch failed. The Logs page has the full story for every session.