ISP Proxies + JustBrowser: Step-by-Step Setup for Stable, Long-Lived Sessions

Three weeks ago, one of our users, an agency running fourteen client-owned Amazon seller accounts, had all fourteen locked in a single day. All fourteen were running on rotating residential proxies — different IPs every session, sometimes multiple times per session. From Amazon's perspective? Fourteen accounts logging in from wildly inconsistent locations, with IP addresses that jumped between cities every few hours. Amazon's login-security checks flagged them in under a month — a textbook case of the common multi-account setup mistakes.

The fix was obvious in hindsight: ISP proxies.

ISP proxies (sometimes called static residential proxies) are the middle ground everyone skips. They're real ISP-assigned IPs — not datacenter IPs that get flagged instantly — but they're static. Same IP every time. Your Amazon account logs in from the same "home" address in Columbus, Ohio, week after week. That's what a normal, consistent user looks like.

By the end of this tutorial, you'll have JustBrowser profiles configured with ISP proxies, proper authentication, sticky sessions, and IP-to-fingerprint pinning. This setup works for Amazon seller accounts, eBay stores, Facebook Business Manager, and pretty much any platform that tracks login consistency.

Prerequisites

Before we start, make sure you have:

JustBrowser installed — the 7-day trial is full access, enough to test this before committing
ISP proxy access — I'll use Bright Data and Smartproxy as examples, but IPRoyal, Oxylabs, Webshare all work
$10-20 for proxies — ISP proxies run $2-5/IP/month depending on location

No coding. JustBrowser's REST API handles automation later if you want it — but start manual. Trust me on this. I tried automating from day one and spent more time debugging my scripts than actually setting up profiles.

Step 1: Get Your ISP Proxy Credentials

First, buy or allocate ISP proxies from your provider. Here's what you're looking for:

Bright Data: In your dashboard, go to Proxies → Add → ISP Proxies. Select your target country. You'll get a proxy address like brd-customer-XXXXX-zone-isp_residential:[email protected]:22225. The key difference from their rotating residential: ISP zones give you dedicated IPs.

Smartproxy: Under Residential → Dedicated ISP, purchase IPs for your target countries. Pricing as of May 2026: roughly $2.50/IP/month for US, $3-4/IP/month for UK/DE. You'll get connection strings like user-XXXXX-ip-XXXXXXXX:[email protected]:7000.

IPRoyal: Their ISP proxy product is called "Static Residential." Around $2.40/IP/month for US. Connection format: username:[email protected]:12321.

Webshare: Cheapest at $1.30-2/IP/month. Smaller pool though — availability varies by country. Format: username:[email protected]:PORT.

Write down your credentials. Host, port, username, password. That's it. Some providers give you a direct IP instead of a hostname — either works.

One thing I learned the hard way (and by "learned" I mean "sat through verification checks on three accounts before figuring it out"): don't cheap out on GEO matching. If your Amazon seller account is registered in Germany, get a German ISP proxy. IP geolocation databases are more accurate for ISP ranges than for residential pools, so mismatches are obvious. Spend the extra $0.50/month.

Step 2: Create a Profile in JustBrowser

Open JustBrowser and create a new profile. Here's the configuration that works:

Profile basics:

Name: Something descriptive — I use AMZN-DE-01 for "Amazon Germany account 1"
Browser: JustBrowser's Chromium core (rebuilt as upstream Chromium moves)
OS: Windows 11 for most cases. macOS if the account was originally created on Mac.

Fingerprint settings:

Screen: 1920x1080 or 2560x1440 — common resolutions, nothing weird
WebGL: Auto-generate (JustBrowser matches this to your selected OS and a believable GPU)
Canvas: Auto-generate
Audio: Auto-generate
Timezone: Match the proxy location. German proxy = Europe/Berlin timezone. This is critical — timezone mismatches are a red flag.
Language: Match the proxy location. German proxy = de-DE primary language.

Why this matters: Fingerprint has to match where your IP claims you are. Browser in de-DE timezone with English-only fonts and a US IP? Three contradictions. Platforms notice. They absolutely notice. I'm convinced Amazon has someone whose entire job is catching this stuff.

For the fingerprint deep dive — especially if you're dealing with canvas and WebGL fingerprinting issues — we've got a separate post that covers the technical side.

Step 3: Configure the ISP Proxy

This is where most people mess up. Not entering credentials — that part's easy. It's the session settings that'll get you.

In your JustBrowser profile, go to Proxy Settings:

Connection type: HTTP or SOCKS5. Most ISP proxy providers support both. HTTP is fine for browsing; SOCKS5 if you need to handle non-HTTP traffic (rare for account management).

Authentication method: Username/Password. Enter your provider credentials exactly as given.

