The setup, in order
- 1Create the profile first and configure the proxy on it, rather than creating a profile and adding the proxy later. The fingerprint values AdsPower derives from the IP are set at creation.
- 2In the profile's proxy configuration, choose a custom or manual proxy rather than any built-in pool.
- 3Set the protocol to SOCKS5 or HTTP, then fill host, port, username and password. Those four values are what your provider issues; ours are on the device page in the dashboard.
- 4Use the built-in proxy check before saving. It reports the exit IP and country, and a mismatch here is nearly always a wrong port rather than a dead proxy.
- 5Save, open the profile, and load an IP-reporting site as the first page it ever sees.
Menu names in these tools change between releases, so the steps above name the field rather than the button. If a label has moved, the values it wants haven't.
Which protocol to pick
AdsPower accepts HTTP, HTTPS and SOCKS5. Either HTTP or SOCKS5 works with a PocketProxy device, and both are live on the same connection, so you don't have to choose at purchase. Pick SOCKS5 if you want the browser to hand DNS resolution to the proxy as well, which keeps lookups on the carrier connection instead of your own.
One protocol trap worth knowing across all of these: Chromium doesn't support SOCKS5 with a username and password. Anything Chromium-based that talks to the proxy outside the browser's own profile handling, including most scripted setups, wants the HTTP endpoint instead. More in SOCKS5 vs HTTP.
Bulk import, and the mistake it invites
AdsPower has a proxy list import, which is the reason a lot of people run it at scale. Paste a list and it creates entries you can assign to profiles.
The mistake is assigning one proxy to several profiles because the import made it easy. Mobile IPs already carry many real subscribers behind carrier-grade NAT, and that's what makes them tolerated. Stacking your own accounts on one address recreates the exact pattern the platform is looking for, inside the one IP you control.
Three things that decide whether it holds
These apply whichever browser you run, and they matter more than any setting inside it.
One profile, one proxy, permanently
The pairing is the point. A profile that logs in from one carrier IP for a month and then appears on a different one has told the platform more than any fingerprint setting can hide. Assign the proxy when you create the profile and leave it alone.
Match the timezone and locale to the exit IP
Every one of these browsers lets you set timezone, locale and WebRTC handling per profile, and most will offer to derive them from the proxy's IP. Take that offer. A US carrier IP reporting a European timezone is a mismatch that costs nothing to avoid.
Verify the exit IP before you log in, not after
Open the profile and load any IP-reporting site first. You're checking two things: that the address is the one you expect, and that it reports as mobile rather than hosting. Doing this after a login attempt means the first thing the platform saw was whatever was leaking instead.
Frequently asked questions
Does AdsPower work with mobile proxies?
Yes. AdsPower treats a mobile proxy like any other manual proxy, so it needs host, port, username, password and a protocol. There's no mobile-specific mode to enable, and nothing about a carrier IP requires different handling inside the browser.
Should you use SOCKS5 or HTTP in AdsPower?
Either works. SOCKS5 hands DNS resolution to the proxy as well, which keeps lookups on the carrier connection, so it's the better default. If a profile behaves oddly on SOCKS5, switching that profile to HTTP is a one-field change and worth trying before assuming the proxy is at fault.
Why does the AdsPower proxy check show a different country?
Usually a wrong port rather than a broken proxy. Providers often expose several ports on one host with different behaviour, and pasting the wrong one gets you a connection that works but exits somewhere unexpected. Re-copy host and port together rather than separately.
Setting up a different browser? The antidetect browser proxy hub covers the rest, and running multiple accounts without bans covers the parts no browser setting can fix.
A carrier IP to point AdsPower at
Every PocketProxy is one real Android phone on a real carrier, with HTTP and SOCKS5 live at once and rotation on demand. The trial is 48 hours and takes no card.