TIL
searchengineland.com/google-srslt...
Google (Search) adds a tracking parameter to organic links, Safari detects a parameter from a tracking (Google) domain and caps expiry of all document cookies to 24 hours (even after leaving the landing page, ITP bug?).
Team play.
"Safari to block tracking by default in 2023"
Dumb AI summarizing fake news 💥
"Safari prevents known fingerprinting scripts from reading state that could be used for navigational tracking, such as query parameters and document.referrer."
Known tracking scripts and unknown scripts will be fine.
webkit.org/blog/16993/n...
> Move the preference to preview
github.com/WebKit/WebKi...
> This change introduces a lower frequency deletion policy if a web site was always loaded with link decoration filtering
github.com/WebKit/WebKi...
> This patch extends that lifetime to 400 operational days.
github.com/WebKit/WebKi...
Are partitioned cookies in Safari expected to be set by third parties that also get user interactions as first party?
It seems that ITP includes partitioned cookies in its periodic removal of data from prevalent/classified (but not "known tracker") domains without user interaction.
Looks like Safari/iOS won't let "known trackers" use partitioned 3rd-party cookies.
"The vast majority of the partitioned cookies we currently see are being set by tracking domains. This doesn't benefit users and only causes more memory usage."
github.com/WebKit/WebKi...
#pinkskyStory
🎉
> Added support for cookies’ Partitioned attribute (opt-in partitioned cookies).
webkit.org/blog/16445/r...
"With bounce tracking mitigations, browsers target redirects that are not desired by publishers. With us, the redirection is used to facilitate the creation of the cross-domain/cross-device 'first' cookie that belongs to our customers."
🤨
www.journaldunet.com/adtech/15359...
"Google has acknowledged that, by necessity (ie model training), the design of event level reports links limited conversion data back to a specific individual and event
on a publisher site."
"API will be mainly used by well-intentioned advertisers"
The problem is more on the ad network/pub side...
Email from Google to Adsense Partners with the text attached below. The section "First-Party Cookie Controls are Changing" is highlighted as well as the text "your first-party cookies will also be shared with Authorized Buyers" Full text of email: Dear Partner, We're making some changes to how first-party cookies are managed in your AdSense account to simplify controls and improve your access to third-party demand. First-Party Cookie Controls Are Changing We've combined the controls for enabling first-party cookies and personalization into one single control. This means that turning on the new control will enable first-party cookies for the publisher, share it with demand sources and enable all usages including personalization. The new control would be set to the existing personalization control to aid the transition. Sharing with Authorized Buyers Currently, the first-party cookies are shared with Google demand sources (Google Ads, Display & Video 360). Starting no earlier than December 12 2024, your first-party cookies will also be shared with Authorized Buyers. However, for the time being, this sharing will not include users in the EEA, Switzerland, UK, California, and some US states. If you're already using first-party cookies for personalization, sharing with Authorized Buyers will be turned on by default. If you're only using first-party cookies without personalization, sharing will remain off. You can find more detailed information about these changes and how AdSense uses first-party identifiers in the Help Center. Sincerely, The Google AdSense Team
This week, Google publicly announced a change to how people will be tracked for online advertising - something so subtle that it hasn’t gotten any coverage yet to my knowledge. Attached is the email they sent to Adsense partners about “Rolling out first-party cookies sharing with Authorized Buyers”🧵
😵💫
"In general, this feature should be off"
github.com/WebKit/WebKi...
testable → stable → internal → ?
> Move the preference to stable and enable it by default, and tie it to tracking prevention.
github.com/WebKit/WebKi...
Link decoration filtering (removal of tracking parameters fbclid/gclid etc. from links) is now enabled by default in Safari TP 206 as part of ITP instead of private browsing only.
CHIPS flavored 3p cookies coming to WebKit?
github.com/WebKit/WebKi...
> Add a feature flag for supporting partitioned cookies
github.com/WebKit/WebKi...
Nice
"Do you want to allow %@ websites to access one another's cookies and website data?"
github.com/WebKit/WebKi...
"Some organizations operate multiple sites and require complicated interactions across those sites"
github.com/WebKit/WebKi...
I guess Conversion APIs won't work with Protected Audience ads ("in the long term")?
"In the long-term, these events could only be exfiltrated using an aggregate report."
"We can confirm that Chrome’s deprecation of third party cookies will impact Google Analytics 4, and we specifically plan to make changes to features like Google Signals"
github.com/google/ads-p...
Consent screen for the Privacy Sandbox Topics API on Android
Looks like a surprisingly proper consent screen.
Small ITP change. Data removed after 30 operational days instead of 7 for sites not loaded with cross-site link decoration.
🤔
"Privacy Budget: No feedback provided this quarter."
developers.google.com/privacy-sand...
👀
"Google has announced that Privacy Budget is no longer being actively considered as part of its Privacy Sandbox proposals. As set out in the Commitments Decision, Privacy Budget was among those proposals aimed at combating fingerprinting."
