\n<\/p>\n
That\u2019s why, in the coming weeks, we\u2019ll be rolling out a feature in\u00a0Display & Video 360\u00a0that uses machine learning to help advertisers manage ad frequency in a way that respects user privacy when third-party cookies are missing. And in the future, we plan to bring this capability to our display offerings in Google Ads.<\/p>\n
Using traffic patterns where a third-party cookie is available, and analyzing them at an aggregated level across Google Ad Manager publishers, we can create models to predict traffic patterns when a third-party cookie isn\u2019t present. This allows us to estimate how likely it is for users to visit different publishers who are serving the same ads through Google Ad Manager. Then, when there is no third-party cookie present, we\u2019re able to optimize how often those ads should be shown to users.<\/p>\n
Since we aggregate all user data before applying our machine learning models, no user-level information is shared across websites. Instead, this feature relies on a publisher\u2019s first-party data to inform the ad experience for its own site visitors. It\u2019s an approach to managing ad frequency that\u2019s more privacy safe than workarounds such as fingerprinting, which rely on user-level signals like IP address, because it respects a user\u2019s choice to opt out of third-party tracking.<\/p>\n
This is a step in the right direction as we work across Google to raise the bar for how our products deliver better user experiences while also respecting user privacy. And this approach to ad frequency management can be a model for how the use case might one day be solved industry wide at the browser level. It\u2019s consistent with Chrome\u2019s explorations<\/a> of new technology that would advance user privacy, while ensuring that publishers and advertisers can continue to sustain access to content on the open web.<\/p>\n As we continue engaging with users and key industry stakeholder groups, we look forward to sharing more of what we learn. Stay tuned for more updates on our blogs.<\/p>\n<\/div>\n