Browser Privacy and Monetate

customers are more concerned about their privacy and security than ever before as a result and in response, web browsers and browser extensions continue to evolve to better control what can and cannot occur on a given site as well as across sites most of these changes aim to mitigate the invasive nature of the advertising technology, or adtech, industry monetate isn't an adtech firm nor is it intent on tracking visitors across sites instead, monetate integrates with clients to deliver personalized web experiences for their customers most browser security features shouldn't affect monetate's functionality, and the company is committed to integrity and client safety monetate's core functionality has no need for cross party or cross site functionality, with a few edge cases while it does rely on persistence of some data at the browser level, that reliance shouldn't pose any issues because local storage of data continues a standard feature of mainstream browsers for the foreseeable future furthermore, because monetate operates with first party storage, any changes to third party storage has no adverse affect monetate and cross site cookies all cookies have an owner, which is domain specified within the cookie settings a third party cookie is a cookie set by, and on, a domain that isn't the domain that appears in the browser address bar a first party cookie is set by, and on, the same domain that appears in the browser address bar the use of cross site cookies is being phased out, and short term adjustments have been made to account for any issues introduced by google chrome's same site cookie requirement nevertheless, the following areas of monetate may be affected due to historical use of cross site (third party) cookies the monetate user interface at marketer monetate net experience previews action builder , event builder , and target builder clients using a monetate tag–based integration might also experience some impact to certain components monetate id cookies ( mt v ) baseline implementation script references specific cookie or storage related actions and who targets this impact is due to using a tag that references a third party script (from the perspective of the client domain) and from certain limitations on third party and quasi first–party cookies that specifically can alter cookie expiration and, consequently, affect monetate analytics and certain multisession targeting capabilities monitoring and mitigation efforts monetate continually changes to accommodate the ever evolving web landscape most of these changes involve the elimination of third party cookies for certain functionality, tighter integrations with clients (for example, server side integrations, cdn proxying ), and increasingly conservative use of certain browser features monetate's server side option and advanced tag based integrations using cdn proxying can circumvent most browser settings contact your dedicated customer success manager (csm) for more information additionally, monetate actively monitors browser announcements and browser usage to prioritize any developments that ensure the monetate platform and its clients experience little to no impact contact your dedicated customer success manager if you have specific questions monetate and specific browsers although monetate focuses on the "big four" browsers—google chrome, apple safari, mozilla firefox, and microsoft edge—it constantly monitors the relative popularity of other browsers to proactively solve potential issues apple safari safari is the most common browser to access monetate client sites, largely due to ever increasing mobile traffic and the fact that safari is the default browser on apple devices apple safari's intelligent tracking protection (itp) is an evolving set of features and rules to control how cookies can track user behavior itp1 x focused primarily on third party cookies, but itp2 x has introduced additional settings that cap the lifespan of client side cookies to 7 days as well as resolve loopholes some vendors used to circumvent the spirit of the rule for the purposes of itp, client side cookies are cookies set via document cookie , the traditional way of setting cookies using javascript cookies set via http, or server side, are not affected this can directly impact monetate functionality because the monetate id (the mt v cookie) is intended to last much longer than 7 days to properly track new and returning status and collect cross session behavioral data here are some specific examples new and returning visitors — returning customers who may have last visited the site 7+ days ago are considered new visitors because the historical sessions are lost behavioral targeting — data about a visitor's past behavior related to who targets, such as products viewed and past purchases, is limited to the previous 7 day unless the visitor has returned to the site and extended the lifespan of the cookie testing analytics — customers who may have last visited the site 7+ days ago can qualify for a separate testing split because their previous variant assignment has been lost see id workaround for safari intelligent tracking protection to learn how clients using the monetate javascript api or a hybrid implementation can configure the monetate tag to look to a client defined unique identifier instead of the monetate id recent updates to safari itp blocks third party cookies on your site this update means that preview mode and the monetate inspector browser plug in may not work in safari monetate has developed an alternative approach to delivering preview mode to the site to have this option enabled for your account, submit a support ticket using the {{monetatesupportcontact}} no workaround is available at this time for monetate inspector monetate recommends using a different browser such as chrome if you need to use the browser plug in google chrome google chrome serves as the default browser for many android phones and is one of the more popular for desktops and laptops starting with chrome v80, all cookies are considered same site (lax) by default unless a same site value of none is explicitly set additionally, non secure third party cookies are no longer allowed changes in the monetate platform account for this issue to avoid any issues with experience previews or the builders by ensuring that the samesite attribute is set in the session cookie and explicitly requiring that all cross site functionality be secure (https) built on the chromium source code, the browser's approach to increased web security has been dubbed privacy sandbox " this functionality involves a suite of features intended to allow most common legitimate use cases (such as cross site login) to continue to function, albeit implemented in a different way chromium developers have indicated their intent to consider the standards of the w3c community and business groups web standards committee and feedback to those standards monetate continues to monitor these sandbox features and make platform updates when and where necessary mozilla firefox mozilla has publicly indicated its commitment to robust browser privacy features while maintaining good site functionality firefox's tracking protection suite, known as enhanced tracking protection (etp), is designed to be both robust in its ability to protect end user privacy and minimally impact website functionality this trade off has been accomplished and refined through a variety of means, including allowing end users to block all third party cookies or just block trackers and to handle private browsing mode as a special case more recent versions of firefox streamline privacy considerations the browser's preferences settings allow a user to select standard, strict, or custom privacy settings, with the custom option allowing the user to block or unblock potential trackers by category (for example, third party ads, fingerprinters, or cryptominers) additionally, users can set exemptions, essentially serving as a whitelist even the standard privacy setting aggressively blocks trackers firefox relies on disconnect, inc ( disconnect me ) for its list of trackers, and monetate is on this list while standard mode doesn't appear to limit monetate functionality, the ease with which users can modify their privacy settings means that monetate can be blocked, either partially or in full depending on various settings using firefox in private mode have monetate blocked by default microsoft edge microsoft's latest browser uses a combination of disconnect and user site engagement scores to determine how to and what to block, from cookies to resources this combination provides a reasonable compromise of privacy and usability whether monetate is blocked by default depends on edge's user engagement score for that site, so it's difficult to know whether monetate is blocked for all users on a given site with microsoft edge 79 and onward, tracker blocking is robust in addition to preexisting features such as care taken to ensure that domain ownership is taken into account (that is, edge understands that one company might own two domains and is less strict in cross site blocking in such a case), trackers are more stringently blocked, and increasingly large number of types of trackers are blocked other browsers not everyone uses one of the four main browser options, so here's a look at how privacy and security measures in certain other browsers impact monetate microsoft internet explorer — internet explorer 11 is a legacy browser that still has some use it's generally strict with third party cookies and blocks many of them by default based on internal, unknown to the public blacklists however, first party cookies are generally allowed opera — this multi platform browser doesn't block third party cookies or trackers by default, although users can change this setting in the preferences brave — this up and coming browser prioritizes privacy it blocks monetate by default monetate and ad blocking browser extensions while individual browsers have improved privacy and security settings, many people use ad blocking browser extensions that can also impact monetate's ability to function the primary purpose of an ad blocker is to remove unwanted third party advertisements, but recent updates and newer options including tracking and privacy protection clients using monetate's tag–based integration or its server side option or advanced tag–based integration can use cdn proxying to circumvent most browser extensions and settings see manage first party proxies for more information faq why can't i see experiences, experience previews, or the builder tools in mozilla firefox's private browsing mode? by default, firefox's private browsing mode blocks all calls made to monetate servers this tracking protection is automatically enabled only for private windows you can change the setting that blocks monetate in private browsing mode by opening the browser settings and clicking privacy & security the default standard setting for enhanced tracking protection blocks tracking content only in private windows to customize the protection, following the guidance on mozilla's firefox support site why can't i see experience previews or the builder tools in safari? apple safari's intelligent tracking prevention (itp) preference blocks all calls made to monetate servers you can change the setting that blocks monetate by navigating to preferences > privacy > website tracking > prevent cross site tracking see browser privacy and monetate docid\ bh938mw ucx2frj n5fgi for more information about monetate and apple safari what are first party cookies? first party cookies originate from the primary domain visited by the user, hence becoming first party cookies this means that the domain of the cookie matches the domain in the browser address bar what are third party cookies? third party cookies aren't written from the primary domain visited by the user, which means the domain of the cookie doesn't match the domain in the browser address bar