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

Text link

Bold text

Emphasis

^Superscript

_Subscript

The decision is whether to treat Marketing Cloud Engagement as a sending tool or as a performance channel with its own targets. As a sending tool it runs large batches split by consent and language. As a performance channel it needs an owner, a test calendar and a revenue metric agreed with finance. The second costs more people time. It is also the version where you can show what the licence returns.

Batch sending leaves most of the platform unused

Many Marketing Cloud Engagement accounts use Journey Builder, the tool for automated multi-step journeys, mainly to send large batches. The same account can run journeys triggered by browsing or purchase behaviour, control how often each contact hears from you and score contacts on their likelihood to engage. The gap is rarely technical. It comes from a team organised around a send calendar.

We see the difference most clearly in retail. Our campaigns reach two million recipients, and at that scale moving from batch sends to behaviour-triggered journeys changes which customers hear from you and how often. The same mechanisms carry over to energy, automotive and B2B, where buying cycles are longer and each contact is worth more. Salesforce's platform-native marketing product follows the same logic, as Marketing Cloud Next and its editions shows.

A performance programme runs on a fixed test calendar

Performance marketing in Marketing Cloud is a repeating cycle: test one change, analyse the result against a business metric and roll the winner into the standard journey. The discipline sits in the calendar. Run one test per journey at a time, write the hypothesis before launch and fix the decision date in advance. Without that date, tests drift and nobody acts on them.

Journey Builder carries most of the testing. Split activities, send time tests and path tests all run inside live journeys, so no campaign has to stop for a test to start. Testing whole sequences brings its own trade-offs on duration and metrics, covered in how Path Optimizer tests journeys.

Revenue per email is the honest measure of the channel

Open rate is the metric most email teams report, and it is the least reliable one. Privacy features in several mail apps load images automatically, which inflates opens without anyone reading. Clicks, sessions on your site and revenue per email sent show what the channel delivers. Unsubscribes and spam complaints show what it costs in future reach.

Connecting email to revenue means tracking the visit after the click. Marketing Cloud Engagement can tag email links for web analytics, so sessions and orders are attributed to the send that caused them. Universal Analytics has been retired, so that tracking now runs on Google Analytics 4 (GA4). The set-up choices are covered in connecting Google Analytics and Marketing Cloud.

Einstein turns test results into decisions per contact

Every test generates behavioural data, and the predictive Einstein features in Marketing Cloud Engagement put that data to work on audience management. Einstein Engagement Scoring ranks contacts by how likely they are to open, click or unsubscribe. Einstein Engagement Frequency shows which contacts are over-mailed and which could receive more. Einstein Send Time Optimization picks the send moment for each contact.

Frequency is where performance gains usually start. Sending less to contacts close to unsubscribing protects the list, and sending more to contacts who respond adds traffic from people who want it. The models learn from history, so their value grows with the volume of sends and the number of tests behind them.

Paid media and email work better from one audience

The advertising audience features of Marketing Cloud Engagement can push email segments to ad platforms. You can then keep existing customers out of acquisition ads, or reach lapsed customers who stopped opening emails. The email database becomes a targeting source for paid media. Consent is the limit: ad audiences need a legal basis of their own, so involve your privacy team before the first sync.

Cross-channel reporting is a separate layer. Datorama (Marketing Cloud Intelligence) brings paid media, email and web data into one view, and what Marketing Cloud Intelligence brings together explains when that reporting is worth adding.

The operating model decides whether it lasts

A performance programme stalls when nobody owns it after the first quarter. Before you commit, name who carries each of these:

A channel owner holds a revenue target agreed with finance.
A test calendar sets one live test per journey with fixed decision dates.
Web analytics tagging covers every email link and is checked before each send.
A monthly review moves winning variants into the standard journeys.

The internal cost is people time, mostly the channel owner and a marketer who builds and reads the tests. External help makes most sense for the set-up and the first cycles. We sit with your team during those cycles so the rhythm becomes yours, and after launch we stay on board to track the KPIs agreed at the start.

Explore Marketing Cloud

Our insights

Button Text

Salesforce developer working alone beside a Salesforce partner team

Salesforce developer vs Salesforce partner: who to hire when

October 28, 2026 5:08 PM

Running performance marketing on Salesforce Marketing Cloud

Key takeaways