Antonio Candela

Hello @rayeason ,

No, selecting only one region is not a paid feature. Quite the opposite: the paid feature is the ability to select two or more regions at the same time.

Best regards,
Antonio

Hello Wayne,

Thank you for the detailed report.

I can confirm that this is a common occurrence that varies depending on the specific theme in use. It happens because Complianz is loading its standard CSS (which is designed for standard light backgrounds), while Flatsome is applying its own dark styling to the containers, resulting in the low contrast you are seeing.

To answer your specific questions:

1. Incompatibility: This is not a plugin incompatibility. It is simply a styling conflict where the theme’s specific table/accordion styles overlap with ours.
2. Dark Theme Support: Currently, we do not natively support a ‘Dark Mode’ for legal documents. However, I have logged this feedback and will forward it to our development team to consider adding native dark theme support in future updates.

That said, I checked your site, and the issue is definitely solvable via Custom CSS, as you have already started doing. The values and approach you are using to override the CSS are correct; you just need to target the specific rows.

You can find the full source code of our CSS here to identify the exact selectors you need: https://github.com/complianz/complianz-gdpr/tree/master/assets/css.

Best regards,
Antonio

Hello @wp_con ,

Thank you for reaching out.
I am sorry to hear about the issues you are experiencing with your main page.

Thank you for the troubleshooting steps you have already taken. While identifying the plugin is a great first step, a 403 Forbidden error is a generic status code. To understand exactly what is triggering the block, we need more specific details.

Could you please check your server error logs or share a screenshot of the error page? Usually, a 403 error is accompanied by a specific reason in the logs (e.g. REST API getting blocked or a file permission issue). Knowing the exact error message will allow us to identify why the server is blocking the request when Complianz is active.

Looking forward to your reply.

Best regards,
Antonio

Hello @rayeason ,

Yes, you can absolutely fire your GTM tags while keeping the banner active and the blocker disabled. You do not need to install a second GTM plugin to achieve this.

If you disable the Cookie Blocker in Complianz, the GTM container will load immediately. However, for your specific tags (Facebook, GA4, etc.) to fire without consent, you must change the Triggers inside GTM.

Here’s an example:

• Current State: If your tags are currently set to fire on custom events like cmplz_event_marketing or cmplz_event_statistics, they will wait for consent.
• Required Change: You need to change these triggers back to standard triggers like ‘Initialization’ or ‘All Pages’.

Regarding the second plugin: Installing another GTM plugin would not solve the issue. Even if another plugin loads the container, if the tags inside that container are still configured to fire on cmplz_marketing, they will simply not fire (or wait indefinitely). The logic lies within the GTM Triggers, not the plugin that loads the container.

I hope this helps!

Hello @rayeason,

Thank you for reaching out.

Our US banner functions as an opt-out banner, so your desired outcome is by design.

• In the Opt-in model (e.g., GDPR): The banner requires a mandatory choice to comply with regulations. Without explicit consent, cookies cannot be set, so an overlay is often used to ensure the user interacts with the banner.
• In the Opt-out model (e.g., US): Cookie acceptance is implied unless the user actively rejects them. Therefore, no blocking overlay is applied because the banner’s role is not to force a decision, but simply to provide an option to opt-out.

Regarding plugins or services like YouTube: Since the opt-out model loads scripts by default, compatibility issues are usually rare. If you are experiencing loading issues, it is likely due to a conflict with a caching plugin. Please try disabling caching or following this guide: https://complianz.io/javascript-delay-in-wp-rocket-and-other-caching-and-optimization-plugins/.

Otherwise, please let us know about any incompatibilities, and we will investigate.

I hope this helps.

Hello @peopleinside ,

thanks for the detailed explanation and for taking the time to create the demos.

However, the plugin you’re trying to integrate with is not available in the WordPress.org repository, so it’s either a custom solution or a commercial/ specific third-party plugin we don’t have access to.

Because of that, and since this kind of deep, plugin-specific integration would require us to debug and adapt our code around a non-public plugin, this falls outside the scope of what we can support in this case.

We’re sorry, but we’re unable to assist further with this specific integration, so we will close this thread.
Thank you for your understanding.

Best regards,
Antonio

Hello @miskitoto ,

Thank you for reaching out.

To answer your questions:

1. What is the correct way to block GA4 and GTM scripts until user consent is given using the free version of Complianz?
   I checked your site and noticed that you have duplicate manual GTM implementations. Since they are manually inserted, there must be a way to locate, modify, or delete them. I recommend checking your Theme Options or your child theme’s header.php file, as double implementation is not recommended.
   
   Our suggestion is to remove the manual scripts completely from your theme files and then configure them directly within our plugin. This ensures they are automatically blocked before consent. You can follow this step-by-step guide: https://complianz.io/definitive-guide-to-tag-manager-and-complianz/ .
2. How can we configure the consent banner so that users can explicitly accept or deny Statistics and Marketing cookies?
   The banner handles this logic by default, but if you want the options to be more explicit immediately (without clicking “View Preferences” first), you can change the layout. Go to Consent Banner > General > Categories and select the option “Accept – Deny – Save Preferences”. The banner appearance will change to the one you desire, showing the specific buttons upfront.
3. Are there any recommended steps or best practices to ensure that GA4/GTM do not send data before consent is obtained?
   Please refer to the solution in step #1. By removing the hardcoded scripts and letting Complianz handle the injection and setting up the triggers as explained, the blocking will be handled automatically.
4. Can we achieve this setup fully with the free version? If not, what exactly requires a premium plan?
   Yes, you can achieve this fully with the free version. Just follow the instructions mentioned in step #1.

Best regards,
Antonio

Hello @rayeason ,

Unfortunately, since the plugin has been disabled, I cannot see the banner to assist you directly.

However, those display issues are usually caused by your theme overriding the banner’s CSS. To fix this, your custom CSS needs to be applied with a higher priority (or specificity). Once your rules take precedence over the theme’s styles, the banner’s appearance will be corrected according to your preferences.

I hope this clears things out.