Store, online and loyalty activity resolved into one shopper profile, so marketing, service and merchandising teams act on the same understanding of each customer.
Data Cloud, now also marketed by Salesforce as Data 360, brings together shopper data that retailers and consumer brands collect in separate systems: point-of-sale transactions, ecommerce orders, loyalty activity, email engagement, service history and website behavior. It matches those records into unified profiles using identity resolution rules, calculates insights such as purchase frequency or category affinity, and makes segments available to Marketing Cloud, commerce, Service Cloud and advertising destinations. For consumer goods companies that sell mostly through retailers, it helps them get the most from the first-party data they do have, gathered from direct sales, registrations, promotions and communities.
Retail data is high volume, fast moving and fragmented by channel. The same shopper may buy in a store with a card, online through guest checkout and through a marketplace, leaving several partial identities behind. Data Cloud adapts through identity resolution that combines exact matches, such as loyalty numbers, with fuzzier matching on names and addresses, and through streaming ingestion that keeps web and app behavior current. Consumer goods brands face a different gap: they often lack transaction data entirely, so their profiles are built from engagement, product registrations, sampling programs and direct-to-consumer orders. In both cases consent must travel with the profile, because a preference expressed in one channel has to be respected in every other.
Store receipts, online orders and loyalty accounts resolve into one profile with lifetime purchase history, preferred channel and store, and recent browsing. Service agents see the full picture when a shopper calls about a return, and marketers stop treating an in-store regular as a brand-new online prospect who needs a welcome discount. Returns and exchanges across channels also stop looking like lost customers in reporting.
Calculated insights track purchase recency and frequency by category, identifying shoppers whose buying pattern has slowed. Segments feed win-back journeys in Marketing Cloud, paid media audiences and store associate clienteling lists, with suppression rules keeping recent purchasers and opted-out customers out of each audience before it is activated. Holdout groups let the team measure whether each win-back effort actually changed purchasing behavior.
Streaming web and app events update profiles quickly enough to trigger abandoned cart messages, back-in-stock alerts or personalized content on the next visit. Combining those signals with purchase history avoids promoting an item the shopper already bought in store the previous week, a small detail customers notice immediately. Rules can also cap message frequency so shoppers are not chased after every single click.
Consumer goods brands gather data from product registrations, recipe or how-to content, sweepstakes, sampling programs and direct-to-consumer sales. Data Cloud unifies those scattered sources into profiles that support loyalty programs, launch audiences and research panels, reducing dependence on third-party data that browsers and regulators are steadily restricting. Consent collected at each source travels with the profile into every later activation.
Three decisions carry most of the weight. First, identity: which keys are trusted, such as loyalty identifiers, hashed emails or customer numbers, and how aggressively rules should merge records that lack a shared key. Second, grain: whether transactions arrive at order or line-item level, which determines whether category and product insights are possible at all. Third, consent: where each channel's permissions are captured, how they map to the Data Cloud consent model and which system wins when preferences conflict. Getting product hierarchy and store attributes right early also makes merchandising analysis far easier.
Store transactions with receipt, line-item and tender details feed Data Cloud in batches or near real time, linked to shoppers through loyalty or receipt identifiers.
Orders, returns, customer accounts and browsing events stream in, giving each profile a current view of online behavior next to store purchases.
Consented segments activate to paid media destinations for targeting or suppression, and campaign exposure data can return for measurement where platforms allow it.
State privacy laws give shoppers rights to access, delete and opt out of certain data uses. Map how consent is collected in every channel, respect it in segments and activations, and build deletion requests into the process. Keep payment card data out of profiles entirely to contain PCI DSS scope.
Overly loose matching merges household members or unrelated people with similar names, while overly strict rules leave shoppers fragmented. Test rules against real samples, review merged profiles with marketing and service teams, and adjust before activating segments at scale. Revisit rules as sources change.
Retail data volumes are large, and Data Cloud usage is consumption-based. Model the ingestion, processing and activation you actually need, filter out low-value events and review consumption regularly with Salesforce, so costs stay predictable as use cases expand. Assign an owner for monitoring usage.
Data Cloud is a customer data platform built into Salesforce, so unified profiles and insights are available natively in Sales, Service and Marketing Cloud records and flows. If you already run another CDP, the question is whether that native access and shared metadata justify a change or a coexistence pattern. We evaluate existing use cases, contracts and data flows before recommending either path.
Yes, though the profile will be thinner than a retailer's. Brands can unify registrations, promotions, content engagement, service interactions and any direct-to-consumer orders. Some also receive aggregated or clean-room data from retail partners under agreed terms. The key is setting realistic goals for what first-party data can support, such as launch audiences and loyalty, before investing heavily.
It can. Clienteling apps and associate tools built on Salesforce can show a shopper's preferences, recent purchases and open service issues when the shopper has agreed to be recognized. Associates can create follow-up tasks or send approved messages. Store teams need training on what they may view and how to use it without making shoppers uncomfortable.
Agentforce can draw on unified profiles to answer order status questions, recommend products based on purchase history or help a service agent resolve a return that spans channels. Grounding the agent in Data Cloud keeps responses tied to real records. We set firm limits on what it can offer, such as refunds or discounts, and route exceptions to staff.
One onshore team with 150 Salesforce certifications, a Salesforce Consulting Partner since 2017.
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.