Title: Cookie Problem
Last modified: May 12, 2025

---

# Cookie Problem

 *  Resolved [executekone](https://wordpress.org/support/users/executekone/)
 * (@executekone)
 * [1 year ago](https://wordpress.org/support/topic/cookie-problem-9/)
 * Hello,
 * I’m experiencing an issue where the website scan never completes. It always gets
   stuck before finishing, sometimes at 60% and other times at 70%. Disabling the
   website scan temporarily resolves the issue, allowing me to rerun it, but the
   next scan also gets blocked.
 * Additionally, I’ve encountered another problem with the Google ID tag field. 
   When I set it to fire the script via Google Tag Manager, the field is missing.
   Also, I have two Google tag headers on my website. When I set it to Google Analytics,
   the line added by Complianz is removed from my website’s header, leaving only
   the functional one (which I believe is added by SiteKit).
 * Best regards,
   Daniel

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Plugin Support [Antonio Candela](https://wordpress.org/support/users/antoiub/)
 * (@antoiub)
 * [1 year ago](https://wordpress.org/support/topic/cookie-problem-9/#post-18462866)
 * Hello [@executekone](https://wordpress.org/support/users/executekone/) ,
 * Thank you for reaching out.
 * To start, having both Site Kit and Complianz insert Google scripts is not ideal.
   If you’re working with multiple Google tags, the best approach would be to use
   Google Tag Manager (GTM). This allows you to manage all tags within a single 
   container.
 * If you’re only adding individual tags, Google Site Kit is the better option. 
   Complianz supports (at a time):
    - One GTM container ID
    - One GA4 Tag for Statistics and up to two Tag for Marketing/Advertising
 * Please also keep in mind that if you’re using Site Kit, Complianz will automatically
   enable the plugin integration under Integrations > Plugins. This disables the
   ability to manually add any ID or tag within Complianz, which helps avoid duplicate
   implementations. So, I’d recommend removing any ID or tag you may have added 
   through Complianz, then enabling the Site Kit integration and checking if everything
   works correctly. We’ve had no issues with this setup so far, and it should integrate
   smoothly.
 * As for the site where the scan is getting stuck, it’s likely that something is
   interfering with the scan process. To troubleshoot, I’d suggest temporarily disabling
   all other plugins and running the scan from a clean browser (incognito mode is
   fine too). This will help determine whether the issue is specific to Complianz
   or caused by a conflict with another plugin.
 * Last but not least, to prevent any further issues, please make sure to exclude
   Complianz from your caching plugin, if you’re using one. We have a dedicated 
   guide available [here](https://complianz.io/javascript-delay-in-wp-rocket-and-other-caching-and-optimization-plugins/).
 * I hope this helps, looking forward to hearing from you soon!
   Best regards, Antonio
 *  Thread Starter [executekone](https://wordpress.org/support/users/executekone/)
 * (@executekone)
 * [1 year ago](https://wordpress.org/support/topic/cookie-problem-9/#post-18463084)
 * Hello,
 * Thank you for your detailed response.
 * I’ll try the steps you suggested to resolve the scanning issue. Regarding the
   Google Tag: Disabling the integration does bring the field back, as you mentioned.
   However, I’d like to clarify something: does enabling **Safe Mode** also deactivate
   the Site Kit integration? When I enable Safe Mode, the field does not reappear,
   even though, according to the description, all plugins should be disabled.
 * Based on your documentation, if I’m using Site Kit and thus the Google Tag Manager,
   I should select **“Yes, and Google Tag Manager fires this script”** in Complianz.
   But when I choose this option, Complianz inserts an empty Google Tag header. 
   Only when I switch to the **Analytics** option in Complianz does this extra line
   disappear, and only the Site Kit version remains.
 * Additionally, I would like to ask: How can I properly enable both **Google Analytics**
   and **Matomo**, as I am currently using both?
 * Best regards,
   Daniel
 *  Thread Starter [executekone](https://wordpress.org/support/users/executekone/)
 * (@executekone)
 * [1 year ago](https://wordpress.org/support/topic/cookie-problem-9/#post-18463443)
 * Additionally, I noticed that when I disable the website scan feature, the overall
   scanning process still works and runs significantly faster without any issues.
   However, if I reset and re-enable the website scan, it functions correctly for
   a few minutes before the problems return.
 *  Plugin Support [Antonio Candela](https://wordpress.org/support/users/antoiub/)
 * (@antoiub)
 * [1 year ago](https://wordpress.org/support/topic/cookie-problem-9/#post-18465715)
 * Hello [@executekone](https://wordpress.org/support/users/executekone/),
 * Thank you for your messages.
 * Going in order: yes, even with Safe Mode disabled, the integration remains active
   and the fields stay hidden. So, if you plan to use Safe Mode, please make sure
   to disable it beforehand.
 * Regarding the double GTM insertion, I found an issue that we’re going to fix 
   moving forward. Basically, if the option “Do you want to force the script in 
   the header” is set to Yes, the GTM script is inserted in the head, which results
   in two scripts being loaded and this shouldn’t happen. So please set that option
   to No. That should resolve the issue for now.
 * Currently, Complianz, can only manage one statistics tool at a time. The best
   setup would be to insert Google Analytics or GTM (since Analytics can be added
   within GTM), and then add Matomo via code, manually blocking it using the Script
   Center.
 * As for the scan itself, something might be interfering. Have you tried disabling
   all other plugins and then running the scan again?
 * Thanks in advance, and apologies for the inconvenience, we’re are now looking
   at the issue.
 *  Thread Starter [executekone](https://wordpress.org/support/users/executekone/)
 * (@executekone)
 * [1 year ago](https://wordpress.org/support/topic/cookie-problem-9/#post-18465908)
 * I believe the scan appears visually stuck but continues running in the background
   until it finishes. When I let it run for a while and then disable the scan via
   the API, it immediately shows as completed and correctly lists all cookies afterward.
   As for the double GMT insertion, it cannot be related to the “Force script in
   header” setting, as I always have it disabled and as a non Pro user, I cannot
   even enable it.
   So what is the actual purpose of Safe Mode if it merely preserves
   the plugin’s last known state, rather than disabling it as described?
    -  This reply was modified 1 year ago by [executekone](https://wordpress.org/support/users/executekone/).
 *  Plugin Support [Antonio Candela](https://wordpress.org/support/users/antoiub/)
 * (@antoiub)
 * [1 year ago](https://wordpress.org/support/topic/cookie-problem-9/#post-18469403)
 * Hello [@executekone](https://wordpress.org/support/users/executekone/) ,
 * Thank you for the details. Due to the specific nature of your issue, could you
   please reach out to us through our website?
 * Thanks in advance!

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Cookie Problem’ is closed to new replies.

 * ![](https://ps.w.org/complianz-gdpr/assets/icon-256x256.png?rev=2881064)
 * [Complianz - GDPR/CCPA Cookie Consent](https://wordpress.org/plugins/complianz-gdpr/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/complianz-gdpr/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/complianz-gdpr/)
 * [Active Topics](https://wordpress.org/support/plugin/complianz-gdpr/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/complianz-gdpr/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/complianz-gdpr/reviews/)

 * 6 replies
 * 2 participants
 * Last reply from: [Antonio Candela](https://wordpress.org/support/users/antoiub/)
 * Last activity: [1 year ago](https://wordpress.org/support/topic/cookie-problem-9/#post-18469403)
 * Status: resolved