SAP Emarsys
How to configure SAP Emarsys at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Receive personalised marketing offers, Personalise the website
Overview
This guide explains how to reflect SAP Emarsys Web Extend in the Consenter Manager. The sources do not document configurable privacy settings for Web Extend, so this guide uses a single fixed-behaviour table.
- Implement the service as described below.
- Map the implementation in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The mapping is an example, not a guarantee of legal compliance. Verify it against your implementation and current provider documentation.
At a glance
Scope. The Emarsys Web Extend tracking code (scarab-v2.js with ScarabQueue).
What the service does in this scope. Web Extend is the data collection module that tracks visitor interactions on the e-commerce site and feeds them to revenue attribution, the Automation Center, Smart Insight and Predict. Server-side implementations show the cookies s, cdv, xp and fc. Emarsys email links append parameters including sc_eh (an email hash) and sc_uid, which connect web activity to a known contact.
No configuration without prior consent. Web Extend sets persistent identifiers and builds contact-level behavioural data.
Step 1 — Implement Emarsys Web Extend
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Receive personalised marketing offers; Personalise the website (recommendations) |
| Loading | Consenter script blocking: load scarab-v2.js and push ScarabQueue commands only after consent |
| Contact identification | setEmail / setCustomerId and email link parameters identify contacts |
| Contract | SAP Emarsys data processing agreement |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Receive personalised marketing offers, Personalise the website | — |
| Tracking method | First party tracking (cross-session) | First-party cookies |
| Identifier | Device identifiers, Direct identifier | Cookies; email hash and customer ID |
| Data categories | Browsing and interaction data, Device identifiers, e-commerce Activity, direct identifier, Users' profiles | Page views, carts, purchases |
| Legal role of data recipient | Processor | Per SAP Emarsys DPA |
| Personalisation model | Profile based | Predict and recommendations |
| Maximum storage duration | Per cookie inspection | Not documented in the sources |
| Processing location | Per DPA | SAP is a German group; add the United States if the DPA lists US cloud sub-processors |
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on