Forum Replies Created

Viewing 15 replies - 331 through 345 (of 769 total)
  • Plugin Support Antonio Candela

    (@antoiub)

    Hello @kartsa2024 ,

    I’m glad to hear that! In this case, the configuration in Complianz should be as follows:

    • Under “Select the types of third-party services you use on your site,” please check Google Fonts.
    • Once you’ve done that, the option “Will you self-host Google Fonts?” will appear, please select Yes.

    Since you’ve already configured OMGF, everything is fine and you don’t need to do anything else.

    I hope this helps!
    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @sumisuknives ,

    Thank you for reaching out.

    To better understand whether Complianz is indeed causing the problem, could you please temporarily disable the Complianz plugin and check if the tracking starts functioning correctly again? Without concrete tests, it’s very difficult to determine the root cause of issues like this, especially when multiple plugins and external services (like Google) are involved.

    I also kindly ask you to please exclude both plugins from the cache, if you have one, from our side you can follow this guide:https://complianz.io/javascript-delay-in-wp-rocket-and-other-caching-and-optimization-plugins/.

    Once you’ve done this, feel free to share the results with us.

    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @numeractive ,

    Thank you for reaching out.

    If the final goal is to make Google Ads show ads, this is something that the standard version of Complianz cannot accomplish; the premium version is needed for that. While for the rest, Complianz and Google Site Kit (which I see you are using) are totally compatible with each other. You can also install the WP Consent API to further ensure that consent is getting all along.
    You can follow this guide to install both without following the ComO v2 part, as it isn’t supported in the standard version.

    I hope this helps.
    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @webvillalba ,

    Thank you for reaching out!

    It looks like the issue is related to user permissions. The Complianz plugin only loads its settings and menu for Administrator accounts. If you’re logged in with a different role (like Editor or a custom role with not enough permissions), you won’t see the configuration options, this is expected behavior.

    Unless there are custom role modifications in place (which we don’t support), only administrators will have access to the Complianz dashboard.

    I hope it helps.

    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @kartsa2024 ,

    Thank you for reaching out.

    The loading of the font from Google APIs actually depends on the theme. It might happen that, even after rejecting cookies and having selected “No” under “Will you self-host Google Fonts?” (a setting that, when set to “No,” blocks all known Google Fonts sources, as stated in the plugin), the font still load, because the theme load fonts early, before the banner can block them. In that case, Google could still receive basic data.

    The setting you mentioned simply asks whether the fonts are already self-hosted, Complianz does not self-host the fonts for you.

    In your case, you could check whether your theme offers the option to self-host the font. Alternatively, you can use a plugin like OMGF, which handles this for you.

    If you’re unsure whether your theme supports this, the best approach would be to check the theme’s documentation or contact their support team.

    I hope this helps clarify things!

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @albarosa ,

    Thank you for the update and for testing the changes.

    It’s great news that the cart now works properly for visitors who aren’t logged in as admin; that means your customers can complete their purchases without any issues, which is what matters most.

    As for the issue that only shows up when you’re logged in as an admin, that kind of thing can sometimes happen due to how scripts or caching behave differently for logged-in users. Since every site setup is a bit different, it’s not always easy for us to pinpoint the exact cause from our side.

    That said, we’re more than happy to support you as much as we can; even if our options are a bit limited when it comes to site-specific configurations. Can you please try to clear the logged-in cache and check again?

    Hope it helps.
    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @albarosa ,

    Thanks for the details! Could you please try to disable the WooCommerce integration and exclude Complianz from the cache by following this guide?

    Please try that and let me know.

    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @albarosa ,

    Thanks for reaching out.

    I am sorry to hear that. Could you please tell us which plugins you are using on your site? Even sharing the site’s URL could help. Could you please try disabling all the plugin integrations in Integrations > Plugins and let us know?

    Thanks in advance.

    Best,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @jmaneyrol ,

    I installed both plugins, and I replicated the same issues you described. I have opened an internal task so the developers can take a look at this and find a solution.

    I hope this helps!
    Best,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hi @slapstudio ,

    Thanks for your feedback. You’re right, AdSense does require the premium version.

    But just to share a bit more: while Google’s own CMP handles only AdSense, Complianz takes care of all services on your site: analytics, marketing, iframes, you name it. Our aim is to be an all-in-one privacy solution.

    Totally understand your point though. I’ll be glad to help you if you decide to come back in the future! 🙂

    Best,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @webepc ,

    Thank you for reaching out.

    The complianz is not defined error appears to be related to the current LiteSpeed settings on your site. Unfortunately, we can’t do much on our side. Our suggestion is to keep tweaking your LiteSpeed Cache settings until the error no longer appears. It seems something in your configuration might be causing additional Complianz/site elements to be cached or deferred.

    You might want to try excluding additional Complianz variables, not just complianz.min.js, following our guide on script exclusions.

    I hope this helps, and good luck reaching that ambitious 100/100/100/100 score!

    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @manjilnepali ,

    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.

    I hope this helps!

    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @nalam-1 ,

    We’re sorry to hear the setup process wasn’t a smooth experience.

    We’d really appreciate it if you could share more details about what you found not user-friendly—this would help us improve the interface and overall experience.

    Also, while the error message might appear general, it’s actually triggered based on specific conditions. Could you let us know which error you’re seeing? We can help you more effectively and understand where things might be unclear.

    Thanks in advance for your feedback!

    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @dizzow ,

    Would you be able to create a staging site with Complianz activated so we can take a look?

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @jestemzmiasta ,

    Thank you for reaching out.

    Due to the current progression of the plugin, we now require domain authentication. Without it, it is not possible to scan the site. I apologize for the inconvenience.

    The only solution in this case would be to roll back to the previous versions of the plugin. You can check the changelog and download the version you prefer that does not have our new solution implemented. Please keep in mind that our domain authentication only improves the cookie search by having two active scanners instead of the classic one.

    I hope this clarifies your doubt. Wishing you a nice day 🙂

    Best regards,
    Antonio

Viewing 15 replies - 331 through 345 (of 769 total)