Multi-Account Operations Glossary for Teams (2026)

8 min read

Multi-account vocabulary in 2026 is scattered across forums and blogs, borrowing terms from sports betting, affiliate marketing and e-commerce. Platforms rarely document most of it, so people pick it up informally and hope they've got it right.

This glossary is written for people who manage multiple accounts with legitimate authorization: agencies working in client accounts with explicit permission, QA and testing teams running cross-geography tests, and sellers whose marketplace explicitly approves more than one account.

Critical: this glossary describes legitimate multi-account operations only. Attempting to bypass platform rules, hide account ownership, or evade enforcement actions violates terms of service and usually ends in permanent account loss. Wherever a term touches compliance or platform rules, we explain what platforms actually permit and how to appeal restrictions.

JustBrowser is a multi-account browser for teams — each profile keeps sessions, cookies, and settings isolated so client accounts or test personas don't interfere with one another. The terms below cover operational concepts, not browser technical features.

A

Asset Reuse

Using the same creative, landing page, pixel or product feed across accounts. Between a client's own accounts that's normal. Across unrelated clients it's a data-hygiene problem: one client's pixel firing for another's campaign pollutes both sets of reporting.

Keep tracking assets per client. It makes reporting accurate and permissions easy to revoke.

B

Batch Restriction

A platform acting on many accounts at once. If it happens to a legitimate portfolio, treat it as a review problem. Read the notice, find the policy it cites, and use the official appeal route.

BM (Business Manager)

Facebook's management layer above ad accounts, pages, pixels and team members. "BM" is often shorthand for a company's whole Facebook advertising presence.

The approved way for one person or agency to manage many ad accounts is through Business Manager and its partner-access roles, not by juggling unrelated personal logins. On the browser side, JustBrowser's profile isolation keeps each client's sessions separate, and ClickzProtect deals with bot traffic on the campaigns themselves.

F

Fingerprint Consistency

A browser exposes a bundle of settings: canvas, WebGL, audio, fonts, screen, timezone, navigator. For QA teams and privacy-minded users the useful goal is consistency. A profile whose settings, timezone and proxy location agree with each other gives you a test session whose results you can trust, instead of a muddle of contradictions.

Each layer is separate. The browser handles profile settings, a proxy handles IP location, and your own processes handle payments and access.

G

Gubbing

Restricting an account without closing it. The term comes from UK sports betting, where bookmakers limit stakes rather than close accounts.

It has spread: a seller account under "Account Health" restrictions, or an ad account with a lowered spend cap. Because nothing is formally suspended, it can be hard to appeal. That's one of the more frustrating parts of platform support, and documentation of what triggered the limit is often thin.

K

KYC Verification

Know Your Customer checks: identity documents, proof of address, business registration. Fintech firms, exchanges and ad platforms use them to verify legitimate business and prevent fraud.

Each account must pass its own KYC with authentic, verifiable information for the business entity that actually owns it. A second account is only valid where the platform explicitly permits it, and only for the reason it allows. Submitting false documents, using another person's identity, or misrepresenting ownership violates platform terms and often breaks laws. Expect permanent account closure, and possibly legal consequences.

P

Payout Separation

Maintaining distinct banking and payment details for legitimately separate business entities or authorized client accounts. Standard business practice: each legally distinct entity keeps its own payment records for accurate invoicing, tax filing, and financial reconciliation.

For agencies, each client's account maintains its own banking relationship with the platform — this is standard, transparent, and expected. It's about business organization, not account isolation. Attempting to use separate payouts to hide or obscure account relationships violates platform terms and can end in account reviews and permanent bans.

Profile Portfolio

A set of accounts you're entitled to hold, maintained with consistent processes: documented ownership, one browser profile per client, defined access.

Proxy Rotation vs Sticky Session

Two proxy patterns, each with different appropriate uses.

Rotation: the IP address changes every few minutes or per request. Useful for collecting public data where no login is involved. Poor for account work, since accounts expect consistent login locations and a jumping IP triggers verification challenges.

Sticky session: the same IP is held for hours or days. Appropriate for account work because the account operates from one consistent location, the way a real person uses it from their home or office.

For client work, give each account its own consistent proxy. You can bring your own or buy a proxy plan in the app; the subscription doesn't include proxies. Proxy providers publish their own pricing and terms, so check those directly.

S

Shadowban

A restriction where functionality degrades without explicit notification: content posts but reach drops, or delivery slows. Platforms rarely confirm one formally, which makes diagnosis difficult.

