-
Google hypocritical stance: "We will not build alternate identifiers to track individuals as they browse across the web, nor will we use them in our products" blog.google/products/ads-commerce/a-more-privacy-first-web/ 🧐 1/On twitter.com
❤️ 4 Favorites
Mood -2 🙁
-
Still bullshit: "We realize this means other providers may offer a level of user identity for ad tracking across the web that we will not -like PII graphs based on people’s email addresses. We don’t believe these solutions will meet rising consumer expectations for privacy" 🧐 2/Permalink On twitter.com
❤️ 1 Favorite
Mood -3 🙁
-
Google (cryptic communication): "We are building a new feature to enable publishers to securely share encrypted signals with Authorized Buyers and Open Bidders via Ad Manager" blog.google/products/admanager/new-ways-publishers-activate-first-party-data/ 🤔 3/Permalink On twitter.com
❤️ 1 Favorite
Mood +1 🙂
-
Google (translated): "Google says it won’t trade on email-based identifiers, once the data is encrypted as an ESP, Google doesn’t know what it is and therefore will allow the ID to be traded on its exchange" adexchanger.com/ad-exchange-news/thursday-11042021/ 🪄 4/Permalink On twitter.com
♻️ 1 Retweets
❤️ 5 Favorites
Mood +1 🙂
-
The correct article: “Google’s Encrypted Signals Program Just Entered Open Beta, And Here’s What You Need To Know About It” adexchanger.com/ad-exchange-news/googles-encrypted-signals-program-just-entered-open-beta-and-heres-what-you-need-to-know-about-it/ 👀 5/Permalink On twitter.com
♻️ 2 Retweets
❤️ 2 Favorites
Mood 0
-
“Platforms that receive bid requests from Google OpenBidding or Google AdExchange will receive the encrypted ID5 ID in the bid request as an eids array, much like the standard DSP integration” support.id5.io/portal/en/kb/articles/google-esp-integration#What_is_Google_ESP 🧐 6/Permalink On twitter.com
Mood +2 🙂