Identity Resolution

💬 In plain words: In Salesforce Data Cloud, every Data Model Object (DMO) gets assigned a category. Profile tells us who someone is (individuals). Engagement tells us what happened (time-stamped events). Other is for reference data. This category is not just a cosmetic label—it dictates exactly how Identity Resolution and Segmentation use your data. 📌 Example: Individual and Contact Point Email are Profile DMOs—they define who . Website clicks are an Engagement DMO—they define what happened and when . A product catalog is Other. If you mis-categorize engagement data as a profile, the system will break down trying to "unify" click events as if they were people. 🎬 Real-Life Example: The Segment Marketing Could Not Build The Ask: Marketing requested a simple audience segment: "People who browsed the website but did not buy anything in the last seven days." The Failure: The tech team couldn't build it natively...

💬 In plain words: Think of Data Spaces as apartment walls inside a single Salesforce Data 360 building. They let separate brands, regional business units, or departments manage their own customer data, models, segments, and permissions independently—without forcing you to purchase and maintain multiple expensive Salesforce orgs. 📌 Real-World Architecture Example: A multi-brand holding company manages two distinct retail lines (Brand A and Brand B) inside one Salesforce Data 360 instance: Brand A Data Space: Marketers can only view, query, and segment Brand A retail customers. Brand B Data Space: Strictly walled off so Brand B marketers never see or market to Brand A profiles. Outcome: Complete logical isolation of data, metadata, and activation processes on a single platform license.

💬 In plain words: Data Lake: Ingests raw data in any native format quickly and affordably (schema on read). Data Warehouse: Cleans, structures, and indexes curated data for business intelligence and SQL reporting. Data Lakehouse: Combines the massive scale of a data lake with the governance, schema structure, and ACID speed of a data warehouse—the core engine of Salesforce Data 360. Master Data Management (MDM): Resolves duplicate identities across independent systems to create a single, authoritative Unified Individual profile. 📌 Real-World Architecture Analogy: Data Warehouse: The corporate finance data mart—curated star schemas, strict tables, and governed dashboards. Data Lake: The scalable cloud storage bucket (e.g., AWS S3)—storing raw JSON payloads, clickstream logs, and high-frequency IoT feeds. Data Lakehouse: The modern Data 360 architecture—storing raw lake files with warehouse-l...

⚡ 1-Minute Summary The 5-step data lifecycle: Connect, Harmonize, Unify, Analyze/Predict, and Act. Data pipeline path: Raw data lands in a Data Lake Object (DLO) , is staged in a Data Source Object (DSO) , and maps to a canonical Data Model Object (DMO) . Segments and insights read only from DMOs. Zero-Copy architecture: Move the query, not the data. Federate large external datasets from Snowflake, BigQuery, or Databricks instead of copying them.

💬 In plain words: First-party tracking collects behavioral events—like page views, product clicks, and form submissions—directly on websites and apps your company owns, storing visitor identifiers under your own domain rather than relying on third-party cross-site cookies. In Salesforce, you implement this primarily through the Salesforce Interactions Web SDK (for Data Cloud and Personalization) or First-Party Tracker Domains (in Marketing Cloud Account Engagement), pairing every event with explicit user consent before streaming data to Salesforce. For years, digital marketing teams relied on third-party tracking cookies—identifiers set by external ad networks on domains the website owner did not control—to follow visitors across the web. Today, Safari's Intelligent Tracking Prevention (ITP), Firefox's Enhanced Tracking Protection (ETP), consumer ad-blockers, and privacy regulations such as GDPR and CCPA/CPRA block third-party cookies or require strict con...