Re:Using the Topics API (Chrome Only, Opposed by Firefox/Saf...
by remus on Monday September 16, 2024 @04:56AM
(#41554109)
> They simply have websites use first party cookies, send the data server side to data harvesters, tie it all to a global user profile using either identifiers from the website or from fingerprinting and then serve targeted ads.
This is legally tricky because GDPR and similar legislation requires getting explicit consent from users for this to happen. Currently this is not very well enforced (imo) but it seems likely that enforcement will become increasingly stringent in years to come.
Re:Using the Topics API (Chrome Only, Opposed by Firefox/Saf...
by realusername on Monday September 16, 2024 @05:42AM
(#41554359)
> They simply have websites use first party cookies, send the data server side to data harvesters, tie it all to a global user profile using either identifiers from the website or from fingerprinting and then serve targeted ads.
That honestly sounds like circumvention of unauthorized access. That's just breaking software protections.
Re:Using the Topics API (Chrome Only, Opposed by Firefox/Saf...
by wombarly on Monday September 16, 2024 @07:11AM
(#41554860)
Websites are moving towards providing md5/sha1/sha256 hashes of your normalized email (stripping the + from gmail) or phone number to advertisers.
A basically permanent ID. Unified ID2 is one version of this.
The 3rd party cookie ban and heavy pushback against alternative solutions suggested by Google just pushed advertisers into going an even worse route privacy wise.
They simply have websites use first party cookies, send the data server side to data harvesters, tie it all to a global user profile using either identifiers from the website or from fingerprinting and then serve targeted ads.
i.e. Conversions API (Meta), Server Side GTM (Google)
I would be surprised if most advertisers would even be interested in this topic API.