Antidetect browsers and Qubix Connector

Qubix collects Facebook data through the eyes of your profiles in an antidetect browser — so the platform sees ad accounts, campaigns and pages the way the account itself does, not as a request from the outside. The link between the antidetect browser and Qubix is the Qubix Connector extension.

The extension is installed once. After that it connects to your antidetect on its own, pulls the list of profiles together with their proxies and keeps in touch with Qubix — you usually don't have to enter anything.

How Qubix differs from ordinary parsers

• Accounts live longer and get banned less often — collection runs from inside your profile, without third-party APIs that Facebook reacts to with bans.
• Your data stays with you — Qubix runs on-premise: no need to hand over keys or connect someone else's apps to your Facebook.
• No need to keep profiles open — collection runs on its own, on a schedule, even when the browser is closed.
• The team is on autopilot — the administrator sets it up once, buyers don't have to do anything.
• 6 antidetect browsers out of the box — AdsPower, Dolphin Anty, Multilogin, GoLogin, Incogniton, Vision.

Why it's safer for the account

Ordinary parsers reach Facebook from the outside — through third-party APIs and access tokens. Facebook notices such requests first, and accounts get banned for it. Middleman services go even further: they ask you to hand over keys or connect their app to your Facebook — and your stats and access end up on someone else's side.

Qubix doesn't do that. To Facebook it looks like the normal activity of your account, not a third-party program — no external requests, access keys or foreign apps. Access and stats go nowhere: everything stays only with you, on your infrastructure.

You don't have to keep the profile open

You don't have to keep the antidetect profile running all the time. Once Connector has passed the session, Qubix keeps collecting data on its own — on a schedule, even when the profile and the browser are closed. The only thing that matters is that the profile stays logged in to Facebook; you don't have to keep it open.

This is especially handy when there are many profiles: a buyer can have dozens — there's no need to keep them all open just for collection, Qubix goes through them itself.

You'll rarely need to step in — for example, if the profile logged out of Facebook and the session needs refreshing. Then Qubix warns you in Telegram: both in the shared collection-errors channel and the responsible buyer personally. You just open the profile, sign in again — and collection continues.

So Connector sees your browser

Connector talks to the antidetect browser's local API on a local port. For most browsers Connector reads the list of profiles and their proxies right there; for some (Dolphin Anty, GoLogin) the local port only confirms the browser is running, and the profile list comes from the provider's cloud API. Either way, the antidetect's local API must be enabled.

In most browsers it's on by default. If the extension reports that the browser isn't found or its API isn't responding, open the antidetect settings and enable the local API (the option may be called Local API, API or Local API Server), so the browser listens on its local address and port. Each browser has its own port — see the table below.

If several antidetects are running on the computer at once, you'll need to pick the right one in the extension window.

The Connector window shows the connection stage: search → API check → profile → server check → ✓ Connected.

Supported browsers

Browser	Local API (port)	API key needed	Key format
AdsPower	50325	Optional	Bearer token
Dolphin Anty	3001	Yes	Bearer token
Multilogin	45001	Yes	email:password
GoLogin	36912	Yes	Bearer token
Incogniton	35000	No	—
Vision	3030	Yes	token
Donut	10108	— (in development)	—

Tip

The port in the table is the address of the browser's local API. If Connector doesn't connect, check that the local API is enabled in the antidetect settings and listening on that port.

Working without a key

Two browsers need no API key at all: Incogniton (its local API has no authorization — it returns full profiles, proxies included) and AdsPower (it gives the current profile's identifier from its launch URL — but only the identifier; the proxy, name and group are read only with a key). For the rest, a key is required.

API key: when it's needed and where to get it

• Without a key Connector sees only the current open profile (and for most browsers — not even that). This is enough if the profile is already known to Qubix (see the Fast path section).
• With a key the extension pulls all profiles from the antidetect at once — with proxies, names, groups and IP country — and sends them to Qubix.

The key is taken from the antidetect browser's own dashboard (the API / settings section) and entered in the extension window via the Admin Mode toggle: open the popup → Admin Mode → paste the key into the API key field (with your browser's name, e.g. «API key AdsPower»). The key format for each browser is in the table above.

