It seems that Google tracks now not only through cookies (that we can block) but through Java script code.
How is iodé affected by these Google changes ( How to Fully Incapacitate Google Tag Manager and Why You Should ) and is there a way to prevent or block it when using an internet browser on iodéOS ?
On my computer, I use Ublocker origin with Java script blocked by default, but when Java script is unabled, many websites don’t work.,.
Please could you provide a link to an article, or other evidence, which supports this assertion?
EDIT:
I did wade through the linked article, which describes how Google’s Tag Manager could* possibly be used for tracking, but doesn’t provide any evidence that Google - or any other actor - actually does use it for the purpose of tracking individuals.
This is from Google:
Google Tag Manager (GTM) extracts information primarily through its Data Layer, a structured JavaScript array on your website that acts as an intermediary between site events and tracking tools.
GTM extracts this data via a three-step process:
Data Push: Your website code pushes event information (e.g., purchases, form submissions, user IDs) into the Data Layer using JavaScript commands like dataLayer.push({key: value}).
Variable Creation: In the GTM interface, you create Data Layer Variables that explicitly tell GTM which specific keys from the Data Layer to monitor and retrieve.
Trigger and Tag Execution: Triggers listen for specific events pushed to the Data Layer; when a match occurs, GTM uses the defined variables to pass the extracted data to Tags, which then send it to analytics platforms like Google Analytics or advertising pixels.
This architecture ensures that GTM only accesses data you explicitly configure it to see, maintaining container efficiency while allowing third-party tools to receive consistent, structured information without direct code modification on your site.
uBlock Origin (which also works in the Iodé browser) can be configured to allow JavaScript in general, but not JavaScript from Google (with specific filters; Filter lists can also be added to Brave’s built-in tracking protection module.). This may already be achieved by some of the built-in tracking blocking lists.
I’ve found these four lists for now:
https://raw.githubusercontent.com/nickspaargaren/no-google/master/pihole-google.txt
https://gist.githubusercontent.com/v1nc/92dc7521516096c7f12c0516ed9c4cc8/raw/b8b779e24330dc3e848ef3dde1dce7ae325a47df/google_without_youtube.txt
https://raw.githubusercontent.com/mypdns/matrix/refs/heads/master/source/alphabet/wildcard.csv
https://raw.githubusercontent.com/mypdns/matrix/refs/heads/master/source/alphabet/wildcard.rpz-nsdname.csv
You can (and should) use NoScript and block GTM (and several others) as “NOT TRUSTWORTHY”. You can still allow JS for the particular TLD.