> For the complete documentation index, see [llms.txt](https://docs.helodata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helodata.com/integrations/antidetect-browsers/adspower.md).

# 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                    |

4. Click **Check proxy** — AdsPower hits `ipify` through the proxy and reports the exit IP.
5. **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".


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.helodata.com/integrations/antidetect-browsers/adspower.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.