Multilogin

Multilogin uses an email:password pair instead of a token. Additionally, in the Mimic profile settings enable Port scan protection → Custom and add the allowed ports 5030,45001 — otherwise Connector won't see your profiles.

Fast path: the admin sets it up once

The most convenient scenario is when there's no need to enter a key for each buyer at all.

If the administrator connects, once, an antidetect browser that holds the team's profiles and enters an API key, Connector reads the whole list of profiles (with proxies) and keeps it up to date in Qubix. After that the profiles are already registered on the server.

Now any buyer, opening their profile, lands on the fast path: Qubix already knows the profile and its proxy, the extension shows a compact ✓ Connected — nothing to enter. Neither a key nor a proxy.

Recommended deployment pattern

The fully automatic path — where the buyer enters nothing — works on the antidetects that need no API key: AdsPower and Incogniton. For a team we recommend AdsPower — it's the most common and lets you push the extension to all profiles centrally. With the others (Dolphin, Multilogin, GoLogin, Vision) you enter a key once in each profile.

On AdsPower:

1. The administrator connects AdsPower and enters an API key — under an account where all the team's profiles are visible. Connector reads the whole list of profiles with proxies and registers them in Qubix.
2. The extension is distributed centrally — AdsPower lets you add it to all the team's profiles at once, no need to install it for each buyer manually.
3. Buyers connect on their own — the profile is already known to Qubix, Connector shows ✓ Connected. An open, logged-in profile is enough.

Bottom line

AdsPower + the administrator's key = the whole team works out of the box, with no keys or proxies on the buyers' side.

What the buyer has to enter manually

Manual input is needed in only three cases.

1. The proxy isn't set

If Qubix doesn't know the profile's proxy yet, the extension shows «proxy not set». You can set the proxy like this:

• in the extension window (buyer) — the string socks5://user:pass@host:port → Save;
• in the antidetect profile settings (buyer) — set the proxy and restart the profile, Connector will pick it up itself;
• in Qubix, Settings → Browsers (administrator) — the profile card → Proxy → Edit (more — Browsers). Available after the profile has appeared in the list (the extension has reported at least once); a buyer may not see a fresh profile of their own — attribution goes by campaigns.

Once the proxy is set in any of these ways, the profile switches to the fast path and you no longer need to enter it in the extension.

2. The API key

If the profile isn't known to the server yet and the antidetect requires a key to access its profiles. Entered via Admin Mode (see the API key section above).

3. Localhost is blocked

If the profile's proxy intercepts local addresses too, Connector can't read the profile identifier. A one-time fix:

1. In the antidetect profile settings switch the proxy to No proxy and save.
2. Restart the profile — Connector reads and remembers the identifier.
3. Restore the proxy in the profile settings and restart again.

After that, all that's left in the extension window is to type the proxy string and press Save.

What the extension collects

Connector passes the antidetect profile's data to Qubix: the identifier, name, group, proxy string, IP and country. The profile identifier is determined automatically — you can't type it manually (the risk of a typo is too high). If the antidetect couldn't be determined or has no key, Connector still doesn't leave you stuck: it creates an identifier itself and asks you to set a proxy — after Save, collection begins. The extension uses the Facebook session already open in the profile — no separate login to Qubix is needed.

Connecting: in short

1. Open Settings → Browsers and click Download extension.
2. Install the extension into the right antidetect browser profile.
3. Make sure the profile is logged in to Facebook.
4. Open the Connector window and wait for ✓ Connected. If needed, enter the key or proxy as prompted.

What's next

• Browsers — the list of profiles, statuses and parsing management.
• FB parser — how Facebook data collection works.
• Connect the FB parser — a step-by-step scenario.