Does SAP Customer Experience require cookie consent?

Conditional. SAP CX spans essential and marketing categories. Core commerce — cart, checkout, authentication — is strictly necessary and consent-exempt. Behavioral tracking, personalization, and customer profiling require marketing consent. Load essential commerce scripts immediately and defer tracking scripts until consent is obtained.

What does SAP Customer Experience collect?

SAP CX collects browsing history, product interactions, search terms, purchase history, and session identifiers. Personalization scripts serve targeted content based on visitor attributes. Data feeds into SAP Marketing Cloud for campaigns, SAP Sales Cloud for lead scoring, and SAP Service Cloud for support context. Cookie names vary by deployment.

How does ConsentStack handle SAP Customer Experience?

ConsentStack splits SAP CX scripts into two tiers. Essential commerce components load without a consent gate. Behavioral tracking and personalization scripts are classified as marketing and blocked until consent is granted. ConsentStack uses script domain patterns and cookie signatures to distinguish between the essential and marketing tiers.

What tracker domains does SAP Customer Experience use?

ConsentStack has catalogued tracker domains for SAP Customer Experience including hybris.com. These are the network destinations SAP Customer Experience's scripts contact, which a consent platform blocks until a visitor agrees.

SAP Customer Experience - CX Data Privacy

Back to Vendor Library

Overview

SAP Customer Experience (SAP CX, formerly SAP C/4HANA) is SAP's integrated customer experience suite encompassing commerce, sales, service, marketing, and customer data management modules. When detected on a website, SAP CX components are typically powering storefront personalization, customer data collection, or behavioral tracking that feeds into SAP's unified customer profile. The platform bridges e-commerce functionality with marketing automation, creating a combined footprint that spans essential commerce operations and non-essential behavioral tracking.

What This Script Does

SAP CX deploys multiple script components depending on which modules are active on the website.

Personalization engine: Client-side scripts evaluate visitor attributes and behavioral data to select and render personalized content variants — product recommendations, targeted banners, and customized page layouts
Customer data collection: Scripts capture browsing behavior (page views, product interactions, search queries), form submissions, and engagement events. This data feeds SAP's Customer Data Platform (CDP) to build unified customer profiles.
Cookies set: The platform sets first-party session cookies for cart management and authentication (essential), plus persistent visitor identification cookies for behavioral tracking and personalization (non-essential). The specific cookie names vary by deployment configuration.
Commerce components: Storefront scripts manage product catalog display, shopping cart, and checkout flows — these are essential e-commerce functions
Data collected: Browsing history, product interactions, search terms, purchase history, customer profile attributes, and session identifiers. The breadth of data collection reflects the platform's goal of creating a 360-degree customer view across channels.
Cross-module integration: Data captured by the web tracking feeds into SAP Marketing Cloud for campaign targeting, SAP Sales Cloud for lead scoring, and SAP Service Cloud for customer context during support interactions.

Consent & Compliance

SAP Customer Experience spans both marketing and functional consent categories.

Under GDPR and ePrivacy, the platform requires a split consent approach. Essential commerce functions (cart, checkout, authentication) qualify as strictly necessary under the ePrivacy Directive. Behavioral tracking for personalization, customer profiling, and marketing automation requires explicit consent, as these cookies and data processing go beyond what is necessary for the core e-commerce service. SAP provides configurable consent management hooks within the CX platform to support this split.

Under CCPA/CPRA, the behavioral profiling and customer data unification across channels constitutes processing of personal information. If this unified profile data is shared with SAP Marketing Cloud for advertising or campaign targeting, it may constitute "sharing" for cross-context behavioral advertising under CPRA.

Should You Block This Without Consent?

Conditional. The commerce components (cart, checkout, product display) are essential and should not be blocked. The behavioral tracking, personalization engine, and customer profiling components should be blocked until the user grants marketing consent. Implement a layered approach: load essential commerce scripts immediately, and defer personalization and tracking scripts until consent is obtained.

Is SAP Customer Experience GDPR compliant?

SAP Customer Experience typically loads marketing and functional trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So SAP Customer Experience can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads SAP Customer Experience, not on SAP Customer Experience itself.

Visit website