Meta agency access: business portfolio, Page and Pixel checklist

1. Map the assets before sending an invitation

Start with the business that will be advertised, not whichever portfolio happens to open first. Record the portfolio, advertising account, Page, Instagram profile and website event source the campaign is meant to use. Names can be similar, so compare identifiers privately as well as display names.

A useful handover sheet has one row per asset: its owner, the person authorized to approve access, the operating team, the required task and the result of the access check. Keep this sheet in your approved workspace, not in a public support post.

On a narrow screen, scroll the table sideways to compare.

2. Separate partner access from staff access

Treat adding a person and working with another business as different decisions. An employee’s individual access is not a substitute for an agreed agency arrangement. Before changing permissions, have the administrator and partner confirm which relationship, assets and responsibilities are intended.

Use the least access that supports the agreed work. Campaign operation, performance reporting, payment administration and managing other users are different tasks. A request for reporting should not quietly become permission to change administrators. If broader access is needed later, review that request separately.

• Identify the partner organization through your established contact.
• Agree the necessary tasks for each asset before choosing permissions.
• Keep ownership and the end-of-service handover arrangement in writing.

3. Have the authorized administrator review the assignment

Open Meta Business Suite or the business settings available to your account and confirm the selected portfolio. Have its authorized administrator locate the relevant people, partners and business assets, then inspect the permission summary for the exact recipient. Screen names vary between account interfaces; use Meta’s current help from within the product when a menu differs.

Review what the final confirmation will grant before submitting it. Confirm the recipient through a separate, trusted conversation if the request arrived unexpectedly. Do not send personal passwords, two-factor codes, recovery codes or browser sessions to an agency. Meta’s linked lessons may require sign-in; this guide is an operational checklist, not a claim that your account’s controls were tested.

4. Verify from the operator’s side

After the assignment, ask the intended operator to reopen the account using their own authorized access. Confirm that they can find the correct advertiser account and the intended Page or Instagram identity. If website events are in scope, also check the intended source and connection. One successful sign-in does not complete all these checks.

Use a draft or read-only review to establish whether the operator can perform the agreed tasks. Do not publish an ad or change spending simply to test a permission. Record missing assets individually so the administrator can correct one assignment instead of repeatedly adding broader access.

5. Diagnose the missing asset, not just the login

When something is unavailable, compare the asset, recipient and selected portfolio first. A Page problem, an ad-account restriction and an event-source problem require different checks. If the platform reports a restriction, review its stated reason and official review options; adding another user is not a way to bypass it.

On a narrow screen, scroll the table sideways to compare.

6. Keep permissions separate from measurement

Once access is correct, test the intended website action and inspect the receiving source. Being able to select a Pixel does not establish that the right event, value or currency arrives. Where browser and server integrations both report the same action, the implementation owner should verify deduplication before reporting results.

The administrator, media buyer and developer can be different people. Write down who is responsible for granting access, maintaining the integration and confirming the business result. Refer to the Pixel setup and conversion troubleshooting guides for the measurement checks rather than treating an access invitation as tracking certification.

7. Document the review and the exit

Keep the review date, asset list, intended operator and unresolved items. Revisit access when people leave or the scope changes. At the end of an engagement, first agree how reporting records and responsibilities will be handed over, then have the authorized owner review the permissions that should remain.

With AdsGorilla, the available platform access and campaign work depend on the agreed service. Confirm the arrangement during onboarding. Neither partner access nor an agency account promises approval, unrestricted delivery or ownership transfer.