If you suspect one:

  1. Compare performance against your baseline during the same period.
  2. Check the platform's policy and account-quality pages for the restriction reason.
  3. Contact official support with specific performance data.

The only legitimate path is through the platform's official appeal process. Creating new accounts to work around restrictions is prohibited and usually ends in permanent bans, often across every related account.

Sticky Session

See Proxy Rotation vs Sticky Session above.

  • Fingerprint vs Profile: a fingerprint is the technical browser identity. A profile is that identity plus cookies, storage, proxy and credentials. People mix these up constantly.
  • Ban vs Suspension vs Restriction: platforms use these words differently, but roughly, a restriction limits functionality, a suspension is often temporary, and a ban is permanent. Check each platform's own appeal route.
  • Proxy vs VPN: a proxy can be set per profile, while a VPN usually routes everything through one exit. Per-profile isolation needs per-profile proxies.
  • Multi-account browser vs Profile manager: a multi-account browser gives each profile its own internally consistent identity settings. A profile manager stores sessions but may not change them.

Honorable Mentions

Cloaking: showing different content to platforms and users. It's a landing-page technique rather than an account-operations term, and platforms actively penalise it.

Botting: automated account operation. It overlaps with multi-account work but is its own discipline.

What to Remember

Legitimate operations serve real business purposes. Client data stays isolated per client, test environments don't interfere with production, and billing/access stays organized. A multi-account browser handles profile isolation, proper proxies maintain consistent location data, and clear bookkeeping tracks each account's business separately.

Evasion fails and ends in permanent loss. Using multiple accounts to bypass restrictions, submitting false identity documents, hiding true account ownership, or replacing restricted accounts with new ones violates platform terms. The usual result is a permanent ban on every related account, and false documents can bring legal action too. The only legitimate path when a platform restricts an account is its official appeal process — it's slower but it's the only path that holds.

When restricted: contact official platform support with documentation, follow their published appeal process, and wait for their response. That is the only legitimate way forward.

For the browser layer: JustBrowser (custom Chromium engine, 40+ identity parameters, local REST API for testing). For bot traffic on ad campaigns: ClickzProtect (2,000+ bot User-Agent signatures). For monitoring errors and conversions: JustAnalytics (all-in-one observability, with session replay and error tracking).

Frequently Asked Questions

What's the difference between a profile portfolio and a pile of unrelated accounts?

A profile portfolio is a set of accounts you're entitled to hold, such as client accounts an agency manages with permission, each kept in its own isolated browser profile with documented ownership and access. Accounts created in bulk with no clear owner are the opposite, and most platforms' rules prohibit them.

Should every account get its own browser profile?

For agencies and QA teams, yes. One profile per client or test persona keeps cookies, storage and proxy settings apart, so one client's logins and tracking never leak into another's.

What does "gubbing" mean in multi-account operations?

Gubbing is sports betting slang for restricting an account instead of closing it. In wider use it means a restriction with the account still open: lower limits, locked features. The fix is the platform's own appeal route, not a workaround.

Why do operators care about payout separation?

Legitimately separate businesses or clients have separate banking and payment records. Agencies keep each client's payment details in that client's own account, so billing, tax and reconciliation stay clean.


Try JustBrowser

A multi-account browser for teams, built on a custom Chromium engine with native C++ integration, not an extension, and patched on every upstream release. 40+ identity parameters per profile, plus a local REST API and CDP for Playwright, Puppeteer and Selenium. 7-day free trial, card required — then $9.99/month or $99.99/year, unlimited profiles, free team seats.

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

Tags
  • multi-account-browser
  • account-operations
  • team-management
  • web-testing
  • qa-automation
  • buildinpublic
  • saasstudio
  • aiworkforce
  • buildwithclaude

Ready to manage multiple accounts?

Seven days free, then $9.99/month — one plan, everything included.

We'd like to use Google Analytics, a Google service, to understand how our website is used. It sets two cookies in your browser and runs only if you click Accept. You can change your choice at any time with Cookie settings. Cookie Policy

Sign-in cookies and the cookie that remembers this choice are always on; the website needs them to work.

Google Analytics, a Google service, helps us understand how our website is used. It sets two cookies, _ga and _ga_TVZHQ99TZW. It is now onoff in this browser. If your browser sends a Global Privacy Control or Do Not Track signal, it stays off. Cookie Policy