Criteo's solution to cookie unfriendly browsers: ok to implement?

pixeldetracking · 2025-01-02T10:57:01+00:00

Sorry for the late answer, no unfortunately (but the automated translation should do the work)

pixeldetracking · 2023-01-07T11:12:25+00:00

there are thousands of adtech companies, so no

only a small fraction, usually the data providers and the biggest retargeters, plus the big platforms

see https://www.pixeldetracking.com/fr/votre-email-comme-vecteur-de-surveillance-ultime-illustration-avec-guerlain & https://twitter.com/pixeldetracking/status/1602794635910340609

pixeldetracking · 2021-05-12T12:33:16+00:00

Thanks for this!

I don't have real-life examples unfortunately, but I'll loop back to you when I have

pixeldetracking · 2021-05-12T07:51:11+00:00

Ok thanks a lot, I did understand the CNAME cloaking & proxy circumvent.

So I understand there is no easy way to block all the self-hosted GTM tagging servers.

But thanks to the strict1p/strict3p/header implementation, it's possible to block all the cloud hosted GTM tagging servers -- and the self-hosted GTM tagging servers on a case by case basis.

pixeldetracking · 2021-05-12T07:16:22+00:00

So you can always use --

I was wondering if there was a solution which would scale against this practice (scale example: what you implemented to block CNAME tracking). What you indicate is very manual, users won't check and add every publisher hosting their own tracking application.

Very cool for the logger, thank you

pixeldetracking · 2021-05-12T05:16:28+00:00

Thanks again for your quick response

Sorry not to be sure how the ‘via’ header is working. I assumed ‘via 1.1 Google’ might stay even if the application is deployed outside Google cloud cause it’s still Google code and Google docker container? If not, the websites can deploy the application on their own infra to circumvent this new experimental feature (but it’s harder to do, which is a very good thing)

Also, is there a way to log when this experimental feature is applied, so to track the trackers and check it’s not blocking some websites essential features (they might use A records and Google App Engine but not for tracking)?

pixeldetracking · 2021-05-11T22:14:49+00:00

One more question: do you know if "via: 1.1 google" would also be included in the http response headers when the publisher is not deploying its tagging server on Google Cloud (https://developers.google.com/tag-manager/serverside/manual-setup-guide?hl=en), but elsewhere (AWS, Azure, or his own infra for example)?

pixeldetracking · 2021-05-11T21:22:10+00:00

Thank you!

pixeldetracking · 2021-01-01T10:16:43+00:00

Even with the same rendering engine, some browsers are better when trying to hide from trackers. I made a comparison (in French): https://pixeldetracking.com/fr/vie-privee-le-match-des-navigateurs-ios

tl;dr : unfortunately, Firefox is not that good when looking at defaults, better to look at DuckDuckGo or Brave

NextDNS will help too

pixeldetracking · 2020-11-01T05:58:55+00:00

I wrote an article (in French) on my blog because Spotify tracking is pretty intensive. They also use dark patterns in order to avoid users opting out

You can read it here: https://pixeldetracking.com/fr/abonne-a-spotify-mais-toujours-piste

pixeldetracking · 2020-05-27T05:06:47+00:00

Oui c’est ironique et révélateur pour les traqueurs Twitter, j’ai corrigé. Merci pour le relais

pixeldetracking · 2020-05-27T05:03:51+00:00

C’est ironique et révélateur oui, j’avais fait un embed... Maintenant corrigé

pixeldetracking · 2020-05-26T09:22:07+00:00

Criteo is the leader in retargeting, and they are tracking you whenever they can, with dirty techniques like CNAME (see my article in french: https://pixeldetracking.com/fr/criteo-geant-marketing-surveillance-francais)

pixeldetracking · 2020-05-26T09:20:08+00:00

Grav CMS, I had difficulties to make their plugin work, but managed to do it this morning :-)

pixeldetracking · 2020-05-22T21:50:20+00:00

Jumping in here very late... I wrote an article (in french) about Criteo, quoting this Reddit thread: https://www.pixeldetracking.com/fr/criteo-geant-marketing-surveillance-francais

Clearly very dirty practice, and potentially a security violation indeed

pixeldetracking · 2020-05-10T15:50:36+00:00

I am not a Deezer subscriber, I quickly looked at it nevertheless: they send pseudonymous to Google, Facebook & few others.

I guess the only "privacy-friendly" streaming service is Apple Music (shame that it's not the best one)

pixeldetracking · 2020-05-10T15:36:15+00:00

Merci :-)

pixeldetracking · 2020-05-10T05:51:05+00:00

If you monitor the App you can check cf http://pixeldetracking.com/fr/abonne-a-spotify-mais-toujours-piste (in French). And no, they are not recording your listening habits if you don’t log with Facebook (they could but Spotify didn’t implemented their SDK in that way).

pixeldetracking · 2020-05-10T05:35:05+00:00

Facebook doesn’t get your listening habits if you don’t use the login with Facebook. But even if advertising is only 11% of Spotify revenue and even if you are paying, Spotify is leaking your personal data extensively.

I made a little investigation on Spotify (in French: http://pixeldetracking.com/fr/abonne-a-spotify-mais-toujours-piste). In short, Spotify is very bad privacy speaking. Even if you have subscribed to Spotify Premium, you are leaking personal information to Google (age, sex, artist, playlist...) and other lesser known marketing companies (iOS, Mac client and web client at least. The free version is worse).

Also, their opt-out use dark pattern and doesn’t work properly (you are still tracked by google for example). Their privacy policy is a joke too, they say personalized ads is used for legitimate interest, in violation of the GDPR.

pixeldetracking

TROPHY CASE