Sticky sessions: ISP proxies are static by nature. If your provider uses session IDs (Bright Data does), put a unique session ID per profile in the proxy username so the same IP is always served.

Here's an example Bright Data connection string with session stickiness:

brd-customer-XXXXX-zone-isp_residential-session-profile001:[email protected]:22225

The -session-profile001 part locks this profile to a specific IP. Change profile001 to something unique for each JustBrowser profile. I literally use the profile name: -session-amzn-de-01.

Test the proxy before saving. JustBrowser's built-in proxy tester shows the exit IP, the ISP or organisation name, country, city and timezone, latency, and a reputation score with any blocklist hits — plus three flags: proxy, hosting and mobile. There is no "residential" or "ISP" type label; the closest signal is a reputation note when a blocklist classifies the address as residential or dynamic. Look for:

Country: Matches your target (Germany, US, whatever)
City: Consistent with the timezone and language you set on the profile
IP type and ISP name: Check these on your provider's dashboard or an IP lookup — you want a real ISP (Deutsche Telekom, Comcast, BT) and "ISP" or "Residential," never "Datacenter"

Shows datacenter? Wrong country? You bought the wrong product. Happens more than you'd think. Contact support, get it sorted. I've wasted hours debugging "broken" proxies that were just... the wrong proxy type.

Step 4: Pin IP to Fingerprint (The Part Everyone Skips)

Here's the thing. Unique IPs? Not enough. Unique fingerprints? Not enough. You need consistent pairing.

If Profile A uses IP 1.2.3.4 on Monday but IP 5.6.7.8 on Tuesday — while both IPs are technically "good" — the account now has an inconsistent login history. Real users don't change IPs every day. (Well, mobile users do, but we're talking static residential here.)

How to pin in JustBrowser:

After configuring your ISP proxy, note the exact IP address you get. The proxy tester shows this.
In the profile's proxy settings, add a note or label with that IP.
Never change this profile's proxy unless the IP gets burned.

If your provider rotates your ISP IP (some do this if you exceed bandwidth limits), contact them immediately to get a static assignment. You're paying for static — hold them to it.

The rotation mistake:

I've seen users set up "rotation logic" for ISP proxies — cycling through 5 IPs on a schedule, thinking more = better. Wrong. So wrong. More IPs means more inconsistency. Faster flags. Save rotation for scraping. For account management? One IP. Stick with it. This is the hill I'll die on.

Step 5: Warm Up the Profile

Don't log into your high-value account immediately. A brand-new profile has zero browsing history, and a short warm-up gives it ordinary cookies and history, like any everyday browser, before the first real login.

Basic warm-up routine:

Open the profile and browse naturally. Visit Google, check a news site, scroll through some results.
Visit 3-5 sites relevant to your account's niche. Running an Amazon seller account? Browse Amazon as a shopper first. Add something to cart. Don't buy — just browse.
Let some ads load. This builds ordinary cookie history in the profile.
Close the profile and wait at least 2 hours before your first real login.

JustBrowser has a built-in cookie warm-up feature that automates this across 127 curated sites in 6 categories. Worth using if you're setting up more than a few profiles. Find it under profile aging and warm-up.

For ad account management specifically — whether you're running Google Ads or Facebook Business Manager — you'll also want click fraud protection on the accounts themselves. ClickzProtect handles that side, making sure bots aren't eating your budget while you're busy configuring proxies.

Step 6: Verify the Setup

Before trusting your accounts to this setup, test it.

Run fingerprint checks:

Open the profile and visit these sites:

CreepJS — look for inconsistencies flagged in red
BrowserScan — check that timezone/language/IP/location all match
IPHey — verify IP geolocation is correct

If any test shows mismatches, fix them before proceeding. Common issues:

Timezone doesn't match proxy GEO — edit profile settings
Language is wrong — edit profile settings
WebGL shows impossible hardware combo — regenerate fingerprint

Run a login test on a throwaway account:

If you're setting up for Amazon, start with your own buyer account on the profile (not a seller account). Browse normally for a few days. If it runs for a week with no verification prompts, your setup is consistent. If it gets prompted or locked, something's wrong — debug before moving a valuable account onto the profile.

Paranoid? Yes. But I've watched people skip this step and get $50K/year seller accounts locked because they assumed things were fine. One guy in our Discord had a seller account he'd run for six years locked. Six years of reviews, six years of buy box history — stuck behind verification because he didn't test first. Test the setup before a valuable account goes near it. Always.

Common Errors and How to Fix Them

Proxy authentication failed

Cause: Wrong username/password, or the credentials expired.

Fix: Double-check credentials against your provider dashboard. Some providers require URL-encoded passwords if they contain special characters. Try resetting the password to something alphanumeric only.

IP shows as datacenter instead of residential

Cause: You're on the wrong proxy product. ISP proxies are a separate product from rotating residential at most providers.

