---
name: set-up-meta-business-manager-and-public-figure-pages
description: "Check who owns the ad tools and the public page. Set up only the parts the job needs."
category: Dollar a Day Campaigns
stage: Promote
definitive_article: /dad
status: needs-work
---

# Set up Meta Business Manager and Public Figure pages

Your page and ad tools should stay under the right owner’s control. This guide helps you check what exists and fill the real gaps. Start with the person or business the page is meant to show.

**The path:** Real identity → existing assets → correct access → checked setup.

**Use this when:** A personal brand needs the Meta assets for an authorized campaign, or an existing setup’s ownership/access is unclear.

## Inputs
- The actual person/business identity, authorized owner and existing portfolio, Page, Instagram and ad-account records.
- An authenticated owner or authorized administrator with the required roles; recovery contact through the official route if access is missing.
- Approved name, headshot, bio, source posts and site link; the exact scope for setup, connections, publishing or billing changes.

## First-run prompt

> Inspect the existing Meta assets for this person or business. Map ownership and roles, reuse valid assets, and make only the setup changes already authorized. Do not ask for shared login credentials or use a paid boost as automatic setup proof. Return checked IDs, access scope and the smallest unresolved gap.

## Steps
1. Identify whether the page represents the person or the company. Keep real names, headshot/logo, bio and website consistent with that entity. Do not imply a personal Page is the company or create an unnecessary duplicate to satisfy the historical task title.
2. Inventory the existing business portfolio, Pages, Instagram identities, ad accounts and event data sources. Record ownership separately from assigned task access. A visible asset does not prove the operator can manage every setting.
3. Use the owner’s existing portfolio where appropriate. If setup or access is missing, use the supported invitation or recovery process with the current authorized administrator. Do not request the owner’s password or bypass account verification.
4. Assign only the roles required for the actual job when those grants are authorized. Preserve business control while allowing agreed agency/partner access. Document who can edit, view reports or spend without publishing private identifiers in a public article.
5. Create or update a person’s Page only when the plan needs it and the action is authorized. Choose an accurate available category; Public Figure is a descriptive choice, not a universal prerequisite for all Meta ads. Review the approved bio, real image and useful source posts.
6. Connect the specific Page, Instagram identity, ad account or event source that the campaign needs using the supported interface. Domain verification and pixel connections apply when required by the chosen features, not as a reason to install every integration.
7. Read back the ownership/role and connection settings, then inspect the public identity and existing content with media silent. Keep seeded draft content separate from actually published posts. A setup check does not need an automatic paid test boost.
8. Save an access map with checked date, role scope, unresolved step and next owner. If a paid test is already separately in scope, hand it to the campaign task with its own budget and dates; setup completion alone does not prove delivery or attribution.

## Definition of done (QA checklist)

- [ ] The real person/company identity and existing assets are correctly mapped.
- [ ] Ownership, assigned roles and permissions are distinct and supported.
- [ ] Only needed, authorized connections or grants were made.
- [ ] Public identity and saved setup were checked without unscoped media or spend.
- [ ] Campaign delivery is a separate next task; access gaps are not concealed.

## Example(s)

**Fictional teaching example:** A bike shop owner already has a personal-brand Page and a business ad account. The operator can view reports but cannot edit the Page bio. The map records that exact gap and names the current Page administrator as the route for the approved edit. No second Page is created and no password is requested. A separate company Page remains a separate entity. The setup report is complete as an inspection even though the bio change is pending; it does not invent a delivered $1 boost.

## Handoff and Content Factory context

Give the checked asset map to [create facebook instagram campaigns with location targeting](https://local-service-spotlight.github.io/task-library/?task=create-facebook-instagram-campaigns-with-location-targeting#task-create-facebook-instagram-campaigns-with-location-targeting) or [boost one minute videos for personal branding](https://local-service-spotlight.github.io/task-library/?task=boost-one-minute-videos-for-personal-branding#task-boost-one-minute-videos-for-personal-branding) when that campaign is in scope. The actual account administrator owns any remaining access step.

This task is in Promote within the [Content Factory](https://blitzmetrics.com/content-factory/). Produce gathers real source material; Process makes useful assets; Post places and checks them; Promote distributes suitable work within its own scope. Use the proof and checked posts from earlier stages; a Promote task does not automatically redo all four stages. Use the actual next step above; catalog neighbors are not prerequisites.

## When this runs

One setup/inspection, with a fresh check after ownership, personnel or integration changes. Recurring access reviews may be part of an existing arrangement, but this guide creates no grants or schedule on its own.

## First-run setup and continuity

Open the supplied task file and its linked source. Verify the project’s real inputs, account, access and output folder before work. This Markdown file is a guide; it does not install an app, connect an account, supply a subscription or create a schedule. Carry out work already authorized; do not ask for the same approval again. Keep any unsupplied destination or new action outside that scope clearly pending.

Save source IDs, versions, decisions, checked outputs and next owner in the project tracker. Before a retry, check the saved state and other workers’ changes. A model name does not guarantee memory or a running timer. Repeated work needs an actual configured trigger and durable state; one-off work can be started by the prompt above.

Keep agent media muted with volume zero before playback. If mute cannot be verified, use captions, metadata or still frames. State the limit: silent visual checks do not prove spoken-word accuracy or audio quality. Do not start sound through the user’s speakers unless explicitly asked.

## Write up the real run

For every actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this recipe and revision, trigger, steps performed, output evidence, measured result, gaps and next owner. Failed, blocked and partial attempts also get a written record. A draft can satisfy writing; publishing it follows the existing job scope.

Keep one stable execution ID across retries and edits. A separately scoped child task may have its own ID linked to its parent. Writing the parent’s meta record is part of that run, not an endless new chain. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains this distinction. Teaching examples are not real executions and must not enter the run count.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** Gate
- **Importance:** 5/5 `●●●●●` — frequency 3, revenue 5, gating 5 (ads/revenue path; unblocks a chain (access/plumbing))
- **Suggested previous station:** `set-up-digital-plumbing-pixels-tracking`
- **Suggested next station:** `claim-and-brand-facebook-page`
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Record only the property IDs, access and checks required by this task in the client register. Pass the verified result to the task that needs it.

## Model routing (same factory, any engine)

- **This task's lane:** `computer` — Logged-in UI (Meta Ads Manager, Descript, GSC, wp-admin when REST is blocked). Requires a supported browser tool and the right account access.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Maintained method: https://blitzmetrics.com/dollar-a-day/
- Source mapping needs reconciliation: the preserved `definitive_article: /dad` points to the coaching program. The method page above is `/dollar-a-day/`; this record does not certify the coaching page as a task recipe.
- Exact task: [Set up Meta Business Manager and Public Figure pages](https://local-service-spotlight.github.io/task-library/?task=set-up-meta-business-manager-and-public-figure-pages#task-set-up-meta-business-manager-and-public-figure-pages)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Dollar-a-Day method](https://blitzmetrics.com/dollar-a-day/)
- [Digital Plumbing training](https://blitzmetrics.com/digital-plumbing/)
- [Meta Facebook Page access](https://www.facebook.com/help/187316341316631)

## Review and evidence still needed

The source contributor status is preserved. It is not certification of this draft or proof of account access, completed work or a live outcome. The worked example teaches the method and is explicitly fictional.
- No actual Meta account was inspected or changed during authoring.
- Current interface labels and feature-specific verification requirements must be checked in the authorized account.