Antonio Candela

Hello @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,
Antonio

Hello @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,
Antonio

Hello @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,
Antonio

Hello @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/8a68abd441b2f0d8b2490b9a1a6176e2

Once 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,
Antonio

Hello @markhowellsmead ,

Thank you for reaching out.

Yes, this is expected. Even if consent is refused, the collect requests 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,
Antonio

Hello @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 collect requests 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.

Hello @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,
Antonio