I have configurated some content groupings through the datalayer (extracted wordpress pagecategory as a variable, and prepared the basic analytics code to tell the content group based on the variable extracted). Everything should be working fine, when I test with the tag manager debugger, you can see the content group extracted perfectly.
The thing is, when you get inside the analytics, you see that sometimes that same page goes to its supposed content group, and sometimes goes to "Not set" group. I implemented the content groups on 9th of august, both have all their data from that date onwards ( so I dont think it has to do with historical data). This seems to be happening with more than 80% of the total traffic. Any idea what I could be doing to debug this? Everytime I get inside the tag manager debugger, the content group call is showed perfectly fine
I use tag manager plugin on wordpress to configurate the datalayer. https://es.wordpress.org/plugins/duracelltomi-google-tag-manager/ Universal analytics tag is implemented. Wordpress is version 4.9.8 .
Here you can see overall data of content groupings inside analytics ( They do seem to be firing)
Here you can see that the page does track effectively inside its content group
But also tracks that same page inside " not set" content group
Its really weird, eveyry time I use debugger on the page, the content group call is donde fine, with no problems. But inside the analytics data that same page is being located to two different content groupings, the true one, and " not set".
How can I debug this? What could be wrong?
here are the configuration pics https://drive.google.com/open?id=10ICT2PTwdBgc1uTyom37IU7CfKKMt9a4
I cant share more than 8, so I had to solve with a google drive share.
Here on the other hand is the content group report update content group report update
ASSUMPTION - the URL is editing thr URL for privacy reasons. I will edit this out after OP comments
The configurations are all correct I have gone through it multiple times to check. The problem is you are sending 3 pageviews at the moment where there should be only 1 on one GA ID.
If you go into the source code, you will find that you have gtag.js firing a pageview, analytics.js firing a pageview and then there is Google Tag Manager firing a pageview.
Now to the meat of the problem - The content grouping that you see is because of the Google Tag Manager configuration, but as you have enabled content grouping, the pageviews from gtag.js and analytics.js do not send any content grouping information hence the (not set). And this also explains why one page would be categorised into a content group as well (not set).
PS - Posting this as the solution as I have already invested enough time trying to debug it :)
