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 whether real-time web personalisation earns a place in a retail stack, and in what order to build it. The tool itself is quick to switch on. What takes time is agreeing which customer behaviour matters, tracking it properly and turning it into campaigns that a merchandising team can run every week. Skip that work and the platform shows the same generic recommendations any webshop plugin could.
What Marketing Cloud Personalization does for a retailer
Marketing Cloud Personalization (formerly Interaction Studio) is the Salesforce product that reads what a visitor does on your website or app and changes what they see in real time. For a retailer, that means product recommendations, offers and content that follow a customer's browsing and buying behaviour. The value depends on how well the platform understands intent. It is one product in the Salesforce marketing family, next to the email and journey tools covered in the Marketing Cloud Next overview.
Neuhaus shows why intent is harder than it looks. The chocolatier began as a pharmacy, sells premium pralines worldwide and has worked with FORWARD across Marketing Cloud, Service Cloud and Commerce Cloud (Agentforce Commerce) since its move to Salesforce. Around 70% of its customers choose Neuhaus pralines as a gift. A gift buyer's browsing often says more about the recipient than about the buyer, so personalisation has to be designed around that behaviour.
Neuhaus started with strategy, then campaigns
Neuhaus began with a series of discovery sessions to break down its online personalisation strategy. Together we decided which campaigns in Marketing Cloud Personalization would serve which strategic objectives. That order kept the project tied to business goals from the first week, and it gave the team a shared list of use cases to prioritise. Use cases came first. Configuration followed.
The alternative is common and expensive. A retailer that starts by configuring recommendations tends to optimise clicks on whatever the widget shows, without knowing whether those clicks serve margin, basket size or repeat purchase.
Tracking design decides what personalisation can do
Marketing Cloud Personalization can only act on behaviour it captures. The tracking design therefore sets the ceiling for every campaign. In our projects, a solution architect works with the retailer during discovery to understand the business context and decide the web tracking architecture. That work produces a blueprint: a document listing every tracking requirement the site needs.
The blueprint is then implemented through the sitemap, the configuration layer that captures customer actions on the website and sends them to Marketing Cloud Personalization. A thin sitemap limits you to basic page views. A sitemap built from a clear blueprint captures product interest, category affinity and basket behaviour, which is what makes one-to-one recommendations possible.
The blueprint also makes ownership explicit. When the website changes, someone has to update the tracking, or campaigns lose their signal without anyone noticing. That owner usually sits between the ecommerce team and the marketing team, and naming them early saves a rebuild later.
