Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Idea – Measure users that blocked GTM and/or GA #245

Open
erikmolenaarnl opened this issue Nov 25, 2022 · 2 comments
Open

Idea – Measure users that blocked GTM and/or GA #245

erikmolenaarnl opened this issue Nov 25, 2022 · 2 comments
Milestone

Comments

@erikmolenaarnl
Copy link

Hi,

In this privacy-first world with increasing usage of adblockers and browsers blocking GTM containers and GA4 events, where server-side GTM is still both costly and lots of hassle, I might have a great idea!

The idea of below article could be implemented within GTM4WP, so it shows stats how many visitors were blocking GTM from the WP Dashboard.

https://www.diogo.in/en/how-to-measure-users-that-blocked-google-analytics-and-google-tag-manager-in-a-private-way/

GTM4WP would get an extra tab with percentages of blocked/succesful GTM containers (and possibly GA).

I am not a great developer myself, but ny team could develop this and commit for the community, but I want to check first what your thoughts are and thus the probability a feature like this will be included in core. What do you think of this idea?

Looking forward to your thoughts. Thanks :-)

@duracelltomi
Copy link
Owner

Hi,

Thanks for the idea!

I would say this could be a great addition, but it needs to be a feature that can be turned on and off and it must be turned off by default.

Also, my biggest concern is always about performance. I do not think this needs to be tracked on all page loads in a session for example. When a user is blocking anything, it will be blocked on all page loads, there is no need to store this information multiple times in a session.

And I would say storing browser name and major/minor version should be enough to prevent any chance of fingerprinting.

@erikmolenaarnl
Copy link
Author

Thanks for your thoughts.

It does need some more pondering, as

A) the GTM container can be blocked

but if it is not

B) its tag events within the container (GA3/GA4/Meta/etc) can subsequently still be blocked.

So reporting should be GTM as well as the individual tag events. I am sure this is achievable within a plugin and/or client-side tracking.

Your thoughts are very welcome in fleshing this concept out! Thanks.

@duracelltomi duracelltomi added this to the later milestone Apr 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants