Opening Ads Manager and seeing reports does not mean you can fix billing, repair website events or remove an agency's access when its work ends. Before launch, identify who controls each asset, who does the daily work and who can handle a loss of access or a broken connection.
8 parts · 3 checkpoints
Show all 8 parts
- 01Understand the account, data, product and advertising jobs
- 02Check who can edit and recover each asset, has a checkpoint
- 03Assign access by job and retain trusted backup
- 04Keep evidence another person can use
- 05Find the right person for an asset problem, has a checkpoint
- 06Plan handover for the working relationship
- 07Run a short review and recovery exercise
- 08Save the handover for the next review, has a checkpoint
What the scale looks like: a store spending $18,000 a month had its payment method on the agency card with a $500 billing threshold, so when the contract ended and the card stopped, delivery stopped that day. The same week event match quality read 5.2 out of 10 because a theme update broke the dedupe key, so the pixel and the Conversions API each reported the purchase and the report showed 2.1 times the real orders. Both numbers are ownership questions, not bidding ones.
Note Do these three things today
- Walk the eight-item inventory below — business portfolio, ad account, Page, Instagram, dataset, catalog, domain, payment method — each with owner, day-to-day operator, and who can remove people. 2. Mark anything uncreated or unclear as "to set up" or "to confirm". 3. Name at least one person who can take over billing, events, and catalog access after an agency leaves, with a review date.
Key point Identify who can handle a problem
Ad-management access covers part of the work. The brand also needs people who can grant and remove access, handle billing and repair data sources over the long term. Check those permissions separately.
Our classroom example is a Shopify store selling insulated tumblers mainly in the United States. It is taking its Meta advertising back from a former agency: the brand has the ad account, while the agency still manages its website dataset and product catalog. It also needs someone responsible for billing and someone to handle Page messages and comments. This is a teaching scenario, with no measured ad results or promised recovery time.
If you are preparing your first ad, start by identifying the assets and mark anything not yet created as “pending setup.” One person can perform several jobs. An existing account or agency change needs the applicable access, evidence and recovery checks. You can study the next lesson before completing live account setup; verify the relevant conditions before connecting systems or spending money.
Understand the account, data, product and advertising jobs
Meta advertising uses several accounts and information sources. Once you know what each one does, it is easier to find the person and permissions needed to solve a problem.
Account control and authorization
A Business Portfolio groups people, partners and business assets such as ad accounts, Pages, datasets and catalogs for management. Older material may call it a Business or Business Manager. Employees sign in through their personal Facebook profiles and work with assigned access. The sign-in profile, business portfolio and ad account are different objects.
In this lesson, the controller is the responsible person who can inspect asset control, grant or remove access and use the recovery methods actually available. “The agency manages it” is not enough to identify that person. A platform access record also cannot settle every contractual or legal ownership dispute.
Website activity and event repair
A product view, cart addition or completed purchase can produce a ViewContent, AddToCart or Purchase event. The Meta Pixel sends activity from the browser; the Conversions API (CAPI) supports server-side reporting. A dataset organizes received event data. Theme code, Google Tag Manager (GTM, a tag-management tool) and Shopify apps may all contribute events.
The data lead must know where events come from, who maintains the connection and who can inspect diagnostics. Events appearing in the Pixel only show that some activity was received. They do not prove that purchase values are correct, duplicates were removed or the brand can edit the setup. A CAPI access token is a connection credential: record who manages it and its controlled storage location, not the token itself on this page.
Product information and updates
A Catalog organizes product titles, prices, availability, images and links. Its source can be an uploaded product-data file (a feed) or a Shopify sync. A product set selects part of the catalog through rules, such as available tumblers or gift bundles.
This store intends to advertise using catalog products. Someone must be able to repair its source, product sets and synchronization first. Sharing a catalog for an ad account to use does not automatically give the brand catalog-management control. The catalog checks here apply to ads using catalog products.
Advertising, brand identity and billing
The ad account supports ad creation, spending and reporting, with time-zone, currency and billing settings. A Facebook Page and Instagram account provide brand identity, profile information, comments and messages. A media buyer may build ads, support may reply to customers and finance may handle payment. Their access requirements differ.
The domain is the store's web address. Shopify access does not necessarily include permission to edit the DNS settings that connect the domain to the store, or to handle verification. Identify the technical contact separately. Payment settings also need checks for the default method, failed charges and billing contact; they are not the same asset as a personal sign-in profile.
Continue with the job you need to do
Schematic; your account's screen may differ
Use the job to find the responsible person. This schematic does not assert asset containment or show a real interface.
- Account authorization: who manages people, partners and recovery of access.
- Website data: who inspects the Pixel, dataset, CAPI and website event sources.
- Product information: who repairs catalog sources, product sets and stock synchronization.
- Advertising and identity: who runs ads, responds to people and handles billing.
The jobs overlap. A buyer may notice faulty purchase reporting while a technical lead traces the source. A wrong catalog price needs the person maintaining product data. Choose a responsibility below to see which evidence to locate first.
Find the records for each responsibility
- Ask first
- If the agency or an employee leaves, can the brand still authorize people, remove partners and handle recovery?
- Inspect
- The business portfolio, people, partners, business information and security settings.
- Retain first
- Keep the business ID, primary and backup admins, partner ID, access level, assigned assets and review date in a restricted record.
- If missing
- Loss of authorization can obstruct billing, agency changes, restriction appeals and handover. Being able to create an ad today does not prove recoverability.
- Ask first
- Who can investigate and repair event reporting, CAPI connections or duplicate purchases?
- Inspect
- Pixel, dataset, website domain, Shopify apps, GTM, theme code and the CAPI connection.
- Retain first
- Record dataset and pixel IDs, event sources, the CAPI lead, the latest Purchase event and diagnostics issues. Leave tokens out of the notes.
- If missing
- Ads may still run while event repair and later attribution checks are blocked. Reported returns then need further verification.
- Ask first
- Who can correct source data when a price, stock level, image or product set is wrong?
- Inspect
- Catalog, product source, feed, product-set rules, Commerce Manager (product and shop management), Shopify sync and diagnostics.
- Retain first
- Record the catalog ID, source, item count, product-set rules, responsible person and last update time.
- If missing
- Seeing catalog items does not mean you can fix prices or stock. Ads using the catalog continue to depend on those product facts.
- Ask first
- Who can build ads, read reports and change budgets, and who separately handles billing and people?
- Inspect
- Ad account and roles, budget, payment settings, billing contact, and Page/Instagram connections.
- Retain first
- Record the ad account ID, roles, time zone, currency, payment lead, available backup arrangement and current billing threshold.
- If missing
- A buyer's operating access does not prove that the brand can change cards, manage people or recover the account. Find the responsible person before a charge fails.
At the tumbler store, ad-account access answers only part of the handover question. With data and products still managed by the former agency, inspect authorization, repair capability and the arrangements after service ends. Test ad spend cannot prove those facts.
Two terms used in the checks
- Partner access
Access granted to an agency or contractor for specified business assets and work. This lesson recommends recording scope, an end or review date, and removal conditions. Writing a date does not end access automatically. If misread When service ends, inspect partner grants, individual people and related connections as appropriate; pausing ads alone does not finish offboarding.
- Return on ad spend (ROAS)
Revenue attributed to advertising divided by ad spend. Meta, Google Analytics 4 (GA4, website analytics), Shopify and finance records may use different dates, attribution, currencies and refund handling. Example: Recording account time zone, currency, data source and billing scope helps establish whether two return figures describe the same thing. ROAS is not profit or incremental sales caused by ads.
Check who can edit and recover each asset
Include the business portfolio, ad account, Page, Instagram account, dataset, catalog, domain and payment arrangements in the inventory. For each one, identify its current controller, daily access, recovery arrangements and evidence. An ad-report screenshot cannot establish that every asset has been handed over.
The brand in our example should first confirm who can manage people and billing, then have the data and product leads inspect the agency-managed assets. The panels below explain what to check for each asset. Mark a missing asset as pending setup rather than confirming it to complete a form.
Inspect an asset's control and recovery
- Check access
- Can the brand inspect business information, security, people and partners, with an authorized person able to grant and remove access?
- Retain
- The actual controller, admins, People, Partners, Security Center and business information shown in Business Settings, with a screenshot date.
- Prepare
- Verify trusted backup admins. Confirm the incoming person can enter before removing access no longer needed by employees or partners.
- Needs action
- Only an agency or former employee can manage access. Restore a brand-side authorization path you can verify before adding new spend.
- Check access
- Inspect ad creation, reports, people management and billing separately; one permission does not establish the others.
- Retain
- Account roles, status, time zone, currency, payment arrangements and billing lead, including reconciliation implications.
- Prepare
- For an established team, this lesson recommends two trusted brand-side admins for continuity, with their actual capabilities checked.
- Needs action
- Spend is live but only a departing person can edit billing. Arrange billing responsibility and trusted backup.
- Check access
- Who handles Page status, comments, messages, brand information, advertising identity and access grants?
- Retain
- The actual type and scope in Page access, brand name, status and responsible person.
- Prepare
- Separate long-term management, daily support and advertising work. Give full control to those who need long-term responsibility.
- Needs action
- Ads are running while Page restrictions or complaints have no owner. Assign handling and escalation, and hold creative that amplifies the dispute.
- Check access
- Check the Page and business connection, and who handles login, reauthorization and brand identity.
- Retain
- Account name, Page connection, business access and brand details. Keep login recovery arrangements private.
- Prepare
- Before removing an old connection, confirm its effect on active ads, the responsible person and the reauthorization method. Do not practice disconnection in production.
- Needs action
- Only one employee holds the account and the team cannot inspect access or recovery. Establish continued brand-side management.
- Check access
- Who can inspect events, assign connected ad accounts, trace sources, maintain CAPI credentials and diagnose duplicates?
- Retain
- Data-source controller, event sources, connected assets, CAPI custodian and diagnostics, without exposing a token in a screenshot.
- Prepare
- Assign data and technical leads. Recheck sources and Purchase reporting after a theme, app or connection change.
- Needs action
- An agency dataset is available for delivery, but the brand cannot repair it. Check sharing or other supported arrangements before deciding on a controlled rebuild.
- Check access
- Who edits product sources, product sets, catalog access and Commerce management settings?
- Retain
- Catalog controller, source, product-set rules, store/domain connection and recent update.
- Prepare
- Product and media leads maintain it together. Before promotions, inspect prices, stock and product sets, retaining the previous configuration.
- Needs action
- The agency manages the catalog and the brand can only see errors. Hold affected catalog-delivery plans until the product source can be repaired.
- Check access
- Who manages the domain, DNS, Shopify connection and any domain verification the current setup needs?
- Retain
- Domain-control record, applicable verification status, DNS/store-connection record and technical contact.
- Prepare
- Review after domain, theme or website-connection changes. Authorized technical staff handle any required DNS edit.
- Needs action
- A domain or connection changed but nobody updated the asset record. Confirm access and verification scope; restructuring ads does not repair it.
- Check access
- Who can add, update or switch payment methods under the actual billing permissions, and who handles failed charges?
- Retain
- Payment settings, default method, billing contact, failure notice and available backup rule, with card and sensitive information redacted.
- Prepare
- Finance and brand admins confirm the handling person, billing route and backup methods available to this account, avoiding reliance on one person.
- Needs action
- Ads are spending money, but nobody has a plan to handle billing problems. A successful charge today does not prove that someone can handle the next card change or failed charge.
If someone can read reports but cannot authorize or repair, do not mark the whole asset healthy. Record the missing action and the person who will resolve it. Transfer, release, sharing and rebuilding have asset-specific conditions. Do not assume every asset can be moved directly into a different business portfolio.
What comes first in an agency handover?
Self-check not answered
Use the same reasoning for catalogs, billing and Pages: establish the relevant capability before deciding on an advertising action. You do not need every asset to fail at once to start checking.
Assign access by job and retain trusted backup
Access should match the work. Media buyers need ads and reporting; support needs messages and comments. Giving everyone admin access makes it harder to decide what to keep or remove when responsibilities change.
Give people the access their work requires
| Role | Usually needs | Do not grant by default | Review when |
|---|---|---|---|
| Long-term brand lead | Applicable business-asset management, authorization and recovery capability, with trusted backup. | Avoid leaving the agency or a former employee as the only business-asset manager. | This lesson recommends monthly reviews, plus checks after entity, financing or major-market changes. |
| Media buyer | Ad creation and management, reports and budget management within the role. | Billing, asset transfer and people management need separate business reasons and authorization. | Responsibility changes, account issues or requests for extra access. |
| Support and social | Page and Instagram messages, comments and status handling. | Usually no ad-account admin or data-source edit access. | Staff changes, Page restrictions or escalating complaints and comments. |
| Agency or contractor | Agreed assets and actions, with an explicit end or review date. | Temporary work does not call for permanent, unrestricted management. | Service completion, contract change, agency switch or task completion. |
The person handling the tumbler store's shipping complaints needs message and comment permissions; there is no reason to grant ad-account admin access for that job. Facebook access to a Page can have full or partial control; task access covers specified jobs. Full control also permits management of other people's access. Check the actual business-asset permissions shown. Meta's Page-access explanation distinguishes these capabilities but cannot confirm this store's permissions.
This lesson recommends two trusted admins for an existing team, with two-factor authentication and recovery arrangements checked. It is a continuity recommendation, not a Meta requirement that every new merchant recruit two admins before learning. A solo merchant can identify single-person dependencies and recovery methods. Do not invite an untrusted person to finish a form or share login passwords.
Keep evidence another person can use
Evidence should answer a specific question. An ad report cannot tell the tumbler store who can repair its agency-managed dataset. Inspect the data source's management and grants, then record event sources and the technical lead. Each asset needs its name, actual page location, screenshot date, permitted actions and next review.
Use the five groups below. An ID identifies a particular asset. Keep IDs, business information and order or billing details in restricted team records. Use nonsensitive role labels and evidence references in this page's form, without real account identifiers, customer data, passwords, card numbers or tokens.
Organize the asset evidence
Inspect the business portfolio and people
Use current business settings to inspect people, partners, security, business information and assigned assets. Privately retain the business ID, legal business name, primary and backup admins, partner ID, access level, assigned assets, review date and recovery lead. Have the backup confirm that the record is findable; an agency's verbal assurance is insufficient for handover.
Inspect the ad account and billing
Check roles, status, time zone, currency, spending limits, default payment method, failed charges and invoices/receipts. Retain the account ID, payment and finance leads, applicable backup method, current billing threshold, issue date, and invoice or receipt reference and restricted storage location. A billing threshold concerns payment collection, not a budget cap or profitable spending level. Do not change currency, time zone or billing merely to make reports appear to agree.
Identify Page and Instagram responsibilities
Record the Page ID, Instagram handle, brand profile URL, current Page status, full-control lead and task-access list. Specify who checks status, replies to messages/comments, manages connections and handles escalation. Posting access does not establish coverage for every other job.
Inspect the Pixel, dataset and CAPI
Retain dataset and pixel IDs, connected assets, domain, event sources, the person managing CAPI credentials, the latest Purchase event and diagnostics issues. Carry event names, Event Match Quality and the deduplication key into the later technical check; that key helps identify the same event reported through two routes. This step identifies who can handle the work. Seeing activity does not verify event quality, and restoring a connection does not necessarily mean retrieving its old secret token.
Inspect catalog sources and product sets
Check catalog ID, access, source, item count, product-set rules, connected dataset, Commerce settings, Shopify sync, diagnostics and update time. Name who maintains the feed and who can restore the previous configuration. The people checking product identifiers such as GTIN, prices, stock and set rules will need this record. Retain the original source and connections before switching; creating a new catalog can affect the setup.
These groups support later event, product and financial checks. They do not guarantee a transfer, successful review or restored delivery. When access is unknown, record what is missing, who will investigate and which actions should wait. Do not fill the gap with an invented interface path.
If the dataset manager, CAPI lead or Purchase-event checks remain unconfirmed, do not treat platform ROAS as reliable. Continue the technical checks for event sources, values and deduplication in the next lesson.
Find the right person for an asset problem
Billing, Pages, events, products and domains need different people. Address active delivery stoppage, loss of control or inability to repair before adding spend and markets. The categories below help diagnosis; they are not a mandatory numbered sequence for every account.
First checks and responsible people for common problems
Failed payment or stopped spend
Inspect first: Account status, billing access, default method and failure notice.
- Retain
- Settings screenshot, notice and someone able to edit billing.
- Who handles it
- Finance and brand admin.
Page restriction or unanswered comments
Inspect first: Page access, actual status and support-task permissions.
- Retain
- Access screenshot, handling log and escalation arrangement.
- Who handles it
- Support, social and an authorized Page lead.
Events cannot be repaired or CAPI credentials are unmanaged
Inspect first: Dataset controller, event sources and technical access.
- Retain
- Events Manager diagnostics, sources and credential custodian.
- Who handles it
- Data and technical leads.
Catalog products cannot update
Inspect first: Catalog controller, source, product sets and Commerce access.
- Retain
- Feed source, settings, errors and update time.
- Who handles it
- Product and media leads.
Lost verification or store connection
Inspect first: Domain records, DNS and Shopify access.
- Retain
- Applicable verification, DNS and store-connection records.
- Who handles it
- Technical or operations lead.
A failed payment, for example, needs someone able to handle billing; changing targeting does not repair payment permissions. In these four classroom situations, choose the first action, then inspect its reason, evidence and work that should wait.
Choose the tumbler store's first repair
- Current situation
- Spend is live, the default method is nearing expiry, and the brand can only read reports with no reliable backup admin.
- Find first
- Payment settings, account roles, billing contact, backup lead and next review date.
- Hold this round
- Budget scaling, new markets and promotion launches until billing and continuity are arranged.
- Current situation
- The brand can see the Pixel and Catalog but cannot maintain event connections, CAPI credentials, product sources or sets.
- Find first
- Events Manager, dataset controller, Catalog settings, sources, product sets and people able to edit.
- Hold this round
- Affected catalog ads, bulk restructuring and high-budget tests; the old connection is not an established long-term recovery plan.
- Current situation
- Tumbler ads are live and buyers question shipping and quality. Support, social and media each assume another person is responsible.
- Find first
- Page access, Instagram connection, Page status, comment lead, response rule and review time.
- Hold this round
- Disputed creative, strong product claims and ads that amplify these problems, until customer complaints and connections are addressed.
- Current situation
- Portfolio, account, Page, dataset and catalog work, but partner access has no end arrangement and nobody scheduled a review.
- Find first
- One restricted evidence folder, controllers, permission table, partner end/review date and monthly review record.
- Hold this round
- A new teammate taking over scaling directly; first have them locate assets, evidence and the responsible people independently.
Repair the particular gap; one issue does not automatically require every business activity to stop. Decisions about existing delivery depend on affected assets, official status and the loss the business can afford. Avoid increasing related budgets or expanding the work while control remains unverified.
Plan handover for the working relationship
A working relationship changes who performs tasks. It should leave the brand with continued ability to manage its business assets. Agree on responsibilities, scope, end conditions and evidence location before assigning access.
The scenarios use RACI: R performs the work, A is accountable, C is consulted and I is informed. These are roles, not departments; one person can hold several. Identify who decides and who covers an absence for each job. Practise recovery with a written exercise or test assets, without casually removing production admins, disconnecting services or making test charges.
Choose a working relationship to examine
- Control and execution
- The brand manages the portfolio and core assets; internal media, support and technical roles perform the work, with trusted admins retaining authorization and recovery arrangements.
- Responsibilities
- R is each task's operator; A is the long-term brand-management lead with trusted backup; C is finance/product; I is incoming and reviewing teammates.
- When duties change
- Review access scope, evidence location and next review date that day. Remove unneeded access and avoid leaving recovery arrangements in private chats.
- Recovery practice
- Both trusted admins locate the permission record and explain, in a test situation, how to add an admin and find the first evidence for billing or a Page issue.
- Hold condition
- An existing team without trusted backup or an evidence location should not add budget or new-market work.
- Control and execution
- The brand manages core assets and grants project-scoped partner access. The agency performs delivery and reporting while the brand retains verification, authorization and removal routes.
- Responsibilities
- R is the agency; A is the brand-management lead; C is finance/product/technical; I is the incoming agency and internal reviewer.
- Before and after contract end
- Record the planned removal date, evidence due and unfinished work. Confirm brand and incoming-operator access first; review each asset afterward, rather than only pausing campaigns.
- Recovery practice
- Use a sample partner record to explain removal scope, then confirm that evidence for the account, Page, dataset and catalog remains findable. Authorized staff perform actual removal under a plan.
- Hold condition
- Without an end or review date, do not expand agency access or make the agency the only party able to handle payment or recovery.
- Control and execution
- The brand retains business control, grants access for defined creative/media/tracking work, and keeps deliverables and configuration records in team storage.
- Responsibilities
- R is the freelancer; A is the brand lead approving, reviewing and revoking access; C is technical/product; I is the next operator.
- Before the final working day
- Record deliverables, removal date, screenshot location and open items. Verify that login, billing and asset-management capability will remain when the person leaves.
- Recovery practice
- Without the freelancer's account, an internal admin uses the record to locate dataset, payment and Page handling routes.
- Hold condition
- Incomplete handover or one remaining recovery contact means holding new tests and bulk structural changes.
- Control and execution
- Find restricted evidence, verify business identity and core assets, then pursue access through supported official methods. Reassess delivery after trusted management is restored.
- Responsibilities
- R is the authorized evidence-gatherer and official-route operator; A is the brand business lead; C is finance, technical and business-identity record keepers; I is media/support.
- Act first
- Stop adding access and high-risk budget, and list former staff/agency access for review. Avoid removing the last usable route before understanding its role.
- Recovery practice
- Start from evidence location and identify who checks identity, handles admins within their authority and inspects payment or Page issues. Without access, use official recovery; complete documents do not guarantee success.
- Hold condition
- Do not restart affected scaling, catalog plans or new markets before recovery capability and trusted backup are confirmed.
In the agency handover, make a separate arrangement for the tumbler store's dataset and catalog. “Account handed over” hides those distinctions. Any retained sharing, changed grant or necessary rebuild needs scope, responsibility, verification and an original-configuration record.
The contract ends: remove the agency first, or confirm the new owner first?

