The “press releases” page (ex) loads an “analytics” path: https://www.privacyguides.org/.ghost/analytics/api/v1/page_hit?name=analytics_events.
Not sure if the analytics payload is common across PG web properties.
If feasible,
- Remove the analytics payload.
- Provide opt-out, or better, make it opt-in.
- Move the analytics payload to its own subdomain so it can be added to domain blocklists.
11 Likes
My vote is primarily for removing the analytics payload outright.
11 Likes
Think given the audience of this site, nearly no one really would be in favour of analytics they couldn’t opt out of.
6 Likes