Switching Meta ads agency: secure your pixel, ad account and data

Anyone who wants to switch their Meta agency usually cancels too early and finds out too late who actually owns the accounts. With Meta that’s trickier than with Google Ads: ad account, pixel, audiences and the server path of the Conversions API each belong to a business portfolio, and that isn’t automatically yours. This checklist separates the ownership questions from the actual handover. That way account history, audiences and measurement survive as far as possible.

For Google Ads I’ve described the handover under freelancer instead of an agency. With Meta, three particularities come on top: the ownership logic of the business portfolio, the learning phase of ad sets, and a measurement chain that often runs through the agency’s infrastructure.

1. Switching your Meta agency: first settle who owns what

Meta organises accounts through the business portfolio, which many people still know as Business Manager. Every asset in it has an owner. Other companies get access as partners. Exactly this distinction decides whether your switch becomes an admin task or a fresh start.

Ad account: owner or just agency?

Meta’s developer documentation distinguishes two types of access to an ad account: a business is either OWNER or AGENCY (Meta Marketing API, ad accounts). It also states that most marketing firms don’t need to claim their clients’ ad accounts at all. The clean normal case: the account belongs to your portfolio, and the agency works with agency access.

It gets critical when the agency’s portfolio is registered as the owner. According to the same documentation, a business cannot remove a confirmed ad account it owns from its portfolio. Only agency access or a still-pending request can be removed. The page doesn’t describe any way to transfer ownership to another portfolio. Claiming an account is also described there as a one-time action.

For you, that means: if your ad account sits in the agency’s portfolio, settle it with the agency and Meta support before you cancel. In the worst case you start in a new ad account, and then campaigns and ad sets begin without any history.

Pixel, or dataset

The pixel, called a dataset in newer interfaces, also has an owner. The API has a dedicated field for the business that owns the pixel, and a list of the agencies or businesses it’s shared with (Meta Marketing API, Ads Pixel). So sharing is built in, and sharing is something other than owning.

Why that matters: the pixel ID sits in your website or your Tag Manager container, and website audiences are rules on the events of one specific pixel (Meta, Website Custom Audiences). A new pixel means a new ID. The audiences are then built from that new pixel’s events, not from the old one’s history.

Audiences

Custom audiences are tied to ad accounts. Between two businesses they can only be shared if a partner relationship already exists between the portfolios. Sharing works in one direction only, the request needs admin rights, and the sharing side must have accepted the Custom Audiences terms (Meta, sharing custom audiences). Customer lists the agency uploaded ideally come from your CRM. Then you can rebuild them in your own account at any time.

Conversions API: token, Gateway, server container

The server path is the part most often overlooked in handovers. Check three places:

• Access token. The token for the Conversions API is generated in Events Manager. Only users with developer rights for the business see the link to do so, and the pixel can be assigned to a system user (Meta, Conversions API Get Started). Find out which portfolio that system user sits in.
• Conversions API Gateway. Meta describes the Gateway as an instance deployed in the business’s own cloud account, on AWS or Google Cloud. Updates are applied with the host admin’s approval (Meta, Conversions API Gateway). If the agency set it up in its own cloud account, the infrastructure lives there and not with you.
• Server container. If the Conversions API runs through a server-side Tag Manager container, the same question applies: whose hosting, whose invoice, whose domain? What’s behind it is in the article on server-side tracking.

The inventory at a glance

Asset	Where to look	Target state	Warning sign
Business portfolio	Business settings	You are admin, at least two people from your own company	Only agency staff are admins
Ad account	Business settings, ad accounts	Owner is your portfolio, agency as partner	Account sits in the agency’s portfolio
Pixel/dataset	Events Manager, data sources	Owner is your portfolio	Pixel only shared with you
Audiences	Ads Manager, audiences	Sit in your ad account	Sit in an agency account and are only shared
CAPI token	Events Manager, settings	System user in your portfolio	Token from an agency system user
Gateway/server container	Cloud account, Tag Manager	Runs in your cloud account	Hosting and invoice with the agency

2. The handover in the right order

The order matters more than any single measure. If you cancel first and then negotiate for access, you’re negotiating from the weakest position.

Step 1: Inventory, before anyone cancels

For every asset in the table, write down the ID, the owner, the partners and the people invited. Document campaign structure, active ads, audience definitions and optimisation events, for example by screenshot or export. Also note who is registered as the payer on the ad account. This list later becomes your handover record.

Step 2: Settle ownership, in writing

