Advertising Studio is retiring: moving your first-party ad audiences to Data 360

If your paid-media team pushes first-party audiences to Meta, Google, or Amazon through Salesforce, there’s a deadline on the calendar you can’t ignore: Marketing Cloud Advertising Studio is being retired in 2026 — the guidance circulating puts the cutoff after mid-August, with subscriptions non-renewable beyond that window. Verify the exact date against Salesforce’s own live retirement notice before you plan around it, because these dates move, but treat it as imminent, not theoretical. The audiences you activate for Customer Match and lookalikes today are running on a product with a clock on it.

The trap is assuming this is a rename you can absorb with a settings change. It isn’t. The replacement is Data 360 Ad Audiences, and Ad Audiences is not Advertising Studio with a new logo — it’s a different platform underneath. Different data model, a different identity layer, a different consent mechanism, and a destination list that doesn’t map one-to-one to what you have today. Teams that treat it as a like-for-like swap discover the gaps during cutover, which is the worst possible time. This post is what actually changes, the match-rate reality that surprises everyone, and a migration sequence that fits the runway you have left.

First, one disambiguation, because Salesforce retired two “Studio” products and people conflate them. Audience Studio was the third-party-cookie DMP, sunset earlier. Advertising Studio — the thing this post is about — is the first-party activation tool that pushes your CRM and Marketing Cloud audiences to the ad platforms. It’s the first-party one that’s moving to Data 360, and first-party is exactly the capability that still matters in a post-cookie world.

Why it’s a re-platform, not a migration

Advertising Studio lived in Marketing Cloud Engagement. Its audiences were built from Marketing Cloud data extensions and CRM data, in Marketing Cloud’s world, with Marketing Cloud’s identity and consent handling. Data 360 Ad Audiences lives in Data 360 — the platform formerly called Data Cloud — and inherits its model of the world. That single shift changes four things at once:

• The audience is now a Data 360 segment. You don’t recreate a Marketing Cloud audience; you build a segment on the Unified Individual — the identity-resolved profile — and activate it to an ad platform as a destination. The audience-building surface, the operators, the refresh model: all Data 360’s, not Marketing Cloud’s.
• Identity comes from Data 360 unification. Who counts as one person is now decided by your identity resolution match rules, not by Marketing Cloud’s subscriber model. Over-merge two customers upstream and they collapse into one audience member; under-merge and one person shows up as several. Your ad audience quality is now inherited from your unification config — which may be excellent, or may be something nobody’s tuned yet.
• Consent is enforced at activation. Data 360 carries consent and can suppress non-consented profiles as part of the activation itself. This is genuinely better than bolting consent on after the fact — but only if you’ve actually modeled consent in Data 360, which many orgs standing up Ad Audiences for the first time have not.
• It’s metered by consumption. Advertising Studio was a licensed capability. Ad Audiences activations run on Data 360 credits — segment rows processed, then activation — so a nightly push of a large audience is now a recurring meter, not a flat cost. Budget for it, and read the credit-optimization levers before you set everything to publish hourly out of habit.

None of these are dealbreakers. All of them are things you have to do, and none of them happen by pointing the old audience at a new button.

How activation to an ad platform actually works

The mechanics are worth understanding because they explain the one number that decides whether the whole exercise was worth it: match rate.

You build a segment on the Unified Individual, then activate it to an advertising destination — Meta, Google Ads (Customer Match) and Display & Video 360, Amazon Ads, LinkedIn, Snapchat, The Trade Desk, and data partners like LiveRamp are the commonly cited targets, though the exact supported list shifts, so confirm your specific destinations. On activation, Data 360 takes the identifiers on those profiles — email, phone — normalizes and hashes them (typically SHA-256) into the format each platform’s customer-match program requires, and sends the hashed keys plus any consent signal. The ad platform then matches those hashes against its own logged-in user base and builds the addressable audience. You never send raw PII to the platform; you send hashes, and the platform matches on its side.

That last step is where expectations meet reality. The match rate — the share of your audience the platform can actually find among its users — is rarely 100%, and is often meaningfully lower. A customer who signed up with a work email but uses a personal email on the platform won’t match on email. A hashed phone number in the wrong format won’t match at all. This isn’t a Salesforce limitation; it’s the physics of hashed-identifier matching, and it was just as true in Advertising Studio — but a re-platform is exactly when someone re-measures match rates, notices they’re lower than they assumed, and blames the new tool. Get ahead of it:

