Meta Business Manager: setting up a portfolio properly

Meta renamed Business Manager to the "business portfolio", and the name is more accurate than the old one. A portfolio is not an account you advertise from. It is a container that holds ownership of business assets - Facebook pages, Instagram accounts, ad accounts, datasets (the artefact formerly known as the pixel), catalogues, domains, WhatsApp numbers, lead-form data - and a permission layer that decides which humans and which partner businesses may touch each one.

Two consequences follow, and they explain most of the pain people experience later. First, the portfolio - not the person - is the legal owner of the assets inside it; individuals only ever hold access. Second, an asset can be owned by exactly one portfolio at a time. Ownership can be transferred, but only by the current owner, and only if that owner still has an admin who can log in. Every horror story about a brand losing its page or its ad history is a version of that second sentence.

A portfolio also carries a reputation of its own. Meta scores business entities, not just campaigns: policy history, payment history, page quality, integrity signals from every asset inside. A clean portfolio makes new ad accounts easier to trust. A portfolio with a history of rejected creative and disputed payments makes every new asset guilty by association.

The first real decision is how many portfolios you need. The default answer is one: one legal entity, one portfolio, everything inside it. Multiple portfolios are not a growth tactic and Meta treats unexplained duplication as a risk signal, not a sophistication signal.

There are legitimate reasons to split. Separate legal entities with separate invoicing and tax registration. A holding company with genuinely independent operating brands. An agency that must keep client assets segregated for contractual reasons. A hotel group where each property is a separate company with its own accountant and its own bank account.

Within one portfolio you then organise by business unit rather than by account. A developer with three towers does not need three portfolios; it needs one portfolio, one verified business, and a naming and structure convention that makes each tower legible: its own page if the brand is genuinely distinct, its own ad account only if budgets and invoices must be separated, and shared datasets and catalogues wherever the audience overlaps.

Assets are the things that do the work. In practice you are managing six types, and each has its own ownership trap.

• Pages. Bring the existing page into the portfolio; never create a duplicate to "start clean". A duplicate abandons followers, reviews, history and every ad that references it. If the current admin is unreachable, the recovery route is a claim through Meta support with proof of the business, not a new page.
• Instagram accounts. Add the professional account to the portfolio directly rather than relying only on a page connection. A personal login connection is a person's password standing between you and your advertising.
• Ad accounts. Owned by the portfolio, paid by a payment method, and worked in by people. Once created inside a portfolio, an ad account cannot be freely detached - so create it in the right place the first time.
• Datasets (pixel and conversions API). The single most valuable asset you hold, because it carries learning history you cannot buy back. Own it in the brand portfolio and share it with the agency. Never let it be created inside an agency portfolio.
• Catalogues. Property listings, menus, product feeds. Owned by the brand, connected to the dataset, maintained by whoever owns the source data.
• Domains. Verify every domain you advertise. Domain verification is what gives you final authority over link edits and aggregated event configuration - and it is a prerequisite for serious iOS measurement.

The rule that prevents ninety percent of future disputes: the brand owns every asset, the agency is granted access to them. It is the difference between renting your own history and holding it.

Meta's permission model has two layers, and conflating them is the most common administrative error. Portfolio-level access says what someone can do to the business itself - add assets, add people, change billing. Asset-level access says what they can do inside one page, one ad account, one dataset.

Give portfolio admin to the smallest possible number of people: typically two, both permanent employees, both with two-factor authentication. Two, because one admin is a single point of failure the day that person leaves, loses a phone, or is locked out. Everyone else - marketing managers, agencies, freelancers, media buyers - gets employee-level access plus specific asset permissions.

On the ad account itself, the useful distinction is between managing campaigns and managing money. A media buyer needs to create and edit campaigns. Almost nobody needs to change payment methods or spending limits, and those are exactly the permissions that turn a compromised account into a financial incident. Access is also a maintenance job: review it quarterly and remove people at the moment they leave, not at the moment someone remembers.

Business verification - submitting registration documents that prove the legal entity behind the portfolio - is optional right up until the moment it is not. Unverified portfolios face lower spending limits, restricted access to some features, slower appeals when something is flagged, and limits on how many ad accounts they may open. Verifying an established business with clean documents usually takes days. Verifying it during a crisis, while campaigns are paused, takes as long as it takes.

Do it early, with documents that match exactly: the legal name on the certificate of incorporation, the registered address, a utility bill or bank statement in the same name, and a business email on the verified domain. Mismatches between the trading name and the registered name are the single most common rejection reason.

Security is the other half. Enforce two-factor authentication for everyone in the portfolio, not just admins. Meta's permission system is anchored to personal profiles, which means a compromised personal Facebook account is a compromised advertising operation - and the compromise usually shows up as unfamiliar campaigns spending real money overnight. Set an account spending limit as a hard ceiling; it is the cheapest insurance available.

The correct pattern is partner access. The client owns their portfolio and all assets; the agency has its own portfolio; the client adds the agency as a partner and grants task-level permissions on the specific assets that need work. Nothing changes ownership. When the relationship ends, the client removes the partner and keeps every page, every dataset, every euro of learning history.

The wrong pattern - still surprisingly common - is the agency creating everything inside its own portfolio and giving the client a login. It looks faster on day one and it is a hostage situation on day four hundred. If you are reading this from inside that arrangement, the fix is an orderly transfer: create the client portfolio, verify it, transfer page and dataset ownership, then re-establish partner access. Ad account history is the piece most likely to be lost, which is why the order matters.

One practical note for anyone changing agencies: request the transfer before you give notice, not after. Access disputes are resolved by whoever currently holds admin, and goodwill is a finite asset.

• A second portfolio to escape a problem. Restrictions follow the people, payment methods and domains involved. Duplicating to evade a restriction is a policy violation in itself and frequently ends with both entities disabled.
• A personal ad account for a business. No permission layer, no transfer path, no continuity. Migrate before it matters.
• Multiple pixels on one site. Split events, broken attribution, no clean learning signal. One dataset per domain, with the conversions API deduplicated against the browser pixel, is the standard.
• An unverified domain. You will discover this at the worst moment, when event configuration or link editing is blocked mid-launch.
• Nameless assets. "Ad Account 2" is a debt. A naming convention - brand, unit, purpose - is thirty seconds of work that saves an hour every month.
• No documentation. Record who holds admin, which payment method is attached, which domains are verified and which datasets serve which sites. Store it outside the platform.

None of this is glamorous, and none of it improves a single ad. It does something more valuable: it makes sure that when the advertising works, the brand owns the machine that produced the result. Structure first, then spend - the same order we apply to everything else.