Text version of this lessonExpand
Meta Ads Basics / Lesson 1
Meta ads do not start with a campaign. They start with asset control. A Pixel held by an old agency, a catalog no one can edit, a Page with no owner, and no billing backup are not campaign-structure problems.
Lesson output: Meta asset control and recovery table
By the end of this lesson, you should be able to put Business Portfolio, ad account, Facebook Page, Instagram, Pixel / dataset, Catalog, domain, payment method, and people access into one table. The table should not only say whether an asset works today. It should show who controls it, who can grant access, who can recover it, where the evidence lives, and when it will be reviewed again.
| Field | What to record | Why it matters |
|---|---|---|
| Asset name | Business, ad account, Page, Instagram, Pixel / dataset, Catalog, domain, payment method | Prevents assets from being scattered across personal profiles, old agencies, or different Businesses |
| Current owner | The person or business that can control, authorize, transfer, and recover the asset | You know who can act when something breaks |
| Permissions and backup | Admins, partner access, backup admin, permission scope, review date | Employee changes, agency handoffs, and payment issues do not block the account |
| Screenshot evidence | Backend location, asset name, screenshot date, warning notice | Handoff, review, and recovery have verifiable proof |
| Recovery action | Who handles billing, Page, Pixel, Catalog, and domain issues | The team knows who to call before spend stops |
Plain terms: these are not backend decoration
- Business Portfolio: The Meta business container for ad accounts, Pages, Instagram accounts, Pixels / datasets, catalogs, partners, and people permissions. Think of it as the master folder for ad assets.
- Ad account: The place that holds delivery, billing, time zone, currency, invoices, and ad permissions. Currency and time zone affect later ROAS, refunds, and finance checks.
- Pixel / dataset: The onsite event signal source. Purchase, AddToCart, ViewContent, Conversions API, and Catalog ads depend on it.
- Catalog: The Meta asset that reads product data. Catalog ads, product sets, and Advantage+ Shopping use it.
- Partner access: Access granted to an agency, contractor, or partner. It should have scope, a review date, and removal rules. It should not stay forever by default.
Check asset by asset: who owns, edits, and recovers
The asset map is not for decoration. It exists so the team knows who can act when something breaks. Use this as a first version of your asset table.
| Asset | Control check | Screenshot evidence | Warning signal |
|---|---|---|---|
| Business Portfolio | Can the brand audit, grant access, remove people, and recover assets? | Owner, admins, Security Center, people access | Only an agency or former employee can change access |
| Ad account | Who can manage ads, view reports, edit payment method, and manage admin access? | Roles, time zone, currency, payment method, billing owner | The account is live, but only one person can edit billing |
| Page / Instagram | Who handles Page status, comments, messages, brand identity, and connection? | Page access, Instagram connection, brand name, status | Ads are live while Page restrictions or comments have no owner |
| Pixel / dataset | Who can view events, edit events, manage CAPI tokens, and diagnose duplicates? | Data source ownership, event source, CAPI token manager, diagnostics | Pixel is in an old Business, so the ad account can use it but cannot fix it |
| Catalog / domain | Who can edit product source, product sets, catalog permissions, domain verification, and site connection? | Catalog owner, product source, product sets, domain verification | Catalog belongs to an old agency, so product errors cannot be fixed quickly |
| Payment method | Who can add, update, or switch payment methods, and who handles payment failure? | Payment settings, default payment method, billing contact | No backup payment path while spend is live |
Permissions are not a trust issue; they are a recovery issue
Admin access should stay with long-term owners. Media buyers, support, social, creative, agencies, and contractors should get only the permissions they need, with a review date.
- Long-term brand owner: Keeps key admin or full control for Business, ad account, Page, dataset, and Catalog. Do not let an agency or employee personal profile become the only controller.
- Media buyer: Gets the permissions needed for ad management and reporting. Billing, asset transfer, and people-admin access should not be default.
- Support / social: Gets Page / Instagram message, comment, and status access. They usually do not need ad-account admin or data-source edit access.
- Agency / contractor: Gets only the project assets and action scope needed. Review and remove inactive partner access when service ends, contract changes, or agency handoff starts.
Asset risk router: fix the layer most likely to stop delivery
The asset table is not equal-weight work. Beginners often polish profile details first, but payment, backup admins, ad-account status, Pixel / dataset, Catalog, and domain ownership are what stop delivery or block recovery.
| Current risk | Priority | First fix | Blocked action |
|---|---|---|---|
| Payment fails, balance is unclear, or only one person can edit billing | Prevent delivery stop | Confirm ad account admins, billing owner, default payment method, and backup admin | Do not scale budget or launch a new market yet |
| Pixel, dataset, or Catalog is held by an old agency | Protect signal and product source | Confirm transfer path; if transfer is not possible, write the rebuild path, event window, and catalog switch boundary | Do not run catalog ads, restructure in bulk, or push high-budget learning yet |
| Page, Instagram, or comment handling has no owner | Stabilize the brand entry point | Separate who checks status, who handles messages, and who manages connections | Do not use disputed creative or strong claims yet |
| Assets work, but screenshots and review rhythm are missing | Document the handoff | Fill asset, owner, permissions, evidence, recovery action, and review date | Do not let a new teammate take over scaling directly |
20oz asset recovery lab: choose the asset risk, then choose the repair action
The same 20oz tumbler account may not have a campaign-structure problem. It may have no recoverable asset path. This exercise is not about memorizing backend entries. It trains the repair order: prevent delivery stop first, protect signal and product source next, stabilize the brand entry point, then document handoff evidence.
| 20oz scenario | First repair | Why | Hold this round |
|---|---|---|---|
| The ad account is spending, the default payment method is close to expiry, and only a former employee can edit Payment settings | Fix billing and backup admin first | Billing and admin access can stop delivery, so add someone who can edit payment, confirm billing contact, and keep screenshot proof | Budget scaling, new-market launch, and promotion campaign |
| Pixel and Catalog sit in the old agency Business; the brand can see them but cannot edit events, CAPI token, or product source | Confirm dataset / Catalog transfer or rebuild | This is signal and product-source recovery risk that can affect Pixel, CAPI, Catalog ads, and reconciliation | Catalog ads, Advantage+ Shopping, and high-budget learning |
| The Page has shipping and quality complaint comments, Instagram connection breaks sometimes, and no one is responsible | Assign Page / Instagram responsible lead | An unstable brand entry point can affect review, trust, comment handling, and ad-to-page continuity | Strong-claim creative, disputed creative, and scaling creative |
| Assets work, but screenshots are scattered in chats and partner access has no expiry date | Document screenshots, permissions, and review date | Being live today does not mean the next person can recover the assets; the handoff must be reviewable on its own | Letting a new teammate take over scaling directly |
If your first instinct is "launch a campaign and test anyway," pause. Being able to run ads does not mean assets are recoverable. When asset control is unclear, a test run can hide billing, signal, product-source, and brand-entry risks.
30-minute asset recovery meeting: do not move the problem into launch week
Close this lesson with a short working meeting. Do not use it to debate creative taste or campaign structure. Use it to answer one operating question: if the ad account, payment method, Pixel, Catalog, or Page breaks today, can the brand recover it without begging the old agency, finding a former employee, or searching old chat threads?
| Time | What to check | What must be left behind |
|---|---|---|
| 0-5 minutes | Open Business Portfolio, ad account, Page, Instagram, Pixel / dataset, Catalog, and payment method | Asset list and screenshot folder, not a verbal "we have access" |
| 5-12 minutes | Confirm controller, admin, backup admin, partner access, permission scope, and review date | Permission table that separates who can edit, who can only view, and who is a temporary partner |
| 12-20 minutes | Pick the highest-risk layer: billing, old-agency dataset/Catalog, Page/Instagram, or evidence packet | Top risk, first repair, held action, and acceptance proof |
| 20-26 minutes | Decide whether the next lesson can move into Pixel and Conversions API | Dataset control, CAPI token manager, event diagnostics entry point, and test-order responsible lead |
| 26-30 minutes | Write the next review date and review triggers | Next review date plus rules for staff change, agency switch, payment failure, theme rebuild, and Catalog re-upload |
If the team cannot produce this packet in 30 minutes, that does not always mean ads must be blocked. It means budget scaling is not ready. A small test can validate page, creative, and offer assumptions, but it cannot replace asset-control acceptance. The more spend and learning history the account collects, the more expensive recovery and reconciliation become when the asset layer is weak.
Four common misreads: easy today, expensive later
- Misread 1: the agency manages it, so the brand does not need to care. An agency can execute media work, but the brand must know who ultimately controls Business, ad account, Pixel, Catalog, and payment method. Otherwise the most valuable signal and product-source assets may not move with the brand when the agency changes.
- Misread 2: report access means control. Reporting access usually cannot fix billing, transfer assets, manage CAPI tokens, edit Catalog product source, or remove old partner access. The asset table must separate view access, edit access, grant access, and recovery access.
- Misread 3: launch now and clean permissions later. If payment fails, Page status changes, Pixel duplicates events, Catalog products are wrong, or domain verification is lost, late permission cleanup turns every diagnosis into a people search. The better order is to confirm the recovery path before asking the system to learn.
- Misread 4: screenshots in chat are good enough. Chat threads are not a handoff packet. Reviewable evidence needs a named folder, screenshot date, backend path, asset name, responsible lead, next review time, and review trigger.
All four misreads confuse "we can operate today" with "we can recover tomorrow." The earlier a Meta account moves into learning, Catalog ads, CAPI, and budget scaling, the more the asset recovery table acts like insurance. You may not open it every day, but when something breaks it determines whether the team recovers in half an hour or loses two days of delivery.
Agency handoff scenario: do not only ask for campaign screenshots
If you are taking Meta Ads back from an agency, do not only ask for campaign screenshots. Confirm whether the brand controls the Pixel / dataset, Catalog, Page, Instagram, domain, and payment method. If one critical asset is still controlled by the old owner, recovery, reconciliation, and scaling remain risky.
Add three fields to the handoff packet: current evidence, next allowed action, and boundary not to break. For example, do not scale budget before Pixel ownership is clear; do not run Catalog ads before product source access is fixed; do not launch a new market before billing backup is ready.
When to stop, and when to move to the next lesson
- Stop first: Critical assets are controlled only by an agency, former employee, or personal profile. Confirm or transfer control before building campaigns.
- Stop first: There is no backup admin and no recoverable billing path. Add a trusted admin, billing owner, and screenshot evidence.
- Add evidence: Pixel, Catalog, or Domain works, but ownership and edit access are unclear. Record owner, event source, product source, and technical owner first.
- Go: Core assets have clear ownership, at least two trusted admins, and a permission table with review dates. Then move to the next lesson: Pixel and Conversions API.
Official check paths
Meta interface names change, but the acceptance rule stays the same: critical assets must be auditable and controlled by the brand. Use Meta Business Help, Ads Manager Help, and official Page access, payment, currency, and time-zone help pages as public check paths.