Certified Data Cloud ConsultantDemo

A streaming data transform can normalize one Contact record containing mobile, home, and work phone fields into separate phone records in a target Phone data lake object. Mapping that normalized DLO to Contact Point Phone makes every phone number available to downstream consumers, including activation. Directly mapping the original DLO supports only one of the source phone fields for a Contact Point Phone record.

Data Cloud supports calculated, streaming, and real-time insights, enabling multidimensional metrics and analysis from unified customer-profile data. Salesforce also states that identity resolution does not make Data Cloud a master data management system.

Data Cloud ingests and harmonizes data from disparate sources, then applies identity-resolution matching and reconciliation rules to link records into unified customer profiles. This unified, harmonized data supports more accurate customer understanding and business analysis.

A unified profile is created when any single active match rule is met. Adding more match rules broadens the ways records can qualify as matches, which can increase the consolidation rate. Reconciliation rules determine which source values are selected after records have been matched, so they do not increase matching consolidation.

Custom fields can extend a standard DMO when the source contains attributes that the standard model does not provide. Adding the beauty-profile attributes to the Individual DMO keeps them associated with the individual profile, which supports downstream identity resolution and segmentation.

Data Cloud defers scheduled segment publishes when the maximum number of simultaneous publishes is reached. Setting different publish-schedule start times distributes the publishing workload, preventing concurrent processing overload while preserving both the existing segments and their publishing frequency.

A data-source connection cannot be disconnected while associated data streams or activations remain. Delete those dependencies before disconnecting the connection. Salesforce Help: Disconnect a B2C Commerce Instance Connection.

A data graph uses Data Model Objects (DMOs) and their relationships. Data Lake Objects (DLOs) must therefore be mapped to DMOs before they can be used in the data graph.

Identity Resolution uses match rules to identify records that represent the same individual and reconciliation rules to select profile values across sources, creating a unified profile.

Tableau connects to Data Cloud through its built-in connector and enables users to explore, analyze, and visualize unified profiles and other customer insights.

A Source Sequence reconciliation rule assigns an order of priority to data sources for values used to build a unified-profile attribute. It can therefore determine the preferred source for attributes such as first name or last name.

Purchase order numbers should be stored as text when their formatting is significant. A text field preserves each character, including any leading zeros, while numeric field types may remove them during numeric interpretation.

The activation name can supply the campaign identifier as part of the export file name, and the filename specification explicitly controls the generated file-name components. A campaign identifier added as an exported attribute affects file contents rather than its name, while a segment name alone does not configure the S3 file name.

The Is Anniversary Of date operator matches the month and day of a stored birth date to the evaluation date without requiring the year to match. A daily segment evaluation therefore includes the people whose birthdays occur that day. Salesforce lists Is Anniversary Of among its supported date segmentation operators.

The Phone data type is modeled on Text: Data Cloud does not validate phone-number format during ingestion, and it accepts any valid text value for a Phone field.

A B2C Commerce data stream created with the Order Bundle loads 30 days of historical data. Loading two years of transactional history requires the B2C Commerce starter bundles for the standard connector mappings and a custom extract to supply the remaining historical records.

A file storage activation target publishes a segment to a file-based destination and produces data files containing the segment members and additional selected attributes. This supplies the contact list needed for a direct-mail campaign.

Data Explorer can query and inspect Unified Individual data, Profile Explorer displays unified-profile data, and Query API supports SQL queries against unified data model objects. Identity Resolution performs matching and reconciliation to create unified profiles, while Data Actions trigger actions based on data rather than validate profile contents.

Calculated Insight metrics can be added as activation attributes, including for personalization and activation decisions. They also support complex, reusable analysis over large historic data sets, while segmentation operators are intended for engagement-data aggregation windows of two years or less. Single-row transformations are instead suited to formulas, and calculated-insight refresh is not triggered simply by being referenced.

The Party Identification object stores alternate party identifiers, such as loyalty or vendor-specific IDs. Identity resolution can use an exact-match rule on Party Identification.Identification Number to unify profiles that share that identifier.

A calculated insight must include a dimension containing the Individual or Unified Individual ID so it can be associated with the profile context. It must also include the primary key of the table being segmented as a dimension, which establishes the required relationship to that segment-on table. The primary key is an identifying dimension rather than a metric.

The Email Studio Starter Data Bundle includes an Enterprise Profile Attributes data stream that brings subscriber demographic and profile context from Marketing Cloud Engagement into Data Cloud as part of the preconfigured Email Studio integration.

Separate source datasets should be ingested into separate data lake objects and mapped to the standard Individual and Contact Point Email data model objects. The Individual DMO represents a person, while Contact Point Email stores that person’s email address; the relationship supports multiple contact points for an individual and enables identity-resolution workflows to reconcile duplicate customer records across sources.

The Data Cloud Marketing Manager permission set enables a user to manage the overall segmentation strategy, including activation targets and activations. This level of marketing-focused segment access supports using Segment Intelligence for ROI-related marketing work without granting the broader administrative privileges of Data Cloud Admin.