Frequently Asked Questions

Yes! If you’ve read the documentation and still have problems with the software setup, please contact support team.

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

Windows 10 or 11 for desktop, or Windows Server 2016+ if you’re running it on a VPS. You’ll need the Microsoft Edge WebView2 Runtime (already included on most recent Windows installs — the installer handles it if it’s missing), 8 GB RAM minimum (16 GB+ if you’re running a lot of threads or Android emulators), and a 4-core CPU or better. If you’re using emulator mode you’ll also need Memu or LD Player installed separately, and Android phone IP changing needs a physical Android device with USB debugging and tethering enabled.

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

Yes — AYB runs on Windows Server 2016 and above for VPS/RDP setups, same as a regular desktop install. Just keep in mind that emulator mode (Memu/LD Player) and Android phone IP changing both need real hardware, so they’re not available on a VPS — proxies or Dalga IPs are the way to change IPs there instead.

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

No. But It doesn’t mean you can’t have. If you have clean google accounts, sending views with logged-in accounts will make your views more solid and it decreases the chance of the view being dropped. A logged-in account is necessary for comment/like/subscribe. Obviously, you can’t do the mentioned operations when you’re not logged in.

UPDATE: Due to the latest changes of the youtube counting system, you’ll need to import Gmail accounts to be able to perform views. This section may get updated if there’s any further updates. Also, technically, you can send unlimited views (with different IPs) by using 1 Gmail account. However, if you import more Gmail accounts, it will have better effects on ranking.

Full guide: Accounts, Cookies & 2FA on docs.dalga.dev

The bot only logs in for the first time, It will save the cookies afterward, Note that you should disable two-step verification from your google account.

Full guide: Accounts, Cookies & 2FA: login behavior on docs.dalga.dev

Yes, actually — through Dalga IPs, our own residential proxy service built right into the app. You pick it as an IP-changing method, choose the country (and optionally region/city), and every thread gets its own rotating residential IP with no third-party account to manage. It’s billed by bandwidth and comes with a monthly allowance on your license, with top-ups available if you need more. If you’d rather bring your own proxies, that still works too — see what kind of proxies to use.

Full guide: Dalga IPs for AYB on docs.dalga.dev

We recommend you use HTTPS proxies, however, AYB also supports socks4/socks5 proxies.

We highly suggest you not use free public proxies as most of them are blacklisted and slow.

It’s recommended to use Residential/4G proxies for the best results.

Full guide: Step 2: Connection — proxies on docs.dalga.dev

Yes, AYB supports rotating proxies. If your proxies have a rotating URL, append it to the proxy line and AYB will rotate the IP for every view automatically:
user:pass@ip:port|https://rotatingurl.com
or if your proxies don’t require a username and password:
ip:port|https://rotatingurl.com

Prefer not to manage your own list? Dalga IPs handles rotation for you automatically.

Full guide: Step 2: Connection — proxy formats & rotation on docs.dalga.dev

We can’t suggest any specific provider, because we can’t guarantee the quality of their services, But It’s better to make sure that you’re using Residential/4G Proxies.

No, in that case, your IP will not change.

Full guide: Step 2: Connection — VPN on docs.dalga.dev

Yes — likes, comments, subscribes, and even liking existing comments on a video, as long as the visitor is logged into a Google account (these actions don’t work anonymously). For comments specifically, you build reusable comment lists in the app and assign one to your Comment task, or set it to pick randomly from a list, so every visitor doesn’t post the same line. Keeping a few varied lists per topic is the easiest way to avoid a spammy, repetitive pattern.

Full guide: Engagement: likes, comments & subscribes on docs.dalga.dev

Yes — AYB now handles authenticator-app 2FA directly. When importing accounts, add the authenticator’s secret key (not the 6-digit code you see on your phone) after the password, and the app generates valid codes automatically at login. Format: [email protected]:password|recoveryEmail|2FAsecretKey — you can include the recovery email, the 2FA secret, both, or neither, depending on what your account needs. The bot still can’t complete a phone-number SMS verification, so if Google asks for that specifically, that login will be skipped.

Full guide: Accounts, Cookies & 2FA on docs.dalga.dev

The keyword is a text that AYB uses in google/youtube search to find your video, Your keyword should be something findable in the google/youtube search on the first page, Otherwise, you can use your video title or your video URL

NOTE: Make sure your URL is in the correct format, read more about the correct URL formatting in this section.

Full guide: Views & Watch Time: how the video is found on docs.dalga.dev

You should use the full video URL, It looks something like this:

https://www.youtube.com/watch?v=ABCDEFGH

In the above example, ABCDEFGH is your video ID, Sometimes, your URL may contain extra arguments in front of the ID for example:

https://www.youtube.com/watch?v=ABCDEFGH&ab_channel=Test&t=3

In this case, you should delete these extra options and just provide the full URL (Like the first example)

Do not use URLs starting with youtu.be, otherwise the bot might not function correctly.

Full guide: Step 1: Goal & Tasks — view target on docs.dalga.dev

It’s recommended to use a good keyword, and the watch time duration should be at least 30 seconds, If your video is 30 seconds or less, The entire video should be watched, otherwise, YOUR VIEWS MAY NOT BE COUNTED.

