How-to

Managing multiple Facebook ad accounts as a team: keep every client, brand and app apart

The expensive mistake when you run several ad accounts is not a slow launch. It is a default carried over from the last account you worked in, or a colleague who could publish when they should only have built. Both are fixable per account.

Adlio teamPublished 31 August 2026Updated 28 September 20266 min read

The short answer

Keep one written set of defaults per ad account and launch only from it. The five settings that leak are the pixel, the Page and Instagram identity, the default copy and URL, the naming pattern and UTMs, and the EU DSA entity. They leak through duplication, a wrong pick in a dropdown, or copy-paste from the last account. Once more than one person launches, add a team layer per account: who has access, who may publish, and who signs off. Land every batch paused, so the check before launch catches what slipped through.

This is the hub for running Meta ads across many accounts with a team, whether the accounts belong to clients (an agency) or to your own apps, brands and markets (an in-house growth team). The guides it links to go deeper on each part.

The five things that leak

When one person launches for several accounts, the same five settings cause almost every cross-account incident:

Setting	How it leaks	What it costs
Pixel and conversion event	A new ad set inherits the last pixel you used, or a duplicated ad set carries the old one	A week of spend optimised toward the wrong site's events
Facebook Page and Instagram identity	Wrong Page picked in the identity dropdown, especially with similar names	Ads running under another brand; usually caught fast, always embarrassing
Default copy and destination URL	Copy pasted from a template doc, URL left from the previous ad	Wrong landing page, wrong offer, sometimes another client's product
Naming pattern and UTMs	One convention typed from memory across accounts	Reporting rows that mix accounts or cannot be split
EU advertiser identity (DSA beneficiary and payer)	Filled from memory or left as the last legal entity used	Delivery blocked in the EU, or the wrong company named as beneficiary

None of these show in the campaign list. You find them by opening the ad, or in the report.

Why it happens

Ads Manager stores structure, not defaults. It knows which pixels an account may use. It does not know which one this account's ads should use by default. Every new ad set starts from Meta's defaults or from whatever you duplicated. At 22:00 with six tabs open, "whatever you duplicated" is the last thing you touched, in whichever account that was.

So the fix is not more attention. It is moving the defaults out of your head and into something scoped per account.

The per-account setup

Do this once per ad account. In a shared document if you have no tool, in the tool if you have one:

Identity: the exact Facebook Page and Instagram account for this account. Write the IDs, not just the names.
Pixel and default conversion event.
Default copy: primary text, headline, description, call to action. The approved version, not the draft.
Destination URL and UTM template. See UTM parameters for Meta ads.
Naming pattern for campaigns, ad sets and ads, with the client or brand code as the first field. See the naming convention guide.
Advantage+ enhancement toggles per creative type. A brand-strict client and a performance-only app want different defaults. See how to turn off enhancements.
DSA beneficiary and payer for any account whose ads can show in the EU. See EU DSA fields on Meta ads.

Then two working rules:

One account per session. Close the other tabs. If your tool has an account switcher, switch. Do not multitask.
Every batch lands paused and gets the sample check. The QA checklist exists for exactly the five leaks above. Checks 1, 2, 4, 5 and 9 catch them.

The team layer: who can do what, in which account

The five leaks are about settings. The moment a second person launches, the risk becomes people: someone in the wrong account, someone publishing what should have waited, or nobody able to say who changed an ad. Each has its own guide:

Question	Guide
How does an agency get access to a new client's ad account?	Partner access, step by step
How do I add a colleague without sharing my Facebook login?	Give a colleague access to your ad accounts
Who can build ads, who can publish them, who can spend?	Meta ad account roles for agencies
How does a client or a lead sign off before anything goes live?	Client approval for Meta ads
Who changed this ad, and when?	Ads Manager activity history
Whose company goes in the EU DSA fields?	DSA beneficiary and payer

Three facts from Meta shape all of it (checked on 28 September 2026):

Limits. "One person can manage up to 25 ad accounts." and "An ad account can be assigned to up to 25 people."
No build-only role. Of Meta's three ad account roles, Admin and Advertiser can create and edit ads, and Analyst can only view. There is no role that builds ads without being able to publish them.
One native publish gate. Peer approval lets the business portfolio that owns an ad account require that "ads must be reviewed by a trusted user of the ad account before they can be published". It is set up by someone with full control of that portfolio, so for a client account it is the client's switch, not the agency's.

Our default on top of that: give every person their own access to only the accounts they work in, keep full control and billing with the account owner, land every batch paused, and have one named person per account switch ads on.

Agencies and in-house teams: same problem, different accounts

An agency runs one ad account per client, in the client's business portfolio. An in-house growth team runs one ad account per app, brand or market, in its own portfolio. The leaks and the team layer are the same. What differs is who owns the account: an agency asks the client for access and lives with the client's settings for approval and spending limits; an in-house team decides those itself. The agency view is on the agency page, the in-house view on the page for in-house teams.

What this looks like in Adlio

We are Adlio, so weigh this section accordingly. Adlio stores all seven items per ad account. Switch accounts in the app and every default switches with it. A launch only ever reads the settings of the account you are launching into. There is no global default that could bleed across, and no "remember last used" between accounts. Every ad lands paused on top of that, so a wrong-account launch is a batch you delete before spend, not an invoice conversation.

On the Team plan, colleagues log in with their own email and launch through the owner's Facebook connection, so they need no role in the client's or your own business portfolio. Each member sees only the accounts you share, and per account you decide whether they may launch. The history shows who launched each batch. Adlio has no approval step of its own: sign-off happens in Ads Manager, when someone with access there switches the paused ads on.

The free tier counts ads, not accounts. Connect every account, set each one up, and use the first 15 ads to check that the isolation holds on your own setup. See how bulk upload works.

Frequently asked questions

What is the most common cross-account mistake?+

Launching into the wrong ad account because several were open in tabs, closely followed by a copied default (pixel, Page, or UTM template) from the last account you worked in. Both are invisible in the ad list. You only see them by opening the ad, or in the report a week later.

Does Meta Business Manager prevent settings from leaking between accounts?+

It scopes assets (which pixels and Pages an account may use), but it does not stop you from choosing the wrong one of the allowed options. And it does not store per-account defaults for copy, naming or UTMs. Those live in your process or in your tooling.

How many ad accounts can one person manage in Meta?+

Meta's help centre: "One person can manage up to 25 ad accounts." and "An ad account can be assigned to up to 25 people." An agency with more clients than that spreads the accounts over more people.

Can a colleague launch ads in one account without access to the others?+

Yes. In Meta you assign people to specific ad accounts in your business portfolio rather than giving everyone everything. What Meta has no role for is building ads without being able to publish them; the one native gate is peer approval, set up by the account's owning portfolio. See the roles and the colleague-access guides linked in this article.

How does Adlio isolate accounts?+

Every default is stored per ad account: Facebook Page and Instagram account, pixel, default copy, destination and UTM template, naming pattern, Advantage+ enhancement toggles, and EU DSA beneficiary and payer. Switch accounts and all of them switch. Nothing from one account is read when launching into another. On the Team plan, each member sees only the accounts shared with them and has launch rights per account. We treat any cross-account leak as a bug of the highest severity.

Sources

Adlio team

Built by media buyers who launch Meta ads in volume. Questions or corrections: support@adlio.ai.

Topic cluster

Teams and client accounts

Running Meta ads across many ad accounts with more than one person: access, roles, approval, and keeping accounts apart.

Start here

Managing multiple Facebook ad accounts without leaks