SAP Campaign Management: What Campaigns Track Across Sales and Engagement Cloud

This is the campaign layer closest to the pipeline, and for a sales led organisation it is often the only one in daily use. What it gives you:

• Leads from the campaign work centerA lead can be created directly from the Sales Campaign work center, alongside the other routes: the quick create icon, an Excel import, the Cloud for Customer APIs, a scanned business card, or a copy of an existing lead.
• The campaign ID on the leadWhen a lead was created as part of a campaign, the campaign ID is assigned to it for identification and reporting. That assignment is the join between campaign and pipeline, and it only exists when somebody or something makes it.
• Assignment rulesDefined under Administrator, Sales and Campaign Settings, with Owner, Marketing Unit and Territory as the result columns. On save, territory data is maintained at header level and the lead is routed accordingly.
• Engagement scores and qualification levelsA score built from link clicks, email opens, form submissions and other marketing interactions. SAP's own example: above seventy, marketing operations can have the lead treated as hot and prioritised for follow up.

Engagement Cloud, the platform that was SAP Emarsys Customer Engagement until 19 February 2026, is where the campaign is actually executed: the journeys, the emails, the personalisation, the segments. Its analytics measure delivery and engagement, and those interactions are what feed the scores Sales Cloud then acts on.

The boundary is worth stating plainly, because it is where most reporting disappointment comes from. Engagement Cloud measures the engagement it created. An email it sent and somebody opened. A link in its own message. A form it hosts. It is excellent at telling you which of your campaigns produced engagement, and structurally unable to tell you which channel produced the person, because the person was anonymous on your website long before Engagement Cloud had a record to attach anything to.

If your campaign management runs on SAP Marketing Cloud, this is the section that matters more than the rest of the page.

• Support ends in December 2026. SAP Engagement Cloud is the designated successor for marketing automation in the customer experience portfolio.
• It is a replacement, not a migration. The two platforms have different data models, and there is no out of the box tool that carries you across.
• More than 2,000 companies are in it, so implementation partners are busy and the calendar is the constraint rather than the budget.
• Reporting built on the old data model goes with it. Anything downstream that reads Marketing Cloud's tables, including dashboards in SAP Analytics Cloud, has to be rebuilt against the new source.

There is an opportunity hidden in that cost. If the campaign reporting is being rebuilt anyway, it is the one moment where you can decide to rebuild it on observed data rather than on assigned data. Rebuilding the same manual campaign ID chain on a new platform gets you back to where you were, with the same blind spot, three quarters later.

Put the question a board actually asks next to what these systems hold: what did the pipeline we closed last quarter cost us in marketing, per channel and per campaign.

1. The spend is not in SAP. No campaign record connects to a Google, Meta, LinkedIn or Microsoft ad account, so cost is typed in or it is absent.
2. The join is manual. Only leads carrying a campaign ID can be traced back, and only campaigns somebody maintained have a meaningful one.
3. One campaign takes the credit. There is no multi-touch model across the systems, so a journey that crossed three channels is recorded as one, whichever one was closest to the form.
4. Nothing travels back. A closed opportunity does not become a conversion in the ad platform, so the algorithms optimising your media never learn which clicks produced revenue.

Every one of those is a data collection problem rather than a reporting problem, which is why it survives every new dashboard.

Plainly first: there is no native SAP connector today. HubSpot, Salesforce, Microsoft Dynamics 365, Pipedrive, Attio, Close and GoHighLevel connect natively; SAP connects through the webhook and the open API, or through an integration layer such as Zapier or Make.

What it adds is the collection step none of the three SAP products performs. One script on your website, live in about 21 minutes, records every session server-side on your own domain at 95%+ accuracy and captures each platform's click ID at the moment of the click: gclid with gbraid and wbraid, fbclid, li_fat_id and msclkid, plus the UTMs and the landing page. When the lead is created, in Sales Cloud or anywhere else, that anonymous history is joined to it, so the campaign on the record is observed rather than assigned.

Spend is pulled from Meta, Google, LinkedIn and Microsoft Ads and joined to the opportunities themselves, so cost per closed opportunity is calculated from two measured numbers. And when the opportunity closes, the amount goes back to the platform that produced the first click. That is the loop the campaign entity was always supposed to close and never could.

Keep going with SAP attribution and what Sales Cloud never sees. The same analysis for CRMs with a native connector: Dynamics 365 campaign management and Salesforce campaign influence. For the models behind all of it, multi-touch attribution and offline conversion tracking.