Many partners have asked OpenX to share its reaction to Google’s May 7th announcement about Chrome UI changes. We provide the following summary as a starting point for updates on this topic as we expect Google\u2019s implementation to become more clear in the coming months.<\/p>\n
Our summary of what Google announced<\/strong><\/p>\n Changes to Chrome were presented as an effort to provide users increased transparency about how cookies are used and to reduce cookie-based tracking to provide greater user privacy.<\/p>\n The announcement pointed to how visited websites should set and use cookies, outlined forthcoming default Chrome features designed to block browser fingerprinting technology used for non-transparent tracking, and improved Chrome user controls for managing cookies.<\/p>\n Google covered publisher controls for setting and using cookies, and specifically cross-site cookies.<\/p>\n What these changes mean to the Programmatic Ecosystem<\/strong><\/p>\n OpenX supports providing consumers with more control over how their data is collected and shared by any technology – and we believe such changes will ultimately be good for the programmatic ecosystem. With browsers, cookies are useful data sharing vehicles for users in two ways: First, publishers\u2019 \u201cfirst party\u201d cookies enable a user to remain logged in to a chosen site in a manner that enables the storage of their site preferences. Second, first and third party cookies make it easier to deliver more relevant and timely content or advertising. Google is especially focused on adding stronger controls for both consumers and publishers in the latter area.<\/p>\n Google has indicated that in coming months Chrome will require publishers explicitly allow first party tracking cookies to be used across websites by opting into the SameSite cookie attribute. When respected by the browser, SameSite prevents sharing of a cookie when it receives a cross-site request. By making SameSite a default feature of Chrome, cross-site tracking will be prevented without a publishers\u2019 opt-in.<\/p>\n Consumers, in turn, will be able to more easily distinguish between first party cookies that store login and preference management capabilities that many users want activated to personalize their content experience, and other cookies. It is safe to say that current levels of tracking will be hindered by Google\u2019s proposed changes and a publisher\u2019s overall effort around setting and managing cookies will increase. However, we believe it is likely these changes will not be implemented without providing marketers and publishers time to ensure opt-ins.<\/p>\n How this impacts OpenX product and services<\/strong><\/p>\n Just prior to the Google Chrome announcement, we announced OpenAudience\u2122, a 100% people-based solution for marketer and publisher audience management across the open web. OpenAudience will help our partners adapt to changes in Chrome and earlier changes to the Safari browser by reducing reliance on cookies as the primary user identity in programmatic advertising. We will do this by providing privacy compliant identities specific to participating publishers and demand partners that we match to available browser cookies, mobile devices and other touch points – all powered by a proprietary database designed to respect publisher permissions and user opt-ins or opt-outs. In turn, OpenX will return permitted cross-domain targeting specs for a user. Because OpenAudience is implemented as a publisher controlled and portable identity solution, we believe our partners will be less \u2018locked in\u2019 to transient identifiers like cookies.<\/p>\n We are more bullish than ever about the future of programmatic advertising. We invite you to learn more about OpenAudience and our approach to providing a superior identity solution for the open web.<\/p>\n","protected":false},"excerpt":{"rendered":" Many partners have asked OpenX to share its reaction to Google’s May 7th announcement about Chrome UI changes. We provide the following summary as a starting point for updates on this topic as we expect Google\u2019s implementation to become more clear in the coming months. Our summary of what Google announced Changes to Chrome were […]<\/p>\n","protected":false},"author":18,"featured_media":62692,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[47],"tags":[105,106],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.openx.com\/wp-json\/wp\/v2\/posts\/62689"}],"collection":[{"href":"https:\/\/blog.openx.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.openx.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.openx.com\/wp-json\/wp\/v2\/users\/18"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.openx.com\/wp-json\/wp\/v2\/comments?post=62689"}],"version-history":[{"count":0,"href":"https:\/\/blog.openx.com\/wp-json\/wp\/v2\/posts\/62689\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.openx.com\/wp-json\/wp\/v2\/media\/62692"}],"wp:attachment":[{"href":"https:\/\/blog.openx.com\/wp-json\/wp\/v2\/media?parent=62689"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.openx.com\/wp-json\/wp\/v2\/categories?post=62689"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.openx.com\/wp-json\/wp\/v2\/tags?post=62689"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}