Setting Up Proxies in Browser Automation Studio
How to configure proxies in BAS the right way — proxy types, per-thread assignment, rotation, and the checks that keep multi-account bots from getting flagged.
Once your first bot runs, proxies are the next thing that decides whether a multi-account project survives or gets flagged within a day. In BAS the mechanics are simple; the discipline around them is what matters.
Why proxies matter in BAS
BAS drives a real browser, but every thread still shares your machine’s IP unless you say otherwise. Run ten accounts from one IP and most sites will link them instantly. A proxy gives each browser instance its own network identity, which is the whole point of multi-accounting.
Proxy types and when to use them
- Residential proxies — IPs from real consumer ISPs. Best for sensitive accounts; hardest to detect.
- Mobile proxies — carrier IPs shared by many real users; very high trust, higher cost.
- Datacenter proxies — fast and cheap, but easier to detect. Fine for scraping public data.
Match the proxy to the risk: high-value accounts get residential or mobile; bulk scraping can use datacenter.
Assigning a proxy in a flow
BAS exposes a proxy step that sets the proxy for the current thread’s browser before navigation. Configure host, port, and credentials, then verify the connection before loading any target site — a dead proxy that silently falls back to your real IP is the classic way accounts get burned.
One proxy per thread
For multi-account work, bind a distinct proxy to each thread, ideally pinned to a specific account. Load a proxy list as a resource and have each thread pull its own line. The rule: an account should consistently appear from the same identity, and different accounts should never share one.
Rotation and verification
- Verify first. Hit an IP-echo endpoint and confirm the returned IP matches the proxy, not your machine.
- Rotate deliberately. Sticky sessions for account work; rotating IPs for scraping volume.
- Handle failures. If verification fails, stop the thread — never let it continue on the real IP.
Proxies plus the first-bot skeleton are the foundation. From here, return to the guide for deeper topics like fingerprints, captcha solving, and multithreading at scale.
FAQ
What proxy type is best for BAS?
Residential or mobile proxies are best for sensitive multi-account work because their IPs look like ordinary users. Datacenter proxies are cheaper and fine for scraping public data where blocks are less aggressive.
Should each thread use a different proxy?
Yes. For multi-account automation, assign one proxy per thread (ideally per account) so that account activity is not all coming from the same IP, which is an obvious flag.
- Browser Automation Studio: The Complete Practical GuideGuide
- Building Your First Bot in Browser Automation StudioA step-by-step walkthrough of creating your first working BAS bot — from a blank project to a flow that navigates, extracts data, and runs in multiple threads.
- Finding Elements in BAS: Selectors That Don't BreakHow element search works in Browser Automation Studio — CSS vs XPath selectors, why recorded ones break, and how to write selectors that survive page changes.
- Filling and Submitting Forms in BASHow to fill, select, check and submit web forms reliably in Browser Automation Studio — typing like a human, handling dropdowns and checkboxes, and verifying the result.