FAQ
Why are Accept all, Reject all and Customize the same size and color?
Section titled “Why are Accept all, Reject all and Customize the same size and color?”European data protection authorities, coordinated by the EDPB cookie banner taskforce, treat a missing or less visible reject option on the first layer as invalid consent. Rejecting must be as easy as accepting. The add-on keeps the three buttons identical on purpose.
Basic or advanced Consent Mode?
Section titled “Basic or advanced Consent Mode?”Basic (default) blocks Google tags until the visitor agrees, so nothing is sent to Google before consent. Advanced loads Google tags with denied signals; Google then receives cookieless pings and can model conversions. Advanced gives more data in Google Ads and Analytics, but several authorities consider any request to a tracker before consent as access to the device under Article 5(3) of the ePrivacy Directive (see the EDPB Guidelines 2/2023 on the technical scope of Art. 5(3)). If you sell in the EU and are unsure, keep Basic.
Is this enough for Google Ads in the EEA?
Section titled “Is this enough for Google Ads in the EEA?”Google requires advertisers who use Google Ads or Analytics data for EEA users to collect consent and pass it with Consent Mode v2 (ad_user_data and ad_personalization). This add-on sends all required signals. Publishers who show Google ads (AdSense, Ad Manager, AdMob) to EEA and UK users must use a Google-certified CMP that supports the IAB TCF; this add-on is not a TCF CMP.
Does it work with Google Tag Manager?
Section titled “Does it work with Google Tag Manager?”Yes. The consent default is pushed to the dataLayer before the container loads. In basic mode the container is held back until analytics consent; in advanced mode it loads at once and your tags should use GTM’s built-in consent checks. The kv_consent_update event is available as a trigger.
A script is not blocked. What can I do?
Section titled “A script is not blocked. What can I do?”Add a custom rule (category|text) under Script blocking, using a unique part of the script URL or code. Or tag the script manually with type="text/plain" data-kv-consent="<category>". Scripts injected later by another script (not printed in the page HTML) cannot be rewritten: block the script that injects them.
A script should never be blocked.
Section titled “A script should never be blocked.”Add data-kv-consent-skip to its <script> tag, or uncheck the service in Script blocking → Services.
Will the shoppers see two banners?
Section titled “Will the shoppers see two banners?”Only if the core GDPR add-on’s cookie notice is also on. The Status block on the settings page detects it and turns it off in one click.
Do I need to change my theme?
Section titled “Do I need to change my theme?”No. The banner uses the theme’s colors and font and is added through a template hook. For the footer link, add the Cookie settings links block in the layout editor.
Where is the choice stored and for how long?
Section titled “Where is the choice stored and for how long?”In the first-party cookie kv_consent for the configured number of days (180 by default). Necessary cookies are not affected.
What personal data does the consent log contain?
Section titled “What personal data does the consent log contain?”A random consent ID, the time, the choices, the policy version, the language, the page path and the IP address with the last part removed (IPv4 /24, IPv6 /48). No name, e-mail, customer ID or user agent. Old rows are deleted after the retention period.
Does it slow the store down?
Section titled “Does it slow the store down?”The consent core is about 6 KB, inline, with no external request. The banner script is about 5 KB and loads at the end of the page. Blocking happens once per page on the server with simple string matching.
Does it work in Multi-Vendor?
Section titled “Does it work in Multi-Vendor?”Yes. The banner and settings are per storefront. Vendor panels are not affected, and vendors cannot see the consent log.
How does it compare to Cookiebot or CookieYes?
Section titled “How does it compare to Cookiebot or CookieYes?”Those are hosted services with monthly fees that load their script from their servers. This add-on is a one-time license, runs inside your store, sends no data to a third party and includes the consent log. It does not scan your site for cookies automatically: you choose the services and add rules for anything else.
The banner disappeared and the admin panel shows a “safe mode” notice.
Section titled “The banner disappeared and the admin panel shows a “safe mode” notice.”Open Add-ons → Manage add-ons → Cookie Consent Manager with Consent Mode v2 (GDPR, KVKK) → Settings → License. The status line says what is wrong: no key, a key for another add-on, a revoked license, or a domain that the license does not cover. Fix it and click Check now. See License. While the license is not valid, the add-on keeps every tracking script blocked and does not show the banner, so the store never tracks without consent (see Safe mode).
Does the add-on work on my staging copy?
Section titled “Does the add-on work on my staging copy?”Yes. Subdomains of your licensed domain (for example staging.example.com) and local development hosts (localhost, private IP addresses, *.local, *.test) are covered by the same license.
What happens if your license server is down?
Section titled “What happens if your license server is down?”Nothing visible: the add-on keeps the last verified result and keeps working for 14 days while it retries. The admin panel shows a notice from the first failed check.
Does the license check slow down my storefront?
Section titled “Does the license check slow down my storefront?”No. The check runs in the admin panel or from cron, once a day. The storefront only reads the stored result.
Legal note: not legal advice
Section titled “Legal note: not legal advice”This add-on and its documentation are technical tools and information, not legal advice. Kavio Labs does not guarantee that using it makes your store compliant with the GDPR, the ePrivacy Directive and national cookie laws, the UK GDPR and PECR, Turkey’s KVKK, or any other law. Compliance depends on your banner texts, your privacy and cookie policies, the services you use, how you configure the add-on and how you process data elsewhere. Requirements also change and differ between countries and regulators. Review your setup with a qualified lawyer or your data protection officer.
Still stuck?
Section titled “Still stuck?”Work through the troubleshooting guide, then contact support with your CS-Cart version, edition, PHP version and the add-on version (1.1.1).