• Resolved Nadav Levi

    (@123nadav)


    I hope you’re doing well.

    I’m facing a dilemma and need some clarification. I’m currently using the CookieYes plugin with a specific banner version designed for visitors from the U.S., along with Google Site Kit’s Consent Mode on my website:

    [ redundant link deleted ]

    As you can see on my website, visitors are not required to click an “Accept” button or anything similar. This is because my audience is primarily based in the U.S., and CookieYes recommends this type of banner for U.S. visitors.

    I previously opened a ticket in the WordPress forum related to Google Site Kit because the Consent Mode is implemented through their plugin. You can view the ticket here:

    https://wordpress.org/support/topic/cookieyes-banner-for-usa-countrys-google-site-kit-consent-mode/#post-18311381

    The Google Site Kit team tested my website from the EU and mentioned that Consent Mode did not trigger for them, which makes sense since it shouldn’t activate automatically for EU visitors. However, I still see data appearing in my GA4 account, so something seems inconsistent here.

    The support team advised me to discuss this issue directly with you and recommended conducting an automated check specifically from within the U.S.

    Unfortunately, I can’t perform this test myself since I am currently located in Spain. If you could assist me with this verification, I would greatly appreciate it. Once we have clarity on this, I’ll return to Google Site Kit to follow up accordingly.

    Thank you very much for your assistance.

    The page I need help with: [log in to see the link]

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Support CookieYes Team

    (@cookieyesteam)

    Hi Nadav,

    We’ve already shared this information with you through your support ticket, but reiterating it here for reference:

    Let’s break this down to understand what’s happening and identify the source of the inconsistency.

    It looks like you’re using the CookieYes plugin with the US State Laws (Opt-Out) banner set to apply Worldwide on your website. Please note that this banner allows cookies by default unless the user opts out.

    Keep in mind that Google Consent Mode is required for Google Ads and Google Analytics users targeting the European Economic Area (EEA), Switzerland, and the United Kingdom. Consent Mode ensures your site adjusts its behaviour based on the user’s consent preferences.

    Since you’re currently using the US State Laws Opt-Out banner, it does not block analytics scripts before consent for users in the EU, which means Google Analytics 4 (GA4) may begin tracking immediately.

    If you receive traffic from the EEA, Switzerland, or the UK and are using Google Ads and/or GA4, you must use the GDPR banner for those regions and properly implement Google Consent Mode with CookieYes by following the guide below. 
    CookieYes Google Consent Mode v2 Integration for WordPress

    Additionally, please ensure that the Google Consent Mode settings are disabled within the Google Site Kit plugin since you are implementing it through CookieYes. This will prevent duplication and ensure proper functionality.

    Let us know if you have further questions, happy to help!

    Thread Starter Nadav Levi

    (@123nadav)

    Hi @cookieyesteam

    I believe there’s been a major misunderstanding, and I’d like to clarify everything as clearly as possible.

    First, the most important point: I am using the CookieYes plugin locally on my WordPress website, not your web app.

    Consent Mode is enabled through Google Site Kit and the WP Consent API, as explained in the official Site Kit documentation:
    https://sitekit.withgoogle.com/documentation/using-site-kit/consent-mode/#consentmanagementplugin

    We discussed this setup a while ago here in the support forum, and at that time, you confirmed it was okay to use the plugin this way.

    Now, here are the main issues I need help with:

    1. Incorrect tracking of EU traffic

    This specific website is for a local business in Orlando, FL, and I am not targeting EU users. I have a different website for the EU. However, I sometimes see EU traffic appearing in my GA4 even though Site Kit correctly detects that consent is not granted for EU visitors (as expected).
    GA4 should not track users from the EU when consent is not granted, but it appears that EU user visits are still being tracked.

    2. Consent mode is not granted for USA visitors by default

    I am suspect the consent mode is not granted even for US-based users, which should not happen. I suspect this is due to the way your plugin handles consent with a button-based logic.

    To clarify:

    • I’m aware Consent Mode is mainly for EU traffic, but I enabled it through Site Kit to create a global fallback in case EU users land on the site.
    • My understanding is that for US visitors, Consent Mode should be automatically granted by default since I’m using the CookieYes US version, which does not require any interaction (no “Accept” button is shown).

    However, based on what I see in GA4 and Google Site Kit behavior, Consent Mode seems to not be granted at all, even for US visitors. This could be causing improper tracking issues.

    In summary, we need to clearify the following:

    1. Why is Consent Mode via Google Site Kit and WP Consent API not working properly with your plugin? It should block GA4 tracking by default for EU users (when consent is not granted), but I still see tracked sessions in GA4.
    2. Why is Consent Mode not granted automatically for US users? There’s no consent button in the CookieYes USA POP UP version, so consent should be automatically granted for visitors in the US. We need to confirm this behavior! (Someone need get inside the website from USA and see if consent mode granted by default without clicking nothing)

    I understand you may want to promote the premium version of your plugin, but I don’t need it. Each of my websites targets a different region, and I’m only looking to ensure the free version works as expected with the WP Consent API and Google Site Kit setup. (as you see guys, its not working properly)

    Thanks in advance for your support,
    I look forward to your help in resolving these issues.

    Best regards,
    Levi

    Thread Starter Nadav Levi

    (@123nadav)

    @cookieyesteam

    I see that no one has responded here yet, so we kindly request Google Site Kit to intervene directly:

    https://wordpress.org/support/topic/cookieyes-banner-for-usa-countrys-google-site-kit-consent-mode/page/2/#post-18408625

    The minimum required is to address these critical issues. My website does not need geo-targeting, as it is neither an international nor an e-commerce site.

    I cannot control the internet or block EU visitors. Therefore, the minimum expectation is a simple fallback Consent Mode V2 solution for EU users. I do not require geo-targeting and certainly shouldn’t have to pay €100 for such functionality. I understand you may want to promote your plugin, but in my case, it simply isn’t necessary.

    Thank you for your attention to this matter.

    Thread Starter Nadav Levi

    (@123nadav)

    OK, i talk with Google Site Kit, and they officially dont want to help, so the only thing left to do, is to move you online web app… i try avoid it for performance reasons, but i will do it because no body want to help me with this isiue.

    you can close the ticket, i will open a new one if i need (for configure the consent mode via your web app).

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    you can close the ticket

    Support topic you mean. We do not have tickets here and never have. I know it seems like a minor point but it is important in setting user expectations. “Ticket” implies customers and there are none of those here too.

    i will open a new one if i need

    If it’s a different topic, cool. If it’s the same, please just continue here. Duplicate topics are archived when found. You can mark this topic unresolved if that happens.

    Thread Starter Nadav Levi

    (@123nadav)

    Hi @jdembowski,

    It’s a similar issue, but in this case, there are no other plugins involved, and I’m exploring a different approach that might better align with both EU and U.S. privacy regulations.

    I believe it’s best to open a new topic/ticket for this method, especially since @cookieyesteam tends to respond slowly and often replies only once per topic or ticket.

    This is a critical issue because non-compliance with these laws can result in fines of up to €25,000 or $25,000, depending on the nature of the violation caused by the plugin.

    @jdembowski, I hope you can understand the urgency here.

    Thanks for your attention!

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    I believe it’s best to open a new topic/ticket for this method, especially since @cookieyesteam tends to respond slowly and often replies only once per topic or ticket.

    No @123nada, really do not do that. The new topic for the same thing will be archived when found. I have archived your new topic. Duplicate topics makes it harder for volunteers to help you.

    These are community volunteer forums. You are not a customer, @cookieyesteam is not a company here. They, like you and I are unpaid volunteers helping community members out of the kindness of their heart for free.

    This is a critical issue because non-compliance with these laws can result in fines of up to €25,000 or $25,000, depending on the nature of the violation caused by the plugin.

    That does not matter here, not even a little bit. While it matters to you and should, remember, you are using free software and getting free volunteer support. if you really have that serious a problem with this plugin or any plugin hosted on this site, feel free to stop using it.

    You always have that option.

    Thread Starter Nadav Levi

    (@123nadav)

    Hi @jdembowski,

    This isn’t exactly the same thing, it’s a similar problem as this topic mention, but function differently and uses a different method, which is fully supported by the CookieYes plugin. This why i open new topic/ticket.

    That said, I noticed you deleted my new topic/ticket instead of making things easier for me, so I’m sharing it here in this message.

    By the way: I understand the plugin i am using is free version and this is a free support forum, but there’s still logic behind the “free support” on this forum, including good reviews, recommendations, and the potential for future paying customers with this free support forum. Right now, I might be using the free version, but I could become a paid customer at any moment. But If I don’t get proper support for something so basic while using the free version, why would I upgrade to premium version?

    I hope this makes sense and you understand where I’m coming from.

    Since my original ticket was removed, I’ll go ahead and post the topic here as you’ve left me with no other choice:

    —————————————————————————————————————–

    So, I’ve already given up after Google Site Kit refused to assist and you not responded over a week. so i try another way, this method is 100% CookieYes plugin and the web-app.

    Here’s what I’ve done so far:

    I connected my website to the CookieYes app without enabling Consent Mode. Now, I’m trying a new approach with your web-app platform, as everything is fully managed by CookieYes, with no additional plugins involved.

    Consent Mode is currently not active on my U.S.-based website:

    [ redundant link deleted ]

    As I mentioned before, this site targets only U.S. customers. However, since I can’t control internet traffic, some users from the EU may occasionally visit the website.

    We do not want to use geo-targeting or purchase the premium version of CookieYes, as it’s not necessary for our situation. (maybe in the future, if we will go worldwide).

    We simply want to block all cookies for EU visitors if they happen to land on the website. We don’t target or sell to them, they are not important to us, we just want to stay 100% compliant.

    Now, when connecting the site to your CookieYes app, I see a few options related to Consent Mode.

    When Consent Mode is activated, there’s a consent management panel where you can select which countries to grant or deny consent by default (screenshot):

    https://ibb.co/JwWw28h4


    In the United States, Consent Mode is not required by law. In fact, I don’t need to activate Consent Mode V2 at all.

    However, because I want to remain compliant and ensure that cookies and tracking tools (like GA4, Google Ads, etc.) are blocked for EU visitors, I’m considering enabling it and managing it properly through your platform.

    Here are my questions:

    1. Do you recommend enabling Consent Mode for U.S. visitors even though it’s not legally required?
    2. If you do not recommend enabling Consent Mode for U.S. visitors, what are my options to remain compliant and block cookies for EU users only?
    3. How does Consent Mode behave when used with the U.S. Privacy (Opt-Out) banner in CookieYes?
    4. Is there an option in the CookieYes Consent Mode management console to automatically block EU visitors by default, as shown in the screenshot I provided?
    5. Can you please confirm the correct setup to block cookies and tracking (GA4, Google Ads, etc) only for EU users while keeping everything functional for U.S. visitors using the U.S. Opt-Out Banner in CookieYes?
    6. Can you confirm if we set consent mode V2 only for EU countrys, the consent mode be “denied” AND GA4, cookies and other tracking cookies will be block as well? as you remember, Google Site Kit + CookieYes consent mode was “denied” for EU users but GA4 still was getting visits and track them with USA Opt-out banner via CookieYes. We need to be sure this will not happend again when we setup Consent Mode v2 only with CookieYes (if you look on the screenshot i sent, you will see maybe has an option to do it the right way)

    I’m pretty sure you understand what I’m trying to achieve here.

    It’s not complicated and honestly, between you and me, there’s no need for geo-targeting for something like this. I simply don’t care about EU visitors/users. I just want all of them to be “denied” by default to remain compliant. (when i said denied, i mean to the cookies + consent mode V2)

    Technically, I could block all EU traffic through my server or firewall, but I prefer not to do that because it could negatively impact SEO.

    I think a major plugin like yours (you have a lot of users you very famous) need to provide a solution for something so basic.

    Thanks again,

    Levi.

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    Right now, I might be using the free version, but I could become a paid customer at any moment.

    That’s great that you are… possibly? open to that? It also changes nothing here.

    If you do become a customer of this developer, I have no idea if they have a paid version or not, you would need to avail yourself of support on their site.

    This site is not for customers or even pre-sales conversations.

    For pro or customer support, you would need to contact the developer on their site. This includes pre-sales information.

    As the developer is aware, customers may not be supported on this site.

    https://wordpress.org/support/guidelines/#do-not-post-about-commercial-products

    NOTE! I know you are not their customer at this time. I’m just explaining about how it will go should you choose that route is all.

    Thread Starter Nadav Levi

    (@123nadav)

    I got you @jdembowski , Shabat Shalom my freind.

    I will wait for their respond (hopefully, i dont think they will replay)

    Plugin Support Ryan (CookieYes Support)

    (@ryancysupport)

    Hi @123nadav,

    Please find the answers below:

    We do not recommend enabling Google Consent Mode for U.S. visitors, as it is not legally required under current regulations.

    If you’re looking to block cookies for EU users while maintaining full functionality for U.S. visitors, you’ll need to use the GDPR banner for the EU and the U.S. State Law banner for the U.S. This setup relies on the Geo-targeting feature, which is only available on the paid plans of CookieYes. It’s not included in the Free version.

    Regarding the U.S. State Law banner, it functions as an opt-out banner. That means consent is granted by default unless users explicitly opt out by clicking the “Do Not Sell” link.

    As for the default region settings under Google Consent Mode, these only apply until the CookieYes banner is loaded. Once the banner is active, actual consent is obtained through the banner, not the default region settings. Therefore, using only the default region settings will not block cookies for EU visitors.

    To summarize:
    It is not possible to use the opt-out banner for the U.S. (or worldwide) while simultaneously blocking cookies for the EU using the Free version. To achieve this setup, Geo-targeting is essential and is only available in our premium plans.

    Plugin Support Ryan (CookieYes Support)

    (@ryancysupport)

    Hello @123nadav,

    It has been quite some time since our last communication. As we did not receive any follow-up questions from you, we will mark this thread as resolved.

    Please open a new thread if you are still facing issues or have questions that you need us to answer.

Viewing 12 replies - 1 through 12 (of 12 total)

The topic ‘Quastion about constant mode and CookieYes banner for the USA’ is closed to new replies.