When ad assets run into trouble, the real issue is often ownership and permissions rather than campaign tactics. Understanding the hierarchy under Business Manager, the scope of restrictions, and how client assets should be owned matters more than simply creating more accounts.
After running ads for a while, you realize that the biggest surprise is not one account being disabled, but discovering afterward that all your assets were tied together. To sort this out, you first need to understand what sits under Business Manager (BM), who owns each asset, and how permissions are assigned.
From a personal account to the BM layer
A personal account is the only entry point into the whole structure. You need one before you can create a BM or accept a BM invitation from someone else. If the personal account is disabled, you lose that identity’s access to the structure, but the assets inside the BM do not disappear. As long as the BM has other administrators, they can continue operating it.
Many teams run into trouble here: the BM has only one administrator, and that person happened to create it with a secondary personal account.
Who owns the assets under a BM
An ad account is the actual unit used for delivery and billing, and it belongs under a specific BM. One BM can contain multiple ad accounts, and their budgets and settings are independent of one another. An ad account generally cannot be moved directly from one BM to another; instead, a new one must be created and access granted again.
A Page is the public-facing identity used by ads. It may be owned by a BM or held under an individual. When it is held by an individual, usage access can be granted to an ad account, but ownership remains with that person.
Pixels and datasets handle conversion tracking, while audiences and product catalogs support targeting and ad materials. These asset types are owned by the BM and can be assigned for shared use across different ad accounts inside it.
A simple way to think about the relationship is this: the personal account is the key, the BM is the container, and ad accounts, Pages, pixels, audiences, and catalogs are the assets inside the container. Who owns an asset determines who can appeal or transfer it when something goes wrong.
What can go down together when something happens
If a personal account is disabled, the most direct effect is that nobody can use that identity to sign in to the BM. If the BM has other administrators, the business can continue, while the disabled personal account goes through its own appeal process.
If an ad account is disabled, the impact is on that account’s delivery and historical data. The Page and pixel are usually not affected. You can create a new ad account, continue running ads, and grant the Page and pixel access to it again.
If a Page is restricted or disabled, every ad tied to that Page is affected, regardless of which ad account it belongs to. This is one of the clearest consequences of mixing assets together.
If a pixel or dataset has a problem, conversion data is interrupted and ad optimization suffers. A new pixel can restore tracking, but historical data cannot be carried over, so learning and attribution have to start again.
If the BM itself is restricted, the impact is broadest: the ad accounts, Pages, and pixels under it all lose their operating entry point. The proper response is to appeal through the official process, and the outcome depends heavily on whether asset ownership is clear and whether there is a history of noncompliant advertising.
Why client assets should have separate ownership
When running ads for a client, placing the client’s Page and pixel under your own BM may be convenient in the short term but creates long-term risk. If your BM runs into trouble, the client’s assets can be pulled into it as well. When the engagement ends, returning those assets can also get stuck because of permission layers.
A more stable approach is to let the client retain ownership of the assets, add the operator’s business to the client’s BM, and grant only the access needed for the project. Use one BM per client, or at least group assets by client, so the boundaries are clear and it is obvious whose problem affects whom.
Permissions and login environments
BM roles are divided into administrators and employees, with different permission levels. The principle is to grant only what is necessary: people running ads do not need budget permissions, and people working with data do not need permission to edit creative. Review activity logs regularly so mistakes can be caught earlier.
On the environment side, the question is who logs in from where. Do not crowd advertising accounts into the same browser environment, especially when they belong to different entities. When several people need to manage a group of accounts, use PurpleMark to give each account its own independent, fixed browser environment and assign it by role. That makes it much easier to keep account ownership aligned with the corresponding login environment.
Only after the structure is organized does it make sense to discuss operating multiple accounts.
