Hi @bduperrin,
Complianz integrates with Monsterinsights. In the wizard, after the question how you manage statistics, you have the following options you can check:
– I have accepted the Google data processing amendment
– Google is not allowed to use this data for other Google services
– Always block acquiring of IP addresses
If you can answer these questions with yes, you can check those questions. This will allow Google Analytics to track statistics before consent.
Hi @rogierlankhorst that’s exactly what I did. Maybe what I did wrong is in the last screen when I chose not to handle GA with Complianz. So if I get you right, I should say OK to manage GA with complianz ? I was afraid to have duplicate tracking code.
The integration should work fine if you choose to let Complianz handle it. As the plugin will detect Monsterinsights, it should not add the analytics code itself.
If you change that setting we can check it for you.
We just did a test: you should indeed choose to let Complianz handle it for you. Because of the integration, it will be handled by Monsterinsights.
This option, to handle the statistics yourself, should not be visible when monsterinsights is active, otherwise this is confusing. I will correct this for the next release. This option was added after the Monsterinsights integration, which is why it is not conditional yet.
Thanks for reporting it!
So I configured as you recommended. It looks like I have two calls for my tracking code in the source code but I can’t tell if its a replicate or just normal.
I think I see the problem. The integration is originally built for the free version, you are using the premium version. Because the plugins checks for a class that does not exist in premium, it doesn’t recognize Monsterinsights. You can try replacing the integrations file in the plugin with this one? (or you can replace the entire plugin)
https://github.com/rlankhorst/complianz-gdpr
File:
https://raw.githubusercontent.com/rlankhorst/complianz-gdpr/master/integrations.php
So I replaced the integrations.php file with the one linked in your post.
Then the tracking code stopped appearing in the source code and the plugin told me that GA was running but not configured in complianz. I ran the assistant twice but it never asked me if I wanted the plugin to configure GA…. So I moved back to the “old” version of integration.php and everything is back to the previous situations with two calls of the tracking ID.
Btw I’m not an expert but looking at how the code is written I was wondering if one call was for the normal page and the other for the AMP version….
It seems that Google Tag Assistant gets only one pageview so everything seems to be ok…
You mean there was no analytics.js at all in the code anymore? It should not show the complianz analytics.js anymore, just the one fro Monsterinsights.
Plugin Author
Aert
(@aahulsebos)
Hi @bduperrin,
Could you log a support ticket at complianz.io? You can use the URL of this thread as the subject.
Thanks! Regards Aert
Ticket created.
So I this time I still have two tracking codes implemented and detected by GTA.
Plugin Author
Aert
(@aahulsebos)
Hi @bduperrin,
The newest release will fix this issue. We send an e-mail with the core files if you can’t wait!
Thank you for your feedback,
regards Aert
