Advertising Studio
Advertising Studio is the Salesforce Marketing Cloud product that synchronises CRM audiences with major advertising platforms, primarily Meta (Facebook and Instagram), Google, LinkedIn, X, and YouTube.
Definition
Advertising Studio is the Salesforce Marketing Cloud product that synchronises CRM audiences with major advertising platforms, primarily Meta (Facebook and Instagram), Google, LinkedIn, X, and YouTube. It lets marketers push segmented lists of contacts to those platforms as Custom Audiences, Customer Match audiences, or Matched Audiences, then run paid ads that target only those people. Advertising Studio also handles audience suppression (excluding existing customers from acquisition campaigns), lookalike modelling, and CRM-driven retargeting based on Marketing Cloud Engagement journey state.
The product has been rebranded several times. It started as Active Audiences, became Advertising Studio in 2016, and is now folded into Marketing Cloud Advertising while overlapping with Data Cloud Activations. Older contracts still see the label Advertising Studio in their orgs and Help docs. Functionally the same workflow underpins all the names: pull an audience from Marketing Cloud, hash the identifiers, push to the ad platform, and refresh on a schedule so the ad audience reflects the current Marketing Cloud segment.
How Advertising Studio connects CRM data to paid media
The supported ad platforms and what each one receives
Meta receives Custom Audiences as hashed email, hashed phone, mobile advertiser ID, and a few demographic flags. Google receives Customer Match audiences as hashed email and Google Click ID where available. LinkedIn receives Matched Audiences keyed on email. X and YouTube use similar hashed-identifier formats. The audiences are uploaded over the platform's API; Salesforce manages the credentials and the refresh cadence.
Audiences and Audience Builder
Inside Advertising Studio, an Audience is a saved query against Marketing Cloud Engagement Data Extensions or Salesforce CRM data. Audience Builder is the visual query designer that lets a marketer combine Data Extensions, contact attributes, and behavioural data into a target population. The audience is the contract between Marketing Cloud and the ad platform; the same audience can be published to multiple platforms in parallel.
Suppression versus acquisition audiences
Two patterns dominate Advertising Studio. Suppression audiences exclude existing customers from acquisition campaigns so the ad budget is not wasted on people who already converted. Acquisition audiences (typically Lookalikes built from existing customers) target new prospects who resemble high-value accounts. Most paid media stacks use both: a positive Lookalike audience plus a negative suppression of current customers.
Identity hashing and match rates
Salesforce hashes every personal identifier before sending it to the ad platform. The ad platform then matches the hashes against its own user base. Match rates of 40 to 70 percent on hashed email are normal; the rest are users without a matching identifier on the destination side. Phone-plus-email together usually pushes the match higher. Match rate is set by the destination, not by Advertising Studio, and is not a defect of the connector.
Journey-triggered ad steps
Inside Journey Builder, an Advertising Audience activity lets a journey add a contact to an ad audience as part of the path, or remove them on exit. This is the pattern behind multi-channel re-engagement campaigns: email opens trigger an entry into the journey, the journey emails the contact twice, and if neither email is opened, the journey pushes the contact into a paid retargeting audience. The journey state is the trigger; Advertising Studio is the bridge to the ad platform.
Web and Mobile Analytics Connect
Advertising Studio also brought engagement events back the other way for a time. Web and mobile analytics traces, Google Analytics integrations, and pixel-based events flowed into Marketing Cloud as Data Extensions, which could in turn build new audiences. This loop is gradually moving to Data Cloud, but legacy implementations still rely on Advertising Studio's analytics connectors.
Lookalike modelling
Most ad platforms support Lookalike or Similar Audience modelling: feed in a seed list, the platform returns a much larger audience of users who resemble the seed. Advertising Studio orchestrates this by uploading the seed audience and configuring the lookalike request. The actual modelling happens on the destination platform. Salesforce only owns the seed and the publish cadence.
Advertising Studio's future under Data Cloud Activations
Salesforce is consolidating Advertising Studio capability into Data Cloud Activations. New customers typically land on Data Cloud Activations directly. Existing Advertising Studio customers are not forced to migrate yet but should expect the feature surface to shift over time. The fundamental shape (audience, destination, schedule, hash, push) stays the same; the configuration surface and licensing get unified under Data Cloud.
How to publish an audience through Advertising Studio
Publishing an audience is straightforward once the platform connectors are configured. The slow part is making sure the source data and the privacy posture are right before any data leaves the org.
- Connect the ad platform
Inside Marketing Cloud Setup, configure the Advertising Studio connector for each destination platform (Meta, Google, LinkedIn, X, YouTube). Each connector needs an admin from the ad platform to authorise the OAuth handshake.
- Build the source audience in Audience Builder
Combine Data Extensions and attributes into the target population. Validate the count against expectations; surprise counts usually mean a join error in the source query.
- Choose hashed identifiers and consent attributes
Select which identifiers (email, phone, mobile ID) Salesforce should hash and send. Include any consent flags the destination requires.
- Publish to one or more destinations
Push the audience to each connected platform. Each platform handles refresh on its own match cycle; Advertising Studio just keeps the source list current.
- Schedule a refresh and monitor match rate
Set a recurring refresh that matches the destination's match window. Check the match rate after first publish; a sudden drop usually means upstream data changed.
Authenticated link to the destination ad platform.
The Marketing Cloud query whose result is published.
Email, phone, or mobile ID prepared in the format the destination expects.
The label on the ad platform that the audience publishes as.
How often the audience is republished.
- Match rates of 40 to 70 percent on hashed email are normal. A low match rate is rarely a connector defect; it is the destination's own identity coverage.
- Hashed identifiers are one-way. Once sent, you cannot recall the data; only stop refreshing. Plan governance before the first publish.
- Consent flags are mandatory on most platforms now. Publishing without a documented consent attribute risks violating the platform's terms of service.
- Advertising Studio overlaps with Data Cloud Activations. Confirm which product owns the audience before building parallel pipelines in both.
Trust & references
Cross-checked against the following references.
- Marketing Cloud Advertising StudioSalesforce Help
Straight from the source - Salesforce's reference material on Advertising Studio.
- Audience Builder for AdvertisingSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. When was Advertising Studio retired?
Q2. What is the recommended Salesforce replacement for Advertising Studio?
Q3. Which of these was a common Advertising Studio use case?
Discussion
Loading discussion…