Activate Data Extensions and Journey Audiences Without Data Cloud

The short answer, since this is the question that brings most readers here: yes — Salesforce Marketing Cloud audiences can be activated to ad platforms without a Data Cloud license. Data Extensions and Journey Builder audiences are sufficient sources on their own. Cezium Ads reads them directly inside SFMC, hashes PII inside Salesforce, and syncs the result to twelve ad platforms: Meta, Google, TikTok, X, Snapchat, Pinterest, LINE, LinkedIn, Amazon, Microsoft, ChatGPT, and Spotify.

This post is the precise version of that answer: which inputs are supported, how refresh actually works, what you need before setup, and — just as importantly — what this approach deliberately does not do.

Supported inputs

Data Extensions — any type. Cezium takes the Data Extension as an input regardless of how it was produced or where it lives:

• Standard Data Extensions, built by imports, automations, or SQL queries.
• Filtered Data Extensions, produced from filter activities.
• Shared and synchronized Data Extensions in Enterprise 2.0 setups — a DE shared from the parent Business Unit works as an audience source the same way a local one does.
• Parent-BU or child-BU Data Extensions alike; audiences built on them are then managed per Business Unit (the multi-BU operating model has its own post).

If it's a Data Extension your team can see in SFMC, it can feed an audience. There is no separate "audience-ready" format to produce and no requirement to restructure existing DEs — the data model you already run is the data model Cezium reads.

Journey Builder audiences. Journeys are a live source, not an export: contacts moving through a journey can be streamed to the ad platform as they hit the relevant step — added to an audience on entry to a step, removed on exit or conversion. And unlike Advertising Studio, where a journey-created audience stayed locked to the journey that created it, any active audience can be attached to or removed from any journey, and reused across destinations.

Multi-source audiences. A single audience can combine several sources — multiple Data Extensions, Journey audiences, or both — and push to any combination of the twelve destinations. One audience definition, several inputs, several outputs.

How refresh works

Two models, matched to the two source types:

• Journey audiences stream. Contacts flow to the destination platform as journey events happen — there is no schedule to configure and no batch to wait for.
• Data Extension audiences refresh on schedule, minimum daily — and can be refreshed manually at any time. A daily automatic cadence covers the standard cases (suppression lists, retargeting pools); the manual refresh covers the moments that can't wait, like pushing an updated exclusion list an hour before a campaign goes live.

In both cases, removals propagate as well as additions: contacts leaving the source DE or exiting the journey leave the destination audience on the same mechanism.

Prerequisites

Setup deliberately requires little:

• An SFMC administrator, to install the AppExchange package and connect the Business Unit(s).
• Ad account administrators for each destination platform, to authorize the connections (OAuth — no credentials stored).

That's the setup cast. After that, day-to-day usage is managed with per-role permissions inside Cezium — who can create audiences, who can push to which destinations — so the admin pair is needed once, not weekly. One field-tested tip: make the platform connections with a dedicated service user rather than a personal login, so a departure never kills a pipeline.

What is deliberately out of scope

This approach activates the data SFMC already has. It does not attempt to be a CDP, and the boundary is worth stating plainly:

• No identity resolution. If the same person exists in three DEs under three emails, they are three records. Unifying them is Data Cloud/CDP work.
• No warehouse or zero-copy sources. Snowflake, BigQuery, Databricks tables are not inputs today; the source layer is SFMC. (Data Cloud segments as a source is on our roadmap for teams that run both.)
• No unified profiles or cross-source scoring. Cezium pushes the audiences your team defines; it doesn't compute new ones.

If your organization needs those capabilities, that's a real CDP requirement and worth its own evaluation. If what you need is your existing Data Extensions and Journeys reaching your ad platforms — the thing Advertising Studio did, now in run-off — a CDP is not a prerequisite for it, whatever the migration proposal on your desk implies.

Frequently asked questions

Can I sync SFMC audiences to ad platforms without Data Cloud?

Yes. Data Extensions (any type, including filtered and shared DEs) and Journey Builder audiences activate directly to twelve ad platforms via Cezium Ads, with no Data Cloud license, no data restructuring, and PII hashed inside Salesforce before transfer.

How often do audiences refresh?

Journey-based audiences stream in real time as contacts move through journey steps. Data Extension audiences refresh automatically on a schedule (minimum daily) and can be refreshed manually at any moment.

Do shared Data Extensions work in Enterprise 2.0?

Yes. Cezium takes the Data Extension as an input no matter its type — local, filtered, shared, or synchronized — and audiences are then managed per Business Unit.

What do I need to set it up?

An SFMC admin (package install, BU connection) and the admin of each ad account (OAuth authorization). Ongoing usage is then governed by per-role permissions inside the app.

What can't this do?

Identity resolution, warehouse/zero-copy sources, and unified profiles are out of scope — those are CDP capabilities. This is audience activation for the data SFMC already holds.

See your own Data Extensions as live audiences — book a demo →