Antonio Candela

Hello @stefansic ,

Thank you for reaching out.

I am sorry to hear that. You can use the following snippet as an MU Plugin (place it in a .php file and upload it to the folder /wp-content/mu-plugins/, or remove the first <?php tag and then put it in functions.php of your active theme) to prevent this behaviour. It will prevent the Complianz resolution from being added. However, note that in themes like Twenty Twenty-Four, other image sizes may still be added (which are not controlled by Complianz).

<?php
function remove_cmplz_banner_image()
{
remove_image_size('cmplz_banner_image');
}
add_action('admin_init', 'remove_cmplz_banner_image', 20);

In any case, we will take this feedback into account and consider the possibility of introducing a toggle for this functionality in the future.

I hope this helps.

Best regards,
Antonio

Hello @h4y3k ,

Thank you for reaching out.

Have you applied this CSS class to the div containing the embedded video or to the outer block?
If you applied it to the outer block, try wrapping the video inside a <div> and assigning the class name block-ytprefs to that wrapper instead, it might help solve the issue.

Let me know.

Best regards,
Antonio

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

I hope this helps, looking forward to hearing from you soon!

Best regards,
Antonio

Hello @007matty ,

Thank you for reaching out.

The feature you’re referring to is “Manage Consent Display Options,” located in Consent Banner > General. By default, it’s set to “Hover on Desktop – Hide on Mobile,” allowing users to revisit their choices. 

If you prefer to remove this option, you can select “Hide Everywhere” from the dropdown menu and click Save. This will make the manage consent tab disappear once cookies are accepted or denied.
If the changes are not reflected, please clear your WP cache.

I hope this helps!
Best regards,
Antonio

Hello @dillhausen ,

Apologies for the long wait. We’ve fixed this issue via cookiedatabase.org. Please sync the cookies again to see the changes reflected.

Let us know if everything works as expected!

Hello @taotier,

Thank you for reaching out.

I am sorry to hear that. Have you made sure to select the right data stream and Google ID (not the measurement ID)? I have made a fresh new GA4 tag and everything went flawlessly, configuring it for GDPR as stated here, and the session_start was recognized every time (screenshot of real-time data here). Could you please double-check that?

Please let me know.

Best regards,
Antonio

Hello @dillhausen ,

I am glad to hear that. By its logic, the Complianz Banner won’t load inside the Cookie Policy, as the possibility to choose preferences is available in the Cookie Policy itself (e.g., selecting which cookie category to enable by checking them in section 7.1).

Anyway, I am glad that we solved this. Wishing you a nice day!

Hello @elo8617 ,

I appreciate your kind words. Unfortunately, this doesn’t strictly depend on us, as you can understand. It’s connected to how Elementor loads the front-end. A final solution, as you suggested, could be moving everything to a dedicated page.

I hope you were satisfied, though. Please feel free to open a new thread if you need further help.
Wishing you a nice day!

Best regards,
Antonio