For the view sources, It’s better to use all options. Also enable the RandomAct feature for more realistic views.

Full guide: Views & Watch Time on docs.dalga.dev

Yes, Every browser instance has a totally unique fingerprint + anti-bot detection features

Full guide: Browsers & Profiles: fingerprints on docs.dalga.dev

No, Not at all.

Full guide: Browsers & Profiles on docs.dalga.dev

No — that’s extremely unlikely unless you send a large volume of low-quality traffic to a monetized video. We’d recommend avoiding monetized videos for testing and enabling the "Block Ads" feature to reduce that risk further.

Yes — you can hand part of a task to an AI agent, which is essentially an LLM that looks at the page and carries out your instruction the way a person would. Set up your provider (OpenAI, Anthropic, DeepSeek, Gemini, or Grok) under AI Configurations, then attach the agent to a task with a plain-language prompt, choose whether it runs before or after the task’s normal actions, and set a timeout. It’s useful for interactions that are awkward to script by hand, and everything the agent does shows up in the Jobs tracker so you can review it.

Full guide: AI Agent on docs.dalga.dev

It’s a standalone browsing mode where the visitor just explores YouTube naturally — Recommended videos, Trending, Shorts — with optional engagement thrown in, instead of going straight to one target video. It’s one of the easiest ways to make a session look genuinely organic, and we recommend turning it on alongside your view settings for that reason.

Full guide: Random Act on docs.dalga.dev

As the latest Youtube algorithm update, To send live views we recommend you use the regular view process for it. Because sending live views with API will cause zero watch time and live view drops. But if you use the regular view also for live videos, you’ll have a much better effect. However, you may be unable to send a few hundred live views with this method because it’s aggressively using the resources. The number of livestream viewers corresponds with the maximum number of threads you can use. You can read about it here.

Yes, AYB is able to send live stream views. You can read the instructions or watch the tutorial video to learn more.

Yes, You can set the playback speed or playback quality. In addition, you can let the bot choose a random speed/quality each time by selecting the "Random" option.

Full guide: Views & Watch Time: playback speed & quality on docs.dalga.dev

AYB is capable of sending views from the youtube search, Recommended videos, and google (It will show as External), And you can customize the view sources since version 1.2.0

Full guide: Views & Watch Time: view sources on docs.dalga.dev

It can take up to 48 hours for the views to be counted, But usually, You will see the results in a shorter timeframe.

You can use a video or channel URL, But It’s always better to use the video URL

Full guide: Engagement: subscribe on docs.dalga.dev

It’s based on your watch time and the video quality. For example, If you have a 480p video that’s 10MB, and you want to watch it entirely, about 10MB will be used for each view. By unblocking Ads, The traffic from the Ads will be also counted. Since version 1.2.0, you can reduce the traffic usage by setting playback speed and playback quality.

Full guide: Dalga IPs: saving bandwidth on docs.dalga.dev

Youtube has so many factors in the comment/subscriber approval process, Including the context of the comments’ text, and your account being flagged as spam. It’s the youtube decision to approve the comments/subscribers. We won’t guarantee YouTube’s approval because of the factors mentioned above. 

You are probably experiencing this because your windows display scale is set to above %100. Do the following steps in order to fix this issue:

• Open the start menu
• Search for "Scale"
• Select the first option
• On the "Make everything bigger" section, set the value to "%100"

It depends on the number of threads, the watch time, and your proxies. If you use 5 threads and set the bot to watch each video for 60 seconds with 5 rotating proxies (rotating every 1 minute), each thread will send 1 view per minute. So, the total number will be 5 views per minute, which generates 300 views per hour. You can calculate this with your own parameters.

This is for sending a view for 1 video. You can send views to multiple videos at the same time with the same proxy. So, if you have 1 proxy and 10 threads with 10 videos link, the bot can send 1 view to each of the videos within a minute. So, basically, you’ll receive 1 view per video, which will total to 10 views.

Full guide: Threads & Capacity on docs.dalga.dev

It depends on your hardware specifications and internet connection speed. You can easily run 5 threads with 8 GB Of RAM and a 4th+ generation CPU. Basically, each “Free” CPU core is able to handle 5-10 threads, So If you’re using a 12-core CPU, you can use about 60-120 threads.

NOTE: If you use PPPoE/Mobile Mode, with more than one thread at a time, You won’t see any results, because your IP will be the same across all threads. If you want to use multi-threads, you should use proxies (each thread will pick a random proxy from the list of proxies).

Full guide: Threads & Capacity on docs.dalga.dev

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

Full guide: IP Changing Methods: broadband bridge (PPPoE / FritzBox) on docs.dalga.dev

Yes! Go to “IP changing methods > Mobile Mode configuration” on the AYB and it’ll walk you through the setup.

Full guide: Step 2: Connection — Android phone on docs.dalga.dev

Yes, it does. This mode uses your SIM card’s internet.

Full guide: Step 2: Connection — Android phone on docs.dalga.dev

No, you don’t. The mobile/phone 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: Step 2: Connection — Android phone 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: Step 2: Connection — Android phone on docs.dalga.dev