Facebook antidetect browser for multiple accounts

Map login identities to clients and ad accounts

Before creating profiles, list the Facebook login identity, client or project, business management area, ad accounts, and responsible team member. Record the Business Manager (BM) and ad accounts that each login is authorized to manage. A business name and a login identity are different parts of that record, even when your team uses the same client name for both.

Create separate profiles for identities that need independent sign-ins. Use names and groups to distinguish daily advertising work from business administration when your workflow requires that separation. The name helps you find a window, but it cannot confirm which ad account is currently selected on the website. Read how browser profile isolation stores the underlying browser data.

Create a Facebook browser profile

In Profiles, choose New profile and select the Facebook platform preset. Choose an OS template and save the generated fingerprint with the profile. The browser engine uses that saved configuration, and the profile has its own data directory and cookies. Configure and check one login before repeating the process for the remaining identities.

Under Account & 2FA, you can store the platform account, password, and 2FA secret. The password manager can also fill saved website credentials. After signing in, compare the identity shown on Facebook with your account list. If they differ, check the session and saved credentials before editing business information.

• Name the profile with a client or project and its purpose so similar accounts remain distinguishable.
• Keep the BM and ad account mapping in your operations checklist alongside the actual login identity.
• Return to the saved profile for later work with the same account and retain its fingerprint configuration.

Check the proxy and exit IP

Bind each profile to its intended proxy and manage the connections in the proxy library. HTTP, HTTPS, and SOCKS5 are supported. Run a connection check and inspect the detected exit IP and location. A proxy label identifies a saved connection; it is not evidence of the current exit. Compare the result with the network assignment in your account list.

Time zone, Language, and Location can use Follow IP. WebRTC supports Proxy only or Disabled. Review these settings when changing a proxy. If an advertising page fails, distinguish a connection problem from a page loading issue or a response from Facebook before changing the configuration. The proxy setup guide covers the setup sequence.

Assign profiles to the advertising team

An administrator can create members, set roles, and assign profile access in the web console. Organize profiles into groups by client or project, then give each person the scope needed for their work. At the start of a task, the member should confirm that the assigned profile belongs to the expected login identity and client.

Profile access controls which profiles a member can use in WGBrowser. Facebook determines what the signed-in identity can view or change inside its business pages. Set and review those permissions separately. The team management guide explains profile assignment and how the client shows profiles that are in use.

Take turns reviewing and editing

When a profile is open, other members can see who is using it. A lease restricts the same profile from running on multiple devices at the same time. Have the current operator finish and save their work, close the profile, and complete synchronization before a reviewer takes over.

Record what was checked, what was changed, and what remains unresolved. When switching clients, save the current task and check the identity and ad account in the next window. Before submitting a significant edit, verify the target account, fields, and values. These are team review steps; the browser does not decide whether the selected Facebook business is the correct one for your task.

Move work to another computer or team

With cloud sync enabled, cookies sync as they change. Selected LocalStorage and IndexedDB data upload after the profile closes. Before changing computers, close the profile and wait for synchronization to finish. Sign in to the same product account on the next computer, open the original profile, and check the Facebook identity, exit IP, and business page. See cloud sync for the data scope.

For a handoff to another product account or team, create a share code when your permissions and plan allow it. Choose whether to include login state, proxy details, and passwords. Claiming creates a profile copy, so agree which copy will be used afterward. Revoking the code stops later claims but does not remove copies already claimed. Follow Facebook rules and work within the permissions you have been granted.

FAQ