Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
The decision on the table is sequencing: which product to license first, and whether you need the second at all. Get it wrong and you pay for a profile nobody activates, or for a real-time engine that personalises on thin, anonymous data. Both mistakes are hard to undo, because the data model and the tracking plan you build first shape every campaign that follows.
Data 360 builds the profile, Personalization acts on it
Data 360 is the data layer. It pulls customer data from your commerce platform, CRM, service desk, loyalty system and data warehouse, matches the records that belong to the same person, and turns them into segments that other systems can use. Older proposals call the same product Salesforce CDP or Marketing Cloud CDP (Data 360). The wider case for that layer sits in Data Cloud as a customer foundation.
Marketing Cloud Personalization is the decision layer. It tracks behaviour on your website and app, reads what a visitor is doing in that session, and chooses the banner, product recommendation or offer to show on the next page. Older material calls it Interaction Studio (Marketing Cloud Personalization). The split is simple to remember. Personalization reacts to what a person does now, while Data 360 remembers their history across channels.
Which product to start with depends on the problem
Start with Marketing Cloud Personalization when the problem sits on the website. Think high traffic, a large share of anonymous visitors and a catalogue big enough that one homepage serves nobody well. Personalization builds its own profiles from on-site behaviour, so it can show results before your wider customer data is unified. Recommendations, category affinity and exit offers all run on that behavioural data.
Start with Data 360 when the problem is fragmentation. If email, service and store data sit in separate systems, every channel works from a partial picture, and no on-site engine fixes that. Unifying first gives marketing, service and sales one set of segments to work from. What marketers can then build on those segments is covered in Data Cloud features for marketers.
Together, the two products close the loop between channels
The combination pays off when what happens on the site should change what happens everywhere else. A segment built in Data 360, such as customers with a high lifetime value or an open service case, can steer what Personalization shows on the homepage. Behaviour captured in the session, such as repeated visits to one category, can flow back into Data 360 and start an email journey. How much of this works out of the box depends on your editions and on how the two products are connected in your Salesforce setup.
That loop is where our marketing automation work sits. We build personalised journeys on behavioural data for campaigns that reach two million recipients, and the value comes from linking the session to the rest of the customer record. For a retail example, our work with Neuhaus shows how a chocolatier uses Personalization.
