Business Manager, now commonly called a Meta business portfolio, organizes business assets and access. An ad account is the advertising asset used for campaigns, spending and reporting. A Facebook Page supplies a public identity. Name the exact layer when requesting access or reporting a problem: the word account on its own is usually too vague.
What to take away
- A portfolio, an ad account and a Page have different jobs.
- Request the asset and action you need, not simply admin access.
- Diagnose a problem at the layer where the evidence points.
Give each part a clear job
This is an operating map, not a promise that every connected asset is ready. Record the IDs once and reuse them in launch briefs, support requests and finance notes. Similar names become much less confusing when the underlying identifiers are visible.
| Part | Main question it answers | Useful detail to record |
|---|---|---|
| Business portfolio | How are the business's assets and access organized? | Business ID and responsible owner. |
| Ad account | Where is this advertising activity operated? | Ad account ID, currency and time zone. |
| Facebook Page | Which public brand identity appears? | Page ID and brand name. |
| Measurement asset | Where is the relevant event activity received? | Dataset or pixel ID and technical owner. |
Describe access as a task
Instead of writing, Please make me an admin, write what the person needs to do. They may need to review reports, create campaigns, approve a budget change or manage who can access an asset. Those tasks do not all need the same authority.
Ask the asset owner to confirm the appropriate permission for that task. Then check the intended workflow with the actual user. Seeing an asset in a list is helpful, but it does not prove that every action your team expects is available. Keep the check limited to the work the person is authorized to perform.
Use the symptom to choose the next check
When a buyer cannot select the intended Page, inspect that identity and its access path. When finance cannot reconcile spend, start with the exact ad account, reporting dates and currency. When a person cannot see the business, inspect their invitation and business access. These are different investigations.
Avoid describing every incident as a broken BM. That phrase encourages broad changes before anyone knows the cause. A useful support note names the user, asset ID, attempted action, time and current message. Leave passwords, tokens and unrelated customer information out of the note.
One healthy asset does not certify the whole setup
An accessible ad account does not tell you whether the intended Page is usable for the proposed ad. A published Page does not show that the campaign has approval. A submitted campaign does not prove that it has delivered. Keep each observation attached to the thing that was actually checked.
For a launch review, write the status of each dependency separately: confirmed, needs action or not yet checked. Add a short explanation and owner. This gives the team a useful next step instead of one green or red label that hides several unrelated conditions.
Document ownership when an agency is involved
A team may operate assets it does not own. That can be a deliberate part of an agency or managed-service arrangement, but everyone should understand it before work begins. Record who controls the business relationship and which rights the customer receives.
Ask how campaign reporting, creative files and unresolved support cases are handled if the relationship ends. Do not assume that a visible button implies ownership or that ownership can be transferred whenever needed. Treat access, reporting availability and asset ownership as separate questions in the service agreement.
Use the same vocabulary across your team
In Advellar, customers work through a managed campaign dashboard and account allocations. Your team still benefits from knowing which brand and ad account a campaign belongs to, who approves changes and where to ask for help. The product workflow should make those decisions understandable without requiring shared personal logins.
Create a short internal glossary with the terms your team actually uses. Add an example from your own setup beside each term. When a new buyer joins, the glossary and asset register give them a much clearer starting point than a long message thread full of account nicknames.
Quick questions
Is Meta Business Suite the same thing as an ad account?
No. Business Suite is a management interface; an ad account is a specific advertising asset. Always identify the ad account when discussing its campaigns, spend or status.
Does Page access include access to every ad account?
Do not assume it does. Page access concerns that Page. Ask for the specific ad account and task permissions your work requires, then confirm the intended workflow.
Which ID belongs in a support request?
Include the exact affected asset ID and explain the attempted action. If the problem involves a connection between assets, include both identifiers and the relevant brand.
Sources & further reading
A clearer way to run your Meta workflow.
Bring your account setup, campaigns and reporting into Advellar.
Create your workspace