Pulsar · Field guide · No. 16 · How Meta Business Manager actually fits together — the objects, the many-to-many links, and the one trap that catches everyone.
The Business Manager Map
One umbrella. Five kinds of thing. A web of many-to-many links. Learn what connects to what — and why your creative library belongs to the ad account, never the page.
Start here: the business owns everything, people just get access
Business Manager (business.facebook.com → Business Settings) is the top-level container a company owns. Every asset — Pages, Ad Accounts, Pixels, Catalogs, Apps — is owned by the business, not by anyone’s personal profile.
Assets belong to the business. People and agencies are only granted access — and access can be taken back without losing the asset.
This one idea prevents the most common disaster: an employee or freelancer “owning” the ad account or pixel on their personal profile and walking away with it. In a proper Business Manager, you add the Page, the Ad Account and the Pixel as business assets, then invite people with a role. Remove the person — keep the asset.
The five things the umbrella holds
Almost everything you touch in ads is one of these five. Learn what each one is for — then the links between them make sense.
Page
your identity
Your public presence on Facebook / Instagram. Ads always run “as” a page — it’s the name and face on the ad.
Ad Account
where money is spent
Holds your campaigns, ads, billing and its own asset library. Currency & timezone are fixed the moment it’s created.
Pixel / Dataset
the data source
Receives events (web, app, offline). Powers optimization, attribution and audiences. Owned by the business, shareable to ad accounts.
Payment method
who pays
The card or credit line that funds spend. Attached to the ad account. A business credit line can fund several ad accounts.
Asset library
images & videos
The uploaded creatives an ad account reuses across its ads. It lives inside one ad account — remember this one.
Two more you’ll meet later: a Catalog (product feed for shopping ads) and your verified Domain — both are business assets too.
The map: who connects to whom
The business owns each object one-to-many. But the objects link to each other in a way that surprises people: mostly many-to-many. Here is the whole thing on one page.
| Relationship | Cardinality | What it means in plain words |
|---|---|---|
| Business → Page / Ad Account / Pixel | 1 : N | the business owns many of each; each asset has exactly one owning business |
| Page ↔ Ad Account | N : N | a page can be advertised by several ad accounts; an ad account advertises several pages |
| Pixel ↔ Ad Account | N : N | one dataset can be shared to many ad accounts; an ad account can use many pixels |
| Payment ↔ Ad Account | N : N | an ad account can hold several payment methods; a credit line can fund several ad accounts |
| Ad Account → Asset library | 1 : N | the library lives in exactly one ad account — assets do not cross ad accounts |
| An Ad → Page + Pixel + Creative | 1 : 1 | one ad picks one page (identity), one pixel (optimization) and creative from that ad account’s library |
Read “N : N” as “many-to-many” — the link table in the middle is where most confusion (and most mistakes) live.
Pages ↔ ad accounts: yes, one page can live in two ad accounts
This is the link people get wrong. A Page is not tied to a single ad account. You assign a page to whichever ad accounts should be allowed to advertise it.
Real example: you run ads for your own Page from your ad account. You also hire an agency — their ad account now advertises the same Page. That Page is linked to two ad accounts at once. And your ad account probably advertises a second Page you own too. Both directions are many — that’s N : N.
Owned vs shared — the reason it’s many-to-many
Every asset is owned by exactly one business, but it can be shared to others. That single fact is what makes pages, pixels and ad accounts cross business boundaries.
Owned
1 owner, forever
The business that created (or claimed) the asset. Only the owner can delete it or hand ownership over. There is exactly one.
Shared (Partner)
many, revocable
Access granted to a partner business (an agency, a client, a contractor’s BM). They can work in the asset but never own it.
The agency model both ways: (a) you own the Page and share it to the agency’s ad account; or (b) the agency owns the ad account and shares it to you. Either way the same Page ends up worked by two ad accounts in two businesses. When the relationship ends, the owner keeps the asset and simply removes the partner — which is exactly why you always want to own your own Page, pixel and (ideally) ad account.
Pixels ↔ ad accounts: share one dataset
A pixel (dataset) is owned by the business — not locked to one ad account. You share it to the ad accounts that need it, and an ad account can be assigned several pixels.
If two ad accounts advertise the same website, share the one pixel to both. Both then optimize on and get attribution from the same events — no second pixel needed (a second pixel would split your data and weaken both). The event itself is one; the credit can appear in every ad account the pixel is shared with. The pixel also feeds audiences (retargeting, lookalikes) that any sharing ad account can use.
Where the money is attached
Payment lives on the ad account (its Payment settings), not the page and not the pixel. An ad account can hold a primary + backup method; a business can run a credit line / consolidated billing that funds many ad accounts.
Two things are frozen when an ad account is created and can never change: its currency and its timezone. Need a different currency? You create a new ad account — you can’t convert one, and you can’t move spend history between them. This is a big reason a single business ends up with several ad accounts. Billing is also where a spending limit and your invoices / receipts live — all per ad account.
The trap: your creative library belongs to the ad account — not the page
Every ad account has exactly one asset library. That same ad account can advertise many pages. So the library is a shared pile — and Meta gives an image or video no page field at all. There is no native “this creative belongs to Page X.”
A shared ad account has one library for all its pages. Meta won’t tell you which creative is whose — you have to label it yourself.
So how do you tell a page’s creatives apart in a mixed library? Three ways — and only the first lives inside Meta:
Name every asset with the page it’s for
The asset’s name is the only free-text, filterable field Meta exposes. Bake the page id into it and the shared library becomes searchable per page:
Then filter the library by the page-<id>- prefix to see just that page’s creatives. This is exactly what Pulsar now does automatically on every upload and generation.
| How to attribute a creative to a page | Where it lives |
|---|---|
| Name / naming convention — page id in the asset name | inside Meta (filterable) |
| Your own metadata — tag the record with the page id | in your tool (Pulsar: tags: page:<id>) |
The ad itself — the page is set in the ad’s object_story_spec.page_id | at ad-build time (the real binding) |
Until a creative is placed in an ad, it is page-agnostic in the library. The name/tag is how you stay organized before that moment.
A naming scheme that survives a shared library
Since the name is your only handle, make it carry everything you’ll ever want to filter by. A good scheme reads left-to-right from broadest to narrowest.
| Part | Example | Lets you filter by |
|---|---|---|
| page-<id> | page-1165695883301380 | which page owns it (the must-have) |
| topic / campaign | quantity-vs-quality | the message or campaign it belongs to |
| format-aspect | stat-1x1, story-9x16 | placement fit (feed vs story vs reel) |
| version | v2 | iterations, so you never overwrite a winner |
Two payoffs: the shared library stays searchable per page, and because an ad name can inherit the creative name, your reporting rows become readable instead of a wall of IDs. Pick the scheme once, apply it on every upload, and never think about it again.
Roles: who can do what
Access has two layers. First business-level (are you an Admin or an Employee of the business), then per-asset roles on each Page, Ad Account and Pixel you’re given.
| Asset | Typical roles | Give this to… |
|---|---|---|
| Business | Admin · Employee | Admin only for the 1–2 people who run the business; everyone else is an Employee |
| Ad Account | Admin · Advertiser · Analyst | Advertiser for buyers (create/edit ads, no billing), Analyst for read-only reporting |
| Page | Full control · Task access (content, ads, insights, messages…) | Task access scoped to what each person actually does |
| Pixel / Dataset | View · Manage | Manage for whoever configures events; View for analysts |
People are individuals inside your business; Partners are whole other businesses you grant asset access to (the agency model from §05). The rule for both: least privilege — give Advertiser, not Admin, unless someone truly needs billing and user management. Turn on two-factor for the whole business.
Scale & automate: Instagram, asset groups & system users
Three pieces you meet the moment you go past a one-person, one-page setup — the identity people forget, the way to grant access in bulk, and the “robot” that lets tools run your account.
Instagram account
the second identity
Add your IG professional account as a business asset and link it to the Page. Ads then run on Instagram with that identity. No IG linked? Ads still show on IG using the Page itself.
Business Asset Group
grant access in bulk
Bundle a Page + its ad account + pixel + IG + catalog into one group, then assign a person or partner to the whole group at once — far cleaner than per-asset grants as you scale.
System User
the robot member
A non-human member of the business that holds long-lived tokens for APIs and tools. You assign it specific assets + tasks (manage this ad account, this pixel, this page). This is what lets software run your ads.
Two verifications that unlock everything
Two separate checks in Business Settings quietly gate a lot of features. Do both early — they’re the difference between a toy setup and a real one.
Business Verification
prove the business is real
Submit business documents. Unlocks higher ad-account limits, the Conversions API at scale, WhatsApp, and general trust. Some features simply won’t appear until it’s done.
Domain Verification
prove you own your website
Add + verify your domain (DNS, meta-tag or file). Required to configure Aggregated Event Measurement for iOS 14.5+ and to control who can edit link content — without it you lose conversion events.
They’re independent: verifying your business is not the same as verifying your domain. You want both. Domain verification is what protects your pixel’s Purchase events on Apple devices.
The limits people ask about
Most Business Manager limits are not fixed numbers — they scale with your ad spend and account standing. Treat these as the shape of the rules, and always confirm the live number in Business Settings.
| Limit | Roughly | Notes |
|---|---|---|
| Ad accounts per Business Manager | starts ~1 (up to 5), scales up | rises with spend & good standing (and Business Verification); agencies/large advertisers reach far higher — no single public max |
| Ad accounts one person can be on | 25 | a personal cap on how many ad accounts a single profile can access |
| Pages a Business Manager can own | many | a business holds numerous pages; not the usual bottleneck |
| Pixels / datasets | a small number per business | you rarely need more than one per website — share it rather than multiply |
| Currency / timezone per ad account | 1, fixed | chosen at creation, never editable — make a new ad account to change it |
Meta changes these over time. The number that matters is in Business Settings → Accounts → Ad Accounts, which shows your current limit and how to request more.
The mistakes that cost people their setup
Almost every painful Business Manager story is one of these. Now that you have the map, they’re easy to avoid.
- ×Assets on a personal profile. The pixel or ad account “belongs” to a person, not the business — when they leave, it leaves. Own everything at the business level.
- ×Letting an agency own your Page or pixel. Make them a partner with access, never the owner.
- ×A second pixel for the same website. Splits your data; both ad accounts learn from half the signal. One pixel, shared.
- ×Assuming the library is per page. It’s per ad account — a shared pile. Name every asset with its page id.
- ×Skipping domain verification. Your iOS Purchase events quietly vanish and you can’t fix attribution.
- ×Admin for everyone. Least privilege — Advertiser and Analyst cover 90% of people.
- ×Wrong currency / timezone. It’s permanent. Double-check before you save a new ad account.
Set it up right, in order
Do it in this sequence from Business Settings and the web stays untangled from day one.
page-<id>-… — so a shared library never becomes a mystery pile.Quick glossary — and how Pulsar rides this map
page_id.How Pulsar maps to all of this: Pulsar reads your pixel, resolves its default ad account, and puts every uploaded or generated creative into that ad account’s library — named and tagged with the owning page id (page-<id>-…) so a shared ad account stays attributable. At publish time it sets the page on the post/ad. In other words, Pulsar automates the exact discipline this whole guide describes — you just pick the pixel.
That’s the whole map. The umbrella owns the objects; the objects link many-to-many; the library sits inside the ad account; and the page-to-creative link is a label you impose. Get those four right and Business Manager stops being a maze.