What the business portfolio holds and why the business must own it
A business portfolio is the layer above campaigns. Some older guides, including parts of this site, still call it Business Manager; the custom audiences guide uses that name. What matters is what it holds. The Meta Ads account audit checklist opens by confirming that the portfolio owns the ad account, the Page, the pixel and the catalogue, and the pixel setup tutorial creates the dataset and verifies the domain in that same portfolio. If those assets sit in the right place, everything downstream inherits a clean owner.
| Asset | What it does | Where this site explains it |
|---|---|---|
| Ad account | Holds campaigns, budgets, billing and reporting | Campaign structure hub |
| Facebook Page | The identity ads run from; messages and comments arrive here | This tutorial, step four |
| Instagram professional account | The identity for Instagram placements and messages | This tutorial, step four |
| Dataset | Receives pixelAn ad platform's browser code that reports page views and events on a site back to the platform. and server events used for optimisation and reporting | Meta pixel setup |
| Catalog | Holds the products that catalog ads show | Meta catalog setup checklist |
| Verified domain | Proves the business controls the website the ads point to | Meta pixel setup |
| People and partners | Who may do what with each asset | This tutorial, step nine |
Ownership matters most at the moment nobody plans for: the end of a relationship. The agency offboarding checklist puts ownership first, including moving any account created under an agency's own business, because an account the business does not own cannot be secured by any later step. The pixel tutorial makes the same point from the measurement side: a dataset created from a personal account belongs to a person, and sharing and verification become a mess when that person leaves. The pillar's policies and account health section lists the habits that keep the layer healthy, which this tutorial turns into steps: two-factor authenticationA sign-in that needs a second proof of identity as well as the password, so a stolen or guessed password alone cannot open the account. on every user, more than one admin, business verification where Meta requires it and a payment method with headroom. The same principles apply beyond Meta, and the tutorial on securing social media accounts extends them to every social account a brand runs, with an account registerThe brand's list of every account it holds on each platform, dormant ones included, with handle, use, status, admins, attached email and phone, and owner., recovery details and a leaver process.
Meta's own help centre, listed in the sources, is the reference for the screens themselves. They are renamed and rearranged from time to time, so the steps below describe what to set and why rather than which button to press.
Before you start
- A named owner inside the business: the person accountable for the portfolio, who will still be there when the agency or the freelancer has moved on.
- A second person to be admin, also employed by the business, so the portfolio survives one of them leaving or losing access.
- The business's legal name, address and website, exactly as they appear on official records, since verification, where Meta asks for it, checks them.
- Admin access to the existing Facebook Page and Instagram account, or the details of whoever holds it today.
- A payment method the business holds and a spending ceiling agreed with whoever controls the budget.
- Access to the website's DNS, head or root folder, for domain verification when you reach the pixel tutorial.
- A list of the people and agencies who need access, with what each of them actually has to do.
- A shared document for the setup record, kept somewhere the business controls.
The steps
Decide who owns the portfolio
Write down who owns the portfolio before anyone opens a browser. The owner is the business, and the person accountable for it is someone the business employs, normally the owner-manager in a small company or the head of marketing in a larger one. A RACI matrix settles the rest in a few lines: who is accountable for the portfolio, who is responsible for the setup, who is consulted (often the agency that will run campaigns) and who is informed (finance, for the payment method and the spending limit). The point of writing it down is the later conversation. When an agency proposes building in its own account, the answer is already on paper, and the agency onboarding checklist treats that proposal as a failed line rather than a convenience.
Create it under a business-owned login with more than one admin
Create the portfolio while signed in as the accountable person, not as a freelancer, an agency employee or a shared login. Name it after the business's legal name, because that is what verification compares against and what anyone granting access will see. Add the second admin straight away. The pillar's account health paragraph names more than one admin as a basic safeguard, and the reason is mundane: people change jobs, lose phones and get locked out, and a portfolio with one admin is one person's bad week away from being unreachable. Keep the admin list short. Admin is for the people who are accountable for the business's assets, not for everyone who will touch a campaign.
Switch on two-factor authentication for everyone
Before granting anyone access, make sure every person who will hold it has two-factor authentication switched on in their own account, and check it rather than taking it on trust. The pillar lists two-factor authentication on every user among the operational parts of account health, alongside more than one admin. A compromised personal account with access to the portfolio puts the ad account, the Page and the payment method within reach of whoever compromised it, and recovering from that takes far longer than the check does. Make the check part of granting access, so that a new person is never added on the promise that they will set it up later. Should a takeover happen anyway, the compromised marketing account response SOP sets out the first hours, from pausing the ads to removing unknown users and checking the payment method.
Add the Facebook Page and the Instagram account
Bring the Facebook Page and the Instagram professional account into the portfolio so that the business owns them, rather than borrowing access to them. If the Page was created years ago by a former employee or an agency, recover it now, while the setup is quiet, rather than during a launch. The same reasoning the offboarding checklist applies to ad accounts held in an agency's business applies here: ask the holder to release it, and if they are slow, the contract is the lever. Add the Instagram account in the same way, so that both identities the ads will run from belong to the business, and note in the setup record which people are expected to answer comments and messages on each, since that becomes a staffing question the moment ads point people at a conversation.
Create the ad account with its time zone and currency chosen deliberately
Create the ad account inside the portfolio and treat its time zone and currency as decisions rather than defaults. The troubleshooting page on spending more than the daily budget explains that the ad account's time zone defines Meta's day, so a finance team reading spend in another time zone will see days that look overspent. Choose the time zone the business plans and reports in. Currency matters because the campaign versus ad set budgets comparison notes that budget minimums depend on the optimisation goal, the billing basis and the account currency, so pick the currency the business is billed and budgets in. Name the ad account with the business name and its purpose, following the naming convention you will write in the last step.
Add a payment method and an account spending limit
Add a payment method the business holds, with enough headroom that delivery does not stop at the threshold, which the pillar names as part of account health. Then set an account spending limit. The spending-over-budget page describes it as the cap on total spend in the ad account, distinct from budgets, which guide pacing, and from the campaign spending limit, which caps a single campaign. Agree the figure with finance and record it with the date and the reason, because a limit set long ago and forgotten is one of the administrative causes of spend stopping that the performance drops guide lists. Review it whenever the budget changes.
Create the dataset and verify the domain in the portfolio
Meta's documentation describes the pixel as code on the website that reports actions back to Meta, and the pixel tutorial creates its dataset in the portfolio that owns the ad accounts and shares it with each ad account that needs to optimise on its events. Do that now, following the Meta pixel setup tutorial, which also covers installation, events, consent and testing; this page does not repeat them. Verify the registered root domain in the same portfolio, as that tutorial explains, because a domain verified in an agency's portfolio leaves ownership and event configuration in the wrong place. Server events sent later through the Conversions APIServer-side event sharing with Meta. go to the same dataset, so getting its owner right now saves a migration later.
Add the catalog where the business sells products
If the business sells products online and will run catalog ads, create the catalog in the portfolio as well, not in an agency's or a platform partner's account. The catalog is filled from a Product FeedA structured file of a store's products, prices and availability used to build shopping and catalogue ads., and the feed, its fields and its diagnostics are the subject of the Meta catalog setup checklist, which this step hands over to. What belongs here is only the owner: the catalog should sit beside the dataset it is connected to, so that product events from the website and products in the catalog are matched inside one business. A service business without products skips this step and notes in the record that no catalog exists.
Give people and agencies the narrowest access that works
Grant each person access to the assets their work needs and nothing more: someone who builds campaigns needs the ad account, not the payment method; someone who answers messages needs the Page and the Instagram account, not the dataset. Agencies should be added as partners working through their own business, not as individuals with personal logins and never through a login the business shares; the agency onboarding checklist asks for access through the business's own accounts and for named access in place of any shared login. The audit checklist's account group reviews people and partner access and removes leavers and unknown agencies, and the guide to selecting, briefing and reviewing agencies covers the relationship that sits around the access. Before an agency is chosen at all, the guide to hiring and evaluating a Meta Ads agency sets out the questions and warning signs that show whether it will work inside the business's portfolio rather than its own. Record who was given what, when and why, and set a date to review it.
Write the naming convention and the setup record
Finish by writing two short documents. The first is a Naming ConventionAn agreed pattern for naming campaigns, ads, events and tracking parameters so that reports can group them reliably. for the ad account, campaigns, ad sets, audiences and the dataset, so that every report can be grouped and every asset's purpose is obvious; the paid social campaign build sheet uses it from the first campaign onwards. The second is the setup record: the owner and admins, every asset with its identifier, the dataset and the verified domain, each person and partner with their access and the date it was granted, the payment method holder, the spending limit and the next review date. Keep it in the business's own storage. It is the document the Meta Ads account audit will ask for, and the one that turns an agency handover from archaeology into a checklist.
Business verification sits outside the sequence because it happens when Meta asks for it rather than at a fixed point. The pillar lists it among the account health basics "where Meta requires it", and the portfolio shows when it is needed. Complete it with the same legal details the portfolio was created under; the documents Meta accepts are set out in its help centre and are not listed here. The campaign itself is the next document, not this one: the build sheet above takes over once the portfolio, the dataset and the access are in place. Before that hand-over, the new ad account setup checklist is a quick way to confirm that ownership, admins, two-factor sign-in, billing and the setup record are all settled, on Meta and on any other platform the business advertises on.
A candle maker's portfolio (illustrative)
Wickerlark Candles sets up its portfolio before an agency starts
Wickerlark Candles, an invented candle maker with an online shop and a weekend market stall, is about to hire a paid social agency. Its Facebook Page was created six years earlier by a former employee, and the founder has been boosting posts from a personal card. Before the agency starts, the founder and the operations manager spend two afternoons on the portfolio and write this record.
| Item | Setup |
|---|---|
| Owner and accountable person | The business; the founder is accountable |
| Admins | The founder and the operations manager, both with two-factor authentication checked |
| Assets owned | Facebook Page (recovered from the former employee in four days), Instagram account, one ad account, one dataset, one catalog of 64 products |
| Ad account settings | Time zone and currency set to match the shop's accounts; spending limit of £3,000, reviewed each quarter |
| Payment | The business's own card, replacing the founder's personal one |
| Dataset and domain | Dataset created in the portfolio and shared with the ad account; root domain verified in the portfolio |
| People | Marketing assistant: Page and Instagram for messages and comments only |
| Partner | The agency, through its own business: ad account, dataset and catalog for building campaigns; no payment access |
| Review date | Access and spending limit reviewed on the first working day of each quarter |
Three months later the agency asks for the payment method to be shared so it can raise the limit before a seasonal push. The record answers the question: the founder raises the limit to £4,500 for eight weeks and writes the change and the end date into the record.
Common mistakes
- Letting the agency or a freelancer create the portfolio. It is quicker on day one and costly on the last day; the business should own every asset from the start.
- One admin. The portfolio then survives only as long as that person's login does.
- Two-factor authentication on trust. Check it before access is granted, not after an account is compromised.
- Accepting default time zone and currency. The time zone decides Meta's reporting day and the currency sets the budget minimums; choose both on purpose.
- A personal card as the payment method. It ties the account to one person and fails when they leave.
- Dataset or domain in someone else's portfolio. Ownership and event configuration end up in the wrong place and are slow to move.
- Access by shared password. Partners work through their own business; nobody uses the business's login.
- No written record. Without one, the next audit or handover starts by rediscovering what exists.
