Win 1 TB Residential Traffic, iPhone 18 Pro Max + 33 More Prizes$50 Top-Up = 1 TicketJoin the GiveAway
Enterprise

How to Integrate a CyberYozh Proxy in BAS Browser Automation

BAS (Browser Automation Studio) is a desktop framework for automating browser actions and HTTP requests. It lets developers and QA engineers build multi-threaded scripts for repetitive web workflows without manual input. Running dozens of concurrent threads from a single local IP address, however, quickly triggers rate limits, endless CAPTCHA loops, or session drops.

Connecting external proxies routes each automation thread through an independent IP address. Using residential or mobile proxies lets your scripts access regional storefronts, distribute request loads across clean subnets, and maintain stable long-running sessions. Proper network routing keeps your multi-threaded scripts running without mid-session connection drops.

In this guide, we show you how to set up a proxy in BAS with CyberYozh App step by step, how to verify your connection, and which network architecture fits each automation task. To read this guide in a different language, click on the flag icon at the top of the page.

Why configure a proxy in BAS (Browser Automation Studio)

Browser Automation Studio executes high-frequency browser tasks such as web scraping, account onboarding, and e-commerce monitoring. Without dedicated proxy routing, target servers see all requests coming from a single network node and restrict access.

Routing browser threads through external proxies allows you to:

  • Run hundreds of isolated automation threads concurrently

  • Rotate residential or carrier IPs per request for large-scale data collection

  • Access localized regional content and verify geo-targeted ads

  • Maintain separate network identities when operating isolated client profiles.

Which proxy for BAS fits your automation task

Selecting the right network type depends on how your target platform filters automated traffic. Compare the four proxy categories and their specifications in the table below:

Proxy type

Best for

Key specifications in CyberYozh App

Rotating residential

Scalable web scraping, price monitoring, localized QA, multi-step onboarding

100M+ IPs across 195+ countries, Pay-as-you-go from $4/GB (3 GB minimum, down to $2.5/GB at 100 GB), automatic Traffic Rollover, free city targeting, per-request rotation or sticky sessions up to 24 hours

Static ISP residential

Long-term e-commerce seller accounts, Fintech, persistent profile sessions

Dedicated fixed home ISP address from $5.29/month, unlimited traffic, 99.9% uptime, SOCKS5 and HTTP support

Mobile (LTE/4G/5G)

Social media workflows, ad accounts, multi-threaded Google SERP scraping

From $1.7/day with unlimited traffic, real carrier CGNAT architecture (highest trust score), instant API link rotation

Datacenter

High-speed open catalog parsing, API load testing, uptime monitoring

From $1.77/month, 99.99% uptime, low latency (not recommended for strict login flows)

Per-request rotation vs. sticky sessions in BAS: High-velocity parsing scripts require rotating proxies that assign a fresh IP on every request so individual nodes never hit rate limits. By contrast, when your BAS project involves account logins, multi-page checkouts, or form submissions, sudden IP changes mid-flow will invalidate your authorization cookies. Locking a sticky residential session keeps the same IP active for the entire duration of the scenario.

Why mobile networks outperform per-GB pools on Google SERP: Search engine result pages are packed with heavy JavaScript and dynamic DOM elements that quickly consume gigabyte-based bandwidth. Furthermore, Google’s anti-bot algorithms flag repeated queries coming from single residential connections. Because cellular carriers route hundreds of smartphone subscribers through shared external IPs (CGNAT), search engines rarely restrict these nodes, allowing multi-threaded BAS scripts to scrape Google results all day on flat-rate mobile channels without bandwidth overages.

How to get a proxy for BAS in CyberYozh App

Sign up on the CyberYozh App platform and select the proxy type that matches your project based on these parameters:

  • Network type: mobile LTE/5G, static ISP residential, rotating residential, or datacenter

  • Session behavior: per-request rotation, sticky session, or permanent static IP

  • Geolocation: target country, state/region, or city

  • Bulk generation & API: use the built-in Mass Credentials Generator or Full API access in CyberYozh App to export hundreds of formatted proxy lines for multi-threaded BAS scripts in seconds.

CyberYozh App platform interface

Fig. 1. Screenshot of the CyberYozh App platform interface displaying IP address (Host), port (Port), username (Proxy Username), and password (Proxy Password) for proxy setup.

