Frequently Asked Questions

Yes! If you read the documentation and still have problems with the setting up of the software, please contact the support team.

Full guide: ATB Quickstart guide on docs.dalga.dev

You don’t need to send us a message to activate your license key. As soon as you buy the software you will receive the license key and you can enter it in the software’s license key check form to activate the software!
If you are unable to use your license key for any reason, feel free to contact us.

Full guide: Installation & license activation on docs.dalga.dev

You can activate the software on two computers with a single purchase code.
if you need to use the software on more than two computers, you will need extra license keys.

(Effective for purchases made after 22th April, 2022)

Full guide: Multi-device & license sharing on docs.dalga.dev

Yes — ATB runs great on a Windows VPS (Server 2016 and above, 2022 suggested), and Dalga IPs, Proxy mode, and VPN mode all work exactly the same as on a desktop, so most users don’t need to change a thing. The one exception is if you specifically want to use Android Phone or PPPoE/FritzBox mode to change your IP — those need a physical device or router connected to the machine, so they’re not available on a VPS. If that’s your plan, you’d want a local desktop setup instead.

Full guide: ATB system requirements on docs.dalga.dev

Yes. With Proxy or VPN mode, it depends on your provider supporting that location. With Dalga IPs, our built-in residential proxy service, you can pick the country and optionally narrow it down to a region or city directly in the app — no external provider needed. See this answer for how it works. And if your goal is local SEO or Google Maps, pair it with GPS Simulation to also spoof the visitor’s device location.

Full guide: Dalga IPs: country, region & city targeting on docs.dalga.dev

You can read this article to help you set up the proxy mode:

https://dalga.dev/use-proxy-mode-in-awesome-traffic-bot/

Full guide: Connection setup: Proxy mode on docs.dalga.dev

Yes, ATB supports rotating proxies. If your proxies have a rotating API URL, you can use the following format to provide the rotating URL to the bot. ATB will automatically rotate the IP of the proxy after each view:
user:pass@ip:port|https://rotatingapi.com
or if your proxies don’t require a username and password:
ip:port|https://rotatingapi.com

Full guide: Connection setup: proxy formats & rotation on docs.dalga.dev

No, IPv6 proxies aren’t supported at the moment — stick to IPv4 for your proxy lists, or use Dalga IPs, which runs on IPv4 by default.

Full guide: IP Changing Methods on docs.dalga.dev

If you want to use your own VPN to change the IP, you will need to use the VPN mode in the bot (It’s been added since version 1.5.4). You can read more about it here.

Full guide: Connection setup: VPN mode on docs.dalga.dev

Yes — AI Traffic lets you describe what a visitor should do in plain language, and the AI looks at the page and does it: searching, reading, clicking, filling out forms, with human-like judgment instead of rigid rules. We support OpenAI, Anthropic, DeepSeek, Gemini, Grok, and even a local model through Ollama if you’d rather not pay per API call. You’ll need to add your provider’s API key under Settings > AI (not required for the local option), and every AI decision shows up in your campaign logs so you can see exactly what it did.

Full guide: AI Traffic on docs.dalga.dev

It’s a visual, drag-and-drop way to build your campaign’s tasks instead of filling out forms one at a time. You place nodes on a canvas — traffic sources, clicks, typing, conditions, loops, captcha solving — and wire them together into one journey. If you’ve already built tasks the classic way, they show up as nodes automatically when you open the Flow Editor, so both views stay in sync and you can switch between them anytime.

Full guide: Flow Editor on docs.dalga.dev

The full version history lives in the documentation: ATB Changelog, covering every release since 2019, newest first.

Updates are delivered through the built-in Update Center, so you get new features and fixes without reinstalling anything.

Yes. When the bot hits a captcha during a normal search-engine session (including Google’s image captchas), it solves it on its own — you don’t need to do anything. You can also trigger captcha solving manually from a task using the "Solve Captcha" action in Advanced Functions or the Flow Editor. Your license includes a monthly credit allowance for this at no extra cost, and if you need more volume than that, you can plug in your own 2Captcha API key instead.

Full guide: Captcha Solver on docs.dalga.dev

Yes — you can point a campaign at a folder or a packed .zip and ATB will launch its browser profiles with those extensions already installed, which is handy for wallet extensions, ad tooling, or anything a genuine user profile would realistically have. Each extension runs isolated so one misbehaving extension won’t crash the session — just keep your list short if you’re running a lot of threads, since extensions do add memory overhead per browser.

Full guide: Browser Extensions on docs.dalga.dev

No. ATB recognizes the difference between sponsored and organic results. It detects Google Search ads and Google Maps business ads, and it will never click your own ad while looking for your organic listing, so your ad budget stays safe while your CTR campaigns run.

You can read how result targeting works in the Search Engine Tasks guide.

With Dalga IPs or your own proxy list, this scales with however many threads you run — each thread gets its own IP, so more threads means more concurrent visitors (see the thread capacity question for hardware limits). If you’re specifically using PPPoE, VPN, or phone mode instead, keep in mind those change the IP of the whole machine, so you’re limited to one IP at a time — the number of visitors then depends on how long each session stays on the page. For example, 1-minute sessions get you around 60 visitors per hour on a single thread, though multi-threading can still send those visitors to different websites at the same time.

