BeTheme GDPR Cookie Consent 2.0: Cookies still load after consent withdrawal and are not removed

Comments

• Phil

  1:01PM

  Hello,

  The theme itself does not create these cookies, and as a result, it cannot technically "reach into" the browser to delete them once they are set by an external domain.

  The primary role of the theme’s GDPR/Consent 2.0 integration is to correctly communicate the user's choice to gtag (Google Tag). Once the user withdraws consent, the theme sends a signal to Google stating that it no longer has permission to use data from the site.

  Ultimately, it is the responsibility of the cookie provider (e.g., Google) to respect the user's choice and stop tracking based on the signals sent by the theme. The theme acts as the messenger, ensuring your site remains compliant by passing the correct consent state to the relevant services.

  
  

  Best regards

  Learn more: Video Tutorials | How To | FAQ Vote on what comes next
• weboo-online-media

  9:18PM

  Hello,

  Thank you for your reply. I would like to clarify a few important points in a friendly way, because I think there is a misunderstanding about what I am expecting and what “GDPR 2.0 / consent” should achieve in practice.

  1. This is not mainly about deleting third party cookies
  2. I understand that the theme cannot technically delete cookies set by external domains in every case. That is not my primary expectation.
  3. The key issue is that tracking requests must stop after withdrawal
  4. A consent tool must ensure that after the user withdraws consent, no further tracking happens. In my case, after I switch consent off later, GA4 network requests such as collect or g collect still fire. This means data is still being sent, which is the real compliance problem. Even if cookies remain in the browser, tracking must not continue.
  5. A signal to Google is only sufficient if it is technically effective
  6. I agree that the theme can act as a messenger, but the result must be that tags stop firing when consent is withdrawn. If collect requests still fire after opting out, then either
  7. a) consent mode is not applied correctly,
  8. b) the withdrawal is not propagated correctly, or
  9. c) analytics is still running independently of the consent state.
  10. Practical implementations usually prevent loading or stop execution
  11. In practice, consent tools either block loading of analytics until consent is given, and/or ensure that once consent is withdrawn, analytics stops immediately. Many implementations also trigger a page reload after changing consent settings to ensure already loaded tags do not continue running.

  Because this feature is labeled as GDPR 2.0, I expect the withdrawal option to reliably stop tracking requests, not only send a consent signal while requests still continue.

  Could you please clarify the following

  1 Is it a known limitation that after changing consent settings, tags may continue unless the page is reloaded

  2 Is there a recommended setting or workaround in BeTheme to ensure GA4 fully stops firing after consent is withdrawn

  3 What is your exact recommended implementation so that no collect requests are sent after opt out

  Best regards