This Cookie Statement was updated on November 5, 2026
This Cookie Statement describes how SAP (hereinafter also “We”, “Our”) uses cookies and similar technologies to collect and store information when you visit news.sap.com. SAP’s Privacy Statement applies in addition to this Cookie Statement. SAP’s Privacy Statement informs you about the way SAP uses, stores and protects personal data collected. It also informs you of your data protection rights and how to exercise them. We recommend that you read SAP’s Privacy Statement.
What are Cookies and similar technologies?
Cookies are small files placed on your device (computer, tablet or smartphone). When you access a website, a cookie is placed on your device and it will send information to the party that placed the cookie.
There are other technologies performing a similar function to cookies. These include pixels, web beacons, clear gifs, and social plug-ins. These are often used in conjunction with cookies to help a website owner understand its users better.
What are first-party Cookies?
SAP’s websites contain first party Cookies. First party cookies are cookies that are specific to the website that created them. These cookies enable SAP to operate an efficient service and to track patterns of user behavior to SAP’s website.
What are third-party Cookies?
The difference between a first party cookie and a third-party cookie relates to who places the cookie on your device. SAP sometimes allows third parties to place Cookies on your device. Third party cookies are placed on your device by a third party (i.e., not by SAP). While SAP allows third parties to access SAP’s website to place a third-party cookie on your device, SAP does not retain control over the information supplied by the cookies, nor does SAP retain access to this information. This information is controlled wholly by that third party according to the respective privacy policy of the third party. For more information about these Cookies, please click the “Cookie Preferences” link in the footer of the webpage.
Analytics and Digital Marketing in the United States of America
In the United States SAP routinely works with third party analytics and digital marketing providers who facilitate and support SAP (and partner) marketing activities including targeted communications. These activities may involve the sharing of limited Personal Information (personal identifiers and contact information, your interests and interactions with SAP, professional/ employment information) for those specific business purposes. In addition to the above, SAP may also share your personal data with other third parties, or for other business purposes, with your explicit consent.
SAP endeavors to recognize common opt-out preference signals at a browser level, and frictionlessly exclude you from advertising cookie tracking.
What cookies are used?
SAP wants you to be in a position to make an informed decision for or against the use of cookies which are not strictly necessary for technical features on news.sap.com. If you elect to reject cookies used for advertising, you will be shown advertising that is less targeted to your interests. This will still allow you to use all of the functionality of news.sap.com.
When tracking and evaluating the usage behavior of users of the Web Presence by means of cookies or similar technologies includes the processing of your personal data, SAP conducts the processing based on the following legal permissions:
- GDPR Article 6.I (a) if it is necessary that We ask you for your consent to process your personal data,
- GDPR Article 6.I (b) if necessary to fulfill (pre-)contractual obligations with you,
- GDPR Article 6.I (f) if necessary to fulfill (pre-)contractual obligations with the company or other legal body you represent as a customer contact (legitimate interest to efficiently perform or manage SAP’s business operation),
- or equivalent legal permissions under other relevant national laws, when applicable.
SAP differentiates between Strictly Necessary Cookies that are necessary to enable technical core functionalities, Functional and Analytics Cookies that allow SAP to remember visitor preferences and analyze site usage, and Advertising Cookies that are used to serve ads relevant to your interests.
How can you manage and delete Cookies?
SAP provides you with the option to adjust your preferences around the placement of Functional and/ or Advertising Cookies on your device. You can access preferences at any time by clicking on the “Cookie Preferences” link in the relevant banner or in the footer of any news.sap.com page.
Each browser provides users or their admins with functionality in their respective technical settings that can be used to prevent the automated download of images, pixels, beacons or other tracking technologies. If you wish to limit the use of cookies, you may not be able to use all the interactive functions.
What are social media plug-ins?
A social media plug-in embedded on a website allows you to share content on a third-party social media provider’s website. You can recognize social plug-ins as buttons displayed on website pages that feature the logo of the social media provider; e.g., for the Facebook page plug-in, you can recognize the button by a white “f” on a black background.
SAP does not have influence or control over the processing of personal data on the social media provider’s website, and the social plug-in remains active until you deactivate it or delete your cookies. Please refer to the privacy and cookie statement or policy of the respective social media providers for more information about the social media provider’s data protection and privacy policies.
On which legal basis does SAP make social plug-ins available?
SAP uses social plug-ins on its websites on the basis of its legitimate interest to make SAP visible on social media pursuant to Article 6 (1) lit. f GDPR or the applicable national law.
How do social plug-ins on SAP websites work?
Where social media plug-ins are offered, you can choose to enable them by clicking on the respective social plug-in. This process allows the establishment of a connection to the server of the respective social media provider, and you will be redirected to that social media provider’s website for next steps.
If you have a user account on the social media provider and are logged in at the time you activate the social plug-in, the social media provider can associate your visit to SAP’s websites with your user account. In this situation, data transmissions can also take place that are initiated and controlled by the respective social media providers. Your connection to a social media provider, the data transfers taking place between the network and your system, and your interactions on that platform are governed solely by the privacy and cookie statement or policy of that social media provider. Personal data may also reach providers in countries outside the European Economic Area that may not guarantee an “adequate level of protection” for the processing of personal data in accordance with EU standards. If you do not want to share any data with the social media provider in connection with an SAP website, do not click on the social media plug-in on SAP’s website.
What are Media Plug-Ins?
A Media plug-in embedded on a website allows you to watch remote content from a third-party media provider’s website. You can recognize media plug-ins as views displayed on website pages; e.g., for YouTube, you can recognize the media plugin by a video showing the play button.
How do media plug-ins on SAP websites work?
If you want to use one of content of these media plug-ins, click on the play-symbol within the media plug-in to establish a direct connection to the server of the respective media provider. The stream of the media will be redirected from the media provider to your browser.
If you have a user account on the media provider and are logged in at the time you activate the media plug-in, the media provider can associate your visit to SAP’s websites with your user account. In this situation, data transmissions can also take place that are initiated and controlled by the respective media provider. Your connection to a media provider, the data transfers taking place between the network and your system, and your interactions on that platform are governed solely by the privacy and cookie statement or policy of that media provider. Personal Data may also reach providers in countries outside the European Economic Area that may not guarantee an “adequate level of protection” for the processing of Personal Data in accordance with EU standards. If you do not wish to share any data via the media plug-in, , do not click on the media plug-in on SAP’s website.
On which legal basis does SAP makes media plug-ins available?
SAP uses media plug-ins on its websites on the basis of its legitimate interest to make remote content visible to the user according to Article 6 (1) lit. f GDPR or the applicable national law.
Use of You Tube Video
This website contains a plugin from YouTube, belonging to Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Irland (Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, US). We use the YouTube No-Cookies function, i.e. we have activated extended data protection, videos are not accessed via youtube.com, but via youtube-nocookie.com, which, according to the provider, only starts storing user information when the video is played. As soon as you start playing an embedded video by clicking on it, the IP address, in particular, which of our web site you have visited is communicated. SAP does not have influence or control over the processing of personal data on the media provider’s website.
What web beacons are used and how you can manage them?
When SAP sends you newsletters or other email communication, SAP uses web beacons (a small .gif image) to determine a user’s ability to receive e-mail in a HTML format. A web beacon is activated when a HTML e-mail is opened. This capability enables SAP to track individual interactions with the content provided.
Browser and email clients provide users or their admins with functionality in their respective technical settings that can be used to prevent the automated download of images, pixels, beacons or other tracking technologies. If you wish to prevent your browser from communicating directly with the sender of an email, you can set your browser to do so.
Advertising Cookies
| Cookie Name | Description | Duration |
|---|---|---|
| 6suuid | A third-party unique identifier for the visitor that is managed by 6sense | 13 months |
| AMCVS_227AC2D754DCAB340A4C98C6%40AdobeOrg | Adobe Experience Cloud uses this cookie as a flag indicating that the session has been initialized. Its value is always 1 and discontinues when the session has ended | Session |
| AMCV_227AC2D754DCAB340A4C98C6%40AdobeOrg | Adobe Experience Cloud uses this cookie to retain the Experience Cloud visitor ID, also known as MID | 13 months |
| AnalyticsSyncHistory | LinkedIn Insight Tag used to track conversions, retarget website visitors, and view Audience Insights on LinkedIn members | 1 month |
| EE | Stores user interest segments based on browsing behavior (Nielsen) | 4 months |
| IDE | Google tags used to track website actions and events across Google Marketing Platform for advertising purposes | 13 months |
| MR | Microsoft Advertising tag records what customers do on your website and sends that information to Microsoft Advertising for conversion tracking and remarketing | 7 days |
| MUID | Microsoft uses to record what you do on website and sends that information to Microsoft Advertising for conversion tracking and remarketing | 13 months |
| TDCPM | The Trade Desk tag collects and processes pseudonymous data about website visitors for targeting, tracking conversions, and reporting | 1 year |
| TDID | The Trade Desk tag collects and processes pseudonymous data about website visitors for targeting, tracking conversions, and reporting | 1 year |
| TEST_AMCV_COOKIE | Temporary cookie to check if the cookie read/write capability is enabled on the browser | 13 months |
| TEST_AMCV_COOKIE_WRITE | Temporary cookie to check if the cookie read/write capability is enabled on the browser | Session |
| UserMatchHistory | LinkedIn Insight Tag provides the ability to track conversions, retarget website visitors, and view Audience Insights on LinkedIn members | 1 month |
| __cf_bm | Set by Cloudflare and is used for bot management | 30 minutes |
| _an_uid | 6sense uses this cookie for collecting information on users’ visits such as the total number of visits, average time spent on the website, and pages loaded | 7 days |
| _fbp | Meta uses to track visitors across websites and collect information to provide customized ads | 3 months |
| _gcl_au | Google Tag Manager uses the cookie to store ad click information, enabling conversion tracking beyond the landing page | 3 months |
| _gd_session | 6sense uses this cookie for collecting information on users’ visits such as the total number of visits, average time spent on the website, and pages loaded | 240 minutes |
| _gd_svisitor | 6sense uses this cookie as a long lived unique identifier of the user | 13 months |
| _gd_visitor | 6sense uses this cookie for collecting information on the user’s visit such as the number of visits, average time spent on the website, and the pages loaded for displaying targeted ads | 13 months |
| _mkto_trk | Set to link a visitor to the recipient of an email marketing campaign, to measure campaign effectiveness | 13 months |
| _twpid | Used to track user behavior for advertising and marketing purposes via X (Twitter) | 13 months |
| at_check | Adobe Audience Manager sets this temporary cookie to check if the cookie read/write capability is enabled on the browser | Session |
| bcookie | Stores a browser ID for LinkedIn’s social network services, ensuring the user is logged in | 1 year |
| bscookie | LinkedIn Insight Tag used to track conversions, retarget website visitors, and view Audience Insights on LinkedIn members | 1 year |
| demdex | Adobe Audience Manager data management platform that helps build audience profiles to identify valuable segments and use them across digital channels | 6 months |
| dextp | Adobe Audience Manager data management platform that helps build audience profiles to identify valuable segments and use them across digital channels | 6 months |
| dpm | Adobe Audience Manager data management platform that helps build audience profiles to identify valuable segments and use them across digital channels | 6 months |
| fr | Facebook tag records what customers do on your website and sends that information to Meta Ads Manager for conversion tracking and remarketing | 3 months |
| li_sugr | Used to make a probabilistic match of a user’s identity | 3 months |
| lidc | LinkedIn Insight Tag used to track conversions, retarget website visitors, and view Audience Insights on LinkedIn members | 1 day |
| mbox | Adobe Target sets this cookie to retain anonymous identifiers about the visitor for a personalized experience | 13 months |
| muc_ads | Used to track user interactions with Twitter ads to improve ad targeting and performance measurement | 13 months |
| personalization_id | Allows the visitor to share content from the website on his/her Twitter profile | 13 months |
| pi | Bombora Visitor Insights tag provides visibility into the companies visiting SAP website for reporting and targeting capabilities | 1 year |
| pxrc | Used by LiveRamp to track when user ID synchronization was last performed | 2 months |
| rlas3 | Used by LiveRamp to store an anonymized user identifier for ad targeting and retargeting | 1 year |
| s_ac | Evaluate and establish correct website domain configurations for data collection | Session |
| s_cc | Verifies whether cookies are activated on your device | Session |
| s_ecid | Contains a copy of the Adobe Experience Cloud ID | 13 months |
| s_plt | Set to track the time that the previous page took to load | Session |
| test_cookie | Google tags used to track website actions and events across Google Marketing Platform for advertising purposes | 15 minutes |
| ud | Stores a unique user ID for tracking across different websites (Nielsen) | 4 months |
Functional Cookies
| Cookie Name | Description | Duration |
|---|---|---|
| CampaignLandingPage | Records the URL of the page that directed you to website through a marketing campaign link | Session |
| campaigncode | Captures a campaign code from the URL of the marketing campaign that led to website | Session |
| client | The SAP Next Generation Data Service uses this cookie to capture the visitor’s ID for building a personalized browsing experience | 13 months |
| s_pltp | Stores the specific page name or URL associated with that page load time metric. | Session |
| url_id | Records the campaign codes present in webpage links you traverse | Session |
Required Cookies
| Cookie Name | Description | Duration |
|---|---|---|
| JSESSIONID | Facilitates account authentication | 15 minutes |
| TAsessionID | Retains a TrustArc session ID to collect and record cookie consent decisions | 30 minutes |
| __VCAP_ID_META__ | Used to store metadata and routing information related to the main __VCAP_ID__ session stickiness cookie. It ensures that subsequent user requests are continuously and reliably routed to the same application instance hosted on the cloud platform | 15 minutes |
| __VCAP_ID__ | Automatically added by the Cloud Foundry router to provide session affinity (sticky sessions). It ensures that requests from a user’s browser are consistently routed to the identical backend application instance or server node for the duration of the session, maintaining stable network connectivity and session state. | 15 minutes |
| _abck | It helps protect the website against cyber threats, automated fraud, and malicious interactions to ensure secure and continuous site operation. | 1 year |
| affinity | The affinity cookie is used to allocate a client a pointer in the ring hash, ensuring that their requests are routed to the same pod where their session exists. | Session |
| bm_sz | Akamai uses this cookie to manage and route web traffic, as part of its Bot Manager solution to detect and mitigate automated bot activity on the website. | 240 minutes |
| botinfo_sap | Used by the system to recognize bots, ensuring a secure and efficient user experience | Session |
| cmapi_cookie_privacy | TrustArc sets this cookie to manage the display of the cookie consent pop-up and to retain the selected settings | 13 months |
| cmapi_gtm_bl | TrustArc sets this cookie to manage the display of the cookie consent pop-up and to retain the selected settings | 13 months |
| country | Stores the user’s geographical location, determined by IP address recognition | Session |
| dgl_suuid | Maintains a unique session identifier (Session ID) for a user related to the SAP digital library | Session |
| dglssnid | Maintains a unique session identifier (Session ID) for a user related to the SAP digital library | Session |
| notice_behavior | TrustArc sets this cookie to store the cookie preferences of visitors | Session |
| notice_gdpr_prefs | TrustArc sets this cookie to capture the chosen cookie categories | 13 months |
| notice_poptime | TrustArc sets this cookie to record the timestamp of when a banner is displayed | 13 months |
| notice_preferences | TrustArc sets this cookie to store the cookie preferences of visitors | 13 months |
| wordpress_test_cookie | WordPress uses this cookie to check whether cookies are enabled in the visitor’s browser. It is a temporary test cookie that is set and immediately deleted to verify cookie support. | Session |