Managing Multiple Facebook Ad Accounts

Advertising agencies routinely run campaigns for many clients on Meta's platforms. The accounts are legitimate, the structure is documented, and the trouble usually comes from infrastructure that makes unrelated client accounts look connected.

This covers the account-health side, not campaign strategy.

Structure before proxies

Meta provides an intended structure for agencies, and using it reduces risk before any network change is considered.

Business Manager as the boundary. Each client's assets live in their own Business Manager, owned by the client and shared with the agency. Accounts are separated by design rather than by improvisation.

User access, not credential sharing. Add people to the client's Business Manager with the appropriate role instead of logging into a shared account. Shared passwords are the single biggest source of both security incidents and linkage.

Payment methods per client. A card or bank instrument must belong to the client account it funds. Reusing one instrument across several ad accounts is a hard linkage signal and a common cause of account groups being actioned together.

Where an agency does hold accounts in its own Business Manager, keep a written record of which client each one serves. That record is what you produce during a review.

What triggers restrictions

Meta's enforcement runs on both policy and pattern. The patterns that cause trouble for legitimate agencies:

• Shared payment instruments across accounts that are not otherwise related.
• One address for many accounts. A group of ad accounts transacted from a single connection looks like a farm, whatever the accounts are for.
• Address jumping. An account with a stable six-month history suddenly transacting from another country.
• Datacenter ranges. Hosting addresses carry a reputation penalty, described in Why Residential IPs Are Trusted.
• Behavioural clustering. Several accounts edited or created within a short window, in sequence.
• Content policy violations in the ads themselves, which is a separate matter from infrastructure.

Most infrastructure causes disappear once each client's account has its own stable address and its own payment instrument.

Address strategy for agency work

Two requirements: stability and locality.

Stability. An ad account that operates from a consistent address builds a reputation with the platform's risk systems. Changing it, even to another clean address, resets that. Use a static address for accounts that transact regularly.

Locality. The address should be in the market the account targets or the client operates in. A Polish client's account running from a US range is a mismatch that shows up in every transaction.

The distinction between the address an account uses to transact and the addresses used to verify how ads render is important. Verification traffic should not come from the account's own address, and the reason is covered in Ad Verification with Proxies.

Team practice

• Named seats, not shared logins. Every action in a client account should be attributable to a person.
• Record the address binding per account, with the country and the date it was assigned.
• Do not let operators rebind addresses to work around a slow session. A slow session is not worth resetting a reputation.
• Separate the account profile from the analyst's personal browser. Sessions that mix personal and client activity create exactly the association you are trying to avoid.
• Keep an escalation path. When an account is restricted, the appeal goes through Meta's process, and the structural fix comes before the appeal where possible.

Verification, separately

Agency ad work needs two different kinds of checks, and they use different infrastructure.

Account health. Confirm the account transacts from the intended, stable address. This is a one-time setup check and an occasional audit, using the Proxy Checker and IP Lookup.

Ad delivery. Confirm the creative renders in the intended country, on the intended device, in the intended placement. That is a read-only activity, it should rotate addresses, and it should never touch the account's own address. The method is covered in Ad Verification with Proxies and, for the market-targeted case, in Geo-Targeted SERP Testing.

Where proxies fit

Proxies do not make a policy problem go away. They remove the accidental association between accounts that should not be related, and they keep each account on the stable, local address its risk history is attached to.

For the workflow, see Multi-Accounting and Ad Verification. For the products, see Residential, Mobile and ISP proxies.