Overview
This section covers putting unified data to work. Its five objectives are to define basic concepts of segmentation and use cases, manage segments within Data 360, publish activations within Data 360, act on data, and use Data 360 in Salesforce flows.
Segments are built on a segment-on entity, usually the unified individual, with filters on direct and related attributes, calculated insights and model scores. Segment types include standard, real-time, waterfall and nested segments, and Einstein can help draft segments from a description. Publishing runs on standard or rapid schedules. Activations send segment members, contact points and attributes to targets such as Marketing Cloud Engagement, Marketing Cloud Account Engagement, advertising platforms, cloud storage and Data 360 itself. Data actions react to record or insight changes by sending events to Salesforce Platform Events, webhooks or Marketing Cloud, and flows can be triggered by Data 360 changes or read Data 360 records.
How it's tested
Questions describe a marketing, service or sales goal and the data available. You choose the segment design, publish schedule, activation target and attributes, or the action mechanism such as a data action or flow that delivers the outcome at the right speed.
-
Design the segment
An audience is described, and you choose the segment-on entity, filters, related attributes, exclusions or segment type.
-
Get it to the target
A segment must reach a channel, and you choose the activation target, contact points, attributes and publish schedule.
-
Act in the moment
A change in data must trigger a response, and you choose a data action, a Data 360-triggered flow or a real-time segment.
A retailer wants to email loyalty members who bought running shoes in the last 30 days but have not opened an email in 90 days. Segmenting on unified individual with a related Sales Order filter and an exclusion on email engagement builds the audience. Activating to Marketing Cloud Engagement with the email contact point and a product attribute delivers it for the journey.
Objectives 5
Official objectives from the Salesforce outline, in outline order.
6.1 Define basic concepts of segmentation and use cases.Segment-on entities, filters, attributes and segment types.
- What it means
- A segment is a group of entities, usually unified individuals, that meet filter criteria. Filters use direct attributes on the entity, related attributes reached through relationships such as orders or engagement, calculated insights and model predictions. Segment types include standard, real-time, waterfall for prioritized exclusive groups, and nested segments that reuse other segments.
- What to understand
- Choose the segment-on entity based on who or what the target is, such as unified individual for people or unified account for B2B. Related attribute filters use container logic, so conditions inside one container must be met by the same related record, such as the same order. Use cases include campaign audiences, suppression lists, advertising audiences, personalization and service prioritization. Einstein segment creation can draft criteria from a plain language description for review.
- How it shows up
- An audience description is given, and you choose the entity, filters, containers or segment type that defines it.
- Common confusion
- Placing conditions in separate containers when they must apply to the same order, which widens the audience.
6.2 Manage segments within Data 360.Publish schedules, counts, exclusions and maintenance.
- What it means
- Managing segments includes setting publish schedules, checking population counts, editing criteria, using exclusions, copying and deactivating segments, and monitoring publish status. Standard publishing runs on longer intervals, rapid publish refreshes more often for supported segments, and real-time segments evaluate as qualifying data arrives.
- What to understand
- Segment membership updates only when the segment publishes, so the schedule should match how fresh the audience must be and how much credit cost is acceptable. Check the segment count after edits to catch unexpected results. Segment membership can be stored in membership data model objects for reporting and analysis. Retire or deactivate segments that are no longer used to save processing. Waterfall segments help when people must fall into only one priority group.
- How it shows up
- A freshness, count or maintenance problem is described, and you choose the schedule, segment type or management action.
- Common confusion
- Expecting a segment to update in its target immediately after editing criteria without a publish run.
6.3 Publish Activations within Data 360.Activation targets, contact points and attributes.
- What it means
- An activation sends a published segment's members to an activation target. Targets include Marketing Cloud Engagement, Marketing Cloud Account Engagement, Marketing Cloud Personalization, advertising platforms such as Google, Meta and Amazon, cloud storage, B2C Commerce and Data 360 itself. Each activation chooses contact points and the attributes sent with each member.
- What to understand
- Set up the activation target first, with authentication and, for marketing targets, the right business unit. In the activation, choose contact points such as email or phone and the source priority for picking one when a person has several. Add direct and related attributes for personalization, keeping only what the channel needs. Members without the selected contact point are left out, so low activation counts often trace back to contact point mapping or consent filters.
- How it shows up
- A segment must reach a channel with personalization, and you choose the target, contact point or attribute configuration.
- Common confusion
- Assuming every segment member will appear in the activation even when some lack the chosen contact point.
6.4 Act on data.Data actions, targets and real-time responses.
- What it means
- Data actions watch Data 360 objects, such as engagement data model objects or streaming insights, and send an event when defined conditions are met. Data action targets include Salesforce Platform Events, webhooks and Marketing Cloud, so a change in data can start a process, alert a team or trigger a journey.
- What to understand
- Use a data action when a single event or insight value should cause an immediate response, such as a high-value cart abandonment sending a Platform Event that a flow uses to create a task. Configure the primary object, event rules, related objects to enrich the payload, and the target. Data actions complement segments: segments group many people on a schedule, while data actions respond to individual changes as they happen.
- How it shows up
- A real-time business response to a data change is required, and you choose a data action and target over a segment.
- Common confusion
- Using a scheduled segment and activation for a response that must happen within seconds of an event.
6.5 Use Data 360 in Salesforce flows.Data 360-triggered flows and flow access to Data 360 records.
- What it means
- Salesforce Flow can work with Data 360 in several ways. Data 360-triggered flows start when a data model object or calculated insight record changes. Flows can also be started from Platform Events sent by data actions, read Data 360 objects, and in some cases run when segment membership changes.
- What to understand
- Choose a Data 360-triggered flow when CRM automation, such as creating a case or updating a field, should follow a Data 360 change without building a separate event. Use data actions with Platform Events when the event also needs to reach other systems or when you want a defined payload. Keep flows efficient, because high-volume triggers can create many interviews. Flows let admins combine Data 360 signals with standard CRM processes without code.
- How it shows up
- A Data 360 change should drive CRM automation, and you choose a Data 360-triggered flow, a Platform Event flow or another option.
- Common confusion
- Writing Apex to poll Data 360 for changes that a Data 360-triggered flow could react to directly.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Segment-on entity
The object a segment counts and returns, such as unified individual.
- Remember
- The wrong entity returns orders or accounts instead of people.
- Tested as
- Segment design questions.
- Trap
- Segmenting on a related object by mistake.
-
Related attribute container
A group of conditions that must all be met by the same related record.
- Remember
- Separate containers can be met by different records.
- Tested as
- Precise audience questions.
- Trap
- Splitting conditions that belong together.
-
Waterfall segment
A segment type that places each person into only the first matching priority group.
- Remember
- Prevents overlap across offers.
- Tested as
- Priority audience scenarios.
- Trap
- Building overlapping segments with manual exclusions.
-
Real-time segment
A segment that evaluates membership as qualifying data arrives.
- Remember
- Suited to immediate personalization, with supported data only.
- Tested as
- Freshness questions.
- Trap
- Using it for every audience regardless of cost.
-
Publish schedule
How often a segment's membership refreshes and reaches targets.
- Remember
- Standard and rapid schedules differ in frequency and cost.
- Tested as
- Freshness and cost trade-offs.
- Trap
- Expecting edits to apply instantly.
-
Activation target
A configured destination for activations, such as Marketing Cloud or an ad platform.
- Remember
- Must be set up before activating.
- Tested as
- Activation setup questions.
- Trap
- Confusing it with the activation itself.
-
Contact point selection
Choosing which contact point and source priority an activation uses.
- Remember
- Members without the chosen contact point are excluded.
- Tested as
- Low activation count scenarios.
- Trap
- Blaming the segment filters first.
-
Activation attributes
Direct and related fields sent with each member for personalization.
- Remember
- Send only what the channel needs.
- Tested as
- Personalization questions.
- Trap
- Sending every attribute by default.
-
Data action
A rule that sends an event to a target when Data 360 data meets conditions.
- Remember
- Targets include Platform Events, webhooks and Marketing Cloud.
- Tested as
- Real-time response questions.
- Trap
- Using a segment for single-event triggers.
-
Data 360-triggered flow
A flow that starts when a Data 360 model object or insight record changes.
- Remember
- Runs CRM automation directly from Data 360 changes.
- Tested as
- Flow integration questions.
- Trap
- Writing Apex polling instead.
-
Einstein segment creation
Generative assistance that drafts segment criteria from a plain language description.
- Remember
- Drafts should be reviewed before publishing.
- Tested as
- AI-assisted segmentation questions.
- Trap
- Publishing a draft without checking filters.
-
Suppression and exclusion
Removing people from a segment based on criteria or other segments.
- Remember
- Supports consent and frequency rules.
- Tested as
- Audience hygiene questions.
- Trap
- Relying on the target platform to exclude them.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Ways to act on Data 360 data
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Segment and activation | Group many people and send them to a channel | Scheduled audience delivery | Using it for instant single-event responses |
| Data action | Send an event when data meets conditions | Per-event, near real time | Using it to build audiences |
| Data 360-triggered flow | Run Salesforce automation on Data 360 changes | CRM automation without a separate event | Choosing Apex polling |
Segment types
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Standard segment | Filter-based audience published on a schedule | Most common, batch refresh | Expecting real-time updates |
| Real-time segment | Membership evaluated as data arrives | Fastest, limited data types | Using it for every audience |
| Waterfall segment | Each member placed in one priority group | Prevents overlap | Using manual exclusions instead |
| Nested segment | Uses another segment as a filter | Reuses existing definitions | Rebuilding the same criteria repeatedly |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Separate containers
- What candidates pick
- Put product type and order date in separate related attribute containers.
- Why it looks right
- Each condition looks independent.
- Why it's wrong
- Separate containers can match different orders, so people qualify without buying the product in the period.
Clue to watch for Both conditions must describe the same purchase.
-
Instant update
- What candidates pick
- Edit segment criteria and expect the ad audience to change immediately.
- Why it looks right
- The edit is saved.
- Why it's wrong
- Membership refreshes when the segment publishes on its schedule, and the target updates after that.
Clue to watch for The question mentions timing after a change.
-
Count mismatch is a bug
- What candidates pick
- Rebuild the segment because activation shows fewer members.
- Why it looks right
- The numbers should match.
- Why it's wrong
- Members without the selected contact point or with opt-outs are excluded from the activation by design.
Clue to watch for Some customers lack email or phone values.
-
Segment for one event
- What candidates pick
- Use a rapid-publish segment to alert sales when a key account visits pricing.
- Why it looks right
- Rapid publish sounds fast.
- Why it's wrong
- A single real-time event calls for a data action or streaming insight, not a scheduled audience.
Clue to watch for The response must happen within minutes of one event.
-
Apex polling
- What candidates pick
- Schedule Apex to check Data 360 for insight changes and create tasks.
- Why it looks right
- Developers know Apex.
- Why it's wrong
- A Data 360-triggered flow or a data action with a Platform Event reacts to changes without polling code.
Clue to watch for An admin-friendly, low-code solution is requested.
-
Overlapping offers
- What candidates pick
- Create three offer segments and hope exclusions prevent overlap.
- Why it looks right
- Manual exclusions seem flexible.
- Why it's wrong
- A waterfall segment assigns each person to only the highest priority group automatically.
Clue to watch for Each customer must get only one offer.
-
Send every field
- What candidates pick
- Add all profile attributes to an advertising activation.
- Why it looks right
- More data seems better for targeting.
- Why it's wrong
- Sending unneeded or sensitive attributes raises privacy risk; include only what the channel requires.
Clue to watch for The target is an external advertising platform.
Answer framework
Use these steps when a scenario asks how to use Data 360 data for an audience or action.
- Decide whether the need is an audience of many people delivered on a schedule or an immediate response to one change.
- For audiences, choose the segment-on entity, then build filters with containers that keep related conditions on the same record.
- Pick the segment type and publish schedule from freshness needs, overlap rules and credit cost, using rapid publish only when audiences must update within hours.
- Configure the activation target, contact points, source priority and only the attributes the channel needs to limit data exposure.
- For immediate responses, use a data action to a Platform Event, webhook or Marketing Cloud, or a Data 360-triggered flow for CRM automation.
Practice question
Want more like this? The Data-Con-101 practice test has questions for every domain.
Checklist
0 of 14
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
This is the largest section, so plan the most time here and study it after modeling and identity resolution. Start with the Segmentation in Data 360 module and build segments in a playground if possible. Practice one audience that uses related order attributes in a single container and another that uses two containers, then compare the counts to understand container logic.
Next, study publishing and activation together. Write out the full path from segment to publish to activation target, noting where contact point selection, consent and attributes are set. Review the advertising and Marketing Cloud Engagement modules to see how targets differ.
Then cover acting on data. Configure or read through a data action that sends a Platform Event, and a Data 360-triggered flow that creates a task. Build a comparison card listing when to use a segment, a data action or a flow. Finally, complete the Agentforce sales and service quick looks, which show Data 360 data driving actions in apps. Use practice questions to test timing and count scenarios, which appear often.
FAQ
How much of the exam is Data Activations and Utilization?
Data Activations and Utilization is 20% of the exam, the largest section, about twelve of the 60 scored questions as a planning estimate.
What is the usual segment-on entity?
The unified individual for consumer audiences, or the unified account for B2B audiences. Choosing a different entity changes what the segment counts.
How often do segments refresh?
Standard segments publish on longer intervals, rapid publish refreshes more often for supported segments, and real-time segments evaluate as data arrives. Check current Help for exact intervals.
What can an activation send?
Segment members with the selected contact points, plus chosen direct and related attributes for personalization, to the configured activation target.
When should I use a data action instead of an activation?
When a single change, such as an event or insight value crossing a threshold, should cause an immediate response in another system or process.
Can flows read Data 360 data?
Yes. Flows can be triggered by Data 360 changes, respond to Platform Events from data actions, and read Data 360 records for use in CRM automation.
Is Agentforce part of this section?
The guide does not name Agentforce here, but the official prep trail includes Agentforce sales and service modules that show Data 360 data being used to act.
Other CRM & Business Applications certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- HubSpot Inbound Marketing Certification Study guide
- Salesforce Certified Platform Developer I Study guide
- Google Ads Search Certification Study guide
- ServiceNow Certified System Administrator Study guide
- Salesforce Certified Platform Administrator Study guide
- ServiceNow Certified Application Developer Study guide
Test your Domain 6 knowledge
You have covered segmentation, publishing, activation targets, data actions and Data 360 in flows. Test your segment and activation reasoning in timed practice questions.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the Data-Con-101 AI tutor Get any concept explained your way