Linking is not one signal
Platforms do not decide that two accounts belong to the same operator from a single value. They build a graph. Nodes are accounts, devices, addresses, payment instruments, phone numbers, domains, business entities; edges are anything two nodes have in common. When a node in that graph is banned, the edges decide what goes with it.
This matters because it changes what an anti-detect browser can and cannot do for you. It addresses one family of edges — the device and browser ones — comprehensively. It addresses none of the others at all.
The uncomfortable corollary is that people frequently buy the right tool for the wrong failure. If the link was a shared card, a perfect fingerprint changes nothing.
The edges a browser can cut
These are the ones per-profile isolation genuinely solves.
Hardware and rendering fingerprints
Canvas hash, WebGL vendor and renderer, AudioContext hash, installed fonts, screen dimensions, colour depth, CPU cores, device memory, timezone, language, platform. Meta alone is documented as collecting over fifty such signals. Two accounts sharing a canvas hash and a font list are, from the platform's perspective, two accounts on one computer.
Cookies and local storage
Cookies are the obvious one and the least interesting, because everyone clears them. The parts people forget: localStorage, IndexedDB, service worker caches, and the HTTP cache itself — an ETag served to one account and revalidated by another is a link. Anything short of a genuinely separate storage partition leaks something.
IP address
Covered at length in the proxy article. Worth repeating that the failure is usually not "datacenter IP" but "same IP as the account that was banned last month".
The edges it cannot
This is the longer list, and the one worth reading twice.
Payment instruments
The strongest link of all, and the least avoidable. A card number, a PayPal account, a bank account, even a billing address reused across accounts ties them together permanently. Meta explicitly bans accounts linked to previously-banned ones through a shared payment method. No browser setting is relevant.
Business entities and asset sharing
Business Manager relationships, shared pixels, shared catalogues, shared page assets, admin overlap. On Meta these are first-class objects in the graph, not inferences. Adding a banned entity's asset to a clean account imports the ban.
Phone numbers and recovery addresses
A phone number used for verification on two accounts links them. So does a recovery email — including one that merely forwards to an address used elsewhere.
Domains and redirects
The landing page is part of the ad. A domain flagged on one account is flagged everywhere. Redirect chains, cloaking infrastructure, shared hosting IPs and shared analytics identifiers are all edges. Ad review in 2026 is multimodal — text, image, video, audio and landing page analysed together, before the first impression — so the destination is examined whether or not anyone clicks.
Behavioural timing
The one people underestimate. Twenty accounts that log in within the same ninety seconds, from twenty different IPs and twenty different fingerprints, have announced themselves through their schedule. Real people do not coordinate. Neither should your profiles.
What "behavioural device lineage" means in practice
Enforcement language in 2026 leans on phrases like continuous behavioural assessment and device lineage. Stripped of marketing, it describes three things that are worth taking literally.
Continuous, not at login. Fingerprint and behaviour are sampled throughout a session, not checked once at the door. Passing a check at login means nothing about the next hour.
Historical, not instantaneous. The comparison is against the account's own past. An account that has always run from one Milan ISP address at Italian office hours, suddenly appearing from a São Paulo mobile IP at 04:00, has changed in a way that is visible without any cross-account data at all. This is why a consistent profile beats a clean one: the platform is comparing you to yourself.
Retroactive. Graphs are re-evaluated. An edge discovered today can be applied to accounts that were fine yesterday, which is why bans arrive in waves and why an account that ran for months can go without anything changing on your side.
Operational rules that matter more than settings
Ordered roughly by how many accounts each one saves:
- One payment method per account. Never reuse a card, a PayPal, or a billing address. This single rule prevents more linked bans than every browser setting combined.
- One proxy per profile, held long term. Static ISP or a long sticky session. Do not rotate inside an identity — see the proxy article for why.
- Never mix assets. No shared pixels, catalogues, pages or domains between account clusters. Treat each cluster as a company that does not know the others exist.
- Stagger everything. Different login times, different session lengths, different days off. Add real variance, not a random jitter of thirty seconds.
- Age accounts before they matter. A profile created and immediately used to run spend behaves like nothing on the platform. Ordinary usage first — see what warmup does and does not do.
- Verify each profile once. Run the consistency checklist and a WebRTC test before the profile touches anything valuable. Five minutes, once.
- Keep clusters small. The graph is transitive. A cluster of five loses five accounts when one edge is found; a cluster of fifty loses fifty.
An honest scope statement
It is worth being direct about what a tool in this category does, including ours.
An anti-detect browser makes two accounts look like two computers. That is a real and necessary thing, and it is not achievable by clearing cookies or opening a second Chrome profile — the fingerprint follows you. If your accounts are being linked by device signals, this is the fix.
It does not make two accounts look like two people. It cannot separate your payment methods, stagger your schedule, diversify your landing pages, or stop you adding a burned pixel to a clean account. Those are operational decisions, and they are where most of the losses actually happen.
Anyone telling you a browser alone prevents bans is selling something. The browser removes one category of link. The other categories are your job.