The company has recently announced a change to its advertising practices: they plan to allow the use of tracking pixels by select advertisers. I am under the impression that this is merely formalising (and better-regulating) existing practices, but I'm not actually sure if my assumptions are correct.
Will the new, limited tracking wholly replace the ad-hoc tracking that advertisers have been doing so far, restricting it only to advertisers on your approved list?
And just confirmed that the Google ads can still perform additional tracking, by observing one sending a fingerprint to Oracle. I am sympathetic to the use of Google ads, since, you know, money – but there's got to be another way. And even if there's not, that's no reason for the other stuff, like Google Analytics, Google Tag Manager, Google's JS CDN (when you have your own, in-house, one), and the Google equivalent of that "Facebook profile pictures leaks data to Facebook" issue […] — wizzwizz4 2023-02-16 08:40:52Z
Or is this additional tracking on top of that?
Will this change invalidate the consent granted by existing users, requiring them to re-consent?
Since you're changing what you're asking permission for, it should. The change should not invalidate the withholding of consent, though: please don't just re-display the box for everyone.
Saying yes to something doesn’t mean saying yes to everything — Consent Is / Is Not
Asking for consent until “no” becomes “yes” is not enthusiastic consent – asking once should be enough. Respect the answer you get. — Confused by consent?
(I hope it's less patronising to provide this guidance pre-emptively. I'm giving it because I really don't know what guidance the company's been given, and I'm aware that the advertising industry has rather abusive and self-serving ideas about various things.)
Do you plan on informing all users about the data sharing, the same way you inform those in GDPR jurisdictions?
I appreciate that you've featured the announcement across the network, but most of us won't know to read that. I'll also note that users may be using VPNs, or otherwise spoofing your location, and your obligations under GDPR still apply to them if they are physically located within the EU (or other applicable territories), so you kinda can't rely on auto-detection at all. Don't listen to the “GDPR-compliant solutions” industry on this one, if they tell you otherwise: they're notorious for selling snake oil, and have provided you with non-compliant “solutions” before.
P.S.: I don't think people should have to worry about all this. For readers who find it dull and wish to just be rid of it, I advise installing the Consent-O-Matic (ff) browser extension, which lets you set-and-forget your consent settings for every website at once. I would be remiss not to mention uBlock Origin (ff, deb) as well: it handles common malware vectors, unapproved client-side tracking attempts, and some fallout of the browser wars… though please consider allowing the ads on Stack Exchange. They must really need the money, even if they still eschew the Wikipedia funding model.