Keep Your Meta Custom Audiences (and Their IDs) When Ad Studio Stops

Most of the Ad Studio retirement conversation happens on the SFMC side: Data Extensions, automations, contracts, term-end dates. This post is about the other side of the pipe — the ad accounts — because that is where the assets live that you cannot rebuild by re-running an automation.

A custom audience sitting in Meta Ads Manager is not just a list of hashed emails. It is a list plus everything the platform has attached to it: the lookalike audiences seeded from it, the campaigns targeting it, the delivery optimization those campaigns have accumulated. Recreate the same list under a new audience tomorrow and the members match — but the lookalikes point at the old seed, the campaigns need re-targeting to the new asset, and the learning starts over. For a paid media team, "we rebuilt your audiences from scratch" is not a migration; it is a reset.

So the question that matters is precise: when your Ad Studio contract ends, what happens to the custom audiences it manages in your ad accounts — and what can you do beforehand so the answer doesn't matter?

What we know about disconnection behavior

Ad Studio's documented and observed behavior when an audience is suppressed on its side differs by platform, and the difference is instructive:

• Google Ads: the customer match audience remains in the ad account. It stops refreshing — no adds, no removals — but the asset survives, and campaigns targeting it keep running against an aging list.
• Meta, X, Snapchat, Pinterest: the linked custom audience is suppressed in the destination ad account along with the connection. The asset itself is at risk, not just its freshness.

What happens at contract expiry, as opposed to a deliberate suppression, is the kind of edge case we would advise no one to test with production lookalike seeds. Perhaps connections lapse gracefully everywhere and every audience is left orphaned-but-intact. Perhaps the teardown looks like suppression. The honest answer is that betting either way is unnecessary, because the defensive play costs a few hours and works in both worlds.

The defensive play: detach on your terms

The principle: an audience whose connection you break deliberately, before term end, is an audience whose fate you chose. Three steps, in order:

1. Retrieve every destination audience ID — now. In each ad account, for each Ad Studio–managed audience, record the platform's audience ID (in Meta Ads Manager: Audiences, the ID column; equivalents exist in each platform's UI or API). This belongs in column 9 of your migration inventory, and it is the single most valuable piece of data in this whole exercise: the ID is the asset's name in the platform's world, the thing lookalikes and campaigns actually reference. If you do only one thing after reading this post, do this.

2. Map what hangs off each audience. For each custom audience: which lookalikes were seeded from it, which active campaigns target it or its lookalikes. This tells you which audiences are load-bearing. A retargeting audience with three active campaigns and two lookalikes is a preservation priority; a test audience from 2023 is not.

3. Break the load-bearing connections before your term ends — once your replacement is ready to take over. Disconnecting from Ad Studio's side ahead of expiry, rather than letting the contract sever the link, is how you keep control of the sequence: replacement platform connected, audience re-attached, then the old connection removed. What you must not do is leave your most valuable audiences connected to a contract that is about to lapse and hope for graceful behavior. Note the timing implication: this is pre-term-end work by definition. After expiry there is nothing left to detach — whatever happened, happened.

Re-attaching: the difference between importing and rebuilding

This is where your replacement platform's capabilities decide whether the preservation work pays off. Two models exist:

Rebuild: the new platform creates fresh custom audiences from your Data Extensions. Clean, simple — and every lookalike must be re-seeded, every campaign re-pointed, every learning phase restarted. This is what a forced, post-expiry migration looks like, and (notably) Data Cloud Ad Audiences does not let you force an existing audience ID at activation — your existing assets are left behind by design.

Import: the new platform re-attaches to the custom audiences that already exist. Cezium Ads' Import Audiences feature was built for exactly this: it retrieves existing audience IDs from your connected ad accounts and lets you resume syncing your Data Extensions into those same audiences. Same ID, same lookalikes pointing at the same seed, same campaigns targeting the same asset — the only thing that changes is what feeds it. For the audiences where history matters most — Meta custom audiences under active lookalikes, Google customer match lists woven into Performance Max — this is the difference between a cutover the media team doesn't notice and a quarter of rebuilt campaign infrastructure.

The pre-term-end checklist

Before your Ad Studio term-end date, in order of urgency:

1. Record every destination audience ID, in every ad account.
2. Map lookalikes and active campaigns onto their seed audiences.
3. Rank audiences by what hangs off them — campaigns and lookalikes first.
4. Connect your replacement platform and re-attach the load-bearing audiences via import.
5. Break the old connections deliberately, highest-value first.
6. Only then let the contract lapse over whatever remains.

Total effort for a typical setup: a day or two, most of it in step one. Value preserved: every lookalike your acquisition program runs on, and every learning phase your campaigns have paid for.

Your Data Extensions were never in danger — they live in SFMC. Your custom audiences are a different story, and they are only yours to protect before the term ends. Get the IDs.

Frequently asked questions

Do Meta custom audiences get deleted when Ad Studio stops?

When an Ad Studio audience is disconnected, the linked custom audience is suppressed in the destination ad account on Meta, X, Snapchat, and Pinterest. What happens at contract expiry specifically shouldn't be left to chance — detach deliberately before term end instead.

What happens to Google Ads audiences after Ad Studio?

The customer match audience remains in the Google Ads account but stops refreshing. Campaigns targeting it keep running against a progressively staler list until you reconnect it to a new sync platform.

Do lookalike audiences survive an Ad Studio migration?

Only if the seed audience survives with the same ID. A rebuilt audience is a new asset — every lookalike must be re-seeded and every campaign re-pointed. Re-attaching by audience ID preserves lookalikes and campaign learning intact.

Where do I find a custom audience's ID?

In Meta Ads Manager under Audiences (the ID column); each platform exposes an equivalent in its UI or API. Record it for every Ad Studio–managed audience while the audiences still exist.

Book a demo of Import Audiences →