Hi @coldrealms65, thanks for reaching out. I’d be happy to help you with this. The exclude Analytics for all logged-in users feature should exclude Analytics tracking to your website when any WordPress user is logged into the site viewing any web pages.
If you are seeing these users being tracked while logged in on your Analytics realtime report could you please share a recording of this so we can see this happening and we can help to determine why this may be happening.
Could you also share your Site Health information. You can use this form to share privately if preferred. There are a number of Analytics filters available but before looking at these, the information above would help us to better understand the issue and if a filter is required for you. Let me know if you have any questions in the meantime.
Without having time to take a video it is pretty simple to replicate. If I as the admin visit back-end page the results are shown in the Realtime analytics.
I visited the following pages:
/wp-admin/edit-tags.php
/wp-admin/update-core.php
And then when I view the realtime I see those pages pop up in the list.
I’ll post my site health via the form you provided.
@coldrealms65 Thanks for sharing the information and interesting that those pageviews are being tracked and that you can see them in your realtime Analytics.
I can see that you have a large number of third-party plugins active on your site so perhaps there’s a conflict originating from one of these preventing these pageviews from being excluded.
You could try testing this on a temporary WordPress test site to see if you encounter the same with just the Site Kit plugin active with a new Analytics property. You can go to this URL which will create atest site for you to use with Site Kit pre-installed. Simply, set up Site Kit and connected Analytics with a new property, make sure the exclude all logged-in users option is enabled and check this in your realtime Aanlytics report as you did with your site.
If you don’t see the same then this points to an issue with something in your setup and likely a conflict as mentioned above. Let me know how you get on with this.
Tested with only your plugin active and same result.
What server level items could cause this?
Turns out it wasn’t you at all, it was a jr dev adding a cloudflare zaraz injection of the tag bypassing…everything.
With a case like this I should have known to look at the resulting tag source.
@coldrealms65 Thanks for confirming this and glad you were able to find the cause.