Fix: Check your provider dashboard. Make sure you purchased ISP/static residential, not rotating residential or datacenter. The zone or product name should explicitly say "ISP" or "Static Residential."

Timezone mismatch detected by fingerprint checkers

Cause: JustBrowser profile timezone doesn't match proxy location.

Fix: Edit the profile, change timezone to match the proxy country's primary timezone. For multi-timezone countries (US, Russia, Australia), pick the timezone that matches the city your IP geolocates to.

Account still got flagged/suspended

Cause: Could be fingerprint issues — including TLS-layer fingerprints that most antidetect browsers leak even when the browser fingerprint looks clean. Could be behavioral — logging in at 3am, checking 500 listings in 10 minutes, you know, doing inhuman things. Could be the IP itself is burned.

Fix: Check if the IP is blacklisted (IPQualityScore works). Clean? Check fingerprint with CreepJS. Also clean? Then it's probably you. If an account is suspended, use the platform's own appeal route rather than working around it. Were you acting like a bot? Slow down. I know it's annoying. I know you have 47 accounts to check. But platforms aren't stupid — they know humans don't click through 200 products in 8 minutes. If you're running cold outreach campaigns alongside your accounts, JustEmails handles email deliverability so you don't burn your sender reputation too.

Next Steps

Once you've got ISP proxies working for one platform, the setup applies to others. Same principles: one IP per profile, consistent fingerprint, match GEO/timezone/language.

If Amazon has approved more than one seller account for your business, our Amazon multi-seller guide covers the platform-specific gotchas — category restrictions, linked payment methods, all that.

If you're managing Facebook Business Manager accounts and running ads, pair this setup with conversion tracking via JustAnalytics so you can verify that your tracking pixels fire correctly across your isolated profiles. Nothing worse than running ads that don't attribute conversions because your analytics setup doesn't account for multi-profile environments.

And if you're doing affiliate marketing at scale, the affiliate setup guide covers some of the operational patterns that work when you're managing more than a handful of profiles.

ISP proxies cost more. About 3-5x more per account. And yeah, that stings when you're running 20+ profiles — we're talking $40-100/month just in proxy costs. But sessions stay consistent. That agency with fourteen locked client accounts? Moved to ISP proxies. Six months later, all still active. Do the math: fourteen accounts at $39.99/month seller fees is $560/month in fees alone, not counting revenue. Spending $70/month on proxies for stable access to accounts that cost $560/month in fees? That's not an expense. That's reliability.

More on the JustBrowser blog. And if this saved you from losing an account, let us know — always nice to hear the war stories.

Frequently Asked Questions

What's the difference between ISP proxies and regular residential proxies?

ISP proxies are static — you get the same IP every time, assigned to datacenter hardware but registered to real ISPs. Regular residential proxies rotate IPs from a pool of home connections. ISP proxies cost $2-5/IP per month but give you consistent identity. Rotating residential proxies cost $5-10/GB but change IPs constantly. For accounts you use daily (Amazon seller, Facebook Business Manager), ISP proxies are worth the premium because platforms track IP consistency.

How many profiles can I run on one ISP proxy?

One. Seriously. The point of a dedicated ISP proxy is a stable, consistent identity for each profile. Many platforms only allow one account per person or business unless they approve more (Amazon, for example, permits an additional seller account only where it has approved one), so check the platform's policy first. For accounts you're permitted to hold, give each its own IP and fingerprint so sessions stay consistent. One profile, one IP. If cost is a concern, use ISP proxies for high-value accounts and rotating residential for lower-stakes work like collecting public data.

Do ISP proxies work for TikTok Shop and Instagram?

TikTok Shop — yes, ISP proxies work well. Instagram — mostly yes, but Instagram's detection leans heavily on mobile device signals. For Instagram accounts that need to look like phone users, mobile proxies often work better than ISP proxies. For Instagram accounts managed from desktop (business accounts, ad accounts), ISP proxies are fine.

What happens if my ISP proxy IP gets flagged?

Contact your provider for a replacement IP. Most ISP proxy providers (Bright Data, Smartproxy, Webshare) offer IP replacement within 24-48 hours. Before requesting a replacement, verify the IP is actually flagged — sometimes the issue is fingerprint inconsistency, not the IP itself. Run a test on IPHey or Pixelscan to check.

Try JustBrowser

Native Chromium antidetect browser — not extension-based. Real C++ engine patches at the canvas / WebGL / audio / font / screen layer, so 40+ identity parameters are genuine, not faked. REST API for Playwright, Puppeteer, Selenium. $9.99/month or $99.99/year. 7-day free trial, card required — cancel any time in the seven days and you are not charged. Unlimited profiles.

Get started → · How it differs from Multilogin / GoLogin / AdsPower