X and Pinterest Audiences After Data Cloud: The Destinations Left Behind
Somewhere in the middle of every Data Cloud Ad Audiences migration, the same meeting happens. The segments are rebuilding nicely, Meta and Google are connected, and then someone from the media team asks the question that stops the room: "Where do the X audiences go?"
The answer is nowhere, because Data Cloud Ad Audiences does not activate to X. Or Pinterest. Or TikTok. Its destination list is Meta, Google, Snapchat, Amazon Ads, and LinkedIn. Advertising Studio — the retired product — actually covered X and Pinterest natively. The designated successor covers neither, and it never added the channel every B2C media plan has spent five years adopting.
This post is for the teams mid-migration or post-migration who have discovered the gap, and for the teams still planning who would rather discover it here than in that meeting.
What the gap means in practice
If you run active Ad Studio audiences on X or Pinterest today, a migration to Data Cloud Ad Audiences strands them twice over.
First, there is no pipe. No activation connector means no syncs: no refreshes, no adds, no removals, no suppressions on those platforms, from the moment your Ad Studio term ends.
Second — and this is the subtle one — the existing destination audiences can't be re-attached later. Data Cloud Ad Audiences does not let you force an existing audience ID at activation; it creates its own audiences in the platforms it does support. So even if a connector shipped someday, the custom audiences you built over years on X and Pinterest, and anything seeded from them, would not be the audiences it fills.
The workaround Salesforce's ecosystem proposes is the one you would expect: work with your system integrator on an external activation — typically Data Cloud exporting segments to an S3 bucket, then a scheduled or manual upload into each ad platform. It functions. It is also precisely the hashed-CSV routine that audience activation software was invented to eliminate, now reintroduced at the end of a six-figure migration, with its own failure modes:
- Upload cadence — audience freshness is only as good as the export schedule.
- File format drift per platform, each with its own matching spec.
- Consent flags traveling in spreadsheets instead of governed pipelines.
- One more custom pipeline whose owner can leave the company.
TikTok deserves its own paragraph
X and Pinterest are about protecting what you have. TikTok is about the growth you are forgoing. Ad Studio never supported it; Data Cloud Ad Audiences doesn't either — which means an organization can complete the full recommended migration, platform and credits and Data Spaces and all, and still be unable to push a first-party audience to the acquisition channel their media agency asks about first. For fashion, beauty, retail, entertainment — the industries where SFMC is everywhere — that is not an edge case. It is the media plan.
The architecture that closes the gap: two activation layers, one source of truth
Here is the thing the all-or-nothing framing misses: activation layers are not exclusive. Your consented, segmented first-party data can feed more than one pipe, and the sane architecture for a post-Ad-Studio, Data-Cloud-committed organization is often exactly that:
- Data Cloud Ad Audiences carries the destinations it supports, for the segments already rebuilt there — Meta, Google, Amazon, LinkedIn, Snap.
- An AppExchange activation layer — this is where Cezium Ads lives — carries the destinations it doesn't: X, Pinterest, TikTok, LINE. Cezium reads standard Data Extensions inside SFMC, so the same source data, the same consent fields, and the same suppression logic feed both layers; and its Import Audiences feature re-attaches to your existing X and Pinterest custom audiences by ID, so nothing built over the years is abandoned.
One source of truth, two pipes, full destination coverage, no CSV in sight. The overlap costs nothing on the Cezium side — consumption pricing means you pay for audiences actually pushed — and the coverage question disappears from your QBRs.
Two honest notes, since we are a party in this comparison. If your X and Pinterest usage was a low-stakes experiment, a workaround or even a wind-down may genuinely be fine — not every audience deserves an architecture. And for organizations that want Data Cloud segments themselves flowing to the missing destinations, Data Cloud as a Cezium source is on our roadmap; today the bridge is the Data Extension layer both systems already share.
If you're mid-migration right now
Three moves, in order:
- Inventory your X and Pinterest audiences today — source Data Extensions, refresh settings, and above all the destination audience IDs from each ad account. Those IDs are what make re-attachment possible, and they are only retrievable while the audiences exist.
- Do not let the Ad Studio term lapse over those connections — detach deliberately, on your schedule, with the IDs recorded.
- Then decide whether each audience earns a second activation layer, a workaround, or retirement — as a media decision, not a default inherited from a destination list nobody read closely.
The retirement of Ad Studio was Salesforce's decision. Which channels your first-party data can reach should still be yours.
Frequently asked questions
Does Data Cloud Ad Audiences support X (Twitter)?
No. Its destination list is Meta, Google, Snapchat, Amazon Ads, and LinkedIn. X audiences from Advertising Studio have no native Data Cloud activation path.
Does Data Cloud Ad Audiences support Pinterest or TikTok?
No to both. Pinterest, which Ad Studio covered natively, and TikTok, which no Salesforce advertising product has ever supported, are absent from the destination list.
What's the workaround for unsupported destinations?
The commonly proposed route is an external activation — Data Cloud segments exported to an S3 bucket and uploaded to each platform, usually with a system integrator. It works, but it recreates the manual CSV routine with its freshness, format, and ownership risks.
Can I run Data Cloud Ad Audiences and another activation platform together?
Yes. Both can feed from the same underlying data — an AppExchange layer like Cezium Ads reads the same Data Extensions and consent fields, covering X, Pinterest, TikTok, and LINE while Data Cloud carries its supported destinations.
Ready to transform your CRM audience activation?
Join marketers who've simplified their workflow with Cezium Ads