How to Inventory Your Ad Studio Audiences When There's No Export Button
Every Ad Studio migration — to Data Cloud Ad Audiences, to Cezium Ads, to a CDP, even to a spreadsheet-and-CSV routine — begins with the same task, and the task begins with the same unpleasant discovery: Advertising Studio has no export function for its own audience list.
After a decade in production, the product that pushed your audiences to Meta and Google every day cannot hand you a table of what those audiences are. There is no extract, no API endpoint for the configuration, no report. If you want to know what you are running, someone has to open each active audience, one by one, and write down what they see.
This post is the method for doing that well, because the inventory is the critical path of your entire migration. Done properly, it turns the cutover into execution. Done badly — or skipped — it is how audiences get lost, suppressions silently die, and someone discovers in February that a churned-customer exclusion hasn't refreshed since the contract lapsed.
Why the inventory is the whole game
An Ad Studio audience is never just an audience. Behind each one sits a small assembly of SFMC components: a source Data Extension, filtered to the media team's spec and to the customer's consent for audience sharing; usually an automation that refreshes that Data Extension on a schedule; the refresh settings on the audience itself; and a destination — a specific custom audience, in a specific ad account, on a specific platform.
Your future platform needs all four pieces to reproduce the audience faithfully. The Data Extension and automation live on in SFMC regardless of what happens to Ad Studio — but the mapping between them and the ad accounts exists only in Ad Studio's UI and in your team's heads. The inventory is the act of getting it out of both while you still can.
The 11 fields to capture for every audience
For every active audience, record:
- Audience name — as shown in Ad Studio.
- Source Data Extension — the exact DE feeding it.
- Data Extension folder path — trivial to note now, painful to reconstruct later. Ad Studio won't tell you where the DE lives; a tool like SFMC Companion will find any DE in your instance from three typed letters, and will save you hours here.
- Refresh settings — one-shot or scheduled, and at what frequency.
- Refreshing automation — the automation (if any) that rebuilds the source DE, and its schedule. At migration time you generally keep these untouched; you need to know they exist so nobody "cleans them up."
- Segmentation criteria — the filter logic that defines the audience, in business terms.
- Consent field — which field carries the audience-sharing consent flag. This must survive the migration exactly; it is your compliance posture.
- Destination platform and ad account — which network, which account ID.
- Destination audience ID — the custom audience's ID in the ad platform itself, retrieved from the ad account. This is the field that lets you keep your existing custom audiences (and the lookalikes seeded from them) instead of rebuilding from zero. Most teams skip it. Don't.
- Business purpose — retargeting, suppression, lookalike seed, journey step. One honest sentence. This is how you will decide, later, what migrates first and what doesn't migrate at all.
- Owner — the human who can answer questions about it in six months.
Three traps in the clicking
Error-state audiences are not dead audiences. An audience showing an error might simply have failed its most recent send while remaining, for all business purposes, active. If you inventory only the green rows, you will drop live audiences. Go through the errors too, and record why each is erroring — some of those answers will save you from migrating problems along with audiences.
Journey Builder audiences don't appear at all. Audiences created by ad activities inside Journey Builder are invisible in the Ad Studio audience UI — there is no way to find them from Ad Studio's side. You have to come at them from the other direction: go through your journeys, find every ad activity, and record it in a separate tab of the inventory with the journey name and step. If your organization uses journey-based advertising, this tab is where the migration surprises live — and where the rebuild options need the most thought.
The inventory ages. An inventory from last quarter is a historical document. Do it close to your migration window, or assign an owner to keep it current. The good news: the second pass is fast, because the structure already exists.
How long it takes
From the migrations we have run and supported: budget two to three person-days per hundred audiences for the SFMC side — audiences, source DEs, automations, filters. A 40-audience setup is a solid day of focused clicking. A 300-audience, multi-BU setup is a real week and should be split by business unit, each BU inventoried by someone who knows its data.
That number is also your argument for starting now rather than "when the migration starts." The inventory needs no decision, no budget, no vendor, and no change to anything running. It is pure option value: whatever platform you choose later, whoever runs the project, this document is the first thing they will ask for.
The template
We maintain a free inventory template with all of the above — the eleven columns, a separate tab for Journey Builder ad activities, and a worked example row — as part of the Cezium Migration Kit. It is deliberately platform-neutral: it describes your Ad Studio setup, not our product, and it will serve you identically whether you land on Cezium Ads, Data Cloud, or anything else.
We would obviously like you to land on Cezium Ads — not least because our Import Audiences feature consumes column 9 directly, re-attaching your existing destination audiences instead of rebuilding them. But that is a decision for after the inventory. First, find out what you actually have. There's no export button, so bring coffee.
Frequently asked questions
Can you export the audience list from Advertising Studio?
No. Ad Studio has no export function, no configuration API, and no report of its own audiences. The only way to list them is manually: open each active audience and record its source, settings, and destination.
How long does an Ad Studio audience inventory take?
Budget two to three person-days per hundred audiences for the SFMC side — audiences, source Data Extensions, automations, and filters. Multi-BU setups should be split so each Business Unit is inventoried by someone who knows its data.
How do I find the Data Extension behind an Ad Studio audience?
Ad Studio shows the source DE but not its folder path. A search tool such as SFMC Companion locates any Data Extension in your instance from a few typed letters, which turns a tedious hunt into seconds per audience.
What about audiences created in Journey Builder?
They don't appear in the Ad Studio audience UI at all. Walk your journeys, find every ad activity, and record them in a separate inventory tab with journey name and step.
Ready to transform your CRM audience activation?
Join marketers who've simplified their workflow with Cezium Ads