Everything that isn’t in your portfolio gets discussed now: ad account, pixel, Gateway, server container, domains. Get the commitments in writing, with a deadline. The same logic applies when choosing the next agency; the right questions for that are under questions to ask a Google Ads agency and carry over to Meta one to one.

Step 3: Bring in the new agency through your portfolio

Here’s a detail that slows down many handovers. Meta states that only the owner of an asset can grant access to it. For assets where a business is only the agency, it cannot pass access on (Meta, Business-to-Business). So the old agency can’t simply give the new one access to your account. You have to do that yourself as the owner: add the new agency as a partner and share the assets it needs.

Step 4: One cut-off date, one responsible party

Set a point in time from which only the new agency changes campaigns, budgets and events. Two parties working on ad sets and pixel events in parallel produce exactly the turbulence you want to avoid in section 3.

Step 5: Remove old access deliberately

Only once the new agency can demonstrably work and the measurement has been checked do you remove the old one. According to Meta, removing access is the same as removing an agency from your business. Besides partner access, also think of individually invited people and of system users. If a CAPI token ran through an agency system user, generate a new one in your portfolio, switch the server side over to it, and then check in Events Manager that the server events keep arriving.

Step 6: Get your data back

If the agency processed personal data on your behalf, such as customer lists for audiences, it is usually a processor. Under Art. 28(3)(g) GDPR, the contract must stipulate that after the service ends, the processor deletes or returns the data at the controller’s choice, unless there is an obligation to store it (GDPR, EUR-Lex). Actively request this, including local copies of CSV files. I’m not a lawyer; settle the details with your data protection officer.

3. Carrying the learning phase, audiences and measurement through the switch

Once ownership is settled, the question is what the platform has already learned. This is where switches lose the most for no reason, mostly through a rebuild nobody can justify.

Don’t reset the learning phase without a reason

Meta counts the conversions per ad set since the last significant edit. Such an edit sends the ad set back into the learning phase. The status then reads “still learning”, “learning phase complete” or “not enough results to exit the learning phase” (Meta, Learning Stage Info). Exactly which changes count as significant is something you should look up in Meta’s Help Centre at the time of the switch. I’m deliberately not repeating fixed thresholds from blog posts here.

Three rules for the first weeks after the handover:

• Keep working in the existing account. New ad sets in a new account start without the conversions your existing ones have already collected. A rebuild needs a reason of its own.
• Stagger changes. If the new agency wants to rework structure, creatives and optimisation event, do it one after another and document it. Otherwise you can neither attribute the effect nor trace why an ad set is learning again.
• Watch the learning status. After every larger change, check in the delivery column whether the ad set is learning again, and only judge performance after that.

Keep audiences or rebuild them

If the pixel stays with you, things are relaxed. New website audiences can use prefill to include website activity recorded before they were created, according to Meta’s documentation up to 180 days back (Meta, Website Custom Audiences). You re-upload customer lists from your CRM, and rebuild lookalikes on the sources in your own account.

If the audiences sit in an agency ad account, you can only get them shared through a partner relationship. Shared doesn’t mean transferred. So plan from the start to build your most important audiences in your own account, rather than relying on a share that can end when the contract does.

Check the measurement chain after the switch

After the cut-off date, check the measurement as if it were new. The check usually takes less than an hour:

• In Events Manager, use “Test events” to run through a real conversion path: submit a form or make a test purchase.
• Check that browser and server events arrive with the same event ID, so Meta doesn’t count twice. The mechanics behind it are in the article on Meta Pixel setup.
• Check that the pixel only fires after consent. An agency switch is a good occasion to review the consent setup as well.

The free tracking check shows you in a few minutes which trackers and which consent tool are installed on your website. Whether the events arrive correctly at Meta is then settled by the test in Events Manager.

If you’re still looking for new support: how to recognise real Meta experience is something I’ve written up under how to spot a senior social ads freelancer. The first question there is the same as here: how is the tracking built, and who owns it?

Conclusion

• Ownership before cancellation. Check whether ad account, pixel, audiences, CAPI token and Gateway belong to your business portfolio. According to Meta’s documentation, an owner can’t simply remove a confirmed ad account from its portfolio, so this question belongs right at the start.
• You grant access yourself. Only the owner can share assets with the new agency. The old agency can’t do that for you.
• One cut-off date, one responsibility. No parallel changes by two providers to ad sets and events.
• Keep the history. Keep working in the existing account, stagger changes and watch the learning status, instead of rebuilding everything.
• Get the measurement chain and data back. Issue new tokens, test server events, have customer data deleted or returned under Art. 28 GDPR.