Zum Inhalt springen

Diese Seite gibt es noch nicht in Ihrer Sprache. Sie lesen den englischen Text.

Platforms

Why Facebook links your accounts: seven signals

Two of your accounts live in separate profiles, each behind its own proxy, and the platform still paired them? It adds up small matches that strangers never share. Below are all seven signals and a way to check your own.

Das ARMANOS-Team8 minUpdated

In short

Matches decide, not names. A platform adds up the exit, clock, language, screen, graphics card and link tags.

A separate profile gives each account its own. Its own exit, its own clock and languages from the exit country, its own graphics card.

The check takes an evening. Six signals show in the developer console, and the seventh is confirmed by the proxy check.

Matches decide this, not names

A platform does not look for one person behind two names. It collects the small things your browser hands over, then watches for two columns sitting too close.

Seven of those small things are named below. The platform takes the first three itself: the handshake between the apps, the logging inside the page, and the counter on other sites. The other four arrive from your side.

The handshake between Facebook and Instagram

Facebook and Instagram belong to one company and pass a user identifier between themselves directly. The exchange runs on a plain page load, with no click of yours and no login form.

One request leaves Facebook, another comes back from Instagram, and each carries the neighbouring app's identifier.

Open both in one profile and you hand them a finished pair of accounts.

  1. 1

    You open the page

    Neither a login nor a click is needed for the exchange.

  2. 2

    Facebook calls its neighbour

    The address facebook.com/ig_xsite_user_ carries the identifier outward.

  3. 3

    Instagram answers in kind

    The address instagram.com/accounts/xuserid names the same person.

The platform's own logging inside the page

Besides that handshake, Meta logs inside the page what you opened, how long you looked, how far you scrolled.

Those requests go to the address you came to, so they look nothing like an outside counter.

An ordinary domain blocker lets them through. Only a rule written against the request address closes them, and a profile on the Social media scenario carries those rules.

Platform and its own requestsAddresses under a rule
Facebook and Instagram11
X6
Pinterest4
In this set altogether21

A rule works only on its own addresses

An address piece like /ajax/bz turns up on other sites too, and cut everywhere it would break unrelated pages.

So the social set's rules are locked to the platforms' own addresses: Facebook and Instagram have two names each, their own and their image store, and five more names belong to X and Pinterest.

On somebody else's site the same piece goes through as usual. On its own platform it is cut, and the platform loses a report rather than a page.

A pixel that waits on other sites

The second layer of record keeping lives off the platform. A shop, a blog or a landing page puts the counter there, and it reports your visit before you click anything.

That counter recognises a browser by the same small things, so it pairs your two profiles just as easily.

Below is the social counter list that comes with the Social media scenario, laid out by network.

Whose counter waits outsideAddresses on the list
Meta6
TikTok13
X5
Pinterest3
Other networks alongside6

One exit address across several accounts

A platform compares the exit address first, and that comparison costs it least. Two profiles on one address look like two tabs of one person, however far apart their fingerprints sit.

A datacentre address is known by whoever owns the range, and Meta has known those ranges for years.

A home or mobile address costs more, and it does not label your profile in advance.

Clock and language against the exit country

A page reads your timezone and your browser language list without asking. When a proxy takes you out through Brazil while the clock says Moscow, a platform sees someone hiding.

The zone and the language set have to follow the exit country, not the machine on your desk.

In the app they come from a table of countries and land in the profile once the proxy country is known.

How ARMANOS finds the exit country

Timezone and languages come from the exit country, and the country has to be learned first. The profile asks up to four independent sources in turn, through its own proxy and over a secure connection.

If none of the four answers, the profile still opens and a warning appears on screen. The country is never guessed.

A window wider than the claimed screen

Your browser tells a page the screen size and the window size, and the page reads both in one line. A window wider than the claimed screen describes a machine that does not exist.

On a large monitor a maximised window often does not fit the screen a profile declares.

The wider the monitor, the more often it happens, so ARMANOS keeps the window inside the declared screen.

The GPU disagrees with the architecture

A site asks the browser for the graphics card name and, separately, for the processor architecture. Each answer alone looks ordinary, and together they describe a machine nobody ever built.

Here is such a pair: the name Apple M1 next to an x86 architecture.

ARMANOS compares the graphics card name with the architecture and keeps them consistent. A real Mac with that card never reports x86.

What ARMANOS does for each signal

ARMANOS gives every account a separate profile: its own folder, its own device and its own way out to the network.

The profile takes its clock and languages from the exit country and fits the window to the screen it declares.

It strips tracking tags from links on click-through and keeps the graphics card and the architecture consistent.

That closes the exit, clock, language, screen, graphics card and tags. What remains is behaviour: the Academy lesson "How to run several accounts with confidence" covers it.

What to check on your own profiles

Six of the seven signals are visible in a browser console in one evening, with nothing to install: the network list is in that same console. The seventh is the exit address, and the proxy check confirms it.

Walk your profiles in pairs: those meant to stay strangers have to differ at least in exit address, clock and screen.

A matching pair is the one a platform writes its rule for.

  1. 1

    Compare the exit address

    Two profiles meant to stay strangers leave through different addresses.

  2. 2

    Compare clock and languages

    The zone and the language set follow the country you exit through.

  3. 3

    Compare screen and window

    A window is never wider than the screen a profile claims.

  4. 4

    Watch the network list

    The first load shows whether the identifier exchange goes out.

Common questions

I already run different proxies, is that not enough?
The address is one signal out of seven. Two profiles on different addresses still pair up by clock, by screen or by the exchange between the apps.
If I never open Instagram, is there no link?
The exchange runs on a page load, not on a login. A tab of the neighbouring app open in the same profile is enough.
Does private browsing help?
It forgets cookies when the window closes and touches neither the exit address, nor the clock, nor the screen, nor the graphics card. Four signals out of seven stay where they were.
Will an ad blocker close these requests?
Domain lists close counters on other people's sites. They leave the platform's own requests alone: those go to the address you came to.
How is this different from changing the user agent?
The user agent string is one field, and there are seven signals. Swapping one field more often creates a fresh contradiction than closes an old one.
How many accounts can I run from one computer?
The limit comes from matches between profiles, not from the computer. Once address, clock, screen and card differ, the question moves from how many profiles to how unlike they are.

See what your browser tells about you

The free check reads 12 values in the window and sends nothing anywhere.