Cookie Statement
This Cookie Statement was updated on July 1st, 2026.
This Cookie Statement describes how SAP (hereinafter also “We”, “Our”) uses cookies and similar technologies to collect and store information when you visit emarsys.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 marketing cookies and associated 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 emarsys.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 emarsys.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 Required Cookies that are absolutely necessary to enable technical core functionalities, Functional Cookies that allow SAP to analyze the 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 emarsys.com
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 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 plugins as views displayed on website pages; e.g., for Wistia, 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 third-party video players:
This website contains plugins from:
- Wistia, Inc., 120 Brookline Street, Cambridge, MA 02139, USA
Wistia tracks how you interact with the media on this site: how much of a media you play at what points in a media you pause or rewind, etc. In some media, SAP pauses the media and requests that you provide your email address or name. You are under no obligation to provide this information, but we reserve the right to limit certain media to identified users. Wistia aggregates the data collected through the media here, including names and email addresses, and provides it to SAP. Other than providing this data to us, Wistia does not sell or provide the data it collects from our media to third parties. SAP uses this data to analyse user engagement with our media, improve the quality and relevance of our content, personalize your experience, and better understand the effectiveness of our marketing and communications. This information also helps us identify areas where users may drop off or lose interest so we can optimize our media and ensure it delivers value to our audience.
SAP does not have influence or control over the processing of personal data on the media provider’s website, and the media plug-in on our site remains active until you deactivate it or delete your cookies.
What web beacons are used and how can you 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 email 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 provided content. 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.
What cookies are on emarsys.com?
Required Cookies
| Name | Description | Duration |
|---|---|---|
| cb%3Atest | Used to test whether the browser supports cookies, ensuring proper session and cookie functionality on the website. | 1 year |
| __cf_bm | Set by Cloudflare and is used for bot management | 29 minutes |
| cmapi_cookie_privacy | TrustArc sets this cookie to manage the display of the cookie consent pop-up and to retain the selected settings | 1 year |
| cmapi_gtm_bl | TrustArc sets this cookie to manage the display of the cookie consent pop-up and to retain the selected settings | 3 months |
| notice_behavior | TrustArc sets this cookie to store the cookie preferences of visitors | 1 year |
| notice_gdpr_prefs | TrustArc sets this cookie to capture the chosen cookie categories | Session |
| notice_poptime | TrustArc sets this cookie to record the timestamp of when a banner is displayed | 1 year |
| notice_preferences | TrustArc sets this cookie to store the cookie preferences of visitors | 364 days |
Functional Cookies
| Name | Description | Duration |
|---|---|---|
| __tld__ | From Segment Analytics.js library; this cookie helps to figure out a top-level domain for a user. | Session |
| ajs%3Atest | Amplitude uses this cookie to perform an A/B test to determine whether the browser supports third-party cookies, helping to ensure accurate user tracking and analytics data collection. | 1 year |
| pfjs%3Acookies | It is used to check if your web browser supports and has enabled cookies. | 1 year |
| _ga_K4R637VJ3G | Google Analytics uses this cookie to persist session state and track page views for a specific Google Analytics 4 property identified by the ID ‘K4R637VJ3G’. It enables measurement of user interactions and site traffic analytics. | 13 months |
| cb_group_id | Clearbit uses primary purpose is to keep track of group information—such as the specific company, business account, or organization you belong to or work for. | 1 year |
| cb_anonymous_id | Clearbit uses this cookie to assign and track an anonymous identifier for website visitors before they are identified or authenticated. It is used to support visitor intelligence and lead enrichment workflows. | 1 year |
| _mkto_trk | Marketo uses this cookie to link a visitor to the recipient of an email marketing campaign, to measure campaign effectiveness | 13 months |
| ajs%3Acookies | Amplitude uses this cookie to track whether a user has consented to cookie usage, supporting analytics initialization and consent state management. | 1 year |
| _ga | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site’s analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors | 13 months |
| ajs_anonymous_id | Amplitude uses this cookie to store an anonymous identifier for a user prior to account creation or login, enabling user journey tracking across sessions. | 1 year |
| ajs_user_id | Amplitude uses this cookie to store an anonymous user identifier for tracking user behavior and analytics across sessions. It helps associate events and actions with a specific user within the Amplitude analytics platform. | 1 year |
| _gcl_au | Google Tag Manager uses this cookie to store ad click information, enabling conversion tracking beyond the landing page | 3 months |
| ajs_group_id | Amplitude uses this cookie to store the group ID associated with a user session for analytics and audience segmentation purposes. It is part of the Segment/Amplitude analytics library (Analytics.js) and helps track user groups across sessions. | 1 year |
| cb_user_id | Clearbit uses this cookie to associate user activity with a unique user identifier. Used to identify and track individual users across sessions for analytics and personalization purposes. | 1 year |
| ubpv | Unbounce uses this cookie to tack page views for analytics, helping measure user engagement and site performance across visits. | 184 days |
| ubvs | Unbounce uses this cookie to record session data (e.g., visit duration, navigation) to analyse user behaviour within a single session. | 180 days |
| ubvt | Unbounce uses this cookie to store timing information for page loads and interactions to monitor site speed and improve performance. | 3 days |
Advertising Cookies
| Name | Description | Duration |
|---|---|---|
| _uetsid | Used by Microsoft to store a session ID for tracking user interactions on a website | 1 day |
| lidc | LinkedIn Insight Tag used to track conversions, retarget website visitors, and view Audience Insights on LinkedIn members | 1 day |
| IDE | Google tags used to track website actions and events across Google Marketing Platform for advertising purposes | 13 months |
| UserMatchHistory | LinkedIn Insight Tag provides the ability to track conversions, retarget website visitors, and view Audience Insights on LinkedIn members | 1 month |
| CLID | Microsoft Clarity cookie used for user tracking and session management | 1 year |
| _uetvid | Used by Microsoft to store a visitor ID to track users across sessions | 13 months |
| _clck | Used by Microsoft to persist a user ID across sessions to track behavior over time | 1 year |
| bscookie | LinkedIn Insight Tag used to track conversions, retarget website visitors, and view Audience Insights on LinkedIn members | 1 year |
| _rdt_uuid | Reddit uses this cookie to track users across sessions for advertising and conversion tracking purposes. It is associated with Reddit’s pixel and is used to measure ad performance and enable retargeting. | 3 months |
| AnalyticsSyncHistory | LinkedIn Insight Tag used to track conversions, retarget website visitors, and view Audience Insights on LinkedIn members | 1 month |
| li_sugr | LinkedIn uses this cookie to make a probabilistic match of a user’s identity. | 3 months |
| test_cookie | Google tags used to track website actions and events across Google Marketing Platform for advertising purposes | 15 minutes |
| _fbp | Meta uses to track visitors across websites and collect information to provide customized ads | 3 months |
| MUID | Microsoft uses to record what you do on website and sends that information to Microsoft Advertising for conversion tracking and remarketing | 13 months |
| SRM_B | Helps track user interactions with Bing ads and improve ad targeting | 13 months |
| ANONCHK | Used by Microsoft Clairty Identifies and tracks users across sessions for session recording and heatmap features in | 10 minutes |
| bcookie | Stores a browser ID for LinkedIn’s social network services, ensuring the user is logged in | 1 year |
| _clsk | Used by Microsoft Clairty to connect multiple page views into a single session recording | 1 day |
| SM | Used by Microsoft Clarity for user session tracking and behavioral analytics | Session |
| 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 |
| _rdt_em | Reddit uses this cookie to track email-based user identification for ad targeting and conversion measurement purposes. It is part of Reddit’s advertising and retargeting infrastructure. | 3 months |