• Send more than one key where consent allows. Email and phone matches more people than either alone.
• Consider an identity partner for reach. Routing through LiveRamp’s RampID resolves fragmented first-party data to a durable identifier and generally lifts match into walled gardens and connected TV beyond raw hashed-email matching — at the cost of another vendor in the path. Whether that trade is worth it depends on your channel mix.
• Measure on a real sample before you cut over. Activate one representative audience to one destination, read the platform-reported match, and set expectations with the media team now — not after they’ve rebuilt their targeting on numbers that turned out soft.

The parity gap that bites during cutover

Here’s the specific thing that turns a smooth migration into a scramble: not every destination Advertising Studio supported exists in Data 360 Ad Audiences, and the ones that do exist can have different setup, different field requirements, and different capabilities. A destination you rely on today might not be a native Ad Audiences connector, or might route through a partner instead of directly.

So the very first migration task is not building anything — it’s an inventory and parity check:

1. List every active audience you push through Advertising Studio and every destination it goes to.
2. For each destination, confirm it exists as an Ad Audiences activation target and note any setup differences — auth, required identifiers, consent fields.
3. Flag any destination with no direct equivalent. Those are your risk items: they need a partner path (often LiveRamp), a different channel, or an explicit decision to drop them.

Do this first because it’s the step that can invalidate your timeline. Everything else is work you control; a missing destination is a dependency you don’t.

Business units, data spaces, and the multi-brand wrinkle

If you run multiple brands or regions and used Advertising Studio’s business-unit separation to keep them apart, that separation doesn’t carry over automatically. In Data 360 the equivalent boundary is a data space — the partition that decides who unifies with whom and what activates where. Multiple business units may mean multiple data spaces, and a segment activates within its data space. This is a modeling decision to make deliberately up front, because data spaces are a hard boundary you don’t cleanly reorganize later. If brand separation matters for your audiences, design the data-space layout before you build a single segment.

A migration sequence that fits the deadline

Working back from an imminent cutoff, the order matters more than the effort. Do it in this sequence:

1. Confirm the Data 360 foundation exists. Ad Audiences needs Data 360 provisioned with your customer data ingested, identity resolution running, and consent modeled. If that foundation is already in place from other use cases, you’re mostly wiring activation. If it isn’t, that’s the real project — Ad Audiences is a thin layer on top of a data foundation, and standing up the foundation is the part with the lead time.
2. Run the parity inventory (above). Resolve every destination gap to a plan before building.
3. Rebuild audiences as segments on the Unified Individual. Don’t lift-and-shift the logic blindly — a re-platform is a chance to consolidate the audience sprawl that accumulates in every marketing org. Nested, reusable segments beat fifty near-duplicates.
4. Wire consent into the activation, not around it. Confirm suppression of non-consented profiles happens as part of the publish.
5. Test match rates on a sample per destination, set expectations, and only then cut real spend over.
6. Model the credits on your real audience sizes and refresh cadence, and default to standard publish cadence rather than the most aggressive one — an ad audience that republishes far more often than the campaign spends is pure meter burn.

The teams that will be calm in August are the ones who started the parity inventory and the Data 360 foundation check early, because those are the two steps with real lead time. The audience rebuild itself is fast once the foundation and the destination plan are settled.

The strategic upside, not just a forced move

It’s easy to resent a forced migration, but there’s a real prize here if you take it. Advertising Studio activated audiences in a silo — a Marketing Cloud capability, somewhat apart from the rest of your data. Ad Audiences activates from the same unified profile your service agents ground on, your analytics measure on, and your personalization runs on. One definition of “high-value lapsed customer” can now drive an ad audience, a service priority, and a lifecycle journey at once, instead of three teams maintaining three drifting definitions. And with Segment Intelligence pulling campaign performance back into Data 360, you can close the loop — measure which activated audiences actually paid off — instead of firing audiences into the ad platforms and reading the results in a separate tool. That’s the version of this migration worth aiming for: not a like-for-like port of the old audiences, but consolidation onto one governed customer definition.

Takeaways

• This is a hard deadline, not a rename. Advertising Studio retires in 2026 (verify the exact date against Salesforce’s live notice) and the replacement, Data 360 Ad Audiences, is a different platform underneath.
• Audiences become Data 360 segments on the Unified Individual, with identity from your match rules, consent enforced at activation, and cost metered in credits — four real changes, none automatic.
• Match rate is the number that matters. Hashed-identifier matching is never 100%; send multiple keys, consider an identity partner for reach, and re-measure on a sample before anyone rebuilds targeting on assumptions.
• Do the parity inventory first. Not every Advertising Studio destination has a direct Ad Audiences equivalent, and a missing destination is the dependency that breaks timelines.
• Model business-unit separation as data spaces deliberately up front — it’s a boundary you don’t cleanly redo later.
• Take the upside. Activating from the same unified profile your agents and analytics use turns a forced migration into one governed customer definition across advertising, service, and personalization.