As text: the whole walk-through
- Plan written First write the removal plan: the removal date, the evidence to hand over and what is still open.
- Agency removed first The agency is removed first, the new owner was never confirmed, and the last working path is gone.
- Plan written Back to before the removal to compare the other order. This is only a comparison, not a claim that a real removal can be undone.
- New owner in First confirm the new owner can really get in. Now both the old agency and the new owner can.
- Looks handed over Then remove the agency: the way in stays with the new owner and the handover looks finished.
- Assets checked Finally check the account, Page, dataset and catalog one by one; stopping the ads is not enough.
Illustrative: the old agency is assumed to be the only one who can handle payment and recovery. No dates are drawn.
Run a short review and recovery exercise
An existing team can use this 30-minute agenda. The time boxes organize the meeting; they are not Meta response deadlines or automatic proof of recovery capability.
An existing account's asset review
0–5 minutes
List assets and evidence locations
Open applicable portfolio, account, Page, Instagram, dataset, catalog, domain and payment records. Identify existing, pending-setup and unverified items.5–12 minutes
Confirm access and trusted backup
Separate viewing, editing, authorization and recovery. Confirm admins, partner scope and review dates, leaving a permission table the next person can understand.12–20 minutes
Choose the risk to address first
Consider billing, agency-managed data/catalogs, brand communication and missing evidence. Record one first action, responsible person, evidence and related work to hold.20–26 minutes
Rehearse the next event check
Locate the dataset manager, CAPI lead, diagnostics and test-order lead from the record. Explain the first response in a test situation; do not modify live tokens or payment settings to demonstrate ability.26–30 minutes
Set review and handover conditions
Schedule the next review. Staff/agency changes, failed payment, theme/domain changes, catalog re-uploads and connection changes trigger a check of affected assets and responsibility.
By the end, identify the current risk, the evidence to inspect first, the responsible person and the next action. Missing records do not automatically mean all ads must stop, but scaling should not be the default. For any small test, specify what is allowed, how much loss is affordable and when to stop. Testing a page, creative or offer cannot replace checking recovery access.
Before continuing work in an existing account
| Stop here | Go |
|---|---|
The brand cannot inspect, repair or remove access to critical assets controlled only by a former agency or employee. | Confirm applicable authorization and recovery arrangements, with a responsible person and evidence, before choosing related setup or delivery. |
| Evidence Current account permissions agree with the restricted team record rather than a verbal promise. | |
There is no trusted backup or person able to handle a payment problem. | Arrange backup management and a billing lead before adding spend or new markets. |
Dataset, catalog or domain works, but its controller, source or editing access is unclear. | Document sources and technical/product leads; hold affected setup and catalog plans. |
The form is complete, but nobody has checked actual access or rehearsed the response. | After control, backup, evidence and recovery are verified, continue the applicable event check. That is not approval to scale. |
Save the handover for the next review
Use the record for an existing-account handover, or practice with the classroom situation. New merchants need not mark nonexistent assets complete. Values stay in this browser unless exported. Enter nonsensitive role names and evidence references, without real account IDs, passwords, card numbers, tokens or customer personal data.
Selecting a scenario supplies a reference; it does not confirm the actual relationship. Fill the remaining fields from your situation. The verification date is when you checked the interface and access, not the day you read this lesson.
What the record still needs
No checkpoint finished in this lesson yet. Start with “Go to the exercise”.
Self-check not answered
Questions before you continue
- Which accounts and assets should I prepare for Meta advertising?
- Identify the business portfolio, ad account, Page, Instagram, Pixel/dataset, catalog, domain, billing and people access. Determine which apply to the intended ads. Mark missing assets pending setup; ads using catalog products need the relevant catalog preparation. Know who controls and handles issues for each applicable asset.
- How does a business portfolio differ from an ad account?
- A Business Portfolio manages business assets, people and partner access. The ad account manages ads, spend, reports and related time-zone, currency and billing settings. Access to one does not establish every permission on the other.
- Who should receive ad-account access?
- Long-term brand leads retain applicable management and recovery capability, with trusted backup recommended for existing teams. Assign media, support, technical and agency access by job, with scope, review dates and removal conditions. Billing and people management should not be automatic for everyone.
- Why include the Page and Instagram account?
- They carry ad identity, brand information and customer communication. Inspect status, comments/messages, connections and responsible people. Posting or ad-creation access does not establish that every other job is covered.
- What if the agency still controls the Pixel, dataset and Catalog?
- Privately establish identifiers, actual managers, sources, product sets and authorized people. Determine what can remain, be shared or be changed. If rebuilding is needed, plan verification and switching while retaining original settings. Do not assume the assets or history can move directly, or use test spend as proof of handover.
- What should I check for domains, billing and payment?
- Identify domain control, applicable verification, DNS and website connections. For billing, check permissions, default method, available backup, threshold and failure notices. Backup cards and payment options depend on the actual account; do not put card numbers or secrets in the lesson record.
- What comes first in the handover meeting?
- List assets, establish managers, trusted backup and partner scope, then select the risk to address with first evidence and held actions. Finish with event-check arrangements, review dates and triggers. Meeting time is not a platform recovery deadline.
- What makes the handover record useful?
- The next person can find the risk, access evidence, responsible lead, applicable recovery method, next action and review arrangements. Scattered chat screenshots are insufficient. Compare this record with restricted evidence and actual permissions; completion alone does not establish successful recovery.
Continue from the gap you found
You can continue studying with a pending-setup list. Before connecting real events, verify the dataset, technical lead and test-order arrangements. The next lesson works through the Pixel and Conversions API checks.