After purchasing a plan, your proxy card displays the connection credentials:

  • Host: Proxy IP address or gateway host

  • Port: Proxy connection port (HTTP/HTTPS or SOCKS5 with UDP support)

  • Proxy Username: Login string

  • Proxy Password: Password

Proxy example:

  • Host: 172.98.60.180

  • Port: 58763

  • Login: 7XbvvWautzmOZMA

  • Password: xdtAof3xB7RSmUr

Pre-flight IP check: Before feeding an IP into your Browser Automation Studio script, test it through the CyberYozh App Fraud Score checker via the dashboard or API to verify that the address has no spam history across anti-fraud databases.

Step-by-step guide: setting up a proxy in BAS

Follow these steps to bind your CyberYozh App credentials to a browser thread in Browser Automation Studio:

1. Open the BAS project editor and launch the Browser module.

BAS Browser

Fig. 2. BAS Browser control panel with the main web content display window.

2. Click “Record” to start recording your script and open the "Browser" module in the action toolbox.

BAS Browser proxy

Fig. 3. Browser Automation Studio control panel, showing the "Browser" module in an active state.

3. Select the "Proxy" action inside the Browser module.

bas browser configuration

Fig. 4. Proxy server configuration in Browser Automation Studio (BAS). The image shows the settings panel with the "Proxy" action activated for network connection integration.

4. In the configuration dialog that opens, enter your connection details (choose SOCKS5 for full UDP and WebRTC support or HTTP):

  • Proxy string (IP address/host and port)

  • Proxy Type (http or socks5)

  • Proxy Login and Proxy Password

For example:

  • Host: 51.79.24.25

  • Port: 9595

  • Username: pcomUjvMAk-res-any

  • Password: xdtAof3xB7RSmUr

Your filled settings window will look like this:

BAS Browser settings

Fig. 5. Proxy server settings in Browser Automation Studio with filled configuration fields. The image demonstrates the proxy connection setup dialog box with IP address (Host), port (Port), username (Username), and password (Password).

5. Open the additional settings section in the same dialog and set the "Change geolocation" option to "true". Enabling this option automatically aligns the browser’s geolocation coordinates, timezone, and WebRTC data with the attached proxy IP so target sites see a consistent environment.

BAS Browser configuration

Fig. 6. Proxy server configuration in Browser Automation Studio software.

BAS Browser geo data

Fig. 7. Proxy settings module in Browser Automation Studio with the geolocation alignment option activated.

6. Click the "OK" button to apply the action.

BAS Browser setup

Fig. 8. Completing the proxy action setup in BAS.

Once applied, BAS executes the action and routes the internal browser instance through your configured proxy node, logging the result in the execution console.

Fig. 9. Results of proxy connection initialization in the Browser Automation Studio console.

Verifying your proxy in BAS on a diagnostic page

Now that the proxy action is active in the script, let’s verify that the outbound IP address and geolocation coordinates resolve as expected.

To test the tunnel, select the "Load" / "Current URL" action in the Browser module.

Fig. 10. "Current URL" module user interface in Browser Automation Studio (BAS).

Enter a diagnostic website URL (such as browserleaks.com/ip or whoer.net) to inspect your network parameters and browser fingerprint, then click "OK".

bas browser interface

Fig. 11. Interface for entering a target URL in the Browser Automation Studio environment.

Once the page loads inside the BAS browser viewport, confirm that the displayed IP address, country, and timezone match your CyberYozh App proxy node.

BAS proxy verification

Fig. 12. Proxy configuration verification through a browser parameter check service.

Your script is now routing traffic through the assigned proxy channel and is ready for multi-threaded execution.

Scaling Browser Automation Studio workflows on one platform

A properly configured proxy in BAS is the foundation for predictable browser automation. By matching the network architecture to your script’s logic and syncing geolocation parameters, you eliminate rate limits and keep multi-threaded tasks running smoothly across long sessions.

Instead of juggling separate providers for your BAS templates, run your entire automation stack inside the all-in-one CyberYozh App ecosystem. Pair your proxy pools with virtual numbers for automated SMS verification during account onboarding, virtual cards, and check IP Fraud Score ratings via API before launching your threads.