Skip to main content
Join the Agentforce Hackathon on Nov. 18-19 to compete for a $20,000 Grand Prize. Sign up now. Terms apply.

Navigate Data Cloud Segmentation

Learning Objectives

After completing this unit, you’ll be able to:

  • Define key terms such as segment, publish, and activate.
  • Identify an activation target.
  • Navigate the segment canvas interface.

Data Cloud Segments

Marketers, are you ready to create meaningful segments with Data Cloud? Then this module is for you! Get ready to explore Salesforce Data Cloud for Marketing, and learn the basics about setting up activation targets, navigating the segment canvas interface, creating and filtering segments, and publishing and activating segments to an activation target. 

Before You Begin

If you’re new to Data Cloud, check out Data Cloud Basics for Marketers first. And if you’re new to Salesforce Lightning, consider reviewing Lightning Experience for Salesforce Classic Users. Be sure your account admin has configured your Data Cloud account and provided you with your user login credentials. Finally, if your data model hasn’t been set up yet, you won’t be able to create segments. Don’t worry—you can follow along in preparation and then come back for a refresher when your account has been fully set up.

Data Cloud Overview

Now that you’re up to speed, we can show you how to use your data to create segments that power personalized and engaging marketing communications for your customers. Let’s start at the beginning, navigating the Data Cloud home page. Data Cloud should look familiar to Salesforce Lightning users, but it may look less familiar to Marketing Cloud Engagement users. So let’s take a look around together.

Data Cloud navigation with callouts.

  • The Data Streams, Data Lake Objects, and Data Model (1) tabs provide insight into your selected data model and connected data sources that are created by the user with the data aware specialist permission set.
  • Data Explorer and Profile Explorer (2) are data-viewing tools, allowing you to view your ingested and unified profile data, respectively.
  • Identity Resolutions (3) is where your team creates match and reconciliation rules to unify individual records.
  • Calculated Insights (4) are predefined and calculated metrics that can help you build segments.  
  • As a marketer, the Segments (5) tab is where you create your filtered audience segments.
  • Activation Targets and Activations (6) are used to manage where segments get exported, for example Marketing Cloud Engagement.
  • Finally, the Setup (7) gear is where admins manage account settings.

Tip: You can customize the order of these tabs.

Note

Learn more about the specific Data Cloud Standard Permission Sets on the help page.

Segment, Publish, and Activate

As a marketer, you'll frequently use features on the Segmentation and Activation tabs. So let’s focus on those areas and the concepts that drive segmentation. To get from raw data to a usable audience segment for a marketing campaign, you must: Segment, publish, and activate.Segment, Publish, and Activate chart.

Segment

Publish

Activate

Filter your data to create useful segments to understand, target, and analyze your customers. 

Publish is the process of building a segment based on the filter criteria and sending results to a destination platform. You can publish your segments on a chosen schedule or as needed.

Activation is the process of moving audience segments to an activation target. For example, during activation an audience segment is created in a shared data extension that can be used in Marketing Cloud Engagement Journey Builder.  

This is the typical workflow for creating segments in Data Cloud but with a new account, there’s an exception. New users need to first create an activation target. Why? As Stephen Covey, author of 7 Habits of Highly Effective People, says, “To begin with the end in mind means to start with a clear understanding of your destination.” 

Activation Targets

Before you can publish a segment, you need to identify an activation target, or the location where you want to use your segment. Once created, you can publish your segments and additional attributes to activation targets, such as Marketing Cloud or an external platform account (Google Ads, Google DV360, LinkedIn, Meta, or Amazon Ads).

The Segment Canvas Interface

Now that we’ve read the last page of the book, let’s go back to the beginning. With our destination in mind, we can now build segments in Data Cloud. First, we review the key elements of the segment canvas interface. Canvas Interface with callouts for each section.

Attribute Library (1)

The attribute library displays attributes associated with a selected segment target that have been mapped in your data model and are marked for use in segmentation. Attributes may be from standard data sources like engagement data from Marketing Cloud Engagement, a custom data object, or system data. Attributes narrow down a segment to your target audiences. There are two types. 

  • Direct attributes are attributes that have a one-to-one relationship with the segment target. Meaning each segmented object has only one data point for a profile attribute. So for customer data, they would only have one entry for postal code or for first name.
  • Related attributes are attributes that can have multiple data points. So for customer data, related attributes would be data points that one person could have multiple of, like purchases or email opens.

Segment targets determine which attributes you can select, so it’s important to understand your data model. Don’t worry, we cover the concept of Segment On in the next unit.

Population (2)

The population is the number of records within your current segment. This is refreshed after publishing or performing an on-demand count.

Containers (3)

Attributes can be dragged into individual containers to create AND/OR relationship logic between the attributes. Containers provide a way to create relationships between your related attributes and are used to build your filter logic. When attributes are placed in one container, your query engine looks for attributes that relate to one another in this way. Attributes in separate containers aren’t connected. 

Note

Values are not case sensitive.

Container Examples

Let’s review an example. Northern Trail Outfitters (NTO), an outdoor apparel company, is looking to send an email to customers who purchased a yellow scarf. Here’s a container they would use. 

Container 1=

  • Related attributes: 
    • Product_Category is equal to scarf
    • Product_Description is equal to yellow 
  • Logic: AND

Example segmentation using one container.

If the NTO team created 2 separate containers, the query engine will look for customers who purchased a scarf of any color and also purchased a yellow product. 

  • Container 1= 
    • Related attributes: Product_Category is equal to scarf
  • Container 2= 
    • Related attribute: Product_Description is equal to yellow 
  • Logic: AND

Example segmentation using 2 containers.

Both options work for marketing campaigns, but it’s good to know exactly what you’re asking for when you start your query. To help you do that, we dive deeper into data and query logic in the next unit.

Resources

Teilen Sie Ihr Trailhead-Feedback über die Salesforce-Hilfe.

Wir würden uns sehr freuen, von Ihren Erfahrungen mit Trailhead zu hören: Sie können jetzt jederzeit über die Salesforce-Hilfe auf das neue Feedback-Formular zugreifen.

Weitere Infos Weiter zu "Feedback teilen"