Blogs

AI personalisation in Marketing Cloud: where to start

AI personalisation in Marketing Cloud works best when it starts with the predictive Einstein features you may already have, and only then adds generated content. Scoring, timing and frequency decide who hears from you and when. Generative AI decides what they read.

Marketing Cloud journey using Einstein engagement scores to personalise emails

Key takeaways

1

Predictive Einstein features decide who hears from you, when and how often.

2

Generative AI scales copy and segments, with brand rules and a person approving.

3

Prove each feature with a holdout group before you roll it out to every journey.

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

  1. Item 1
  2. Item 2
  3. Item 3

Unordered list

  • Item A
  • Item B
  • Item C

Text link

Bold text

Emphasis

Superscript

Subscript

The decision on the table is which AI features to switch on, in which order, and how to prove they pay off. Switch on everything at once and you cannot tell which feature moved your results. Start with the predictive layer and you get measurable gains on journeys you already run, plus cleaner engagement data for the generative features that follow.

Predictive features decide who, when and how often

Marketing Cloud Engagement, the Salesforce email and mobile messaging platform, includes several predictive Einstein features that personalise without writing a word. Einstein Engagement Scoring predicts how likely each contact is to open, click or unsubscribe, and groups contacts into engagement personas. Journeys can then branch on those scores, sending loyal openers one path and lapsing contacts another.

Einstein Engagement Frequency uses the same signals to show which contacts are under-saturated, on target or saturated, so you can adjust how often each group hears from you. Einstein Send Time Optimization scores every hour of the week for each contact and sends when that person is most likely to open. None of these needs new content. They change the timing and volume of messages you already send.

Volume decides how much the predictive layer returns

These models learn from engagement history, so their value grows with the number of sends and contacts. Engagement Frequency can fall back on the behaviour of your whole contact base when a new subscriber has no history yet, which makes it usable early in the customer lifecycle. For a small list with a monthly newsletter, the gains are modest. For a retailer sending triggered journeys every day, small improvements in timing and frequency repeat across millions of messages.

That is the scale our marketing automation work runs at, with campaigns that reach two million recipients and journeys built on behavioural data. At that volume, frequency control protects the list as much as it lifts engagement, because every avoidable unsubscribe is a contact you cannot reach again. How predictive and generative AI divide the work in Salesforce more broadly is set out in predictive and generative AI compared.

Recommendations personalise the content block

Einstein Recommendations fill an email or web block with the products or articles each contact is most likely to want. You define the rules, such as which catalogue items qualify, which ones to exclude and which to boost, and the model weights the rest by each contact's behaviour and affinities. In Marketing Cloud Personalization, the same logic runs through recipes that combine those rules.

Recommendations are only as good as the catalogue and behaviour data behind them. Missing categories, stale stock or untracked browsing all show up as irrelevant suggestions. Fix the feed before you judge the model. Where behaviour sits in several systems, it needs unifying first, which is the case made in Data Cloud as a customer foundation.

Recommendations are only as good as the catalogue and behaviour data behind them.

Author to be assigned

|

FORWARD

Generative AI scales copy and segments

Einstein Content Creation generates subject lines and body copy for email and mobile messages, based on a brand personality you configure. It is useful for variation: more subject lines to test, more versions per segment, faster first drafts. A marketer still chooses and edits what goes out, and your brand rules belong in the configuration before anyone generates at scale.

On the data side, Data Cloud for Marketing (Data 360) lets marketers describe an audience in plain language and get a draft segment back, which they then refine. Lookalike modelling finds contacts who resemble a high-value group. Both depend on unified customer data. The segmentation features themselves are covered in Data Cloud features for marketers.

Prove each feature with a holdout group

Every AI feature in Marketing Cloud should earn its place against a control. Keep a random share of contacts on the old rule, such as a fixed send time or a fixed frequency, and compare opens, clicks, conversions and unsubscribes after a full buying cycle. The size of the holdout depends on your volume: large enough to show a difference, small enough that the rest of the list gets the benefit.

Measure against numbers you already report, such as revenue per send, unsubscribe rate and the hours your team spends writing variants. Switch on one feature at a time. If the programme stops after the predictive layer, the scores, the cleaner engagement data and the testing discipline keep their value.

Own the rules as well as the models

AI personalisation needs an owner in the marketing team who decides which scores drive which branches, which brand rules apply to generated copy and when a test is finished. Without that owner, features stay switched on long after anyone has checked them.

Our Head of Marketing Cloud runs every Marketing Cloud community event across Belgium and the Netherlands, so we see how other marketing teams set up these features and where they stall. We bring that into your journeys and stay on after launch to track the KPIs agreed at the start.

Explore Marketing Cloud

Our insights

Button Text
No items found.
No items found.
No items found.