Google Ads antidetect browser for multiple accounts

Organize profiles by client and Google identity

Make a list of clients, Google login identities, ad accounts, and responsible members. Give identities that need separate sign-ins their own profiles. If one identity can access several business accounts, record that relationship in the task list. A profile named after a client does not prove that the corresponding ad account is selected in the browser.

Choose New profile in Profiles and select the Google platform preset. Save the fingerprint generated from the chosen OS template. Use a client or project group and a name that describes the purpose, such as daily campaign work or report review. Each profile has its own browser data directory and saved cookies. The fingerprint feature explains this isolation.

Set the proxy and browser location

Bind each profile to its intended entry in the proxy library. HTTP, HTTPS, and SOCKS5 connections are supported. Check connectivity first, then compare the detected exit IP and location with your records. Keep the provider connection details and the detected exit information distinguishable: they describe different parts of the connection.

Time zone, Language, and Location can follow the exit IP. WebRTC can use Proxy only or Disabled. These are browser settings; they do not update the business information or settings inside a Google Ads account. When a proxy needs changing, check the replacement and save the profile configuration before the next session. Follow the proxy setup guide for the individual controls.

Verify the ad account before making changes

After opening a profile and signing in, check the Google identity, current ad account, and project shown on the page. You can save the platform account, password, and 2FA secret in Account & 2FA and fill those details when signing in. Similar account names make the comparison with your client list particularly useful.

Finish or save the current edit before moving to another client window. Separate profiles retain separate sessions, but they do not evaluate whether the account selected inside Google Ads matches the task you were given. Before a submission, inspect both the target account and the fields that will be saved.

• Confirm that the browser profile belongs to this client and that the website shows the expected Google identity.
• Check the ad account selected in the business page before reading results or changing settings.
• Review the date range, page options, and entered values for this task, then record the result for the next operator.

Give operators and reviewers profile access

Administrators can create members, set roles, and assign profiles by client or project in the web console. Give campaign operators and reviewers the profile scope they need. If a reviewer should only view advertising data, the permission to do that must also be configured for the Google identity used on the platform. Profile access alone does not establish Google Ads permissions.

The client shows occupancy information while another member uses a profile. A lease restricts the same profile from running simultaneously on different devices. Have the operator save the current changes, close the profile, and finish synchronization before the reviewer opens it. The team collaboration page covers this assignment and handoff model.

Resume the original profile on another computer

When cloud sync is enabled, cookies upload as they change and tab addresses can sync. Selected local storage, including LocalStorage and IndexedDB, is packaged and uploaded when the profile closes. Close it on the original computer and wait for the upload to finish before opening it elsewhere under the same product account.

On the next computer, check the restored login state and proxy exit, then verify the current ad account. Windows and Apple silicon Mac clients can use the same product account. Sync restores browser data; a website session that has expired or requires verification still needs the login steps shown by Google. See cloud sync for what is transferred and when.

Hand off a client project and keep a backup

Within a team, keep the original profile and adjust who can use it. Write a handoff note covering the client, Google identity, ad account, proxy, and unfinished work. For another product account or team, a share code can include selected login state, passwords, 2FA details, and proxy data, subject to the available features and permissions.

The recipient claims a copy. Check the identity and business account in that copy, then agree who will continue using which profile. Revoking a share code prevents additional claims; it does not remove a copy that has already been claimed. The profile sharing guide explains the transfer options.

For a file backup, finish synchronization before exporting a .fgbx file and review the selected contents. At the end of a project, retain any required backup, adjust profile access, and review unused share codes. Handle Google business permissions separately from access to the browser profile. Follow Google platform rules.

FAQ