AdsPower

AdsPower lets you assign a different proxy per browser profile — a natural fit for ISP proxies (one IP per profile) and residential sticky sessions (one session per profile).

Per-profile setup

1. New profile → Proxy settings.
2. Pick Custom (not "AdsPower built-in").
3. Fill in:

Residential / Mobile (gateway)

Field	Value
Proxy type	HTTP, HTTPS, or SOCKS5
Proxy host	gate.helodata.io
Proxy port	7777
Account	helo_s1a2b3c4d5e-type-res-region-us-session-prof01-sesstime-30
Password	sub-user password

Use a unique session-XXX per profile so each profile holds its own IP.

ISP

Field	Value
Proxy type	HTTP, HTTPS, or SOCKS5
Proxy host	198.51.100.42 (one IP per profile)
Proxy port	8000
Account	helo_s1a2b3c4d5e
Password	sub-user password

1. Click Check proxy — AdsPower hits ipify through the proxy and reports the exit IP.
2. Save → launch the profile.

[screenshot: AdsPower proxy settings dialog]

Bulk import (ISP)

For batches of profiles each tied to an ISP IP:

1. My profiles → Import → Proxies.
2. Upload an ip:port:user:pass file — exactly the format helodata ships.
3. Map each line to a profile.

AdsPower also accepts the CSV export (ip,port,user,pass,country,city,asn) for richer metadata.

Profile templates

• Browser fingerprint: pick a fingerprint matching the proxy's country/city (Mac UA for a US IP, etc.). AdsPower's "Match country" toggle auto-aligns the fingerprint to the proxy geo.
• Time zone: set to match the proxy country.
• WebRTC: set to Replace to avoid leaking the local IP.

Verify

In the launched browser, visit https://ipv4.icanhazip.com and https://browserleaks.com/ip — confirm IP matches the proxy and no WebRTC leak.

Common pitfalls

• Same session ID across many profiles — sticks all profiles to one IP. Each profile must have a unique session-XXX.
• ISP IP reused across profiles — defeats the per-profile isolation. One IP, one profile.
• Fingerprint timezone misaligned — a US IP with Asia/Shanghai locale is a strong bot signal. Use "Match country".