Antonio Candela
Forum Replies Created
-
Forum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] Stuck on Website scanHello @shustus ,
Thank you for reaching out.
I’m sorry to hear that. Yes, it is possible to restart the scan, but if it’s not working it will probably get stuck again. You can disable the new scanner in Settings > APIs > Disable Website Scan, this will reset the scan.That said, we are currently testing some releases and are just a few steps away from publishing a branch on GitHub for testing, so affected users can try it out.
Regarding your ticket, if you haven’t received a confirmation it means it was not submitted correctly, as we always send a confirmation and are on track with all support requests.
I will update this thread with the GitHub branch soon. Thank you for your patience.
Best regards,
AntonioForum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] wp-admin/remoteHello @jairoochoa ,
Thank you for reaching out. Yes, this comes from our plugin and we are currently testing some releases. We’re just a few steps away from releasing a branch on GitHub for testing, so our users can try it out. The remote call is necessary for the new scanner to work properly.
I will update this thread with the GitHub branch soon. Thank you for your patience.
Best regards,
AntonioHello @mvittorio ,
Their support team has provided us with all the necessary information, and I’ve updated everything on our side. Please feel free to sync the cookies again so your cookie policy will reflect the latest data.
Please note that the aosRemoveClassesTimeoutCode entry is considered an administrative cookie, as it’s only used to assist with animation previews while editing content. For this reason, it won’t appear in the public cookie policy. If you’d like to change that behavior, please refer to this guide: https://complianz.io/why-some-cookies-dont-show-in-your-cookie-policy-and-how-to-fix-it.
That said, I’ve also requested additional details from Spectra so we can ensure that all of their cookies are fully documented and nothing is left unlisted.
I hope you appreciate this update.
Best regards,
AntonioHello @kingbrown75 ,
Thank you for the detailed explanation.
In this case, the reason your tags in GTM are not firing is that you have selected “Yes, with Google Analytics” in the Statistics configuration. To make GTM actually fire your tags (that includes Analytics), you’ll need to select “Yes, and Google Tag Manager fires this script” instead. Once you do this, the tags will trigger as expected.
Please make sure to apply the proper consent triggers as described in this guide: https://complianz.io/definitive-guide-to-tag-manager-and-complianz.
Regarding the 404 documentation links: we are currently restructuring the page and they should be back online later today or tomorrow.
I hope this helps! Please let me know if you have any other questions.
Best regards,
AntonioHello @projectmanuk ,
Thank you for the update.
The
collectrequest should indeed be visible in the Network tab, and I can confirm I do see it on my side (screenshot). This indicates that the implementation is working correctly and the data is being passed on to GA as expected.I also noticed that you’re using LiteSpeed, we recommend excluding Complianz from caching to avoid potential issues with consent handling. You can follow our guide here: https://complianz.io/javascript-delay-in-wp-rocket-and-other-caching-and-optimization-plugins/.
I hope this helps.
Forum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] Document Links aren’t workingHello @mattenser ,
Thank you for reaching out.
The “Manage services” text refers to the Consent per Service link. It provides granular control so visitors can enable or disable individual services (you’ll see a checkbox next to each service). This feature only works correctly when the Cookie Policy is generated by Complianz. If the policy isn’t generated, the link may fall back to an unrelated page.
If you want to keep this level of granularity, you can leave it enabled. Otherwise, you can disable it by selecting “No” under “Do you want to use ‘Consent per Service’?” in Wizard > Consent > Services.
I hope this helps.
Best regards,
AntonioHello @kingbrown75,
Thank you for reaching out.
These articles do not depend on the specifics of Google Analytics Pro (the WooCommerce add-on), though it does have its own integration in our plugin. I want to assure you that the WP Consent API is mandatory for this kind of setup, and Google Site Kit complies with it; it’s required regardless of whether Consent Mode (which is not mandatory) is enabled.
Please also share the issues you’re currently experiencing and, if possible, the steps to reproduce them so I can assist you better.
Best regards,
AntonioHello @ythhj ,
Thank you for reaching out.The PHPSESSID cookie is only visible in the backend because it is considered an administrative cookie. For this reason, it is not displayed in the public Cookie Policy.
However, you can change this behavior if you prefer to list it in your Cookie Policy. You can use one of the two scripts we provide, which modify the database value that tells Complianz to ignore the cookie. Depending on the script, you can insert either the slug or the name of the cookie. To find the cookie’s slug, you will need to check the database, specifically the cmplz_cookies table. Otherwise, using the cookie name as it appears in the cookie list will be sufficient.
Slug script: https://gist.github.com/tonai126/e9ae3d00698b3a3633537cf81cd4e3bb
Name script: https://gist.github.com/tonai126/8a68abd441b2f0d8b2490b9a1a6176e2Once added and kept active, the cookie will be shown in the Cookie Policy, and the setting will remain even after a new scan or sync.
I hope this helps.
Best regards,
AntonioHello @markhowellsmead ,
Yes, that’s correct. The request is technically still sent to Google, but without consent the data is discarded and does not appear in the GA reports.
Hello @markhowellsmead ,
Thank you for reaching out.
Yes, this is expected. Even if consent is refused, thecollectrequests are still sent, Google’s Consent adapts the data. Without consent, no identifiers or cookies are transmitted, only minimal anonymous information. The request is still visible, but its content changes according to the consent state.
I hope this clears things out.
Best regards,
AntonioHello @mvittorio,
Thank you for reaching out.
I’ve checked the cookie, but I wasn’t able to find any information about it. I’ve contacted Spectra directly, and as soon as I receive more details from them I’ll update you with a full answer.
Best regards,
AntonioHello @projectmanuk,
Could you please try temporarily removing the login wall on the site? Otherwise, the tracking code may not work properly. Also, in the Network tab of your browser inspector, check if you see
collectrequests going out to Google Analytics after accepting the banner and performing actions.Please let me know if anything changes. If it’s running properly in debug mode, you should also see your GA4 data stream receiving data.
Forum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] Accessibility issueHello @guidotg ,
Thank you for reaching out.
The structure of the consent banner follows a fixed framework, and adjustments to this specific aspect are currently planned. That said, Complianz does offer the option to build a fully custom banner from scratch, which allows you to meet any specific accessibility or technical requirements you might have: https://complianz.io/create-your-own-banner-from-scratch.
This way, you can adjust the markup to your needs while still benefiting from the compliance features of the plugin.
Here you can follow the GH Thread about this here: https://github.com/complianz/complianz-gdpr/issues/436.
I hope this helps, wishing you a nice day!
Best regards,
AntonioHello @projectmanuk ,
Thank you for reaching out and for appreciating our plugin.
Both guides are valid for your end goal, and you can use either or even both. With the free version, Consent Mode is not available, so you won’t be able to use or test it. However, you can still test your GTM setup with GA4.
When Consent Mode is active, a consent trigger is not required, as it will behave based on the consent signals of CM v2 itself. Without Consent Mode, however, a consent trigger is needed (in this case you should follow the Definitive Guide), since our plugin will automatically load GTM. If you want to load the entire GTM instance after consent, you can also follow this guide.
Note: For tags that are not reliant on Consent Mode (e.g. Facebook Pixel or a non-native Google tag like a Custom HTML), a consent trigger based on our events is still required; otherwise, they will fire regardless of consent.
I hope this clears things up. If you have more questions, please let me know, we’re at your disposal.
Best regards,
AntonioHello @niharikaverma95 ,
Thank you for reaching out.We support both Microsoft Clarity and the TCF Framework, but just to clarify, the TCF is a premium feature and therefore not available in the free version. If you need to use the TCF, you can consult our website for more information.
I hope this helps, wishing you a great day!