Frequently Asked Questions



  • 1. What does this app do, and how does it work?

    Our app lets you easily take control of your privacy policy and consent effort. It will help you have a GDPR or CCPA compliant store with little to no hassle.


    IMPORTANT: Make sure that you do not have other similar app(s) or a cookie bar active at the same tim.

  • 2. What is GDPR? What is CCPA?

    GDPR (General Data Protection Regulation)

    The GDPR EU legal framework took full effect on May 25, 2018.

    Its purpose is to unify the current data protection laws throughout the countries in the European Union and give more power to EU/EEA citizens to protect their personal information. With the hefty penalties from the European Commission, our GDPR module is how you can stay compliant with the latest regulations. Variations of the law name across other countries & languages: GDPR, DSGVO, RGPD.

    CCPA (California Consumer Privacy Act)

    The CCPA law took full effect on January 1, 2020. Although it has many of the same characteristics as the GDPR law, CCPA is intended to enhance privacy rights and consumer protection for residents of California, United States. To learn more, check the questions "What are the similarities and the differences between GDPR and CCPA?" and "What are the transparency requirements for GDPR and CCPA?" in our help center.

    *** Keep in mind that our application does not provide full GDPR/CCPA compliance. You should also manually update your privacy policy and terms & conditions texts to be compliant with all requirements.

    Don't have a Privacy Policy/Terms & Conditions page? Follow these instructions to see how you can create your store policies.

  • 3. Are there any additional steps that I should do after I install the app?

    Yes, we have combined all of the setup information in this Guide If you have any questions on it you can contact us at: apps-support@isenselabs.com

  • 4. Why the Cookie Consent bar is not shown in my store?

    There are a few possible reasons why the Cookie Consent Bar is not shown on the front end:

    1) The app is not enabled.
    As a first step, please make sure that the app main setting in Global Settings > Show Cookie Consent Bar is set to Enabled.

    2) The location from where you are testing. 
    Note that the Free plan allows you to enable the app on the following locations: EU/EEA countries, Brazil, and the state of California. These are the countries where the GDPR/CCPA laws apply to.  If you are not located in any of the mentioned countries, then the bar will not be visible to you. However, note that it will be shown to your visitors from EU/EEA countries, Brazil, and California state (based on the configuration of the setting Enable For Specific Regions). In this case, in order to test how the bar looks like you can do one of the following:

    1. Test with a VPN service with an EU, Brazil, or California IP.
    2. Enable the app admin mode from General Settings > Show Cookie Consent Bar > Admin Mode. This setting will disregard the enable for specific regions selection and will show the cookie consent bar for you as a Shopify store admin. Note that you need to test it on the same browser where you are connected as an admin in your Shopify store. 
    Note: If you would like to display the app on all of the countries you can do so by enabling the setting Enable for All Countries (available only for the Premium plans). 

    3) You have exceeded the quota limit for your plan.
    GDPR/CCPA app plans are working based on the number of page visits per store. If you exceed the limit of the page visits for your plan, the app will stop working, therefore the Cookie Consent Bar will not be visible. Once this happens, you will get a notification in the app settings with an upgrade option. At the same time, you will receive multiple email notifications in regard to this.  If you decide to upgrade, the issue will be solved.

    4) You have already opted-in/opted-out on the Cookie Consent Bar.
    The cookie consent bar is shown once per browser session. If you have seen the cookie consent bar once and clicked any of the buttons (Accept/Close) then the cookie consent bar will not show again on the same browser session for you. If you would like to test, you can simply clear your browser cookies or open a new incognito/private window on your browser, and access your store from there.

    If none of the above is your case, please contact our support, by opening a live chat message or send an email at apps-support@isenselabs.com

  • 5. What is the difference between the Free and the Premium plans (Standard, Pro, and Enterprise)?

    The Free plan will give you all the required tools to have your store GDPR Compliant. All the tools are free to use and they will be forever free. You do not need to be on a Premium plan to achieve full GDPR/CCPA compliance. However, the Premium plans will allow your visitors to have a more personalized experience in your store + they are suitable for stores with more than 10k page visits a month. In order to check the perks of the paid plan, please go to the Upgrade Plan tab in the admin side of the app.

  • 6. I noticed that the cookie bar appeared at the bottom of the store. Can I change that?

    By default, the cookie bar is displayed at the bottom part of the screen. If you wish to change that, you have to navigate to Design Settings -> Position.


    Help Center question


    NOTE: We have also recorded a video on how you can change the Design and Position of the Cookie bar. You can do this by following our steps. You can find it below:


    Help Center question
  • 7. The bar is overlapping with other widgets on my store. How to fix that?

    To fix that, you can change the position of the cookie bar from Design Settings -> Position. If this does not work for you, please contact us about the matter. We will find a solution for you.


    Help Center question


    NOTE: We have also recorded a video on how you can change the Design and Position of the Cookie bar. You can do this by following our steps. You can find it below:


    Help Center question
  • 8. Can I make additional changes to the cookie bar?

    The colors can be changed from Design Settings. There is a live preview so that you can see the changes instantly. As for the texts, they can be modified from the Cookie Consent Bar tab. You can modify every aspect of the cookie bar.


    Help Center question
    Help Center question
  • 9. Can I change which cookies should be blocked from the cookie bar?

    We have added the most used cookies in the app. However, if you want to change them, you can do that from Cookie Consent Bar -> Cookie Management. Modify these cookies only if you are an advanced technical user.


    Help Center question
  • 10. The GDPR law is only for the EU/EEA customers, can I activate the cookie bar only for EU/EEA visitors?

    Yes, you can do that from Global Settings -> Enable For Specific Regions. Once you do that, the cookie bar will be visible only for the countries below.


    The EU countries are: Austria, Belgium, Bulgaria, Croatia, Republic of Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, and the UK.

    The EEA countries are all EU countries plus: Iceland, Norway, and Liechtenstein.

    Switzerland is neither an EU nor EEA member but is part of the single market - this means Swiss nationals have the same rights to live and work as other EEA nationals.

    Help Center question
  • 11. Is there a way to show the preferences popup after a visitor has already accepted the cookies?

    You can easily do that by a button or a link on a page of your preference. You just have to choose one of the examples below:

    Button:

    <a class="btn btn--secondary" onclick="jQuery('.cc-settings-view').fadeIn('300');">Cookie Preferences</a>
    Link:
    <a onclick="jQuery('.cc-settings-view').fadeIn('300');">Cookie Preferences</a>

    Note: The code will not work if you try to add it to a Legal page ( Settings > Legal ), due to limitations from Shopify, which are not allowing the Javascript code to run properly.

    IMPORTANT: This is a generic HTML code that will display a button, which you can use to provide your customers to change their cookie preferences at any time. You can also change the text in the button/link. If you have any request about the styles or the design, feel free to contact our team, we will happy to help you!

    Help Center question
  • 12. Where is my GDPR page, and how can I access it?

    We have automatically created a GDPR page for you. You can access it from Global Settings -> View Your GDPR Page. It includes the necessary GDPR tools for your store to be compliant with the EU/CCPA laws.

    NOTE: This page is also important for CCPA compliance.


    Help Center question
  • 13. How can I add the GDPR page to my store front?

    You can add it on the navigation menu, in the footer or on any page that you want. You can see the link of the page from the question "Where is my GDPR page, and how can I access it?" in this help center.

    If you want to add the page in one of your navigation menus, you have to go to "Online Store" and then "Navigation". Check the video below for more details.

    Adding a link to a specific page depends on the theme that you are using. If you need help with any of this, do not hesitate to contact us - our team will be more than happy to help you.


    Help Center question
  • 14. How can I track the policy acceptances and the GDPR requests?

    You can track them directly in the app. There are three tabs - Policy Acceptances, GDPR/CCPA requests and Deletion requests.


    Help Center question
    Help Center question
  • 15. A customer changed his/her personal data via a GDPR request. Can I see the changes?

    Yes, you will be notified by email about each change.

  • 16. A customer requested his/her personal data to be removed. How should I handle that?

    When a customer requests this, you can erase the personal data from the Customers page. You have to locate the customer and then navigate to Customer privacy -> Erase Personal Data.


    Help Center question

  • 17. How to enable better Google Tag Manager blocking?

    The blocking will be done with an additional script. The script below will block Google Tag Manager based on a Container ID.

    Here is how the script works: Google Tag Manager will be set based on a condition, which is checking one of the cookies, that are set by our app. This cookie is storing information on which exact cookie group is blocked currently, either based on the initial state, or the preferences of each customer. When the initial state is set to block the Analytics cookie group or the customer opts out, the script which is setting the Tag Manager will not be executed.

    Here are instructions on how to implement the script:

    1. Open Shopify Admin.
    2. Click on Online Store link in the left menubar.
    3. Click on the "Actions" dropdown button and select "Edit Code" from there.
    4. A new page will open with a list of files on the left side of the screen. Open the "theme.liquid" file.
    5. Find where you have set the script for GTM in the "<head>". It should look similar to this:
    Help Center question
    6. After you have located the script, copy its contents between "<script>" and "</script>" and paste them here:

    <script>
    function checkGDPRGTM() {
          	if (window.isenseGDPR !== undefined && window.isenseGDPR.Cookies.get('cookieconsent_preferences_disabled') !== undefined) {
              let cookie = window.isenseGDPR.Cookies.get('cookieconsent_preferences_disabled');
              if (cookie.indexOf('analytics') == -1) {
                <!-- YOUR COPIED CODE HERE -->
              }
            } else {
              setTimeout(function() {
                  checkGDPRGTM();
              }, 500);
            }
        }
        
        checkGDPRGTM();
    
        window.addEventListener('click', function (e) {
          if(e.target && (e.target.className == 'cc-btn cc-btn-accept-all' || e.target.className == 'cc-btn cc-allow' || e.target.className == 'cc-btn cc-btn-accept-selected')){
            checkGDPRGTM();
          }
        });
    </script>
    
    7. The final result should look like this:
    Help Center question
    8. That's it!

    NOTE: We have also recorded a video on how you can do this by following our steps. You can find it below:


    Help Center question
  • 18. How to enable better Google Analytics blocking?

    Here is how it works by default: Our app deletes the Google Analytics cookies on page load. However, those cookies are then created by Google again on the next page load. Because of that, we are removing the GA cookies on every refresh. With that said, when a customer visits a page, a small bit of information is sent to Google. Since we are constantly deleting the cookies, each page load is considered as a new visitor session. That way, Google cannot fully track what the customer is doing in your web store. We are using this method due to Shopify's limitations preventing us from getting the tracking codes for each store.


    However, if you want to add additional protection for the visitors that do not want to be tracked, there is one more thing you can do. Here are the steps that you should follow:


    1. Open Shopify Admin.
    2. Click on Online Store link in the left menubar.
    3. Click on the "Actions" dropdown button and select "Edit Code" from there.
    4. A new page will open with a list of files on the left side of the screen. Open the "theme.liquid" file.
    5. Find the string "</head>" in there.
    6. When you do, add the following snippet before "</head>":

    <script>
    var gaProp='UA-XXXXXX-X';
    var iac=(document.cookie.match(/^(?:.*;)?\s*cookieconsent_preferences_disabled\s*=\s*([^;]+)(?:.*)?$/)||[,null])[1];
    if(iac!=null&&iac.indexOf('analytics')>= 0){window['ga-disable-'+gaProp]=true;}
    </script>
    
    7. IMPORTANT! Make sure to replace the "UA-XXXXXX-X" string with your Google Analytics tracking ID.
    NOTE: If you are using Google Analytics 4, make sure to replace the "UA-XXXXXX-X" string with your Measurement ID, which should be in format "G-XXXXXXX".
    8. Click on the "Save" button.
    9. That's it!

    NOTE: We have also recorded a video on how you can do this by following our steps. You can find it below:


    Help Center question
  • 19. How to enable better Google Analytics 4 (GA4) blocking?

    The blocking will be done with an additional script. The script below will block Google Analytics 4 based on a Global Tag.

    Here is how the script works: Google Analytics 4 will be set based on a condition, which is checking one of the cookies, that are set by our app. This cookie is storing information on which exact cookie group is blocked currently, either based on the initial state, or the preferences of each customer. When the initial state is set to block the Analytics cookie group or the customer opts out, the script which is setting the Tag Manager will not be executed.

    Here are instructions on how to implement the script:

    1. Open Shopify Admin.
    2. Click on Online Store link in the left menubar.
    3. Click on the "Actions" dropdown button and select "Edit Code" from there.
    4. A new page will open with a list of files on the left side of the screen. Open the "theme.liquid" file.
    5. Find where you have set the script for Global Site Tag in the "<head>". It should look similar to this:
    Help Center question
    6. Paste the script below between the two script tags from step 5. Afterwards follow the next three steps:
    Help Center question

    <script>
         
         let gaScript = document.getElementById('ga4');
         let gtmLink = '{{ Your src link }}';
         
         
         function checkGDPRGAF() {
          if (window.isenseGDPR !== undefined && window.isenseGDPR.Cookies.get('cookieconsent_preferences_disabled') !== undefined) {
          	let cookie = window.isenseGDPR.Cookies.get('cookieconsent_preferences_disabled');
            
            if (cookie.indexOf('analytics') == -1) {
              gaScript.setAttribute('src', gtmLink);
            }
          } else {
            setTimeout(function() {
              checkGDPRGAF();
            }, 500);
          }
         }
         
        checkGDPRGAF();
    
       window.addEventListener('click', function (e) {
           if(e.target && (e.target.className == 'cc-btn cc-btn-accept-all' || e.target.className == 'cc-btn cc-allow' || e.target.className == 'cc-btn cc-btn-accept-selected')){
             checkGDPRGAF();
           }
       });
      </script>
    
    • Step 1. Comment out or delete the original script tag. Make sure to copy the link which is inside the src attribute. Help Center question
    • Step 2. Add a new script tag above the newly added script, as shown in the screenshot below. You can copy the script tag from here:
      <script async id="ga4"></script>
      
      Help Center question
    • Step 3. Replace 'Your src link' with the link that you have copied earlier from step 1.(check section 3 in the screenshot below)
    Help Center question
    7. The final result should look like this:
    Help Center question
    8. That's it!

    NOTE: We have also recorded a video on how you can do this by following our steps. You can find it below:


    Help Center question
  • 20. How to enable better Google Ads blocking?

    The blocking will be done with an additional script. The script below will block Google Ads based on a Global Tag.

    Here is how the script works: Google Ads will be set based on a condition, which is checking one of the cookies, that are set by our app. This cookie is storing information on which exact cookie group is blocked currently, either based on the initial state, or the preferences of each customer. When the initial state is set to block the Marketing cookie group or the customer opts out, the script which is setting the Tag Manager will not be executed.

    Here are instructions on how to implement the script:

    1. Open Shopify Admin.
    2. Click on Online Store link in the left menubar.
    3. Click on the "Actions" dropdown button and select "Edit Code" from there.
    4. A new page will open with a list of files on the left side of the screen. Open the "theme.liquid" file.
    5. Find where you have set the script for Global Site Tag in the "<head>". It should look similar to this:
    Help Center question
    6. Paste the script below between the two script tags from step 5. Afterwards follow the next three steps:
    Help Center question

    <script>
        let gadsScript = document.getElementById('google-ads-script');
        let gadsLink = 'https://www.googletagmanager.com/gtag/js?id=AW-AABBBCCC';
    
        function checkGDPRGADS() {
          if (window.isenseGDPR !== undefined && window.isenseGDPR.Cookies.get('cookieconsent_preferences_disabled') !== undefined) {
            let cookie = window.isenseGDPR.Cookies.get('cookieconsent_preferences_disabled');
            if (cookie.indexOf('marketing') == -1) {
              gadsScript.setAttribute('src', gadsLink);
              
              window.dataLayer = window.dataLayer || [];
              function gtag(){dataLayer.push(arguments);}
              gtag('js', new Date());
    
              gtag('config', 'AW-AAABBBCCC');
            }
          } else {
            setTimeout(function() {
              checkGDPRGADS();
            }, 500);
          }
        }
    
        checkGDPRGADS();
        
        window.addEventListener('click', function (e) {
          if(e.target && (e.target.className == 'cc-btn cc-btn-accept-all' || e.target.className == 'cc-btn cc-allow' || e.target.className == 'cc-btn cc-btn-accept-selected')){
            checkGDPRGADS();
          }
        });
      </script>
    
    • Step 1. Comment out or delete the original script tag. Make sure to copy the link which is inside the src attribute. Help Center question
    • Step 2. Add a new script tag above the newly added script, as shown in the screenshot below. You can copy the script tag from here:
      <script async id="google-ads-script"> </script>
      
      Help Center question
    • Step 3. Replace 'Your src link' with the link that you have copied earlier from step 1.(check section 3 in the screenshot below)
    Help Center question
    7. The final result should look like this:
    Help Center question
    8. That's it!

    NOTE: We have also recorded a video on how you can do this by following our steps. You can find it below:

  • 21. How to enable better Facebook Pixel blocking?

    In the moment, the pixel blocking works the same way as the default Google Analytics blocking works. You can read this from the "Here is how it works by default" section in the question 18. How to enable better Google Analytics blocking?.

    However, if you want to add additional protection for the visitors that do not want to be tracked, there is one more thing you can do. Here are the steps that you should follow:

    1. Open Shopify Admin.
    2. Click on Online Store link in the left menubar.
    3. Click on the "Actions" dropdown button and select "Edit Code" from there.
    4. A new page will open with a list of files on the left side of the screen. Open the "theme.liquid" file.
    5. Find the string "</head>" in there.
    6. When you do, add the following snippet before "</head>":

    <script>
    !function(){var e=null,n=[],t=(document.cookie.match(/^(?:.*;)?\s*cookieconsent_preferences_disabled\s*=\s*([^;]+)(?:.*)?$/)||[,null])[1];
    Object.defineProperty(window,"fbq",{get:function(){return e},set:function(o){Object.defineProperty(o,"queue",{get:function(){return null!=t&&t.indexOf("marketing")>=0?[]:n},set:function(){}}),e=o}})}(); 
    </script>
    
    7. Click on the "Save" button.
    9. That's it!

    Warning: If you have the option Limit tracking for customers in Europe turned off, the Facebook Pixel might still fire initially on the first load, after the above script is applied. The reason for this is because the cookie from our app has to be set, in order for the script to work, and initially, Shopify is firing the Pixel before our app has loaded. This is occurring only on the first initial load. Aftewards the Pixel is blocked correctly if the customer has opted-out. Feel free to check section 70. How do the options for Customer Privacy work with our app? (Cookie Consent API) for more information on how this opition works with our app.

    Note: We have also recorded a video on how you can do this by following our steps. You can find it below:


    Help Center question
  • 22. How to implement the Facebook Flag for Limited Data Use (LDU)?

    Facebook has recently released a Limited Data Use feature, which will give businesses more control over how their data is used in Facebook's systems. In order for the feature to function, a LDU flag has to be set once a customer opts-out of the Marketing cookie group. The flag indicates that Facebook should limit the use of the customer's personal data. The signal is sent through an array called Data Processing Options. This rule should apply for customers from California only.

    The implementation of the flag in our app will happen in the following way: We have created a script which will be triggered once the visitor opts-out from the marketing cookies. The script will set the flag in regard to the LDU.

    NOTE: Check question number 21 if you would like to fully disable the Facebook Pixel for all the visitors who opt out from the marketing cookies.

    Here are instructions on how to implement the script:

    1. Open Shopify Admin.
    2. Click on Online Store link in the left menubar.
    3. Click on the "Action" dropdown button and select "Edit Code" from there.
    4. A new page will open with a list of files on the left side of the screen. Open the "theme.liquid" file.
    5. Find the string "</head>" in there.
    6. When you do, add the following snippet before "</head>":

    <script>
    var iac=(document.cookie.match(/^(?:.*;)?\s*cookieconsent_preferences_disabled\s*=\s*([^;]+)(?:.*)?$/)||[,null])[1];null!=iac&&iac.indexOf("marketing")>=0&&"function"==typeof fbq&&fbq("dataProcessingOptions",["LDU"],0,0);
    </script>
    
    7. Click on the "Save" button.
    8. That's it!

    NOTE: We have also recorded a video on how you can do this by following our steps. You can find it below:


    Help Center question
  • 23. Can I translate the app?

    Yes, you can translate almost everything in the app. It consists of five elements:

    1) Cookie consent bar
    2) GDPR/CCPA compliance page
    3) GDPR/CCPA notification/confirmation emails
    4) GDPR/CCPA request pages
    5) Data Collection Text - By clicking on the above buttons, I give my consent on collecting my IP and email (if registered). For more check Privacy Policy?

    You can translate 1) and 2) from the Shopify admin panel. The cookie bar can be translated from the app itself by editing the text fields in the Cookie Consent Bar tab. The compliance page can be edited from Online Store -> Pages -> page GDPR Compliance. The steps are similar for the CCPA Compliance page.

    The GDPR request pages (4) and the emails (3) are already translated into English, German, French, Italian, Portuguese, Finnish, Bulgarian, Romanian, Slovenian, Spanish, and Hungarian. If you want them translated in a different language, contact us so we can work together and add your translation.

    For (3) and (4), you can change the language from Translation -> Set Language For The GDPR/CCPA Requests Emails And Pages.

    Help Center question

    Note: For the Standard, Pro, and Enterprise plan customers, the Language Detection feature is automatically enabled. For more information on how this works, please check section 49. What is the Language Detection feature and how exactly does it work?

    Point (5) can be translated from Translation -> Language for the Data Collection Text ( *By clicking on the above buttons, I give my consent on collecting my IP and email (if registered). For more check Privacy Policy ) for more information on this text please check section 59. What is the meaning behind the text located under the Accept Selected and Accept All buttons: By clicking on the above buttons, I give my consent on collecting my IP and email (if registered). For more check Privacy Policy?

    Help Center question

    The only thing that cannot be translated at the moment is the admin panel of the app, however, we are working towards this.

    Help Center question
    Help Center question
    Help Center question
  • 24. I am using the Langify app and I cannot translate the GDPR Compliance page?

    Since the GDPR Compliance page is not a regular page and has some actions in it, the translation should be done in a different manner. You have to open the Langify app and start translating it from the "Custom Content" section. Once you do that, the page will work with no issues on your other language(s).

    Note: This is only if you are using the Langify app. If not, then you should simply change the texts from the Pages section in Shopify Admin.

  • 25. I accidentally deleted my GDPR Compliance page. How can I get it back?

    For your convenience, the GDPR compliance page is automatically created once you install the app.

    If you happen to delete it and want to get it back, you can do so by downloading the archive below. In it, you will find an HTML page with the contents of the GDPR compliance page. In order to place it in your store, you have to go to Online Store -> Pages -> Add page. Then you have to click on the Show HTML button, which will switch the editor to use HTML code. Then you can simply copy the code from the HTML file and paste it Content section of your new page. You can click on the Show HTML button to revert the editor to its original state, and you should be seeing the page now. Also, don't forget to set a Title and save the page. That's it!

    Also, if you are on a Premium plan, you can generate the GDPR or CCPA pages automatically, by navigating to Global Settings -> Generate new GDPR/CCPA pages section.

  • 26. How can I set the cookie bar to block marketing, analytics or functionality cookies by default?

    If you want to set the cookie bar to block marketing cookies, analytics cookies or functionality cookies, you will need to navigate to the Cookie Consent Bar tab and scroll down to the Initial State Of The Cookie Consent Bar filed. From there you will be able to select the following options: 

    • Keep all store cookies until visitor opts-out
    • Block marketing cookies until visitor opts-in
    • Block analytics cookies until visitor opts-in
    • Block functionality cookies until visitor opts-in

    What is the benefit of this? For some European countries (i.e. Germany) the law states that the marketing and analytics cookies should be blocked until there is consent by the visitor. In these specific cases, you will have the ability to choose from the above-listed options.

     
    Help Center question
  • 27. I want to add custom JavaScript code to be triggered once a visitor accepts the terms in the cookie bar. Can I?

    This might be useful if you are adding third-party tracking codes manually or if you want to trigger something only if the customer has accepted the terms in the cookie bar. You can do this with the following snippet of code:

    <script type="text/javascript">
    function isl_rc(n){for(var r=n+"=",t=document.cookie.split(";"),e=0;e<t.length;e++){for(var i=t[e];" "==i.charAt(0);)i=i.substring(1,i.length);if(0==i.indexOf(r))return i.substring(r.length,i.length)}return null}
    if (isl_rc('cookieconsent_status')=='allow') {
        // Add your code HERE
    }
    </script>
    

    You can now proceed to add your code by replacing the line "// Add your code HERE". Depending on what you are trying to achieve, you probably have to add the entire snippet in your header.liquid, footer.liquid or other file in your template.

    Note: If you have reset the preferences of your customers by pressing the button Reset Customer Consent, located in the Global Settings, you would need to double-check what is the exact name of the cookieconsent_status, because the cookie name will be changed each time you reset the consent of the customers.

  • 28. What are the similarities and the differences between GDPR and CCPA?

    The main rights of the CCPA and GDPR include the right to be informed, the right of access, and the right to portability. They also include the right to deletion (CCPA) and the right to erasure (GDPR), with very minor differences between the two, also the right to opt-out (CCPA) and the right of prior consent (GDPR).


    The latter two are in a sense incomparable, since the right to opt-out (CCPA) is best likened to the right to withdraw consent (GDPR), whereas the fundamental right of prior consent (GDPR) has no equivalent in the CCPA. Fortunately, you can use the option Initial State Of The Cookie Consent Bar in the Cookie Consent Bar tab to set the app to be GDPR or CCPA compliant.

  • 29. What are the transparency requirements for GDPR and CCPA?

    The GDPR requires that you tell customers:

    • What your business does
    • How they can contact you
    • Why you are processing personal data
    • What types of data you collect and how long you will store it
    • Disclosure of where data is being shared


    The CCPA requires that you tell customers:

    • What types of information you are collecting
    • For what purpose you are collecting data
    • Specifics of what is being collected
    • Disclosure of where data is being shared

  • 30. I changed my theme. Should I make some adjustments to the app as well?

    The app has no relation to the theme that you use, so you can switch to as many themes as you want. In addition to that, our product does not make any changes to your themes, so there will be no need for you transfer any codes or data from your old theme to your new theme.

    The only thing that you would probably like to change in the app would be the color settings for the cookie bar so they can match your new theme. If you have any questions in regards to that, feel free to contact our support team.

  • 31. I clicked on the "Accept" button but I still see the cookie bar. Why?

    This can only happen if you have more than one cookie bar active on your store. Make sure that you disable/uninstall all other cookie apps that you currently have on your store.

    IMPORTANT: Sometimes you may keep seeing two cookie bars even when you uninstall one of them. This can happen if said app made changes to your theme files. This means that you have to locate the leftover codes and remove it. If you have trouble doing this, feel free to contact our support team.

  • 32. The CCPA law is only for the customers in California, can I activate the cookie bar only for them?

    Yes, you can do that from Global Settings -> Enable For Specific Regions. Once you do that, the cookie bar will be visible only for the residents for which CCPA applies to.


    The CCPA regions are: California (USA)


    Help Center question

  • 33. I upgraded to a Premium plan. How can I reach the new settings?

    Congrats on upgrading! In order to reach the new settings, you simply have to navigate to the Design Settings tab. Once you do that, keep scrolling until you reach the Premium Settings section. From there, you will be able to do the following things:

    • Modify the background color and the text color of the GDPR request pages
    • Show your store logo in the GDPR request pages
    • Add custom CSS to the pages
    • Add custom JavaScript to the pages
    • Add custom email sender for the GDPR emails
    • Change the background color of the main button in the emails
    • Add custom HTML content in the beginning of the email
    • Add custom HTML content in the end of the email
    • Reset all of your customer consent preferences
    • Cookie Scanner


    Help Center question
  • 34. I am on one of the Premium plans. How can I cancel it and go back to the Free plan?

    You can simply go to the Upgrade Plan tab, and then click on the button Switch Plan in the Free column.

  • 35. When will a charge occur after the Free Trial ends?

    Once the trial is over, the app charge is issued, then invoiced monthly with all the other app and subscription charges. Merchants can see the breakdown of app charges all under one bill - the Shopify invoice. More information about this you will be able to find here: https://help.shopify.com/en/manual/your-account/manage-billing/your-invoice/apps

  • 36. How to remove the "Preferences" button from the cookie consent bar?

    This can be done easily with a small stylesheet tweak. Open the Design Settings tab and navigate to the Custom CSS setting. Add the following code in the field:

    .cc-settings{display:none !important;}
    That's all!

  • 37. How to remove the "Close" button from the cookie consent bar?

    This can be done easily with a small stylesheet tweak. Open the Design Settings tab and navigate to the Custom CSS setting. Add the following code in the field:

     .cc-dismiss{display:none !important;}
    That's all!

  • 38. Which are the CSS selectors for the Consent Bar and the Preferences popup?

    As you already may or may not know, you can apply CSS to different elements of the Consent Bar and the Preferences popup. Here is a list of the CSS selectors:

    Note: Keep in mind that applying Custom CSS may override your current settings which you have applied for the colors and the styling of the bar.
    Consent Bar


    Help Center question

    1. .cc-message
    2. .cc-dismiss
    3. .cc-settings
    4. .cc-allow
    Preferences Panel


    Help Center question

    1. .cc-settings-dialog > .main_information > .cookie_settings_header
    2. #cookieconsent\:settings > div > div.main_information > label:nth-child(4)
    3. #cookieconsent\:settings > div > div.main_information > #strict-cookie-category-text
    4. #cookieconsent\:settings > div > div.main_information > label:nth-child(9)
    5. #cookieconsent\:settings > div > div.main_information > #analytics-cookie-category-text
    6. #cookieconsent\:settings > div > div.main_information > label:nth-child(14)
    7. #cookieconsent\:settings > div > div.main_information > #marketing-cookie-category-text
    8. #cookieconsent\:settings > div > div.main_information > label:nth-child(19)
    9. #cookieconsent\:settings > div > div.main_information > #functionality-cookie-category-text
    10. .cc-btn-accept-selected
    11. .cc-btn-accept-all

    The colors of the checkboxes and the ticks can be configured from Design Settings > Checkbox Color & Checkbox Tick Color


    If you would like to apply a global setting for all of the text in the Consent Bar or Preferences Popup, for example change the font-size or the font, you can apply it with the following selectors:

    Consent Bar:

    .cc-window

    Preferences Popup:
    .cc-settings-dialog

    Example:

    .cc-window { font-family: "Times New Roman", Times, serif; }

  • 39. What does the Cookie Scanner do?

    It will show you all the cookies present on your store when a customer visits for the first time. It also shows a Last scan date underneath the field.

  • 40. How can I add custom email sender for my GDPR/CCPA emails?

    This feature is currently available only for the merchants that have upgraded to a Premium plan.

    If you want to upgrade to a Premium plan, click on the Upgrade Plan tab and follow the steps there. You will also get access to other premium features!

  • 41. Can I customise my GDPR/CCPA email messages?

    In the Free plan, the emails are with white background and blue buttons. This is the default color scheme for all Shopify emails. However, if you switch to a Premium plan, you will be able to add custom header, footer and change the button color.

    If you want to upgrade to a Premium plan, click on the Upgrade Plan tab and follow the steps there. You will also get access to other premium features!

  • 42. Can I customise my GDPR/CCPA request pages?

    The pages are fully functional, however, if you are on the Free plan, you cannot change the design of the pages. The customisation options for the GDPR/CCPA request pages are available only in the Premium plans. If you switch to them, you will be able to change the background color, the text color, add custom CSS, and also to add your store logo. In addition, you will also be able to add snippets of JavaScript codes (i.e. for analytics or something similar).

    If you want to upgrade to a Premium plan, click on the Upgrade Plan tab and follow the steps there. You will also get access to other premium features!

  • 43. How the GDPR Compliance page works?

    If a customer wants to edit his data or send a deletion request, he should send a request with his account email. Our app is using the customer data from your Shopify store, and searches through all emails of the customers. After the customer submits the request, an email with a link will be sent to the customer email, from where he can edit his personal data, or approve the deletion request.

    Note: All of the information is taken directly from Shopify. We do not store any personal data, except the email of the customer, only if he/she makes a GDPR request, otherwise, we are not storing it.

  • 44. Can I export the data in the app?

    You can export the data from the tabs Policy Acceptance, GDPR Requests, and Deletion Requests. You will find the button Export under the results of each tab.

    The available formats as of now are CSV, XLSX, and ODS.

  • 45. I want to uninstall your app. What are the steps that I have to go through?

    We are sorry to hear that you want to uninstall our app. We would appreciate it if you contact us in regards to what you are missing or if you have any suggestions/complaints.

    Still, if you are confident about your decision and there is nothing we can do to change your mind, you can simply go to Shopify Admin -> Apps and then uninstall our app. This is all that is needed, and there is nothing else that is required from your side. If you are on a paid plan, it will be canceled automatically.

  • 46. Why am I seeing a message for reaching a quota limit? 

    If you are seeing this popup message below, it means that you have reached the Quota Limit of the plan that you are currently using. If you want to understand more about the new plan structure, please check the question: What is the meaning behind the new plan structure? Now that you are familiar with the plan structure, you should know that the reason for seeing the quota limit popup is that you have reached its maximum page visits per month. I.e. If you are on a Free plan and you see the quota limit popup, this means that you have reached the 10k page visits maximum for this plan. If you still want to show the Cookie Consent Banner on your storefront, you should upgrade your current plan to the next available one. More on this you will be able to see on the: How can I upgrade my plan? question.

    Help Center question

  • 47. What is the meaning behind the new plan structure? 

    In the past few months, we were mainly focusing on improving the performance of the app, and here is where the new plans' structure came along. We made several tests in order to inspect the different Shopify Store plans and the amount of usage each plan can have on a daily, weekly, and monthly basis. From here, we decided that the best way to deliver the app performance that we want is to implement this new plan structure. It consists of 3 plans with as follows: 

    • Free Plan - up to 10k page visits a month
    • Standard Plan - from 10k - 30k page visits a month
    • Pro Plan (Most Popular) - from 30k - 100k page visits a month
    • Enterprise Plan - more than 100k page visits a month
    A page visit is considered each time that the Cookie Consent Bar is loaded on your website for your customers while browsing the store. I.e. If I land on your home page and then I go to a product page - the Cookie Consent Bar will be loaded twice - once on your home page and once on your product page. This is considering that the customer has not interacted with the Cookie Consent Bar on the Home Page and that is why it will load each time they load a new page on your website.

  • 48. How can I upgrade my plan?

    Navigate to the Upgrade Plan tab in your admin and you will see the plan that you are currently using + the plans that you are able to upgrade to.

    Help Center question

    In this page you can see all different features included in each plan + tooltips that provide further explanations. 

     
    Help Center question
  • 49. What is the Language Detection feature and how exactly does it work?

    Our app currently has the request pages and email for the GDPR and CCPA translated in the following languages: EN, FR, DE, IT, PT, FI, RO, BG, SL, ES, HU, NL, CZ, HR, SV, LV and NO. If your store is multi-lingual, our app will automatically detect the language that the customer is currently viewing the store, and it will translate the requests and the emails in the corresponding language, which we have already translated. If a customer is viewing the store in a language that is not present, the app will use the language that is set from the settings from the app, which is located in the Translation > Set Language For The GDPR/CCPA Requests Emails And Pages.

    Note that the language detection will be turned on and will work only on the Premium plans (Standard, Pro and Enterprise)

    Currently, the Consent Bar and the Preferences popup can be translated with the following translation apps: Langify, GTranslate, Weglot, Translate my store and Translation Lab.

  • 50. How does the Cookie Information Panel work and what does each field do? 

    This new feature is located in the Cookie Consent Bar tab right under the Cookie Management section and it is only available to the Premium Plans (Standard, Pro and Enterprise) Here is how it looks like: 
    Help Center question
    As you can see you have 3 options:

    Display Cookie information

    - If enabled, this option will allow your visitors to see the detailed cookie information for each cookie on the preferences popup. Here is how it will look like:
    Help Center question

    - Upon clicking on the arrows your visitors will be able to see each cookie associated with the respective category and also check the additional information listed under them as part of their description:
    Help Center question

    Alternatively, if you select to disable this option and set it to No, this information won't show to your website visitors.

    - Next, you have the Add cookie option. Here you will be able to add custom cookies, add the respective description for them, and assign them to one of the listed categories. Once added here you will be able to see them in the above lists. Here is an example of adding a test_cookie and how it shows in the Marketing and Retargeting list of cookies:

    Help Center question

    And last but not least we have the Select a cookie to modify field. From here you can select an existing cookie and edit its description and/or category. if you want to modify the cookie itself like it's name, we would advise you to select the respective cookie, delete it and then try adding it again by following the example from the previous point. Here is how it would work if we wanted to edit the cookie from the previous example, let's say move it to a different category:
    Help Center question

  • 51. How can I Hide/Show the Close button?

    The option to Hide the Close button in the Cookie Consent Bar can now be found under the Cookie Consent Bar tab as well right next to the Action When the "Close" Button is Clicked field:
    Help Center question

    By selecting Hide or Show you can either have the Cookie Bar looking like this

    - Without a Close button: Help Center question

    or like this

    - With a Close button: Help Center question

  • 52. How does the Accept All and Accept Selected buttons work in the preferences popup?

    Upon clicking the Accept ALL button your visitors will accept all cookies no matter what the Initial State Of The Cookie Consent Bar option is set to. Similarly, if you decide to select specific cookies that you would like to accept you can do so by checking the respective checkboxes and then clicking on the Accept Selected button. No matter which of the two buttons you click, after this action is done both the Popup and the Cookie Consent Bar will be closed.
    Help Center question

  • 53. How can I have an Accept All button added to the Cookie Consent Bar?

    If you want the Accept button in the Cookie Consent Bar to act like an Accept ALL button, you will have the option to do that as well. You will simply need to rename the button from Accept > Accept ALL and then in the additional settings section select the option for the Accept button to disregard (choose 'No') the Regard the Initial State Of The Cookie Consent Bar for the 'Accept' button, so it could work as the one in the Preferences popup.
    Help Center question

    If you want the Accept button to work as it is, you simply need to make sure that this setting is set to Yes.

  • 54. How do the statistics in the General Settings work?

    Help Center question

    The graphs under the Daily Accepted Policy and Daily Deletion Requests fields will show the respective requests you have received for the past 7 days. The bar marked in green will always show the current day and then you will see the data for the past 6 days in the blue bars listed before.


    The Quota Limit section shows the page views you have received so far based on the total amount of views your monthly plan is supporting. This information will update every 6 hours and it will reset each month based on the date that you have installed the app on. I.e. if you have installed the app on the 25th of July, the quota will reset for you on the 25th of August. You will also be able to see how many days are left until the next quota reset.

  • 55. How to test/adjust the design settings for the Cookie Consent Bar if you are not from a GDPR/CCPA region?

    In order to see the Cookie Consent Bar on the storefront for testing and design changing purposes, you can use the Admin Mode located in the Global Settings tab under the Show Cookie Consent Bar field.

    Help Center question
  • 56. How to change the color of the checkboxes and ticks in the Preferences Popup?

    You will need to navigate to the Design Settings tab in the admin of the app and locate the color-changing buttons for the Checkbox Color and the Checkbox Tick Color.

    Help Center question

    Once you save the settings here, you can go on the storefront and check the Preferences popup in order to see the changes.

    Help Center question

    If you don't see the changes right away, clear your browser cache and refresh the page, so you could trigger the Cookie Consent Bar and click on the Preferences button.

  • 57. How to blur out the store's pages until the customer gives his consent?

    In order to blur out the page until the customer gives his consent, and also position the Consent Bar in the middle of the screen, please paste the following CSS code in Design Settings > Custom CSS:

    .cc-window {
    	position: fixed;
    	height: 100%;
    	width: 100% !important;
    	padding: 0px 25% !important;
    	background-color: rgba(0, 0, 0, 0.6) !important;
    }
    
    #cookieconsent\:desc {
        text-align: center;
    }
    
    @media (max-width: 1025px) {
      div.cc-window {
    	align-items: center !important;
    	padding: 40% 8% !important;
    	display: block;
    	margin-left: auto;
    	text-align: center;
    	margin-right: auto;
     }
    }
    @media (max-width: 500px) {
    	div.cc-window {
    		padding-top: 70% !important;
    	}
    }

    Note: If you would like to configure the transparency of the background, you can change the current value of 0.6 (min value 0, max value 1) in the following line:

    Preview:
    With close button:

    Help Center question
    Without close button:
    (Can be configured from Cookie Consent Bar > Show Close Button)
    Help Center question

    Important: Make sure that in the Design Settings tab > Position you have selected "Bottom" or "Top" in order for the script to apply correctly!

  • 58. How can the app integrate with Rakuten Advertising?

    In order for our app to integrate with Rakuten, certain variables should be set, in order for Rakuten to differentiate the cookie preferences for each customer of your store. You would need to set up the following two variables:

     <script type="text/javascript">
    
    	var rakISenseConsentModule = function() {
    
    		function rakConsent() {
    			window.__rmuspc = 'YN';
    			 
    			function isl_rc(n) {
    				for (var r = n + "=", t = document.cookie.split(";"), e = 0; e < t.length; e++) {
    					for (var i = t[e]; " " == i.charAt(0); )
    						i = i.substring(1, i.length);
    					if (0 == i.indexOf(r))
    						return i.substring(r.length, i.length)
    				}
    				return null
    			}
    	 
    			// Default is no purposes
    			var GDPRpurposes = [];
    			// function that allows to add GDPR purposes selectively to array
    			var addGDPRpurposes = function (purpArray) {
    				var purposeIDs = purpArray || [];
    				var tmpRMCP = [];
    				if (purposeIDs.length !== 0) {
    					tmpRMCP = GDPRpurposes || [];
    					for (var i = 0; i < purposeIDs.length; i++) {
    						// Only add purpose if it not already exists
    						if (tmpRMCP.indexOf(purposeIDs[i]) === -1) {
    							tmpRMCP.push(purposeIDs[i]);
    						}
    					}
    					GDPRpurposes = tmpRMCP.sort(function(a, b){return a-b});
    				}
    			};
    	 
    			var cookieconsent_status = isl_rc('cookieconsent_status');
    		  
    			if (cookieconsent_status == 'accept_all') {
    				window.__rmcp2 = [1,2,3,4,5,6,7,8,9,10];
    			} else if (cookieconsent_status == 'allow') {
    				window.__rmcp2 = [1,2,3,4,5,6,7,8,9,10];
    			} else if (cookieconsent_status == 'accept_selected') {
    				 
    				var cookieconsent_preferences_disabled = decodeURIComponent(isl_rc('cookieconsent_preferences_disabled')).slice(0, -1);
    				var cookieconsent_preferences_disabled_split = cookieconsent_preferences_disabled.split(',') || [];
    				var consent_analytics = true;
    				var consent_marketing = true;
    				var consent_functionality = true;
    				 
    				//detect disabled purposes
    				for(var i = 0; i < cookieconsent_preferences_disabled_split.length; i++) {
    					if(cookieconsent_preferences_disabled_split[i] === 'functionality') {
    						consent_functionality = false;
    					}
    					else if(cookieconsent_preferences_disabled_split[i] === 'marketing'){
    						consent_marketing = false;
    						window.__rmuspc = 'YY';
    					}
    					else if(cookieconsent_preferences_disabled_split[i] === 'analytics'){
    						consent_analytics = false;
    					}
    				}
    				 
    				// If consent for analytics allow purposes 1,7,8,10
    				if (consent_analytics) {
    					addGDPRpurposes([1, 7, 8, 10]);
    				}
    				// If consent for marketing allow purposes 1,2,3,4,7,9,10
    				if (consent_marketing) {
    					addGDPRpurposes([1, 2, 3, 4, 7, 9, 10]);
    				}
    				// If consent for functionality allow purposes 1,5,6,10
    				if (consent_functionality) {
    					addGDPRpurposes([1, 5, 6, 10]);
    				}
    				 
    				window.__rmcp2 = GDPRpurposes;
    			}  
    			 
    		};
    		 
    		rakConsent();
    		
    	 	if(!window.jQuery) {
    			// Load the script
    			var script = document.createElement("SCRIPT");
    			script.src = 'https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js';
    			script.type = 'text/javascript';
    			script.onload = function() {
    				//accept all
    				jQuery(document).on("click", ".cc-allow, .cc-btn-accept-all", function () {
    					rakConsent();
    				});
    			 
    				//when the user clicks Prefrences but just closes the popup without selecting anything.
    				jQuery(document).on("click", ".cc-btn-accept-selected", function () {
    					rakConsent();
    				});
    			};
    			document.getElementsByTagName("head")[0].appendChild(script);
    		}
    		else {
    			//accept all
    			jQuery(document).on("click", ".cc-allow, .cc-btn-accept-all", function () {
    				rakConsent();
    			});
    			
    			//when the user clicks Prefrences but just closes the popup without selecting anything.
    			jQuery(document).on("click", ".cc-btn-accept-selected", function () {
    				rakConsent();
    			});
    		}
    	}();
    </script>
     
    Feel free to add this code just before the </head> tag of your theme.liquid file.

    If any issues or concerns arise, you can always reach out to us in the live chat of the app, or via email: apps-support@isenselabs.com

  • 59. What is the meaning behind the text located under the Accept Selected and Accept All buttons: By clicking on the above buttons, I give my consent on collecting my IP and email (if registered). For more check Privacy Policy?

    The purpose of this text is for the visitor/customer in your website to know that by clicking on the above-listed buttons they are giving their consent that we (iSenseLabs LLC) as a processor of information will use the up-listed data (IP and email if registered) in order to execute the request. We keep this information for 12 months and after this period is over, the information gets deleted as per the GDPR/CCPA laws.

    In the text there is also a link, in which both the link itself and the wording will work based on the option Enable for Specific Regions. Here is how the link works:

    1. If your bar is set to show for EU/EEA Visitors (GDPR) + Brazil (LGPD) the link will redirect to your GDPR Compliance page.
    2. If your bar is set to show for California Visitors (CCPA) the link wil redirect to your CCPA Compliance page.
    3. If your bar is set to show for EU/EEA + Brazil & California Visitors (GDPR & CCPA) the link will redirect to your GDPR Compliance page.

    If you do not have GDPR/CCPA pages generated, the link will redirect to our app's Privacy Policy.

    Note: This text can be translated by the Language for the Data Collection Text ( *By clicking on the above buttons, I give my consent on collecting my IP and email (if registered). For more check Privacy Policy ) option, located in the Global Settings tab, or if your store has set up metafields, it will work with metafields as well.

    Help Center question

    This is also covered in the GDPR and CCPA pages where upon submitting a request the customer/visitor is required to check the following in order for the request to get processed:

    Help Center question

  • 60. How does the cookie blocking of Facebook Pixel and Google Analytics works on the Checkout page?

    Our app is blocking the cookies on each page load based on the customer's preferences or the initial state of the app. However a flag has to be set via the Shopify's Consent Tracking API, in order for the Facebook Pixel and Google Analytics cookies be blocked correctly on the Checkout page, because the script for the blocking from our app is not loaded there by default. In order to do this, we have integrated Shopify's API in our app and this flag will be set accordingly, based on which button the customer will press and with which preferences. If a customer has accepted all of the cookies, the flag will not block any cookies on the Checkout page. If a customer has opted out of the Marketing or Analytics cookies gorups, or both - the flag will block the Facebook Pixel and Google Analytics on the Checkout page.

    You can find more information in regard to Shopify's API in the following URL: https://shopify.dev/docs/themes/consent-tracking-api

  • 61. How to add an additional link in the Consent Bar, next to the Privacy Policy link?

    In order to add a second link in the Consent Bar, you should add the following code in the Cookie Consent Text field, located in the Cookie Consent Bar settings tab:

    <a aria-label="learn more about cookies" role="button" tabindex="0" class="cc-link" href="{{ URL }}" rel="noopener noreferrer nofollow" target="_blank">{{ TEXT }}</a>
    
    Make sure to replace the URL and TEXT fields with the URL, where you would like the button to redirect to, and the text of the link.

    Your link should look similar to this:

    Help Center question

  • 62. How to enable the Limit Tracking for customers from Europe and the state of California?

    Our app is integrated with Shopify's Consent Tracking API, which helps with the prevention of tracking your customers, based on the GDPR and CCPA laws. In order to limit the tracking for the customers from Europe and the state of California, you would need to navigate to your Shopify Admin Panel > Online Store > Preferences > Customer Privacy > Limit data collection for EU buyers & Limit data collection for California buyers

    For more information, feel free to check the following link - https://shopify.dev/docs/themes/consent-tracking-api

  • 63. How to configure an 'Accept only necessary cookies' button on your Consent Bar?

    If you would like to configure a button, which upon clicking will allow only the Strictly required cookies to be allowed, here is what you would need to do:

    1. Set the initial state of the app to Block marketing & analytics cookies until visitor opts-in. You can do this from Cookie Consent Bar > Initial state of the Cookie Consent Bar.
    2. Make sure that the Regard the Initial State Of The Cookie Consent Bar for the 'Accept' button option is set to Yes. This option is located in the Cookie Consent Bar settings tab.
    3. Rename your current Accept button. An example would be: "Accept only necessary cookies". You can do this from Cookie Consent Bar > Accept Button Text.
    In this way, by default when a customer enters the store for the first time, the Marketing & Analytics cookies will be blocked by default, and upon pressing the Accept button only the necessary ones will be always active. The customer can still accept all of the cookies by pressing one of the Accept buttons from the Preferences popup (Accept Selected or Accept All)

  • 64. How are the customer preferences reset automatically?

    Our app sets a cookie immediately after the customer presses one of the Accept buttons from the Preferences popup or the Consent Bar. This cookie's expiration date is set to 12 months, meaning that unless a customer browses from another browser or clear his cookies manually, the bar will not be shown after the acceptance within this period of time. The cookie will be deleted automatically after 12 months, meaning that the Consent Bar will show again and the customer will be able to configure his preferences.

    If you want to set up a button, which upon clicking will trigger the Preferences popup, in order to allow the customer/website visitor the ability to reconfigure their cookie preferences before the cookie has expired, please navigate to question #11.

    Our app also has the feature to reset the consent to all of the customers of your store. In order to do this, navigate to Global Settings > Reset Customer Consent. This feature is part of the Premium features of the app.

  • 65. Should I have a Privacy Policy statement in my store for inactive accounts and their data erasure?

    The short answer is yes. User data should be stored as long as it is useful, or until a customer has requests the data to be erased (the second can happen through the GDPR/CCPA compliance pages of the app. For more information check questions number #12, #16 and #43) In any case you should have a statement in your store's Privacy Policy on how you are managing the inactive customer information, for what period of time you are storing it and why. We would advise you to set and communicate (in your store’s Privacy Policy) a period of inactivity that will result in data erasure.

  • 66. How do we change GDPR compliance for the UK after Brexit?

    For the first 4 to 6 months of 2021, the flow of data between the EU and the UK will remain the same. It all depends on the adequacy decision that the EU will make about the data flow.

    What does Adequacy mean?

    ‘Adequacy’ is a term that the EU uses to describe other countries, territories, sectors, or international organizations that it deems to provide an ‘essentially equivalent’ level of data protection to that which exists within the EU.

    The UK is seeking adequacy decisions under both the General Data Protection Regulation (GDPR) and the Law Enforcement Directive (LED). The effect of an adequacy decision is that personal data can be sent from an EEA state to a third country without any further safeguard being necessary.

    What can you do right now?

    Since the UK GDPR is almost word for word completely identical to the EU’s GDPR:

    • it requires your website to obtain explicit consent from users before processing their personal data via cookies and third-party trackers
    • it requires you to safely store and document each valid consent
    • it requires your website to enable users to change their consent just as easily as they gave it
    • and it gives a set of rights to UK users, chief among them the right to delete and the right to have corrected already collected personal data
    What you can do right now is change the name/wording of the already generated GDPR compliance page to UK GDPR compliance from Online Store > Pages > GDPR Compliance as shown here:

    Help Center question

  • 67. What exact cookies is our app setting on your store?

    Our app is setting two cookies on your store, in order for the app to function properly.

    Here is a brief explanation for these cookies:

    Cookie name: cookieconsent_status

    This cookie will be set as soon as one of the Accept buttons or the Close button is pressed. It holds information about which exact button is pressed. Here is a list of all of the available options for the cookie's contents:

    • dismiss - When the 'Close' button is pressed
    • allow - When the 'Accept' button from the Consent Bar is pressed
    • accept_selected - When the 'Accept Selected' button is pressed ( from the Preferences popup )
    • accept_all - When the 'Accept all' button is pressed ( from the Preferences popup )

    Cookie name: cookieconsent_preferences_disabled

    This cookie will be set based on the selected option from the app setting Initial state of the cookie consent bar. It holds information about the cookie groups, which are currently blocked. The blocking can be either based on the initial state or when the customer manually opts out of a certain cookie group. Here is an example:
    If you have checked the options Block marketing cookies until visitor opts-in and Block analytics cookies until visitor opts-in this would mean that the Analytics and Marketing cookie group will be blocked initially. The information, which this cookie will contain will be: marketing%2Canalytics

    The information, which this cookie contains, will be changed every time when the customer changes his preferences. Based on this cookie, the blocking of the cookies is maintained.

  • 68. What happens if a customer submits a request through the Compliance page without having an account?

    When a customer places an order in your store, without having an account registered, Shopify automatically creates a new account for this customer with all of their information, which he/she has inserted during the checkout process. This includes e-mail addresses and physical addresses. Once the account is created, the status of the account is Disabled meaning that the account is there, however the customer cannot access it, because he/she does not have a password yet. In order for the customer to be able to set his/her own password, the store owner should send an invite to the customer to his/her e-mail with a link, from where they can set up their password and use the account afterward.

    This would mean that even if a customer has not created the account himself, he/she will still have an account generated automatically and can submit different types of requests from the Compliance pages, generated by our app, with the e-mail that they have placed their order with.

  • 69. Does the app affect Shopify's Conversion Rate tracking?

    The conversion rate of your store might be affected by our app if a customer chooses to block the analytics cookies, or the initial state is set to block the analytics cookies by default. What happens is that on each page refresh only when the cookies are blocked, a session is counted in Shopify's Analytics dashboard, because the cookies are loaded initially and afterwards blocked by our app, which results in duplication of sessions.

    If the sessions are duplicated, the conversion rate in the Analytics dashboard might drop, since there are more sessions than the current orders that your store has. Below you will find the variants on how this can be fixed:

    1. Remove the cookie that is counting the sessions from our app's cookie list in the Analytics cookie group. We believe the cookie that is counting the sessions is _shopify_y since when this cookie is not blocked, the sessions are not duplicated on each page refresh. In order for you to remove it, feel free to navigate to the Cookie Information Panel, located in the Cookie Consent Bar settings tab, locate the cookie and press the button Delete cookie. If you are on the Free plan, you can simply remove the cookie from the lists of cookies, that is located above the Cookie Information Panel In this way the cookie will not be blocked by our app in any way.

    2. Change the option Initial state of the Cookie Consent Bar to allow all of the cookies by default, however we do not recommend this option since the customers should give their consent, before they are being tracked.

    3. Make the consent bar required in a way before the customer starts browsing your site, by positioning it in the middle. In this way when the customers enter your store and press the 'Accept all' button on the consent bar, all of the cookies will be allowed. If you would like to position the consent bar in the middle, you can check the following FAQ section for more information on how you can do that - 57. How to blur out the store's pages until the customer gives his consent?

  • 70. How do the options for Customer Privacy work with our app? (Cookie Consent API)

    Shopify currently has the options to limit the tracking of data for customers from Europe (GDPR) and customers from the state of California (CCPA) by enabling the two options, which you can find in Online Store -> Preferences -> Customer Privacy. If these options are selected, customers must give consent before their data can be collected. By selecting these options, the following changes will occur:

    • The Facebook Pixel and Google Analytics will be blocked initially until the customer explicitly gives his consent. This is happening on Shopify's side, with the Consent Tracking API, which our app is integrated with. How it works is once the page is loaded and the cookies are initially blocked by Shopify, each customer has the option to opt-in or opt-out of the different cookie groups. Once the customer presses one of the 'Accept' buttons, a flag will be sent to Shopify which will be set either to true or false, depending on how the customer has configured their preferences. If he/she has accepted all of the cookies, then all of the cookies will be allowed. If not, then the flag will be set to false and Shopify will continue to block the cookies the same way as they were blocked initially. The blocking will also work with the cookies, set on the Checkout page.
    • The cookies, which are in regard to Shopify for example - _shopify_y, _shopify_s, _y, etc. will be set as session cookies, meaning that they will be deleted as soon as the customer closes their browser. If the customer however has accepted the cookies, i.e. the flag mentioned above is set to true the cookies will be upgraded to persistent cookies, which are stored in the browser and will not be deleted when the customer closes their browser.

  • 71. How to translate the app by using metafields?

    We have recently introduced a new tab in the settings of the app called Translation. There you will see the two options for changing the language for the GDPR/CCPA Request pages and emails, and the Language for the data collection text, which are now moved to this new Translation tab. We have also introduced two new buttons: 'Refresh Metafields' and 'Add metafields to theme.liquid'. Here is what each button does:

    1. Refresh Metafields - you will need to press this button when you want to set up the metafields for our app, in order for them to be visible in your translation app's settings.
    2. Add metafields to theme.liquid - this button will add the necessary code, in order for our app to work correctly with those metafields. If you are on a Free plan, you would need to manually add the code in your theme.liquid file. Check the instructions below for more information.

    In order for the metafields to work with your app for translation, you would need to press the Refresh Metafields button, and afterwards add the code to the theme.liquid file either manually, or by pressing the button. Afterwards, the metafields should be visible in the settings of the translation app you are using.

    How to add the code needed manually to the theme.liquid file?

    1. Navigate to your theme.liquid file. You can do this by navigating to Online Store -> Themes -> Actions -> Edit code -> theme.liquid.
    2. Locate the <head> tag. It is at the very beginning of the file.
    3. Download the file from below and paste its contents after the <head> tag.
    4. Save the settings.

  • 72. How does our app block cookies related to Hotjar?

    In order for our app to block cookies, set by Hotjar, you would need to add them manually in our app's settings. For additional information on how to add third-party cookies to be allowed or blocked by our app, feel free to check question #50.

    Here is a list of all the cookies, which might be set from Hotjar - https://help.hotjar.com/hc/en-us/articles/115011789248-Hotjar-Cookie-Information

  • 73. How to change the font family and font size of the Consent bar and Preferences popup?

    In order to change the font family or the font size of the Consent Bar & Preferences popup, you would need to navigate to the Design Settings tab and locate the two fields called Font Family and Font Size. From there you can set the corresponding font family and the font size of your choice. Note that the limit of the font size is 25 pixels.

    Example:

    Before:
    Help Center question

    After:
    Help Center question

    For additional information or fonts, feel free to check Google Fonts

  • 74. How to set up a Reject/Refuse button?

    In order for you to set up a Reject/Refuse button, which upon clicking will block all of the cookie groups, you would need to:

    1. Navigate to Cookie Consent Bar tab > Close Button Text and rename the button accordingly to your preferences. (i.e. Reject/Refuse)
    2. Navigate to Cookie Consent Bar tab > Close Button Text and make sure the option is set to Show.
    3. Navigate to Cookie Consent Bar tab > Action when the 'Close' button is clicked and check the following options:
      • Block marketing cookies until visitor opts-in
      • Block analytics cookies until visitor opts-in
      • Block functionality cookies until visitor opts-in
    4. That's it!
    Also, feel free to check the video below for additional instructions:
    Help Center question

  • 75. How to be GDPR compliant as per the French CNIL (Commission nationale de l'informatique et des libertés)?

    First, you will need to add a Reject All button in the Cookie Consent bar. Please follow the steps below in order to do that:

    Help Center question

    The code from the video can be copied from here:

    button.cc-btn.cc-dismiss {
    	color: #{{ COLOR CODE }} !important;
    	border-color: transparent;
    	background-color: #{{ COLOR CODE }} !important;
    	outline: none;
    	border-radius: 3px !important;
    	margin-left: .5em;
    }
    

    Secondly, you should set up an Accept All button. In order to make the Accept button in the Cookie Consent Bar to act like an Accept All button, you will simply need to rename the button from Accept > Accept All and then in the additional settings section select the option for the Accept button to disregard (choose 'No') the Regard the Initial State Of The Cookie Consent Bar for the 'Accept' button, so it could work as the one in the Preferences popup.

    Help Center question Help Center question

    Last but not least, this new requirement asks for a detailed explanation of each cookie group and each specific cookie. This can easily be achieved by adding your specific description in the designated places in the Cookie Consent Bar tab:

    Additional description for the cookie categories:

    Help Center question

    Additional description for each specific cookie:

    Help Center question

    That's it! After you have followed all of the steps, you should be compliant with the French CNIL.

  • 76. How to add/show the duration of the cookies?
    There is no dedicated field for duration yet, so the only way you can add this for each specific cookie is through the Cookie Consent Bar tab > Cookie Information Panel. You can select a cookie to add/modify and put the duration description as shown in the below example:


    Help Center question

    after that, when you save this, it will show in the Preferences Popup under the Analytics category like this:


    Help Center question

    In order to find out the exact duration of each cookie, you can use services like: the Chrome dev tools, Chrome EditThisCookie extension, or other specific services which make this check. We came across this service www.cookieserve.com which gives the exact duration of the cookies, not the expiration date as the other methods do. You can make a check for your store and add the data about it in the cookie's description field in the app.

    On our end, we can confirm that we set two cookies: cookieconsent_status and cookieconsent_preferences_disabled which both have a duration of 1 year.

  • 77. Why is the cookie bar and the buttons focused by default and how can I update the styling?

    The blue outline focus on the cookie bar's elements is there to help users with motor impairments, which could be anything from permanent paralysis to a sprained wrist. These users operate their computer almost entirely with the keyboard or other input device. For those users, focus is critical, it's their primary means of reaching everything on the screen. For that reason, the Web AIM checklist states in section 2.1.1 that all page functionality should be available using the keyboard.

    In order to change the styling of the focus on our cookie bar's elements

    Help Center question Help Center question

    just add the required styling in the CSS selector that we have provided below (located in the Design Setting tab > Custom CSS):

    .cc-window button:focus, .cc-window a:focus, .cc-settings-dialog button:focus, .cc-settings-dialog a:focus, .cc-settings-dialog input:focus + .cc-checkbox {
    box-shadow: 0 0 0 {Width} {Color};
    }

    Example with white color:

    CSS Code:
    .cc-window button:focus, .cc-window a:focus, .cc-settings-dialog button:focus, .cc-settings-dialog a:focus, .cc-settings-dialog input:focus + .cc-checkbox {
    box-shadow: 0 0 0 2px white;
            }

    Result:
    Help Center question

    Note: In case of difficulties or issues with styling the focus of the cookie bar's elements, please contact us at apps-support@isenselabs.com.

  • 78. I scanned my store with cookiebot.com? Why it is not shown as complaint?
    The cookie scanner by Cookiebot is only able to interact with its own banner script and all external banner scripts are ignored, including our app’s cookie consent bar. However, this does not mean that the cookies are not blocked with our app, it is just that this result is not displayed by the Cookiebot cookie scanner.
  • 79. How to translate the app by using Langify?

    At the moment, you can translate the Consent Bar & Preferences popup with Langify in the following two ways:

    1. With Metafields
    2. By adding the texts manually in the Custom Content section

    How to translate with Metafields:

    1. Follow the instructions from question #71.
    2. Once you have completed these steps, the texts of the app should be visible in Langify's Metafields section:
      Help Center question

    How to translate by adding the texts in Custom Content:

    1. Navigate to Langify > Custom and press Global
      Help Center question
    2. Add the corresponding texts of the Consent bar and the Preferences popup from here:
      Help Center question

  • 80. Can I remove the Close button from the Cookie Consent Bar?

    The short answer is Yes, however you need to remove not only the text from the Close Button Text field, as show here:

    Help Center question

    but also select “Hide“ in this option below:

    Help Center question

    Once both of these are done, the button will be removed from the Cookie bar.

  • 81. How does the Admin Mode option work?

    If you are not located in a GDPR and/or CCPA region, the only way for you to test/try out the app and see the Cookie bar on your storefront (witouht making it live for your webstore visitors) is with the Admin Mode option located in the Global Settings tab > Show Cookie Consent Bar. Once the Admin Mode is enabled, make sure to open your store in Preview mode as shown in the below screenshot (step 4):

    Help Center question

  • 82. How is the quota calculated?

    All of our plans have a quota limit that is based on the page visits/views. Tracking page visits/views is not the same as overall website visitors. Here is a short description of how the quota is being calculated:

    The page visits/views are counted each time a customer/website visitor opens a page in your store. For example, if a customer first navigates to the Home page and after that to a Product page, the page visits count will be increased by 2, since the app is loaded on both of those pages. The reason for this is because the app is loaded on every page, in order to maintain the same blocking of cookies on each page. This is what makes the website compliant with the user's choice. You can also check the following FAQ question for additional information - 46. Why am I seeing a message for reaching a quota limit?

  • 83. How to add a Reject All button to the Preferences popup?

    In order to achieve this you will need to make a couple of small changes:

    1. Locate the Accept Selected Button Text in the Cookie Consent Bar tab:

    Help Center question

    2. Change the text from Accept Selected to Reject All

    3. Locate the Initial State Of The Cookie Consent Bar settings in the Cookies Consent Bar tab and block all cookie categories as shown here:

    Help Center question

    4. Save the settings and Preview your store from here:

    Help Center question

    The Accept Selected button should now work as a Reject All in the Preferences popup. The end result should look like this:

    Help Center question

  • 84. Why am I seeing an N/A in the Policy Acceptances tab?

    This means that the acceptance or blocking of cookies came from a customer that is generally not registered in your website or they are registered but are currently not logged in into their account. Hence, we are not able to retrieve the data for their e-mail and customer ID. That is why these acceptance entries will be marked as Guest Customer and N/A under the Customer # column.

    Help Center question

  • 85. How to make the Consent Bar and Preferences Popup a bit/slightly smaller?

    In order to make the Consent Bar and the Preferences Popup smaller you should apply the following CSS code in Design Settings > Custom CSS :

    div.cc-window {
      padding: 0.8em 1.2em!important;
      font-size: 14px!important;
    }
    .cc-settings-view .cc-settings-dialog {
      font-size: 13px!important;
      padding-top: 30px;
    }
    .cc-settings-view .cc-settings-dialog label, .cc-settings-dialog .cookies_info h3 {
      font-size: 13px!important;
    }
    .cc-settings-dialog .cookies_info p {
      margin-bottom: 12px;
    }
    .cc-settings-view .cc-settings-dialog h3.cookie_settings_header {
      font-size: 18px!important;
    }
    @media screen and (max-width: 428px) and (orientation: portrait), screen and (max-width: 926px) and (orientation: landscape) {
      .cc-window .cc-highlight {
        margin-top: 5px;
      }
      .cc-window .cc-message {
        margin-bottom: 0px;
      }
      .cc-settings-view .cc-settings-dialog {
        font-size: 14px!important;
        padding-top: 10px;
      }
    }
    Preview:
    Consent Bar on desktop device:

    Help Center question
    Smaller Consent Bar on desktop device:

    Help Center question

    Consent Bar on mobile device:

    Help Center question

    Help Center question
    Smaller Consent Bar on mobile device:

    Help Center question

    Help Center question

    If you require an even smaller Consent Bar after applying the modifications, feel free to contact our support team at apps-support@isenselabs.com.

  • 86. How to add cookies to the different cookie categories as a free user?

    You will need to navigate to the Cookie Consent bar tab in the admin side of the app and scroll down to the Cookie Categories. There you will be able do directly click and add/remove/edit any cookie you want. Please check the attached video for a step-by-step explanation.

    Help Center question
  • 87. What is the correct way to scan which cookies are set/blocked on my store?

    In order to properly check which cookies are set/blocked in your store, we recommend installing and using a cookie scanning extension to your browser. We suggest that, as scanning your store's cookies from the site information popup left to the web address will always show that no cookies are blocked. The reason for that is that the cookie scanner in the above-mentioned popup is scanning your store's cookies before our app's script is loaded, which results in the cookie scanner showing you that no cookies are blocked.

    The tool we recommend using is called EditThisCookie - a Chrome extension. It will show more accurately what cookies are currently active and what cookies are blocked.

  • 88. The buttons on the Preferences popup are not visible. How can I fix that?

    If the buttons on the Preferences popup are not accessible, feel free to apply the following code below in Design Settings > Custom CSS:

    #cookieconsent\:settings { overflow: auto; }
    

    After you have saved the settings, the next time you open the Preferences popup you should be able to scroll to the bottom of the popup and access the Accept Selected and Accept all buttons.

    If you have any additional questions or concerns, feel free to contact us at apps-support@isenselabs.com.

  • 89. How to style the cookie categories' descriptions in the Preferences Popup?

    In order to modify the stylings of the cookie categories' descriptions, you will need to navigate to the Design Settings tab in the settings of our app. After that depending on what you require, you should apply one of the CSS code snippets we provided below to the Custom CSS field.


    To apply the styling to all four of the cookie categories' descriptions, you can apply this CSS code:

    .cc-settings-dialog .cc-cookie-category-text {
    color: #ff0000;
    font-size: 18px;
    font-family: Calibri;
    }

    To apply the styling only to one of the cookie categories' description, please apply one of those CSS codes, depending on which category you want to style:

    1. Strictly Required cookie category styling:

      #strict-cookie-category-text { color: #ff0000; font-size: 18px; font-family: Calibri; }
    2. Reporting and Analytics cookie category styling:

      #analytics-cookie-category-text { color: #ff0000; font-size: 18px; font-family: Calibri; }
    3. Marketing And Retargeting cookie category styling:

      #marketing-cookie-category-text { color: #ff0000; font-size: 18px; font-family: Calibri; }
    4. Functional cookie category styling:

      #functionality-cookie-category-text { color: #ff0000; font-size: 18px; font-family: Calibri; }

    Note: You can change the values of the color, font-size and font-family properties so that they fit your requirements.

  • 90. How to activate the consent bar to load via app embed block?

    With the new changes that Shopify has introduced with Online Store 2.0, they suggest that the apps that are currently using a ScriptTag API to load their scripts, to now use theme app extensions, and the file that was loaded before to be hosted and loaded now directly from Shopify's CDN network.

    In order to activate this, here are the steps that you would need to follow:

    1. Navigate to Online Store -> Themes
    2. Press the Customize button of your current live theme
    3. Navigate to Theme settings in the bottom left corner
    4. Click App embeds
    5. Locate the GDPR Consent Bar and turn on the app embed.
    6. Save the settings
    7. That's it!
    Once this option is ON, the script for the app will be loaded directly from Shopify. Note that you would need to leave this option ON at all times. If you would like to turn OFF the consent bar, you can do it by navigating to the settings of the app -> Global Settings -> Show Cookie Consent bar -> Disable.

    Also, feel free to check the following video below for instructions:

    Help Center question
  • 91. How can I add a CCPA Do Not Sell Rule link to the store footer?
    You can add it on the navigation menu, in the footer, or on any page that you want. The link for accessing the Do Not Sell My Information section is composed of 2 parts:
    • The current CCPA Page link. You can access this link as shown here monosnap.com In the corresponding tag is an example the URL https://your_store_url.com/pages/ccpa-compliance
    • The selection code for the section ?id=do-not-sell
    In total the respective link will look like this: https://your_store_url.com/pages/ccpa-compliance?id=do-not-sell
    If you want to add the link in one of your navigation menus, you have to go to "Online Store" and then "Navigation". Make sure to paste the formed link.
    Adding a link to a specific page depends on the theme that you are using. If you need help with any of this, do not hesitate to contact us - our team will be more than happy to help you.
    You can check the below video showing how the whole process works.
    Help Center question
  • 92. How to translate the app with Transcy?

    In order to translate the content of the Consent Bar and the Preferences popup, you would need to first set up the metafields for our app. For more information on how this can be done, check question #71 - 71. How to translate the app by using metafields?

    By default Transcy has the option to translate metafields, however at the moment, their app is only detecting metafields related to Products or Variants. Since the texts for our app are not related to the Products or Variants, the metafields have to be synced manually on Transcy's side. For this, you will need to contact their support team and ask them to manually sync the metafields for our app. You can contact their support team on the following email - support@fireapps.io.

  • 93. Why is the text in the Cookie Consent Bar and Preferences popup not changing?
    If the text in the Cookie Consent Bar or the Preferences popup is not changing after modifying it in our app's settings, most likely the case is that you have our app's meta fields code applied to your store's theme.liquid file. When you have our app's meta fields code applied to your store, you would have to refresh the meta fields every time you change any text that is displayed in the Cookie Consent Bar or the Preferences Popup. In order to refresh the meta fields, navigate to the Translation tab located in our app's settings and click on the Refresh Metafields button. This is required since the app that you are using to translate the meta fields will not detect the modified text in the meta fields, so a manual refresh is required by clicking on the Refresh Metafields button.
  • 94. How to block Klaviyo from collecting information?

    In order to block the tracking from Klaviyo so that no information is being collected if a customer has opted out of the Marketing cookie group, you would need to add an additional script in your main theme file. Here are the steps that you would need to follow:

    1. Open Shopify Admin.
    2. Click on Online Store link in the left menubar.
    3. Click on the "Action" dropdown button and select "Edit Code" from there.
    4. A new page will open with a list of files on the left side of the screen. Open the "theme.liquid" file.
    5. Find the string "</head>" in there.
    6. When you do, add the following snippet before "</head>":
    7. <script>
      function checkGDPRKlaviyo() {
            if (window.isenseGDPR !== undefined && window.isenseGDPR.Cookies.get('cookieconsent_preferences_disabled') !== undefined) {
              let cookie = window.isenseGDPR.Cookies.get('cookieconsent_preferences_disabled');
              if (cookie.indexOf('marketing') == -1) {
                document.cookie = "__kla_off=;expires=Thu, 01 Jan 1970 00:00:00 GMT";
              } else {
                document.cookie = "__kla_off=true"; 
              }
            } else {
              setTimeout(function() {
                checkGDPRKlaviyo();
              }, 500);
            }
          }
      
          checkGDPRKlaviyo();
      
          window.addEventListener('click', function (e) {
            if(e.target && (e.target.className == 'cc-btn cc-btn-accept-all' || e.target.className == 'cc-btn cc-allow' || e.target.className == 'cc-btn cc-btn-accept-selected')){
              checkGDPRKlaviyo();
            }
          });
      </script>
      
    8. Click on the "Save" button.
    9. That's it!

    For additional reference on how the script works, feel free to check the documentation for Klaviyo here - About Cookies in Klaviyo

    How the script works? - We are setting the Klaviyo cookie __kla_off to true, which should stop Klaviyo from tracking onsite activity data, if the customer has opted out of the Marketing cookie group through our app.

  • 95. How to position the Consent Bar in the middle of the screen?

    In order to set the position of Consent Bar in the middle of the screen, please paste the following CSS code in Design Settings > Custom CSS:

    .cc-window.cc-banner { background-color: rgba(0, 0, 0, 0.6)!important; }
    
    .cc-window {
    height: 100%;
    display: flex;
    justify-content: center;
    align-items: center;
    background-color: rgba(0, 0, 0, 0) !important;
    top: 50% !important;
    padding: 0px 25% !important;
    left: 50% !important;
    transform: translate(-50%, -50%);
    }
    
    #cookieconsent\:desc { text-align: center; }
    
    #cookieconsent\:settings, div.cc-window { overflow: auto; }
    
    .cookieconsent-wrapper { 
    background: black; /* SET CONSENT BAR BACKGROUND COLOR HERE */  
    padding: 20px; 
    border-radius: 5px; 
    }
    
    .cc-banner>.cookieconsent-wrapper {
    flex-wrap: wrap;
    justify-content: space-around;
    }
    
    .cc-compliance {
    flex-wrap: wrap;
    }
    
    @media ( max-width: 875px ) {
    div > button.cc-btn.cc-allow {
    margin-top: 0.5em;
    }
    }
    
    @media (max-width: 875px) {
    	div.cc-window {
    		width: 90%;
    		padding: 0px !important;
    	}
    }

    Note: If you would like to change the background color to be other than black, you can locate the background: black; line of the code and set the color to whichever you would like.

    Preview:
    With close button:

    Help Center question
    Without close button:
    (Can be configured from Cookie Consent Bar > Show Close Button)
    Help Center question

    If you would like to remove the blurring of the background, you can do this by deleting the first line of the code above - removing the .cc-window.cc-banner { background-color: rgba(0, 0, 0, 0.6)!important; } code. Here is a preview of how the consent bar will look like:

    Important: Make sure that in the Design Settings tab > Position you have selected "Bottom" or "Top" in order for the script to apply correctly!

    Help Center question
  • 96. What should I do if I update my store theme?

    If you update your store theme, there is no need to delete or reinstall the GDPR/CCPA app. It will load regardless of the theme since it is using the Script Tag API. Only if you are using the app embed option in the theme settings, you would need to go and enable it on the new theme too. We would recommend enabling this option!

    If you have added any additional blocking scripts or metafields to your previous theme (in the theme liquid files) for translation or for blocking Google Analytics, FB Pixel, you would need to apply them again in your new theme files.

  • 97. I have a feedback/suggestion for the app

    Great! We would love to hear what you want to say. You can contact us directly from the "Message Us" button at the bottom right corner of your browser. You can also contact us at apps-support@isenselabs.com.

  • 98. I don't see my question here. How can I contact you?

    You can contact us directly from the "Message Us" button at the bottom right corner of your browser. You can also contact us at apps-support@isenselabs.com.