Here is a step-by-step process for marketers to follow.
1. The Foundation: Granting Permissions
Before you can use a custom field, your technical admin must ensure it's accessible to Data Cloud. Think of this as giving the marketing team a key to the data.
Why it matters to a marketer: If your campaign needs a specific data point, like a customer's loyalty tier from a custom field, this step ensures Data Cloud can see and use that information. Without it, you can't build your hyper-personalized segments.
Action: Ask your Salesforce admin to confirm the 'Data Cloud Salesforce Connector' permission set grants 'Read' and 'View All' permissions on the custom field within the relevant object.
2. The Data Connection: Ingesting the Field into a Data Stream
Now that the field is accessible, you need to pull it into Data Cloud. This is where you tell Data Cloud to start listening for updates on your new data point.
Why it matters to a marketer: This is how you make a piece of information, like a product interest code or customer satisfaction score, available for all your marketing activities. The sooner you do this, the sooner you can start activating on it.
Action:
3. The Transformation: Mapping to the Unified Profile
After the data is ingested, it exists in a raw format called a Data Lake Object (DLO). You need to map this raw data to the Individual DMO (Data Model Object), which is the central hub for your unified customer profiles.
Why it matters to a marketer: This is the most crucial step for personalization. It's how you connect the new custom field to a specific individual customer's profile. You can now use this data to create advanced segments like "customers with a high CLV (Customer Lifetime Value) who have abandoned a cart."
Action:
4. The Activation: Refreshing Identity Resolution
The final technical step is to run Identity Resolution. This process matches and merges fragmented data points across your various sources to create a single, unified profile for each customer.
Why it matters to a marketer: This action ensures that the new custom field you've just mapped gets added to the correct unified customer profiles. Without it, the data will sit in your Data Cloud but won't be usable for personalization. Once complete, your new custom field will be ready to use in Data Graph Merge Fields to power dynamic content in emails and journeys.
Action:
Creating Custom Field
Creating a Data Graph
004754257

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.