How to use residential IPs for sensitive accounts

Sensitive accounts are accounts that are costly to lose or rebuild: ad accounts, marketplace seller profiles, LinkedIn and other social profiles, and accounts with several weeks of gradual activity. Platforms compare each sign-in with the earlier sign-ins of the same account. The proxy settings decide what that comparison shows. The exit is the IP address that websites see when traffic goes through the proxy. For a sensitive account, use a residential exit in the city and internet service provider (ISP) where the account usually signs in, with a separate sticky session for every account.

​

Signals a platform compares

Platforms do not expect an account to keep one IP address forever. Phones switch between Wi-Fi and mobile data, and home routers receive new addresses from their ISP. In common anti-fraud practice, a platform asks for extra verification when a change does not fit the account history.

• Network type. IP databases such as MaxMind Anonymous IP mark hosting ranges. A residential exit comes from a home connection.
• City. A sign-in far from the usual location can look like an account takeover. Set City to the usual sign-in city.
• ISP. A different provider in the same city looks like a different household. Set ISP, or the autonomous system number (ASN) of that provider when only the network number is known.

​

Exit types compared

Residential exits accept a country, region, city, or ZIP code. Datacenter and static ISP addresses are typically limited to the cities that a vendor stocks. A static ISP address fits a workflow that needs one fixed address, for example a partner IP allowlist. For signing in to an account, a residential exit in the city and ISP of the account owner matches more of the sign-in signals.

​

How an exit changes in a sticky session

A sticky session requests the same exit for related steps. A residential exit is a real home connection, so the device behind it can go offline. The session then continues from another device, and the city and ISP settings limit which devices qualify. With City and ISP set, ProxyLane requests the next exit inside the same city and ISP. A new IP in the same city and ISP is closer to a home router receiving a new address than a move to another city. If no matching device is online, the connection can fail. Run the exit check after a reconnect.

​

Set up each account

The setup needs a ProxyLane account with available traffic and a browser profile for each account, for example in one of the browser profile apps.

1. Open Residential proxies.
2. Choose Country, then City, then ISP where the account usually signs in. To use an ASN instead of an ISP, enter it in ASN under Advanced options. If the ISP selector stays unavailable after a city is chosen, ProxyLane has no ISP choice for that city; keep City set and leave ISP unset.
3. Open Advanced options and check that IP rotation is set to Keep the same IP. It is the default.
4. Set Endpoints to the number of accounts that share this city and ISP. Each endpoint is a separate sticky session.
5. Click Create proxy. ProxyLane saves the result as a list under Saved lists.
6. Copy one row (one endpoint) into each browser profile. These rows are the saved list, so later copies come from Saved lists. The connection settings guide shows where each part goes.

For accounts in another city, repeat the steps with that city. To add an account later, reload the dashboard page first, then create a new list for the same city and ISP with Endpoints set to 1. Without the reload, the first row of the new list repeats the session of the first row in the earlier list.

​

Keep accounts apart

• Use one endpoint and one browser profile per account.
• Set the browser time zone and language to match the pinned city.
• Turn on the WebRTC and DNS leak protection in the browser profile app. WebRTC and DNS are browser features that can reveal the real IP address or the local DNS resolver outside the proxy.
• Keep one active session per account. Sign out of the account on other devices while automation uses it.
• Keep the same pinned city and ISP for the life of the account.
• Increase activity on a new account gradually instead of starting at full daily volume.

Proxy settings change network signals only. Spam reports, sudden volume increases, and repeated identical messages lead to restrictions on any type of IP.

​

Check the exit

1. Under Saved lists, click Use proxies on the list and open the Test connection tab. Enter the port of one endpoint in Check port and click Run check. The check shows the exit IP of that endpoint and uses a small amount of traffic.
2. In the browser profile that uses that endpoint, open My IP. The IP matches unless the exit changed between the two checks.
3. Compare the city and the ISP, shown as “Network / ISP”, with the pinned city and ISP. If an ASN is set, compare the ASN too.

The result matches when the city and ISP are the pinned ones. My IP uses a different database, so the ISP name can be spelled differently from the dashboard. The time zone on My IP is also the value for the browser profile. If a check fails:

• A check fails after an ISP or ASN is set. Clear ASN first, then ISP, and keep City. Then create the list again and copy the new rows into the browser profiles, because the old rows keep the old targeting.
• An exit appears outside the pinned city. Send the country, city, and time of the change to ProxyLane support.

For help choosing a city and ISP, send the usual sign-in location of the account to ProxyLane support.