Isolation is not “install an antidetect and open forty tabs”. It is two lists of parameters: one that must differ between profiles, and one that must match inside a single profile against the history of the batch. Below is the list worth running over a batch before the first login, not after half the accounts have gone into review.
Three layers where accounts get linked
The account layer is the login, password, email and 2FA secret. The profile layer is the browser fingerprint the account lives in. The channel layer is the address the profile goes out through. As long as every account keeps its own second and third layer, the batch behaves like a set of unrelated people. The moment two accounts share a fingerprint or an address they become one cluster: a review triggered on one arrives on the whole cluster right after.
Linking is almost invisible at login time. The platform needs a while to match sessions against each other. The typical picture is a clean login, a quiet day, and on day two or three reviews landing in a batch across every account that sat on the same address. So “it worked yesterday” confirms nothing about isolation.
List 1. What must differ between profiles
Compare pairwise, not “across the batch in general”: one match is enough to tie two profiles together.
- Canvas and WebGL — separate noise per profile. Two identical hashes read as one machine even when the addresses differ.
- Screen resolution and devicePixelRatio — forty profiles at 1920×1080 with the same pixel density look like one farm.
- Font list — cloning a profile copies it whole. The most underrated marker of the set.
- Audio fingerprint, hardwareConcurrency, deviceMemory — these come from the profile template, not from your hardware, and changing them is a deliberate step.
- User-Agent down to the minor build number — one identical build across the batch stands out exactly as much as one identical Canvas.
- Storage — own profile folder, own cookies, own localStorage, own cache. A shared downloads folder links profiles no worse than a fingerprint does.
- The password you set after purchase — if the whole batch moves onto passwords built from one template, you are linking the accounts on your own side.
None of this can be assembled by hand in a normal browser: it serves one fingerprint to every window, and its profiles share both storage and history. What you need is a browser that keeps a profile as a separate machine, with its own fingerprint, its own storage and its own channel. We work in AdsPower: a new user is given two free profiles there, and that is enough to run the list on a couple of accounts and see where your setup diverges. After that it is only a question of how many profiles the batch volume needs.
List 2. What must match inside one profile
Here it is the other way round: a mismatch inside the profile is itself the signal. Check it against the product description.
- Time zone — from the channel address, not from yours. Verify it in the profile console with new Date().getTimezoneOffset().
- Interface language and Accept-Language — from the batch country. A Cyrillic interface language sitting on an address in Brazil shows up without any analysis.
- Platform — batches in IAM, IGAM and INSTAMEN format lived in the mobile API, and a desktop User-Agent on them contradicts the account history.
- Browser geolocation — set to follow the channel address. Blocking geolocation outright is a mismatch too: ordinary devices do not block it.
- navigator platform and architecture — a Windows profile carrying a mobile User-Agent falls apart at the first script check.
- WebRTC — substituted with the channel address. Once the real address leaks, time zone and language stop mattering.
List 3. The channel: criteria instead of brand names
The name of the service decides nothing here. Four properties do.
- Type — mobile or residential. A datacenter address causes more first-login refusals than every other reason put together.
- Country — from the batch country, not from your convenience.
- Stickiness — the address holds for at least the whole session. Rotation mid-session reads as moving to another country within a minute.
- Exclusivity — one profile per address. A pool spread over the batch is the same shared address, only delayed.
Stickiness takes ten minutes to verify: open an address-lookup service inside the profile, leave the profile running, then refresh the page. The address and the city must not change. If they do, that channel is unfit for a first login however fast it is.
List 4. The run-through before the first login
Order matters: every step checks what the next one would break.
- 1. Start the profile empty, with no platform open. Open an address-lookup service and compare country, city and time zone against the product description. A time-zone mismatch is a stop; do not go further.
- 2. On the same service check for WebRTC and DNS leaks. Only the channel address may be visible.
- 3. Read the delivery string. login:pass|cookie means the session ships with it; login:pass:2fa_code|cookie adds a one-time code generator; IAM, IGAM and INSTAMEN are software strings and are not pasted into a browser by hand at all.
- 4. If cookies ship with the batch, convert them to Cookie-Editor form and import them into the profile before you open the platform. The string can be rebuilt in the format converter, which computes everything locally in the browser.
- 5. Open the platform. With a live session the feed opens straight away and no sign-in form appears. If the form appears anyway the session has expired: do not type the login over it, clear the profile storage first and only then sign in normally.
- 6. The first fifteen minutes are for reading the feed only. No follows, no messages, no avatar change — that is the single most common cause of a day-two review.
- 7. Close the profile properly instead of killing the process from the task manager. Cookies are written out on exit, and a killed process leaves you without the fresh session.
List 5. What links profiles most often
Four mistakes that keep coming up in buyer correspondence.
- Cloning a profile. The copy inherits fonts, Canvas and part of the storage. Build a fresh profile per account instead of duplicating a ready one.
- Logging in as a batch. Forty first logins in ten minutes is not how forty different people behave. Keep at least a few minutes between them and do not walk the whole batch through within one hour.
- One mailbox for several accounts. The email:emailpass format ships its own address per account; there is no reason to collapse them into one shared mailbox.
- Checking the fingerprint in the wrong window. Opening a lookup service in the ordinary browser, seeing the home address and deciding the channel is dead. The check is done from inside the profile or it means nothing.
How many profiles to keep on one machine
The limit is memory and address count, not the processor. A running profile is a separate browser instance at 300–600 MB of RAM each; on 16 GB you can realistically keep 15–20 open at once, beyond that swapping starts and profiles answer with a lag. You rarely need that many at once anyway: there can be a hundred profiles with five of them running. What has to be counted is addresses — you need exactly as many as you have accounts in work.
If the list passes and the login still fails
When all five lists show no mismatch and the credentials are still rejected, the environment is out of the picture — the account is invalid. Instara covers that case with replacement of invalid accounts within 30 minutes, and the sooner you write, the easier it is to confirm the state of the account at acceptance. Putting the case aside for a week and coming back to it does not work: over a week the account changes under whoever was using it.
The order in one line
Channel, then time zone and language, then fingerprint, then delivery format, and only then the first login. A mismatch at any step is cheaper to catch before the login than to unpick after a review. Accounts whose registration platform and delivery format are stated in the description are collected in the antidetect category; current stock per batch is visible in the catalog.