Activations
In Salesforce Data Cloud, an Activation is the published delivery of a segment of unified profiles to a downstream destination, such as Marketing Cloud Engagement, Google Ads, Meta Ads, an Amazon S3 export, or another connected system.
Definition
In Salesforce Data Cloud, an Activation is the published delivery of a segment of unified profiles to a downstream destination, such as Marketing Cloud Engagement, Google Ads, Meta Ads, an Amazon S3 export, or another connected system. An Activation specifies which segment to send, which attributes to include in the payload, which channel to push to, and on what schedule the publish should run. Activations are the bridge between the unified data graph inside Data Cloud and the channels that act on it. Without an Activation, a segment is a query result that nobody downstream can use.
Activations were called Activation Targets in early Customer Data Platform releases and got renamed when CDP merged into Data Cloud. The feature has steadily gained more destinations and richer payload controls. Each Activation runs through a configured Activation Target (the destination connector) and an Activation Schedule (one-time, recurring, or change-triggered). The published payload typically includes a unique identifier suitable for the destination, an email hash for ad platforms, a contact key for Marketing Cloud Engagement, or a record ID for sales platforms, along with whichever profile attributes the destination needs for personalisation.
How Activations actually deliver segments to downstream channels
Activation Target, the destination connector
Every Activation runs against a configured Activation Target. The Target encapsulates the destination (Marketing Cloud Engagement, Meta, Google, S3, Snowflake, Amazon S3, custom Apex) and the credentials needed to push payloads there. Targets are configured once per destination and reused across many Activations. Reusing Targets keeps credential management in one place and makes audit easier.
Segment versus Activation, what each piece does
A Segment is the query that defines which unified individuals or accounts qualify. The Segment lives entirely inside Data Cloud and produces a published count when it runs. The Activation is the act of sending that Segment elsewhere. One Segment can have many Activations: one to Marketing Cloud for journeys, one to Meta for paid social, one to a partner via S3 export. Changing the Segment changes every Activation that uses it.
Mapping attributes to the destination payload
Each Activation configures Attribute Mappings: which Data Cloud attributes get packaged into the payload sent to the destination. Different destinations have different requirements. Meta wants hashed email, hashed phone, and country. Marketing Cloud Engagement wants Contact Key, Email Address, and any personalisation attributes used in the journey. Picking the minimum attribute set avoids over-sharing data with downstream systems.
Activation Schedule and refresh cadence
Schedules can be one-time, recurring on a clock, or driven by change-data capture. Recurring Activations publish the segment at the chosen cadence, picking up new qualifiers and dropping those who no longer qualify. CDC-style Activations publish only when the underlying data changes. The schedule shapes how often downstream channels see new audiences, and it also controls how much API consumption the Activation generates.
Activations in Marketing Cloud Engagement
Marketing Cloud Engagement is the most common destination. The Activation publishes a Data Extension containing the unified profile records and their selected attributes. Journey Builder treats that Data Extension as an Entry Source, so changing the Activation effectively changes who flows through the journey. Coordination between Data Cloud and Marketing Cloud admins matters here; mismatched Contact Key conventions break the join.
Activations to ad platforms
Meta, Google, LinkedIn, TikTok, and the Trade Desk are the headline ad destinations. The payload is usually hashed identifiers (email, phone, mobile ad ID) plus optional consent flags. Salesforce maintains the connector and refreshes the audience on the destination's match cycle. Most ad platforms see partial match rates of 40 to 70 percent on hashed email lists; the rest is destination-side identity loss, not a Data Cloud problem.
Identity resolution and the published key
Data Cloud unifies multiple source records into one Unified Individual via Identity Resolution. Activations publish only attributes from the unified profile, which is why two source records with the same email collapse into one row in the destination. Picking the right published key (email for ad platforms, Contact Key for ESPs, internal ID for CRM) is the difference between a clean handoff and a duplicate explosion downstream.
Limits, throttling, and audit
Activation publishes count against Data Cloud consumption (CDP Credits) plus any destination-specific rate limits. Salesforce throttles automatically when destinations rate-limit. The Activation Run history tab logs each publish, the rows sent, the rows accepted, and any errors. Run history is the first place to look when a journey or ad set stops getting new audiences.
How to create an Activation
Creating an Activation assumes a Segment is already built and an Activation Target is already configured. The Activation itself is the assembly step that links the two and adds the runtime details.
- Open the Segment
In Data Cloud, navigate to the Segment that should be activated. Confirm the Segment count is the population you expect; activating the wrong segment is hard to undo.
- Create a new Activation
Click Activate on the Segment record. Choose the Activation Target (the destination) and name the Activation after the use case, for example High-Value Renewal - Meta Lookalike.
- Map the attributes
Select the attributes from the unified profile to include in the payload. Match the destination's required fields and keep optional fields lean to avoid over-sharing.
- Set the schedule
Pick one-time, recurring, or change-triggered. Recurring is the default for ongoing journeys and audiences. Set the cadence to match the destination's matching window.
- Publish and monitor the first run
Publish the Activation. Watch the first run in the Activation Run history. Confirm the destination receives the audience and that downstream automation picks it up. Fix the mapping before the second run if anything is off.
The Segment whose qualifiers are published.
The destination connector to push the audience to.
The identifier shared with the destination (email, Contact Key, ad ID, etc.).
Which unified attributes go into the payload.
One-time, recurring, or change-triggered cadence.
- Changing the Segment definition changes every Activation that uses it. Audit downstream Activations before editing a shared Segment.
- Each destination has its own match rate. A 60 percent match on hashed email is normal, not a bug, and is set by the destination, not Data Cloud.
- Activations count against CDP Credits. Recurring Activations on huge Segments can burn through quota faster than expected.
- Publishing the wrong attribute (a raw email instead of hashed, a Contact Key without the expected prefix) is hard to recall once the destination has it. Test on a small sample first.
Trust & references
Cross-checked against the following references.
- ActivationsSalesforce Help
- Activation TargetsSalesforce Help
Straight from the source - Salesforce's reference material on Activations.
- Create an ActivationSalesforce 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. What is the primary benefit of Activations for Salesforce administrators?
Q2. Can a Salesforce admin configure Activations without writing code?
Q3. In which area of Salesforce would you typically find Activations?
Discussion
Loading discussion…