One IP per profile
Give every profile its own sticky residential IP with a unique -session- tag. Reusing one IP across profiles is the fastest way to get a cluster of accounts linked and banned together.
Integration Antidetect browser
AdsPower Proxy Integration
AdsPower isolates every account into its own browser profile, but a clean fingerprint still leaks if two profiles share one IP. This guide shows you exactly where AdsPower keeps its proxy fields and how to bind a ProxyOmega residential IP to each profile so your accounts stay separate and stable.
- 200+countries
- 1.5M+residential IPs
- 60 hrmax sticky session
AdsPower
What is AdsPower?
AdsPower is an antidetect (multi-account) browser built for people who run many online accounts at once, marketers, dropshippers, affiliate teams, agencies and e-commerce sellers. Each account lives in its own 'profile', and every profile carries a separate cookie jar, local storage, canvas and WebGL fingerprint, timezone, language and user-agent. To the sites you visit, each profile looks like a different person on a different device.
AdsPower runs on Windows and macOS as a desktop app and also exposes a local API for automation with Puppeteer, Playwright and Selenium. Teams use it to keep dozens or hundreds of profiles organised, share them across members with permission controls, and launch them in bulk. The one thing AdsPower deliberately does not do is give you IP addresses, that part is up to you, which is where a proxy provider comes in.
AdsPower
Why AdsPower needs residential proxies
AdsPower can forge almost every signal a website reads, but it cannot forge your IP address. If ten profiles all connect from the same home or datacenter IP, the platforms you are targeting can link those accounts together no matter how unique each fingerprint looks. The IP is the one identifier the browser cannot spoof on its own, so it has to come from a proxy.
Residential IPs matter because datacenter ranges are widely flagged. A residential IP looks like an ordinary broadband customer, which is exactly what a real account holder would use. Pairing one clean residential IP with one AdsPower profile is the core pattern that keeps multi-account setups alive.
Consistent geo and timezone
A profile that claims to be in Berlin should also exit from a German IP. AdsPower auto-matches timezone, geolocation and WebRTC to the proxy IP, so pick the country in your username and let the browser align the rest.
Stable sessions
Account work like logins and checkouts breaks if the IP changes mid-task. Sticky sessions hold the same exit IP for up to 60 hours so a profile keeps one identity across a whole session.
AdsPower
How to set up ProxyOmega in AdsPower
AdsPower keeps proxy settings inside each profile, so you configure the IP as you create or edit a profile. You can also pre-save proxies in the standalone 'Proxies' manager and assign them later, but the per-profile flow below is the one to learn first.
Your ProxyOmega username carries the targeting. Parameters attach to the username with dashes, for example youruser-country-us-session-profile01-ttl-1440, and your password is always the account API key from your ProxyOmega dashboard, not your dashboard login password.
- Click 'New Profile' in AdsPower, name it, and scroll down to the 'Proxy Configuration' block.
- Set the proxy account to 'Custom' rather than any built-in AdsPower proxy option.
- In the 'Proxy type' dropdown choose 'HTTP/HTTPS' or 'Socks5'. Every ProxyOmega port serves HTTP, HTTPS and SOCKS5 on the same port, so either works, use the same host and port for both.
- In the 'Host:Port' field enter
residential.proxyomega.com:10000(use one of your assigned ports in the 10000-10199 range). - In 'Proxy username' enter your account username plus targeting, e.g.
youruser-country-us-session-profile01-ttl-1440. - In 'Proxy Password' paste your account API key copied from the ProxyOmega dashboard.
- Click 'Check Proxy' and wait for 'Connection test passed'. Confirm the detected country matches your -country- value.
- Click 'OK' to save. As long as you keep the same -session- id and -ttl-, that profile will keep the same exit IP.
AdsPower
Which ProxyOmega plan to pick
AdsPower is plan-agnostic, any ProxyOmega product works, so choose based on the workload behind your profiles. Most multi-account users start on Budget Unlimited and move heavier or higher-value profiles onto Platinum or Static ISP.
| Workload | Plan | Why |
|---|---|---|
| Bulk profile farming, many accounts | Budget Unlimited | Flat port-based pricing. Give each profile its own -session- id on a shared port to get a unique sticky IP per profile. |
| High-value accounts needing precise geo (state, city, ASN) | Platinum | Pay-per-GB Tier-1 residential with country, state, city, ASN, session and TTL targeting. |
| Mobile-app or carrier-sensitive accounts | Mobile | Real 4G/5G carrier IPs with country and session control on port 20229. |
| One permanent US identity that never changes | Static ISP | Dedicated fixed Dallas IP on isp.proxyomega.com that does not rotate. |
| Bandwidth-heavy in-browser scraping | Premium Unlimited | Dedicated 200Mbps-1Gbps speed tier on premium.proxyomega.com:8000. |
AdsPower
Troubleshooting
Most AdsPower proxy failures come down to the password field or a targeting parameter the plan does not support. Work through these before contacting support.
407 Proxy Authentication Required
Two common causes. First, the password must be your ProxyOmega account API key, not your dashboard login password. Second, a targeting parameter the product does not support (for example a -city- tag on a Budget Unlimited username) rejects the entire username. Check that every dash-parameter is valid for your plan.
Connection refused or reset right after connecting
You almost certainly have IP whitelisting enabled. Once any IP is whitelisted on your account, only whitelisted IPs can connect and username/password auth is ignored. Either whitelist the machine running AdsPower, or clear the whitelist and use credential auth.
Check passes but the country is wrong
The -country- code was missing or misspelled, so you got a random-country IP that still authenticated. Use a valid two-letter code such as -country-de and re-run 'Check Proxy'.
SOCKS5 will not connect
Do not look for a separate SOCKS5 port. Use the same host:port you use for HTTP and simply switch the 'Proxy type' dropdown to 'Socks5'.
FAQ
Frequently asked questions
Does AdsPower support SOCKS5 with ProxyOmega?
Yes. Choose 'Socks5' in the 'Proxy type' dropdown and enter the same residential.proxyomega.com host and port you would use for HTTP. Every ProxyOmega port serves HTTP, HTTPS and SOCKS5, so there is no separate SOCKS5 port.
What do I put in the AdsPower password field?
Your ProxyOmega account API key, copied from the dashboard. This is different from your dashboard login password. Using the login password returns a 407 error.
How do I give each AdsPower profile a different IP?
Add a unique -session- id to each profile's username, for example -session-p01, -session-p02, and so on, with a -ttl- in minutes. Each distinct session id maps to its own sticky residential IP even on the same port.
Can I target a specific country per profile?
Yes. Append -country- and a two-letter code to the username, such as youruser-country-gb. AdsPower will auto-align the profile's timezone, geolocation and WebRTC to that IP.
How long does a sticky IP last?
Set the duration with -ttl- in minutes on the username, up to a 60-hour ceiling. Within that window the profile keeps the same exit IP; after it expires you receive a fresh IP.
Should I whitelist my IP or use username and password?
For a desktop running AdsPower, username and password auth is simpler because your home IP can change. Only use IP whitelisting if you have a static IP, and remember that once any IP is whitelisted, credential auth stops working from every other location.
Run every AdsPower profile on its own clean residential IP Start routing today.
200+ countries, sticky sessions, HTTP and SOCKS5 on one port.
ProxyOmega