Full guide: Limitations: visitors per hour & threads on docs.dalga.dev

We’ve had multi-threading since version 1.5.4, and the number of threads you can run comes down to your hardware and internet speed — each "free" CPU core generally handles 5-10 threads, so a 12-core CPU can comfortably run 60-120 threads with enough RAM and bandwidth. If you’d rather not do the math yourself, AutoPilot adjusts your thread count automatically based on your hardware and current workload — see the Threads & AutoPilot docs. One note if you’re specifically using PPPoE, VPN, or phone mode instead of Dalga IPs/proxies: those change your whole machine’s IP, so multiple threads will share the same IP unless you enable Multi-Threading, which rotates the IP between session batches.

Yes, you can, however, if you wish to get the best performance we suggest not using your computer while the software is running.

Not directly, and that is expected. Tools like SEMrush, Ahrefs, and SimilarWeb do not track live visitors the way Google Analytics or Search Console do. Their numbers are estimates built from crawling, third-party panels, and sampling, so bot-generated visits may not show up in their dashboards at all.

ATB traffic is counted where it matters: Google Analytics and Google Search Console. As your CTR and rankings improve, third-party tools usually catch up indirectly, in the form of more organic keyword visibility, higher estimated traffic scores, and SERP position changes.

Yes, The bot supports all.

Full guide: Task types: Search Engine, Direct & AI traffic on docs.dalga.dev

Most traffic bots inject a fake Referer header so your analytics show visits "from" Google or Facebook. That traffic is cosmetic: there is no real search, no engagement, and no SEO value, just spoofed metadata.

ATB works differently. It opens the real search engine, types your keyword, scrolls the results, clicks your site, and browses like a genuine visitor, with realistic user agents, screen sizes, and browser fingerprints. Those sessions are counted by Google Search Console and Analytics, and they feed the CTR and engagement metrics that actually influence rankings. See how search engine tasks work.

If you specifically want social-style referral visits, a Referrer option still exists in Direct mode, but do not expect SEO value from it.

Yes, the software can work in all countries. However, you must meet the requirements, otherwise it won’t be able to change your IP.

Yes, but views can drop because of another factor of view evaluation in the google account or the software may not login into google accounts.
By the way, we’ve specifically developed a bot for YouTube. You can check that out if you want to use the bot specifically on Youtube. It’s called Awesome Youtube Bot

ATB ships with a multilingual interface. English, Turkish, Korean, and French are available today, and more languages are added over time.

On the traffic side, the visitors themselves are localized too: the browser language of each visit is matched to the IP country automatically, using a dataset that picks the most spoken language for countries with more than one.

Full guide: Installation: choosing the interface language on docs.dalga.dev

You should ask your ISP if your router and ISP support PPPoE mode (bridge mode). This is the easiest way to figure out.

Full guide: IP Changing Methods: PPPoE / Fritzbox bridge mode on docs.dalga.dev

In PPPoE mode, technically you can only connect to your modem via 1 PC and not more. If you don’t want to do so, you can use mobile mode with a dedicated PC/laptop to use the bot. Mobile mode will use your sim-card internet and you won’t need to change anything in your router.
New: if you are using fritzbox modems, you won’t even need to connect your computer to the router via LAN. Also, you don’t need to configure your modem for PPPoE mode. So, you can use the software on the PCs that are connected to the same router.

Full guide: IP Changing Methods: PPPoE / Fritzbox bridge mode on docs.dalga.dev

Yes! Since version 1.5.3, you can configure any phone with ANY android version to use by the ATB. Go to “Configure > Mobile Mode configuration” on the ATB and you’ll be guided to set it up!

Full guide: Connection setup: Android Phone (3G/4G/5G) on docs.dalga.dev

Yes, this mode uses your sim card’s internet.

Full guide: Connection setup: Android Phone (3G/4G/5G) on docs.dalga.dev

No, the mobile mode gets used only as an internet hotspot device. So, the bot uses your mobile’s internet through USB, and you don’t need to install anything on your phone.

Full guide: Connection setup: Android Phone (3G/4G/5G) on docs.dalga.dev

Unfortunately no. The software doesn’t support IOS devices for changing/generating IP in the 4G/5G phone mode.

Please note that the bot generates traffic with IOS and MacOS user agents. This question is about the phone IP changing method, which requires an android phone to make the bot able to change the IP using its internet carrier.

Full guide: Connection setup: Android Phone (3G/4G/5G) on docs.dalga.dev

Yes! The Mobile mode is only being used for the IP-generating part of the software. The visitors will be sent with different user agents, screen resolutions, and browsers!

Full guide: Connection setup: Android Phone (3G/4G/5G) on docs.dalga.dev

It can, with one extra step. Chrome (and the Chromium build ATB relies on) stopped supporting Windows 8.1 and Windows Server 2012 back in early 2023, so from ATB V1.6.8 onward you’ll need to swap in an older Chromium folder to keep it running. We’ve written up the exact steps here. Windows 7 isn’t supported by this workaround or otherwise.