REETAIN / CUSTOMER DATA ARCHITECTURE

Salesforce Data 360 for luxury: from unified profiles to meaningful action.

A practical guide to Salesforce Data Cloud, now called Data 360, for luxury and premium brands. How to connect customer signals, preserve governance and activate trusted data across Marketing Cloud and retail.

Reetain point of view · Updated November 2026 · Salesforce terminology checked against official documentation

START WITH THE PROBLEM

What should a customer data platform solve for a luxury Maison?

A typical luxury customer relationship spans point-of-sale transactions, boutique notes, e-commerce, marketing consent, appointments, customer service and regional systems. Each source may describe the same person differently. A customer data platform helps connect those signals and make them usable for analytics and activation, provided identity rules, permissions and operating ownership are well defined.

Salesforce renamed Data Cloud to Data 360 on 14 October 2025. The two names refer to the same product during the transition. The platform can ingest or federate data, harmonize it to a common model, resolve identity, calculate insights and activate audiences. Those capabilities do not by themselves establish a complete enterprise master-data-management system.

IDENTITY

One coherent view, not magic deduplication

Matching and reconciliation logic should be explained, validated and monitored. Ambiguous matches can damage the experience as much as missed matches.

GOVERNANCE

An eligible action is not always a permitted action

Consents, purpose, region, contact-point preference and suppression must be modeled and enforced at activation.

ACTIVATION

A profile becomes valuable when something changes

Use richer context to improve a journey, inform a client advisor or avoid contacting a customer at the wrong moment.

REFERENCE ARCHITECTURE

Separate data ownership, unified context and channel execution.

A practical architecture can preserve existing systems of record while using Data 360 to connect signals and support specific activation use cases. The architecture must be designed around the actual Salesforce editions, markets, data latency and consent model, not a generic product diagram.

Systems of recordPOS, CRM, e-commerce, service, consent and master data
Data 360Ingestion, harmonization, identity resolution and insights
Activation policyEligibility, contact pressure, priorities, jurisdiction
ExecutionMarketing Cloud, retail advisor workflows and digital channels

Six technical design choices that matter

  1. Source ownership: identify the authoritative system for identity, consent, transactions and advisor notes. A unified profile is not automatically a new golden record.
  2. Match and reconcile: test identity-resolution rules on hard cases, including shared contact details, changed surnames, travel retail and multiple regional accounts.
  3. Contact points: distinguish known identity, channel reachability, permission and contact preference. They are not interchangeable.
  4. Data freshness: use an appropriate mix of batch, streaming and federation based on business need, cost and system constraints. Do not call every interaction real time.
  5. Activation contract: specify which segments, attributes and contact keys are published to each destination, with failure handling and refresh expectations.
  6. Observability: reconcile audience counts, suppressions, unexpected merges, data latency, downstream delivery and consumption of platform credits.

For Salesforce Marketing Cloud Engagement, Data 360 audience activation can populate sendable Data Extensions; the design of subscriber/contact keys and consent logic still needs explicit attention. Capabilities vary across Marketing Cloud products and editions.

ILLUSTRATIVE USE CASES

Three situations where better identity changes the outcome.

01 / DUPLICATE OUTREACH

One client, two market records

A client appears in both European and US data sources. Matching reveals a probable shared identity, but regional permissions still govern where and how to activate. The outcome is more coherent treatment, not automatic global consent.

02 / CLIENTELING

Boutique context meets digital context

A known client has an upcoming appointment. Relevant product interests and service history can inform preparation, subject to role-based access and proportionate data use.

03 / JOURNEY RELEVANCE

Suppress the wrong reminder

A customer purchases in-store after abandoning an online basket. More current transaction context can prevent an irrelevant cart-recovery communication, if data latency and identity linkage permit.

These are conceptual examples, not disclosed client projects or claimed performance results. See our clienteling strategy and decisioning framework for the operating model around this data layer.

ROADMAP

A use-case-first deployment path.

STEP 1

Define a business decision

Choose one measurable activation pain point and document its baseline, owner, contact policy and current data gaps.

STEP 2

Establish a trusted profile

Map minimum necessary sources, identity rules, consent and reconciliation responsibilities.

STEP 3

Activate, verify, measure

Pilot one destination, test failure scenarios, track incremental impact and data quality, then expand deliberately.

Frequently asked questions.

Is Data Cloud the same as Data 360?

Yes. Salesforce changed the product name in October 2025. Documentation may still use both terms during the transition.

Does Data 360 replace an enterprise MDM solution?

Not automatically. Its identity resolution unifies profiles for use cases, but does not itself create an enterprise golden record or replace every system-of-record responsibility.

Do unified profiles automatically solve consent discrepancies?

No. Consent interpretation requires explicit rules for purpose, jurisdiction, effective date, channel and source precedence.

Is Salesforce Marketing Cloud Engagement itself a CDP?

It is primarily a marketing execution and engagement platform. Data 360 provides the cross-source data and identity layer in the Salesforce ecosystem.

Product references

For exact availability and configuration details, consult Salesforce documentation: About Data 360, Unifying source profiles, and Marketing Cloud Engagement activation. Product functionality and licensing should be validated against the target organization.

WORK WITH REETAIN

Make your customer data useful, not just unified.

Reetain works from customer strategy to Salesforce integration and activation, with particular attention to the realities of luxury retail.

Independent consulting analysis by Reetain, updated November 2026. Salesforce product documentation is linked for technical reference. Reetain is not claiming a product capability beyond the cited documentation.