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 time.

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.

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

⚠️ Before testing the preview of the Cookie bar in your store, please make sure to enable the App Embed option for the GDPR/CCPA + Cookie Management app in the store settings as shown in this video. That will set the script of the app to be loaded from a Shopify CDN server, asynchronously with all the other content of your store, and will prevent conflicts with other scripts loading on the webpage.

There are a few possible reasons why the Cookie 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 Bar is set to Enabled.

2) The location from where you are testing:
Note: Please check the success banner in the app to see if you have enabled the cookie bar to show for your location. If that is not the case, you will see the following message there:

Bear in mind that the Free plan allows you to enable the app on the following locations: EU/EEA countries, Brazil, the state of California, the state of Virginia, Japan and Canada. These are the locations where the GDPR/LGPD/CCPA-CPRA/VCDPA/APPI and PIPEDA 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, California state, Virginia state, Japan or Canada (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, California, Virginia, Japan or Canada IP.
2. Enable the app admin mode from Global Settings > Show Cookie Consent Bar > Admin Mode. This setting will disregard the Enable For Specific Regions selection and will show the Cookie 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. 

We have also recorded a video on how you can check the reasons for the Cookie bar not being shown in your store. You can find it below:

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

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 views 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.

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 > Position.

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

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:

If you want the Cookie bar to appear on top of the widget (i.e. a chat widget or other types of widgets you use in your store), you can add the CSS code below to the Design tab > Custom CSS field. The CSS code we provide will modify the z-index property of the Cookie bar to the max value (2147483647) so that it shows on top of other elements.

CSS Code:

.cc-window {
z-index: 2147483647 !important;
}

NOTE: if this does not work, it means that the widget's z-index property is set to the max value (2147483647) as well. In this case, the widget's z-index property should be reduced by 1 so that it appears below the Cookie bar. If you are having difficulties doing that, you can contact us and we will create the CSS code for you.
Alternatively, you can also check our FAQ 95. “How to position the Consent Bar in the middle of the screen?" to avoid any overlapping of the Cookie bar with any other widget on your store front.

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

If you are running any of our paid plans, you also have the option to change the layout of the Cookie bar and the Preferences popup from the same Design tab > Bar Layout section.

Preview:

Default:

Classic:

Modern:

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 > Cookies Management. Modify these cookies only if you are an advanced technical user.

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.

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:

<button class="btn btn--secondary" onclick="showPreferences();" 
style="cursor: pointer;
color: black; /*BUTTON TEXT COLOR*/
background-color: white; /*BUTTON BACKGROUND COLOR*/
border-color: black; /*BORDER COLOR*/
border-radius: 0px /*BUTTON ROUNDING (min 0px - max 15px*/
;">Cookie Preferences
</button>

<a onclick="showPreferences();"
role="button"
tabindex="0"
style="cursor: pointer;
text-decoration: underline;
">Cookie Preferences
</a>

In the code for the Button option you can change the colors and the rounding or the corners as per your preferences so it can match the styling of your store.

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!

You may also find our FAQ 107 ”How to add a Cookie Bar Widget to the bottom of the page?” helpful, which can give the customers a different option to change their cookie preferences.

If you have any request about the styles or the design, feel free to contact our team: apps-support@isenselabs.com

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.

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 - from the "We Are Here" button at the bottom right corner of your browser or at apps-support@isenselabs.com our team will be more than happy to help you.

You can track them directly in the app. From the Records tab you can check the - Policy Acceptances, GDPR/CCPA requests and Deletion requests.

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

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.

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 or Marketing cookie groups, or the customer opts out, the script which is setting the Google Tag Manager will not be executed.

Automatic enabling of the Google Tag Manager's blocking script

The Google Tag Manager's blocking script can be integrated automatically by opening our app's settings and navigating to Integrations tab > Service Tracking page > Google Tag Manager and clicking on the button Add blocking script to theme.liquid.

Note: This option is only available for the merchants that have upgraded to a Premium plan (Standard, Pro or Enterprise).
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!

Manual enabling of the Google Tag Manager's blocking 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 Google Tag Manager script in the head HTML elment - "<head>". It should look similar to this:

6. Copy the content of the file provided below and paste it under the script tag from step 5. Afterward, follow the next two steps:

• Step 1. Copy the content of the Google Tag Manager script and paste it under the comments “// The content of Google Tag Manager script goes here”.
  
• Step 2. Comment out or delete the Google Tag Manager script and save the changes.
  
  

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

Here is how the script works: Google Analytics 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.

Automatic enabling of the Google Analytics's blocking script

The Google Analytics's blocking script can be integrated automatically by opening our app's settings and navigating to Integrations tab > Service Tracking page > Google Analytics and clicking on the button Add blocking script to theme.liquid.

Note: This option is only available for the merchants that have upgraded to a Premium plan (Standard, Pro or Enterprise).
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!

Manual enabling of the Google Analytics's blocking 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 HTML elment - "<head>". It should look similar to this:

6. Copy the content of the file provided below and paste it under the script tags from step 5. Afterward, follow the next three steps:

• Step 1. Copy the link which is inside the src attribute and replace {{ 'Your src link' }} with the copied link.
  
• Step 2. Copy the content of the Google Analytics script and paste it under the comments “// The content of the Google Analytics script goes here”.
  
• Step 3. Comment out or delete the Google Analytics scripts and save the changes.
  

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.

Automatic enabling of the Google Analytics 4's blocking script

The Google Analytics 4's blocking script can be integrated automatically by opening our app's settings and navigating to Integrations tab > Service Tracking page > Google Analytics 4 and clicking on the button Add blocking script to theme.liquid.

Note: This option is only available for the merchants that have upgraded to a Premium plan (Standard, Pro or Enterprise).
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!

Manual enabling of the Google Analytics 4's blocking 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 HTML elment - "<head>". It should look similar to this:

6. Copy the content of the file provided below and paste it under the script tags from step 5. Afterward, follow the next three steps:

• Step 1. Copy the link which is inside the src attribute and replace {{ 'Your src link' }} with the copied link.
  
• Step 2. Copy the content of the Google Analytics 4 script and paste it under the comments “// The content of the Google Analytics 4 script goes here”.
  
• Step 3. Comment out or delete the Google Analytics 4 scripts and save the changes.
  

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.

Automatic enabling of the Google Ads's blocking script

The Google Ads's blocking script can be integrated automatically by opening our app's settings and navigating to Integrations tab > Service Tracking page > Google Ads and clicking on the button Add blocking script to theme.liquid.

Note: This option is only available for the merchants that have upgraded to a Premium plan (Standard, Pro or Enterprise).
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!

Manual enabling of the Google Ads's blocking 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 HTML elment - "<head>". It should look similar to this:

6. Copy the content of the file provided below and paste it under the script tags from step 5. Afterward, follow the next three steps:

• Step 1. Copy the link which is inside the src attribute and replace {{ 'Your src link' }} with the copied link.
  
• Step 2. Copy the content of the Google Ads script and paste it under the comments “// The content of the Google Ads script goes here”.
  
• Step 3. Comment out or delete the Google Ads scripts and save the changes.
  

Here is how it works by default: Our app deletes the Facebook Pixel cookies on page load. However, those cookies are then created by Facebook again on the next page load. Because of that, we are removing the cookies on every refresh. With that said, when a customer visits a page, a small bit of information is sent to Facebook Pixel. We are using this method due to Shopify's limitations preventing us from getting the tracking codes for each store.

Automatic enabling of the Facebook Pixel's blocking script

The Facebook Pixel's blocking script can be integrated automatically by opening our app's settings and navigating to Integrations tab > Service Tracking page > Facebook Pixel and clicking on the button Add blocking script to theme.liquid.

Note: This option is only available for the merchants that have upgraded to a Premium plan (Standard, Pro or Enterprise).
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!

Manual enabling of the Facebook Pixel's blocking 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 Facebook Pixel script in the head HTML elment - "<head>". It should look similar to this:

6. Copy the content of the file provided below and paste it under the script tag from step 5. Afterward, follow the next two steps:

• Step 1. Copy the content of the Facebook Pixel script and paste it under the comments “// The content of Facebook Pixel script goes here”.
  
• Step 2. Comment out or delete the Facebook Pixel script and save the changes.
  
  

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>

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

1) Cookie bar
2) GDPR/CPRA/APPI/compliance page
3) GDPR/CPRA/APPI notification/confirmation emails
4) GDPR/CPRA/APPI 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 App Dashboard.

If your original store language is different from the default one for the app - English, you have the option to set the language for the Cookie bar and Preferences popup from the Translation tab > "Set Language For The Cookie Bar & Preferences popup" section, as shown below:

The Cookie bar can be translated from the app itself by editing the text fields in the Cookie Bar tab > Cookie Bar Content section as well if the language you have as a default one is not available in the app settings.

The compliance page can be edited from Online Store > Pages > page GDPR Compliance. The steps are similar for the CCPA Compliance page.
If you are subscribed to any of our paid plans you can translate the Compliance pages to the original language of your store automatically from the Translations tab of the app as shown below:

In our FAQ section 115. How to translate the app if my original/default store language is not English? you can check more information on the matter.

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.

For your convenience, the Compliance pages are automatically created once you install the app.

If you happen to delete any of them 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 compliance pages.

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 in the 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!

NOTE: If the newly generated page is not correctly linked to the app settings (i.e. showing with an "X" sign in the Global Settings), this means that it is not connected to the Preferences popup as well, where it is usually linked, as shown here . In this case, feel free to reach our support team on apps-support@isenselabs.com or from the "We Are Here" button at the bottom right corner of your browser, and provide them with the Page ID. This way, they will be able to fix the linking for you in no time. Here is how you can find the Page ID - click here.

Also, if you are on a Premium plan, you can generate the Compliance pages automatically, by navigating to Global Settings > Generate Compliance Pages section, as shown below:

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 Bar tab Cookie Bar Behavior > Initial State Of The Cookie Consent Bar section. 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.

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>
    function addEventListenerForAcceptBtn() {
      if (window.isenseGDPR !== undefined && window.isenseGDPR.Cookies.get('cookieconsent_preferences_disabled') !== undefined) {
        window.addEventListener('click', function (e) {
          if(e.target && (e.target.className == 'cc-btn cc-btn-accept-all' || e.target.className == 'cc-btn cc-allow')){
			// ADD YOUR CODE HERE
          }
        });

      } else {
        setTimeout(function() {
          addEventListenerForAcceptBtn();
        }, 500);
      }
    }
    addEventListenerForAcceptBtn();
</script>

You can now proceed to add your code by replacing the line "// ADD YOUR CODE HERE". Once you have the whole snippet, including your code, you can follow the below steps so you can implement it in your store:

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. Copy the snippet and paste it after the <head> tag.

Note: The script will fire only if the Accept button on the Cookie bar, or the Accept All in the preferences pop up are clicked. If you are looking to have your function triggered in any other condition, you can reach our support team on apps-support@isenselabs.com or from the "We Are Here" button at the bottom right corner of your browser so they can look into this for you further.

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 last two mentioned are in a sense incomparable since the right to opt-out (CCPA) is best linked 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 Bar tab > Cookie Bar Behavior section, to set the app to be GDPR or CCPA compliant.

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

The LGPD requires that you tell customers:

• Explain that you collect personal data and specify what Information is being collected
• Specify what are your reasons for collecting it
• Inform people of their rights
• Explain how they can contact you to exercise those rights

The PIPEDA requirements are that:

• Organizations must state the purposes for data collection before or at the time of data collection
• Organizations must customize a privacy policy to describe their organization’s data handling practices to comply with the PIPEDA openness requirement.
• Organizations must honor users’ rights in accessing, reviewing, and correcting personal information.

The APPI main point for transparency is that:

• Companies looking to become APPI-compliant must ensure that they have a privacy policy that stipulates the purpose of using the collected information. They must apply cybersecurity measures and physical safeguards that guarantee the security of the personal information they process.

The VCDPA requirements include:

• Stating what categories of personal data are collected
• Obtaining affirmative consent for sensitive data before collecting it
• Providing an option for access and correct personal information.
• Providing opt-out mechanisms 
• Providing data protection assessments 
• Honor deletion requests
• Provide data breach notifications

After changing your theme you should not make any adjustments to the app itself, however, if you have added any of the below scripts in your theme.liquid file, you will have to apply them to your new theme's theme.liquid file as well.

These are the scripts that you should be aware of:

1. Translation -
   • Metafields - If you have added our app’s metafields code to the theme.liquid file of your old theme, in order to translate it, you will have to re-apply them again in the new theme. For more information on the metafields code and how it works, you can check section 71 of our FAQ page.
     Note: Our app has a specific metafields code for the translation done by GTranslate’s premium plan users that should be applied to the new theme’s theme.liquid file as well. More information on this case can be viewed in section 97 of our FAQ page.
   • Privacy Policy Links - The script for having different Privacy Policy links for every language on your store should be added to the theme.liquid file of the new theme as well. More information on that script can be found in section 108 of our FAQ page.
2. Blocking scripts - If any of our app’s blocking scripts have been added to the theme.liquid file of your old theme, then you will have to add them to the new theme’s theme.liquid file as well. You can find more information about our app’s blocking scripts in point 4 of our Guide on “How to be GDPR/CCPA compliant”.
3. Integrations - If your store is using any of our app’s scripts for integration with other services, they should also be added to the theme.liquid file of your new theme. Our app has integration scripts for Google Consent Mode, Rakuten, and Klaviyo.
   More information on the Google Consent Mode integration can be found in section 104 of our FAQ page, The integration for Rakuten in section 58, and the integration for Klaviyo in section 94.
4. Features - If you have applied the Cookie Bar Widget script to your old theme's code or the Cookie Preferences link to the footer of the old theme, make sure to also add them to the new theme. For more information on these scripts, you can check section 107 of our FAQ page for the Cookie Bar Widget script and section 11 for the Cookie Preferences link.
5. Custom JavaScript Trigger - Our app has a Trigger script that is used for triggering custom JavaScript functionality when the Cookie bar is accepted. If you have used this script in any of your old theme files, you should make sure to apply it to the new one as well in order to trigger that functionality when the Cookie bar is accepted. More information on that script can be found in section 27 of our FAQ page.

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 or from the "We Are Here" button at the bottom right corner of your browser.

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 the 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 from the "We Are Here" button at the bottom right corner of your browser or at apps-support@isenselabs.com.

Yes, you can do that from Global Settings > Enable For Specific Regions > Enable Only For California Visitors(CCPA) . When set this way, the Cookie bar will be visible only for the residents for whom the CCPA law applies to.

Congrats on upgrading! In order to reach the new settings, you simply have to navigate either to the Global Settings, Cookie Bar, Design or the Translation tab. Once you do that, keep scrolling until you reach the section with the features marked with the Premium Feature label as shown below:

From there, you will be able to access the following new settings:

• Generate new GDPR/CCPA/APPI pages
• Enable the bar for All Countries
• Reset all of your customer consent preferences

• Cookie Information Panel
• Cookie Scanner
• Cookie Information Table

• Position > Center or Center with Blocked Content
• 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
• Change the layout for the Cookie bar and Preferences popup

• Automatically Add metafields to theme.liquid file
• Set Language For The Compliance Pages
• Set Language For The Cookie Bar and the Preferences Pop-up

• Services Tracking - automated blocking scripts for tracking services

You can simply go to the Upgrade Plan tab, and scroll down to the bottom of the page where you will see the Free plan section. Click “Choose” in order to downgrade:

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

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

.cc-settings {display:none !important;}

This is possible. You only need to select "Yes" in the “Show Close Icon" option shown below:

Once this is done, you will have an “X” icon on the Cookie bar as well. This option can be accessed through the Design tab.

The behavior of the “X” icon can be set from the Cookie Bar tab > Cookie Bar Behavior section > “Action When the "Close/X Icon" is Clicked on the Cookie bar”

As you already may or may not know, you can apply CSS to different elements of the Cookie bar and the Preferences popup. This can be done in the Custom CSS section of the Design tab, as shown here:

Here is a list of the CSS selectors:

The colors of the checkboxes/switchers and the ticks can be configured from Design Settings > Checkbox Color & Checkbox Tick Color. Alternatively for the Classic and Modern layouts Design Settings > Switcher Inactive and Switcher Active.

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

Cookie bar:

.cc-window

.cc-settings-dialog

Example:

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

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.

More information on how the Cookie Scanner works you will be able to find in this video:

This feature is available under the Design tab > Email Template Settings field. Check the below reference:

This option is only available 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!

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.

You can navigate to this option from the Design tab > Email Template Settings field. Check the below reference:

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!

The pages are fully functional, however, if you are on the Free plan, you cannot change the design of the pages. The customization 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 add your store logo. In addition, you will also be able to add snippets of JavaScript codes (i.e. for analytics or something similar).

You can navigate to this option from the Design tab > Request Page Settings field. Check the below reference:

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!

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.

More information on how the Compliance pages work and what is their relation to the Request Emails and Request Pages, you will be able to find in this blog post article:

You can export the data from the Records tab > Policy Acceptance, Data Subject Requests, and Deletion Requests sections there. You will find the Export button above the results in each tab, along with the option to select the time frame for which you can download the stats, as shown here:



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

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 as a feature 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, before uninstalling you will have to remove all of our app’s scripts that you have applied to your theme’s files as well as the GDPR/CCPA Compliance pages that are automatically generated when you install our app.
The GDPR/CCPA Compliance pages can be located and deleted from Online Store > Pages section.
As for our app's scripts that might be applied to your theme, this is a list of the ones you should be aware of:

1. Translation -
   • Metafields - Our app’s metafields code should be removed from the theme.liquid file of your store's theme. For more information on the metafields code and how it looks like, you can check section 71 of our FAQ page.
     
   • Privacy Policy Links - The script for having different Privacy Policy links for every language on your store should be removed from your theme's theme.liquid file as well. More information on that script can be found in section 108 of our FAQ page.
2. Blocking scripts - If any of our app’s blocking scripts have been added to the theme.liquid file of your store's theme, then they should be removed as well. You can find more information about our app’s blocking scripts in point 4 of our guide on “How to be GDPR/CCPA compliant”.
3. Integrations - If your store is using any of our app’s scripts for integration with other services, they should also be removed from your theme's theme.liquid file. Our app has integration scripts for Google Consent Mode, Rakuten, and Klaviyo.
   More information on the Google Consent Mode integration can be found in section 104 of our FAQ page, The integration for Rakuten in section 58, and the integration for Klaviyo in section 94.
4. Features - If you have applied the Cookie Bar Widget script to your theme's theme.liquid file or the Cookie Preferences link to the theme's footer file, make sure to remove them since they won't work after uninstalling our app. For more information on these scripts, you can check section 107 of our FAQ page for the Cookie Bar Widget script and section 11 for the Cookie Preferences link.
5. Custom JavaScript Trigger - Our app has a Trigger script that is used for triggering custom JavaScript functionality when the Cookie bar is accepted. If you have applied that script to the theme.liquid file of your store's theme, you should make sure to remove it since it won't be triggered when our app is uninstalled. More information on that script can be found in section 27 of our FAQ page.

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.

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 or from the "We Are Here" button at the bottom right corner of your browser.

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 views 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 10 000 page views 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.

Lately, 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 4 plans with as follows: 

• Free Plan - up to 10k page views a month
• Standard Plan - from 10k - 30k page views a month
• Pro Plan (Most Popular) - from 30k - 100k page views a month
• Enterprise Plan - more than 100k page views a month

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

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

If you are looking to get a discounted price on our paid plans, you can check the annual payment options. You can do that from the Upgrade plan tab where you can easily switch between Monthly and Yearly views of the plans, as shown below:

The discounted annual prices are available for all of our paid plans, as you can also see in the screenshot below:

• If you enroll to the Annual Standard plan, you will save $10 as opposed to what you will pay in total if you are paying monthly.
• If you enroll to the Annual Pro plan, you will save $20 as opposed to what you will pay in total if you are paying monthly.
• If you enroll to the Annual Enterprise plan, you will save $30 as opposed to what you will pay in total if you are paying monthly.

NOTE: If you have any issues when upgrading the plan, please make sure your Shopify account has all the permissions to make this change. You can check this with the admin of the store directly. Below, you can find an example of the page you might be redirected to if you don't have the needed permissions:

In need of further assistance, you can reach our support team on apps-support@isenselabs.com or from the "We Are Here" button at the bottom right corner of your browser.

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, NO and LT. If your store is multilingual, our app will automatically detect the language in which the customer is currently viewing the store, and it will translate the requests and the emails in the corresponding language. This is only for the Paid plans. 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 of 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, Translation Lab, Transcy and Langshop.

For more information on the relation between the GDPR/CCPA Compliance pages and the Request Emails and Request Pages, please check the following article.

This new feature is located in the Cookie Bar tab under the Cookies Management section and it is only available to the Premium Plans (Standard, Pro and Enterprise) Here is how it looks like: 

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:

- 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:

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:

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:

More information on how the Cookie Information Panel works you will be able to find in this video:

The option to Show the Reject button in the Cookie bar can now be found under the Design Settings tab right under the “Font Size” option as shown here:

In addition, you can also check FAQ “37. Can I have an “X” icon on the Cookie bar?”

Upon clicking the Accept ALL button your visitors will accept all cookies no matter what the Initial State Of The Cookie 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 “Save my choice” button. No matter which of the two buttons you click, after this action is done both the Preferences popup and the Cookie bar will be closed.

If you are running any of our paid plans, you will have the option to show an additional button in the Preferences popup, which is “Reject All”, and is available for the Classic and the Modern layouts, which you can check in the Design tab, as shown here.

Preview:

Classic:

Modern:

Note: The button is set by default to reject all cookie groups, except for the necessary ones, regardless of the initial state of the cookie bar and the selection made in the Preferences popup. This can not be configured.

If you want the Accept button in the Cookie 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 Cookie Bar Behavior section set the option for the “Regard the Initial State Of The Cookie Consent Bar for the 'Accept' button” to “No”, so it could work as the one in the Preferences popup.

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

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.

In order to see the Cookie 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 Bar section.

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

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

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

In order to blur out the page until the customer gives his consent, please paste the following CSS code in Design > Custom CSS:

.cc-window {
    width: 100%!important;
    -ms-flex-direction: row!important;
    flex-direction: row!important;
    height: 100%;
    display: flex;
    justify-content: center;
    align-items: center!important;
    padding: 0 25%!important;
    border-radius: 5px;
    background-color: rgba(0,0,0,.6)!important;
}
.cc-window .cc-btn.cc-allow {
    min-width: 100px;
}
.cc-window.cc-close-icon .cookieconsent-wrapper, .cc-window.cc-close-icon .cookieconsent-wrapper {
    position: relative;
}
.cookieconsent-wrapper {
    background: black; /* SET CONSENT BAR BACKGROUND COLOR HERE */
    border-radius: 5px;
    margin-right: 0px!important;
    padding: 20px 35px 20px 20px;
}
/* tablet, landscape iPad, lo-res laptops ands desktops */ 
@media (max-width: 875px) {
div.cc-window {
    padding: 5%!important;
 }
}
 /* smartphones, Android phones, landscape iPhone */
@media (max-width: 400px) {
div.cc-window.cc-default .cc-compliance {
    flex-direction: column;
}
div.cc-window.cc-default .cc-compliance button {
    width: 100%;
    margin-bottom: 0.5em;
    margin-left: 0;
 }
}

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

If you want the Cookie bar to be showing on the bottom or on top of the website when the content is blurred out, you can use the codes in the text files below.

Note: This codes applies only to the Default layout. If you use any of the other layouts you can blur the content by editing the position to "Center Blocked Content" in the Design tab > Position section.

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();

document.addEventListener("DOMContentLoaded", function() {

document.addEventListener("click", function(e){
    if(e.target.classList.contains("cc-allow") || e.target.classList.contains("cc-btn-accept-all") || e.target.classList.contains("cc-btn-accept-selected")){
        rakConsent();
    }
})
})
}()
</script>

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-CPRA/VCDPA/APPI/PIPEDA 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:

• If your bar is set to show only for EU/EEA Visitors (GDPR) + Brazil (LGPD) the link will redirect to your GDPR Compliance page.
• If your bar is set to show only for California Visitors (CCPA-CPRA) the link will redirect to your CCPA-CPRA Compliance page.
• If your bar is set to show only for Canada Visitors (PIPEDA) the link will redirect to your PIPEDA Compliance page.
• If your bar is set to show only for Japan Visitors (APPI) the link will redirect to your APPI Compliance page.
• If your bar is set to show only for Virginia Visitors (VCDPA) the link will redirect to your VCDPA Compliance page.
• If your bar is set to show for all the regions available for the Free Plan users - EU/EEA + Brazil, California, Virginia, Canada and Japan, the link will redirect to the respective page as per the visitor's location.
• If your bar is set to show for All Countries, and a visitor from a region, different from the ones listed above, the link will redirect to your GDPR Compliance page.

NOTE: If you do not have any of the compliance pages generated, the link will redirect to our app's Privacy Policy & Terms of Service.

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 Translation tab, or if your store has set up metafields, it will work with them as well.

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

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

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

<a aria-label="learn more about cookies link (opens in a new tab)" class="cc-link" href="{{ URL }}" rel="noopener noreferrer nofollow" target="_blank">{{ TEXT }}</a>

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 >and in the section for “Choose when marketing and analytics data is collected for customers from the EU, EEA, UK, and Switzerland:” you can select one of the available options, as shown below:

Check the description for each option and select the one that is most suitable for your store.
The recommended “Collected after consent” option is the one you can select in order to have the Shopify’s and our app’s settings fully integrated with each other and have tracking on visitors corresponding to their consent.

Note: If you have Google tracking services added through Shopify's Online Store > Preferences, you need to tick the option for "Use Enhanced Ecommerce", in order for them to be blocked before consent, as shown below:

There you can also find the one that is for “Limit data collection for California buyers”.

If you have any difficulties activating the limit data collection for California buyers you can also check our FAQ question 98. Why I can not activate the Limit data collection for California buyers?

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

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 Bar tab > Cookie Bar Behavior section > 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 Bar tab > Cookie Bar Behavior section as well.
3. Rename your current Accept button. An example would be: "Accept only necessary cookies". You can do this from Cookie Bar tab > Cookie Bar Content section > Accept Button Text field.

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.

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.

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

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 Cookie 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.

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.

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 Bar tab> Cookies Management section, 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?

Shopify currently has the options to limit the tracking of data for customers from EU, EEA, UK and Switzerland(GDPR) and customers from the state of California (CCPA) by enabling the two options, which you can find in Online Store -> Preferences -> Customer Privacy and also a guide on how this can be done is available in our FAQ 62. 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.

In the app settings, locate the Translation tab. There you will see the options for changing the language for all the elements of our app, like Cookie Bar & Preferences popup, Language for the Data Collection text, GDPR/CCPA Request pages and emails, and the GDPR and APPI Compliance pages as well. There you can also find the options for 'Refresh Metafields', 'Add metafields to theme.liquid' and 'Remove metafields from theme.liquid', as shown in the screenshot below:

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.
   It is also recommended to press this button after making any change to the text content of the Cookie bar or the Preferences popup.
2. Add metafields to theme.liquid - this button will add the necessary code, in order for our app to work correctly with the 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.
3. Remove metafields from theme.liquid - this button will remove the metafields code from the theme.liquid file of the store. That is recommended at the time of uninstallation of the app, in order to avoid having any leftover scripts and code in the store files.

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

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

1. Navigate to your theme.liquid file. You can do this by going to Online Store > Themes > Actions > Edit code > theme.liquid.
2. Locate the opening <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.

Below, you can check how the exact process works:

If you need help with the applying the code, don’t hesitate to contact our support team at: apps-support@isenselabs.com or from the "We Are Here" button at the bottom right corner of your browser.

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

In order to change the font family or the font size of the Cookie bar & Preferences popup, you would need to navigate to the Design 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:

After:

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

In order for you to set a Reject button, which upon clicking will block all of the cookie groups, you would need to navigate to the Design tab > Show Reject Button option, as shown below:

The text in the button can be changed from the Cookie Bar tab > Cookie Bar Content section > Reject Button text field:

Note: The button is set by default to reject all cookie groups, except for the necessary ones, regardless of the initial state of the cookie bar. This can not be configured. If you like to have an option you can configure, you can refer to our FAQ “37. Can I have an “X” icon on the Cookie bar?”

First, you will need to add a Reject All button in the Cookie bar. Please follow the steps in FAQ 74.How to set up a Reject button on the Cookie bar?.

Secondly, you should set up an Accept All button. In order to make the Accept button in the Cookie bar to act like an Accept All button, you will simply need to rename the button from Accept > Accept All. Then for the option “Regard the Initial State Of The Cookie Consent Bar for the 'Accept' button”, select "NO", so it could work as the one in the Preferences popup.

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 Bar tab:

Additional description for the cookie categories in the Cookie Bar Content section:

Additional description for each specific cookie in Cookies Management section > Cookie Information panel:

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

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.

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

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;
        }

Copy

Result:

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 or from the "We Are Here" button at the bottom right corner of your browser.

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

1. With Metafields

• Follow the instructions from question #71.
• Once you have completed the steps there, the texts of the app should be visible in Langify's Metafields section:

2. By adding the texts manually in the Custom Content section

• Navigate to Langify > Custom and press Global

• Add the corresponding texts of the Cookie bar and the Preferences popup from here:

You can follow our short guide below for your reference.

1. You can start by adding our app's metafields to your theme.liquid files by following the instructions in our FAQ Section"71. How to translate the app by using metafields?"

2. Once the metafields are added, you must navigate to the app settings and refresh them from the Translation tab > "Refresh Metafields" button, as shown below:

3. You can then navigate to the Translate & Adapt app > Localized content > "Auto-translate" button. The translation process will take several minutes or hours, depending on your store's content. Please check the image below for your reference:

4. If you want to translate only the content of our app, you can navigate to the Translate & Adapt app > Store Metadata section and select Edit. There you will be able to see and translate only the content of the Cookie bar and Preferences popup. As shown in the reference below, there is an option for manual and auto-translation as well:

5. In order to ensure that the translations are applied correctly, you would need to use our "Refresh Metafields" option again.

6. Lastly, you can add the Language switcher by adding a menu button to your store's Footer/Main Menu section, for each language. Below, you can check a reference of how the exact process works:

If you're having difficulty with the translation process, don't hesitate to contact our support team at: apps-support@isenselabs.com or from the "We Are Here" button at the bottom right corner of your browser.

If you are not located in any of the regions the app can be enabled for (GDPR, LGPD, CCPA, PIPEDA, APPI) the only way for you to test/try out the app and see the Cookie bar on your storefront (without making it live for your website 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):

Note: No page views are generated when the app is set to Admin Mode, either by the admin of the store during the time of testing or by any visitors that may be viewing the store, at this time.

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?

If you are running any of our paid plans, you have the option to set a Reject All button in the Preferences popup by changing the Cookie bar layout to either Classic or Modern from the Design tab, as shown here:

Below you can see an example of how the layouts look with the reject button added as an option:

Preview:

Classic:

Modern:

The text in the button can be changed from the Cookie Bar tab > Cookie Bar Content section > Reject All Button Text field:

Note: The button is set by default to reject all cookie groups, except for the necessary ones, regardless of the initial state of the cookie bar and the selection made in the Preferences popup. This can not be configured.

If you are using the Default layout for the Cookie bar in your store, and want to have a Reject/Reject All option, available for your visitors, we would recommend having a look at our FAQ section "74. How to set up a Reject button on the Cookie bar?"

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.

In order to make the Cookie bar and the Preferences popup smaller you should apply the following CSS code in Design > 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 .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:

Cookie bar on desktop device:

Smaller Cookie bar on desktop device:

Cookie bar on mobile device:

Smaller Cookie bar on mobile device:

If you require an even smaller Cookie bar after applying the modifications, feel free to contact our support team at apps-support@isenselabs.com or from the "We Are Here" button at the bottom right corner of your browser.

You will need to navigate to the Cookie Bar tab > Cookies Management section in the admin side of the app and go to the Cookie Categories. There you will be able do directly click and add/remove/edit any cookie you want. Please check the attached screenshot:

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.

If the buttons on the Preferences popup are not accessible, feel free to apply the following code below in Design > 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.

In order to modify the stylings of the cookie categories' descriptions, you will need to navigate to the Design 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, 
.cc-settings-dialog.classic .cookie-settings-section-paragraph {
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:

Note: The individual selectors given below apply only for the Default and Modern layout.

1. Strictly Required cookie category styling:

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

   Copy

2. Reporting and Analytics cookie category styling:

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

   Copy

3. Marketing And Retargeting cookie category styling:

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

   Copy

4. Functional cookie category styling:

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

   Copy

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

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.

You can do this from the app settings, by clicking on the Enable option in the banner available once you access the app dashboard. From there, once redirected to the theme settings you will be able to enable the option and save the changes, as shown below:

Below are the steps that you would need to follow if you do it from the store admin dashboard:

1. Navigate to Online Store -> Themes
2. Press the Customize button of your current live theme
3. Navigate to App embeds icon on the left of the screen and click on it
4. Locate the GDPR Consent Bar and turn on the app embed.
5. Save the settings
6. That's it!

A reference on this process can be checked below as well:

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.

• The current CCPA Page link. You can access this link as shown below and copy it, as it is in the browser https://your_store_url.com/pages/ccpa-compliance
  
• The selection code for the section ?id=do-not-sell

In order to translate the content of the Cookie 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.

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>":

<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>

Copy
7. Click on the "Save" button.

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.

Once you’ve successfully added the script, you need to add the Klaviyo cookie __kla_id into our app by navigating to Cookie Bar tab > Cookies Management section.

• If you are a paid plan user, you can add the cookie from the Cookie Information Panel, as shown below:



• For free users, you may add the cookie directly to the Cookie Categories, as shown below:

If you have any questions, don't hesitate to contact our support team at: apps-support@isenselabs.com or from the "We Are Here" button at the bottom right corner of your browser.

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

.cc-window {
    width: 100%!important;
    -ms-flex-direction: row!important;
    flex-direction: row!important;
    height: 100%;
    display: flex;
    justify-content: center;
    align-items: center!important;
    padding: 0 25%!important;
    border-radius: 5px;
    background-color: rgba(0, 0, 0, 0) !important;
}
.cc-window .cc-btn.cc-allow {
    min-width: 100px;
}
.cc-window.cc-close-icon .cookieconsent-wrapper, .cc-window.cc-close-icon .cookieconsent-wrapper {
    position: relative;
   }
.cookieconsent-wrapper {
    background: black; /* SET CONSENT BAR BACKGROUND COLOR HERE */
    border-radius: 5px;
    margin-right: 0px!important;
    padding: 20px 35px 20px 20px;
}
/* tablet, landscape iPad, lo-res laptops ands desktops */ 
@media (max-width: 875px) {
div.cc-window {
    padding: 5%!important;
 }
}
 /* smartphones, Android phones, landscape iPhone */
@media (max-width: 400px) {
div.cc-window.cc-default .cc-compliance {
    flex-direction: column;
}
div.cc-window.cc-default .cc-compliance button {
    width: 100%;
    margin-bottom: 0.5em;
    margin-left: 0;
 }
}

Preview:

With Reject button:



Mobile view:

Without Reject button:
(Can be configured from Design tab > Show Reject Button)

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

If you like to have the Cookie bar in the middle of the screen with the content blurred out as well, you can check the following FAQ: "57. How to blur out the store's pages until the customer gives his consent?"

Note: This codes applies only to the Default layout. If you use any of the other layouts you can blur the content by editing the position to "Center Blocked Content" in the Design tab > Position section.

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!

You can check how this can be done in our FAQ question 90. How to activate the consent bar to load via app embed block? .

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.

If you are using a premium version of the GTranslate app for translation, you will need to do an additional configuration on your end in order to make it work with our GDPR/CCPA app. Below you will find instructions on what exactly you would need to do:

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>":

{%- assign privacy_policy_text = shop.metafields.consentbar_text["privacy_policy_text"] -%}
  {%- assign accept_button_text = shop.metafields.consentbar_text["accept_button_text"] -%}
  {%- assign change_cookies_text = shop.metafields.consentbar_text["change_cookies_text"] -%}
  {%- assign text = shop.metafields.consentbar_text["text"] -%}
  {%- assign strict_cookies_checkbox = shop.metafields.preferences_text["strict_cookies_checkbox"] -%}
  {%- assign strict_cookies_text = shop.metafields.preferences_text["strict_cookies_text"] -%}
  {%- assign analytics_cookies_checkbox = shop.metafields.preferences_text["analytics_cookies_checkbox"] -%}
  {%- assign analytics_cookies_text = shop.metafields.preferences_text["analytics_cookies_text"] -%}
  {%- assign marketing_cookies_checkbox = shop.metafields.preferences_text["marketing_cookies_checkbox"] -%}
  {%- assign marketing_cookies_text = shop.metafields.preferences_text["marketing_cookies_text"] -%}
  {%- assign functionality_cookies_checkbox = shop.metafields.preferences_text["functionality_cookies_checkbox"] -%}
  {%- assign functionality_cookies_text = shop.metafields.preferences_text["functionality_cookies_text"] -%}
  {%- assign popup_header = shop.metafields.preferences_text["popup_header"] -%}
  {%- assign dismiss_button_text = shop.metafields.preferences_text["dismiss_button_text"] -%}
  {%- assign accept_selected_button_text = shop.metafields.preferences_text["accept_selected_button_text"] -%}
  {%- assign accept_all_button_text = shop.metafields.preferences_text["accept_all_button_text"] -%}
  {%- assign data_collection_text = shop.metafields.preferences_text["data_collection_text"] -%}

  <script type="text/javascript">
    var final_JSON = { 
      "all_txt": {
        "privacy_policy_text": "{{ privacy_policy_text | replace: '"' , '\"' }}",
        "accept_button_text": "{{ accept_button_text | replace: '"' , '\"' }}",
        "change_cookies_text": "{{ change_cookies_text | replace: '"' , '\"' }}",
        "text": "{{ text | replace: '"' , '\"' }}",
        "strict_cookies_checkbox": "{{ strict_cookies_checkbox | replace: '"' , '\"' }}",
        "strict_cookies_text": "{{ strict_cookies_text | replace: '"' , '\"' }}",
        "analytics_cookies_checkbox": "{{ analytics_cookies_checkbox | replace: '"' , '\"' }}",
        "analytics_cookies_text": "{{ analytics_cookies_text | replace: '"' , '\"' }}",
        "marketing_cookies_checkbox": "{{ marketing_cookies_checkbox | replace: '"' , '\"' }}",
        "marketing_cookies_text": "{{ marketing_cookies_text | replace: '"' , '\"' }}",
        "functionality_cookies_checkbox": "{{ functionality_cookies_checkbox | replace: '"' , '\"' }}",
        "functionality_cookies_text": "{{ functionality_cookies_text | replace: '"' , '\"' }}",
        "popup_header": "{{ popup_header | replace: '"' , '\"' }}",
        "dismiss_button_text": "{{ dismiss_button_text | replace: '"' , '\"' }}",
        "accept_selected_button_text": "{{ accept_selected_button_text | replace: '"' , '\"' }}",
        "accept_all_button_text": "{{ accept_all_button_text | replace: '"' , '\"' }}",
        "data_collection_text": "{{ data_collection_text | replace: '"' , '\"' }}",
        "gt_translate_keys":[{"key":"data_collection_text","format":"html"},
"privacy_policy_text",
"accept_button_text",
"text",
"strict_cookies_checkbox",
"strict_cookies_text",
"analytics_cookies_checkbox",
"analytics_cookies_text",
"marketing_cookies_checkbox",
"marketing_cookies_text",
"functionality_cookies_checkbox",
"functionality_cookies_text",
"popup_header",
"dismiss_button_text","accept_selected_button_text","accept_all_button_text"]
      
      }
    };
    
    window.isense_gdpr_privacy_policy_text = final_JSON.all_txt.privacy_policy_text;
    window.isense_gdpr_accept_button_text = final_JSON.all_txt.accept_button_text;
    window.isense_gdpr_change_cookies_text = final_JSON.all_txt.change_cookies_text;
    window.isense_gdpr_text = final_JSON.all_txt.text;
    window.isense_gdpr_strict_cookies_checkbox = final_JSON.all_txt.strict_cookies_checkbox;
    window.isense_gdpr_strict_cookies_text = final_JSON.all_txt.strict_cookies_text;
    window.isense_gdpr_analytics_cookies_checkbox = final_JSON.all_txt.analytics_cookies_checkbox;
    window.isense_gdpr_analytics_cookies_text = final_JSON.all_txt.analytics_cookies_text;
    window.isense_gdpr_marketing_cookies_checkbox = final_JSON.all_txt.marketing_cookies_checkbox;
    window.isense_gdpr_marketing_cookies_text = final_JSON.all_txt.marketing_cookies_text;
    window.isense_gdpr_functionality_cookies_checkbox = final_JSON.all_txt.functionality_cookies_checkbox;
    window.isense_gdpr_functionality_cookies_text = final_JSON.all_txt.functionality_cookies_text;
    window.isense_gdpr_popup_header = final_JSON.all_txt.popup_header;
    window.isense_gdpr_dismiss_button_text = final_JSON.all_txt.dismiss_button_text;
    window.isense_gdpr_accept_selected_button_text = final_JSON.all_txt.accept_selected_button_text;
    window.isense_gdpr_accept_all_button_text = final_JSON.all_txt.accept_all_button_text;
    window.isense_gdpr_data_collection_text = final_JSON.all_txt.data_collection_text;
</script>

Once you have added the code, all of the contents of the app should be translatable with the premium version of GTranslate.

The option "Limit data collection for California buyers" cannot be enabled for any cookie management app (including ours) since Shopify removed the integration with that option and enabled it only for their cookie management app (the Customer Privacy app). Nevertheless, if you have followed our guide on How to be GDPR/CCPA compliant your store will still meet the requirements for the CCPA compliance law.

If you are looking to have the option activated anyway, here are the steps you need to follow in order to achieve this.

1. Navigate to the Online Store > Preferences > Customer privacy. Click Activate for the option on “Limit data collection for California buyers” and select Install Customer Privacy app.

2. Once you finish with the installation, in the app settings you can navigate to the “Add CCPA information page for California customers” section, as shown here and click on Start Setup.

3. Add the Opt Out page and the navigation link leading to it (as per your preferences) as shown below:

4. Click the “Activate” button on the top right corner of the app settings.

Once you have it set up, you can navigate to the Online Store > Pages and find the “Do not sell my personal information” page that the Shopify’s Customer Privacy app generated and delete it (as you already have this option in your CCPA compliance page generated by our app).

In order to avoid the interference between the features of the two cookie apps you will need to delete the Shopify Customer Privacy app from the app list.

NOTE: The option for the “Limit data collection for California buyers” will stay activated even after removing the Shopify’s Customer Privacy app.

We know that this is a deranged procedure to follow but this is the only workaround available at this moment for activating the Limit data collection for California buyers. We are working with Shopify in order for them to enable again this option for all other apps that may need to use it.

Note that this restriction does not affect the Limit data collection for European buyers option, which means that it is still compatible with our app and can be integrated properly with any cookie management apps.

If the Cookie bar and the Preferences popup are not translated by the translation app - Weglot, you should set them to be translated dynamically, which is an option provided by Weglot.

In order to do that, navigate to Weglot’s Settings page, open the Shopify Settings tab and add the CSS selectors .cc-window (for the Cookie bar) and .cc-settings-dialog (for the Preferences popup) using the Add Dynamic option. Check below screenshot reference:

For more information on translating dynamic content with Weglot, you can check their Guide Page

If the issue persists after applying the CSS selectors to the Dynamic Elements section, you can try to add the .cc-banner selector as well, and then remove it. Adding and removing the .cc-banner will refresh the detection of the elements in the translation app. As a final result, again only the ".cc-settings-dialog" and ".cc-window" should be left in the dynamic translation.

In need of further asssitanc, you can reach our support team on apps-support@isenselabs.com or from the "We Are Here" button at the bottom right corner of your browser.

By default, you can choose to enable or disable the feature of getting notification emails when customers submit GDPR/CCPA/APPI Account Edit, Deletion or a "Do Not Sell Rule" requests. This feature is accessible through the Global Settings tab, under the field Receive An Email When Account Deletion or Edit Request Is Submitted as shown here:

When this feature is enabled, the notification emails will be sent by default to your Shopify store owner email. In order to set a custom email for receiving these notifications, you can add the email of your preference to the field named Add Custom Email Address To Receive Data Deletion/Edit Request Notifications as shown here:

With the checkboxes underneath, you can choose to either receive all notifications to this new email (for Account Edit, Deletion, Do Not Sell) or only one of them, depending on your preferences. If you choose only one, the other types of requests will be sent to the admin email as it is by default.

The Cookie bar tab in the app settings was updated and is now separated into three sections, which are Cookie Bar Content, Cookie Bar Behavior, and Cookies Management.

In each section you can find the following options:

Cookie Bar Content:

• Editable text fields for the Cookie bar and Preferences popup, in which the content can be changed in accordance with the store’s needs like direct translation of the fields or any specific piece of text related to your privacy policy, on which you like to notify your visitors.

Cookie Bar Behavior:

• Option to set the initial state of the cookies in your store which will apply to all visitors when they access your store for the first time.
• Configure the behavior of the buttons (Accept and Close) in the Cookie bar.

Cookies Management:

• The Cookie Categories section is available to all free users. From there you can add or remove cookies in each category manually - directly through the list.
• The Cookie Information Panel section is available for the paid users where they can edit each of the cookies, change the category they are added to and also add/edit their description.
• The Cookie Scanner section is available for our premium plan users. It simply shows all of the cookies, that are present in your store, when a customer visits the store for the first time.
• The Cookie Information Table section is available for our premium plan users as well. It gives the option to get a table with all the cookies set in your store, divided by categories, which can be added either to a separate page of your store (i.e. a Cookie Information page) or as an addition to an existing one. This is all explained in our FAQ “118. How does the Cookie Information Table feature works?”

Once the consent bar is enabled, our app will set the consent_status event within the dataLayer object in your store. Once this event is set, you will be able to access real-time information about which cookie groups has the customer given his consent for. I.e., if a customer has opted-in for all of the cookie groups, all of the categories within the event will be set to true. Here is an example:

analytics: true
functionality: true
marketing: true
necessary: true

The easiest way to access this is by navigating to your store > Open the Inspector tools > Console > type dataLayer.

You can use this information within your Google Tag Manager to set specific events based on the information that the dataLayer contains.

Note: If you have set the consent bar to show for the customers that are browsing for the EU & Brazil only, and a customer browses from another country that is not part of the EU nor Brazil, you will see the consent_status event set to non_gdpr which would mean that the customer is browsing from a country outside of the EU & Brazil.

When a customer submits a deletion request through the GDPR/CCPA Compliance pages and afterward confirms it via email, the request will be logged in the app's Records tab > Deletion Requests section tab, reference:

Note that our app does not delete any customer information for a client's account on your store automatically. The logged deletion requests are for your reference only. Once a customer submits the deletion request, you would need to navigate to the Customers section of your Shopify store, locate the customer and submit a request for erasing personal information as shown here:

Once you press this button, you will request the erasing of the personal data for this particular customer from Shopify. That personal data includes the customer's name, address, email, IP, credit card number and account. Note that it will take a few days for Shopify to completely delete all information in regard to this customer, and they will decline the request if the customer has made an order in the last 6 months (180 days), in case a chargeback occurs.

Note: Only the store owner or a staff member with the Erase customer personal data permission can request a customer's data to be erased. If you are not the store owner and do not have the required permission, the Erase personal data button will be missing from the page.

Automatic integration with Google Consent Mode

Google Consent Mode can be integrated automatically by opening our app's settings and navigating to Integrations tab > Service Tracking page > Google Consent Mode and clicking on the Enable button.

Note: This option is only available for the merchants that have upgraded to a Premium plan (Standard, Pro or Enterprise).
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!

Manual integration with Google Consent Mode

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. Locate the Assets folder and click on it in order to expand it. After that, click on Add a new asset and upload the file isense-gcm-blocking-script.js provided under this step.

<script src="{{ 'isense-gcm-blocking-script.js' | asset_url }}"></script>

Once this is done, the integration of the Google Consent Mode with our app will be successfully set in your store. If you want to test if the integration was successful, please check question #105.

For further information on how our app works with Google Consent Mode, continue reading the text below:

Google Consent mode has two variants.

1. There are the default settings that the page will use while waiting for the user’s consent status to be given.
   When your customers visit your store, the integration we provided will initially run the default settings and populate the ad_storage and analytics_storage in the dataLayer to granted or denied depending on how the option Initial State Of The Cookie Bar is set.
   Note that the services will be blocked, but the services' tags will be fired. This is not an issue and it is how Google Consent Mode works.
2. Then there are the update settings that are sent as soon as consent has been given.
   After that, when your store visitor gives his consent by accepting the Cookie bar, the updated settings will set ad_storage and analytics_storage to granted or denied depending on which cookie categories the visitor chooses to block. If no cookie categories are blocked, Google Tag Manager will unblock the services by setting their cookies to the visitor's browser.

Note also that the services that have built-in consent checks are Google Analytics, Google Analytics 4, Google Ads, Google Floodlight, and more.

In order to test if the Google Consent Mode is set properly you should first clear your browser's cookies or open your store through incognito mode and follow those steps:

1. Start off by checking if Google Tag Manager's tags are fired initially, before the Cookie bar is accepted. In order to check if the tags are fired, you can either use Google Tag Manager's preview mode, or if you don't have access to Google Tag Manager use the Google Tag Assistant browser extension which you can download from here.
2. After that you should make sure that the ad_storage and analytics_storage are properly set to denied in the dataLayer. In order to do that, you can simply write dataLayer in the console and check if the first entry is:

   {"consent","default",{"ad_storage":"denied","analytics_storage":"denied"}}
   

3. After making sure that the dataLayer is properly set, you should check your store's cookies since the cookies _ga, _gid, and _gat should not be set before the Cookie bar is accepted. Note that if any of the cookies are set, then you are likely adding them through an inline script, like analytics.js (which doesn't support Google Consent Mode). In order to properly check which cookies are set to your store, we recommend using the EditThisCookies browser extension, which you can download from here.
4. Lastly, you should give your consent by accepting the Cookie bar and making sure that the Marketing and Analytics cookie categories are not blocked. After accepting it, you will have to check if the cookies that we mentioned in step 3 (_ga, _gid, and _gat) are set to your store and also if the ad_storage and analytics_storage are set to granted in the dataLayer as shown in this image:
   
   If the cookies and the update settings in the dataLayer are set then the Google Consent Mode should be working properly.

If every step of the testing is successful but you are not getting the data you are expecting, unfortunately, we can't provide any further help in this regard.

Google Consent Mode is essentially an API which we use to pass consent data to Google Tag Manager. How a tag is supposed to respond to this data is beyond our purview. We can, and will be happy to check if you have correctly set things up in regards to our app's sending, and Google Tag Manager's receiving of consent settings. However, we have no insight in what tags do with these settings. We can't comment on how Google Analytics should behave when it receives the Google Consent Mode instructions, or speak on Google's behalf in regards to what data should be logged. This may seem dismissive, but there's nothing we can do on our end to improve the data logging in Google Analytics. Our app's scripts merely respectively set and update the consent state to Google Tag Manager.

For more information on Google Consent Mode and the behavior of tags, you can check Google's own documentation on Consent Mode from here.

Starting from the 10th of January, 2022 the Italian Garante requires that all websites comply with the newly published regulations for the GDPR Garante’s privacy. By default our app complies with most of the requirements, however, there are specific settings you should be aware of in order to configure the app as per the regulation. Let’s go through the steps one by one:

1. Make sure to add your store's Privacy Policy link.

After you have generated your Privacy Policy page, make sure to properly link it in the Privacy Policy Link field under the Cookie Bar tab > Cookie Bar Content secton as shown in the screenshot below:

2. Add cookie information.

You can add general information regarding the cookies under the Cookie Bar tab > Cookie Bar Content section > Cookie Consent Popup Header Description field. There you can describe the consent time validity (which must be more than 6 months) and any specific information valid for your local compliance.
You can check the location of the Cookie Consent Popup Header Description text box in this screenshot:

Also, make sure to add a cookie description for each individual cookie. In order to do so, you can use the Cookie Information Panel also located in the Cookie Bar tab > Cookies Management section, as shown below:

More information on how to locate and use the Cookie Information Panel you can find in this FAQ: 50. How does the Cookie Information Panel work and what does each field do? You can also check this video:

Additionally, we have set up default cookie categories descriptions, but if you need to edit/add more to them, you can do so under the Cookie Bar tab > Cookie Bar Content section > Strict Cookies Description, Analytics Cookies Description, Marketing Cookies Description, and Functional Cookies Description.

3. Provide a way for the customers to withdraw their consent.

You should add an update cookie preferences button or link. For more information on how to set this up, please check this FAQ: 11. Is there a way to show the Preferences Popup after a visitor has already accepted the cookies? There, you will also find a detailed and helpful video guide about how and where to implement the required code.
You can also check our latest solution on this in our FAQ question 107. How to add a Cookie Bar Widget to the bottom of the page?

4. Make sure the initial state of the Cookie bar is set to: Block all cookies unless for the strictly required ones.

The initial state of the app must be "blocked" for all cookie categories (marketing, analytics, and functional). In order to do so, you must locate the Initial State Of The Cookie Consent Bar setting in the Cookie Bar tab > Cookie Bar Behavior section and block all cookie categories as shown here:

5. Configure the Reject Button in the Cookie bar.

You will need to start by making sure that the Reject Button is enabled. You can check this FAQ for more information on how to do that: “74. How to set up a Reject button on the Cookie bar?”

Next, you should change the text of the Reject button to: “Continue without agreeing”. You can do so from the Cookie Bar tab > Cookie Bar Content section > Reject Button Text field, as shown in the screenshot below:

6. Clear Cookie bar design.

Choose one of the default designs of the app upon installation, and be mindful of the user's ability to read the Cookie Bar and the Preferences Popup’s content when you change the style options and when adding CSS code changes. The Cookie Bar and the Preferences Popup must be clear and visible at all times. Remember that no "cookie walls" are allowed.

Note: Our app is compliant with the Web AIM checklist.

In order to add a Cookie bar widget to the bottom left corner of the store’s page that will let the customer change their cookie preferences at any time, you should insert the scrip below, right before the closing </body> tag of the theme.liquid file as shown in this screenshot:

After adding the script from the file, the Cookie bar widget should appear at the bottom left corner of your store, as it is shown in this example:

The Cookie bar widget script:

In order to set a different Privacy Policy link for each language that your store is translated in, you should follow these steps:

1. Apply the script from the file provided below to the head HTML element in your store’s theme.liquid file.
   
2. Add an object in the variable privacyPolicyLinksTranslations for every language that you want to have a different Privacy Policy link for.
3. Add a key to each of the objects called language with a value of the ISO code of the language.
   *For a full list of the ISO language codes, you can check this link.
4. Add another key to each of the objects called link with a value of the Privacy Policy link you use for your store when it is translated to the corresponding language.
5. Save the changes.

After following these steps the script should look as the example shown in the screenshot provided below but with the languages and Privacy Policy links that your store uses:

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 or from the "We Are Here" button at the bottom right corner of your browser.

While checking your store for cookies in order to see which of them are currently allowed or blocked, you might notice that part of Shopify's default Analytics cookies are not blocked, even if you have opted out of the Analytics cookie group. The reason for this is most likely that in some of the requests that are being executed on your store, those cookies that are part of Shopify's Analytics suite, are set again as soon as the request is executed. The most common example is with the Cart Shopify API, which sets these cookies each time:

If you have a third-party application that might be using this or another Shopify service, then those cookies can be set multiple times on the page.

At the moment, our app is able to block those cookies only once, after that they will be set again from this or оther request. The app does not block those cookies multiple times because this might interfere with the overall Shopify Analytics on your store.

We have contacted Shopify multiple times regarding this however, they do not provide any information for this behavior, they have only advised us to not delete those cookies multiple times because of the reason mentioned above. Also, they have notified us recently that this topic is part of their 2022 roadmap, so they would notify us when they could provide additional information in regard to this and how to proceed further.

In order to translate our the Cookie bar by importing a CSV file containing the translations, please follow these steps:

1. Apply our app’s metafields code by following the instructions shown in section 71 of our FAQ page.
   Note: Make sure to Refresh the metafields after adding them as it is mentioned in section 71 before you proceed to the next step.
2. Go to your Shopify Admin.
3. Open your store’s settings by clicking on the Settings button on the bottom left side of the screen.
4. A new page will open with a list of the sections for your store’s settings. Select the Languages section.
5. Click on the Export button located at the top of your screen.
6. A new window will pop up with the export settings. For Language - choose All Languages, for the Content setting - choose All and make sure that Metafields checkbox is marked, and for the File settings - make sure to pick the option - CSV for Excel, Numbers, or another spreadsheet program as shown in this example:
   
7. A CSV file with the translations will be sent to your store’s email address. Open that CSV file and translate our app’s content into every language listed as shown in this example:
   
8. Click on the Import button in the Language section and import the modified CSV file.
9. A new window will pop up with the import settings. Make sure that the checkbox Overwrite any existing translations for this language is not checked unless you want to overwrite your theme’s current translations, and click on the Upload and continue button as shown in this example:
   
10. An email will be sent to the store admin that will contain the updates made to your store’s translations.

In order to translate the Cookie bar using your theme’s locale files, please follow these steps:

1. Go to your Shopify Admin.
2. Click on Online Store link located on the left menu bar.
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. Scroll down to the Locales folder which contains your theme’s locale files.
5. Copy the JSON code provided in this file:
   
6. Paste the JSON code to the {language}.json files that your store is translated to as shown in this example:
   
7. Translate the properties of the JSON code to the corresponding language as shown in the example above.
8. Save the changes on the locale files by clicking on the Save button.
9. Copy the modified metafields code provided in this file:
   Note: If you have already added the metafields code, you should replace it with the one provided in the file above.
10. Open the theme.liquid file and paste the metafields code under the <head> element.
11. Save the changes on the theme.liquid file by clicking on the Save button.

First, make sure that the Enable For Specific Regions option is set to Enable for Canadian Visitors (PIPEDA)

• You can generate the page from the option available for our paid plans users located in the Global Settings tab, as shown below:



• The page can also be created manually for our Free users by following the steps in our FAQ section "25. I accidentally deleted my Compliance page. How can I get it back?"

And the third step would be to add this page to your storefront as shown in FAQ 13

That is it!

Note: Since the 3rd of November 2022 we added the option for the PIPEDA Compliance page to be automatically generated when you install our app so if you have installed our app after that date you should already have the page generated.

If you have any questions on this, do not hesitate to reach our support team on apps-support@isenselabs.com or from the "We Are Here" button at the bottom right corner of your browser.

As of this moment, our app does not provide a solution for the Google Fonts to be blocked initially before consent is given by the visitor via the Cookie bar in your store. 

The reason for that is the many different ways this service gets implemented in Shopify-based stores.

In some cases, it gets implemented automatically in the theme when you select any new font to be used in the Typography section of the theme customization settings.

The other cases, it is through a 3rd party app related to any visual and design-related solutions, which is using the service in order to function properly.

The best way to avoid any fonts being loaded from an outside source, like it is for Google fonts, as Shopify recommends, it would be best to load the fonts locally and you can do this by following the guide in the article they created on this called “Shopify self-hosting & preloading fonts”.

We are working towards finding a better solution to this, and we will update the FAQ section once we have more details and more suitable ways to integrate with the Google Fonts service.

If you need help оr have questions do not hesitate to contact our support team at: apps-support@isenselabs.com or from the "We Are Here" button at the bottom right corner of your browser.

The app constantly monitors whether you have reached at least 85% of the quota of your current plan. If you reach this quota percentage, you will receive an email saying that you have reached approximately 90% of the quota limit of your plan and also the approximate days in which you will reach the actual quota limit that will result in hiding the Cookie bar from your store. You can see an example of how the 90% emails look like below:

After the first email is being sent and if the plan of the app is still not upgraded, you will receive a second reminder email, three hours after the first email has been sent.

The main purpose of these emails is for you to be aware that soon the quota of the app will be reached, which will stop the cookie consent bar from showing. Once you get notified you will need to upgrade your plan right away or wait for the next quota reset day which is not recommended as during this time your store will not be compliant.

If your original store language is different from the one in our GDPR/CCPA + Cookie Management app - English, here are the options for translating our solution:

You can translate the Cookie bar and the Preferences popup automatically, from the Translationtab > Set Language For The Cookie Bar & Preferences popup section (there are more to come).

If your store language is different from the ones available there, you can check the following steps for manual translation.

The manual translation of the Cookie bar and the Preferences popup can be done as follows:
- Navigate to the Cookie Bar tab > Cookie Bar Content section in the app’s settings and translaте all the editable text fields with the content that will be shown in the Cookie bar and the Preferences popup. Check the below screenshots for reference:

For more information on the options for translating the GDPR/CCPA + Cookie Management app you can also refer to our FAQ 23."Can I translate the app?"

At the moment, you can translate the Cookie bar & Preferences popup with ETranslate in the following way:

• Follow the instructions from question #71.
• Once you have completed the steps there, the texts fields of the app should be visible in ETranslate's Metafields section:
  

As for the GDPR, CCPA and APPI Compliance pages, if you are subscribed to any of our paid plans, you now have the option to translate the GDPR and APPI Compliance pages automatically from the Translation tab of the app, as shown here:

If you are a Free Plan user, you can translate them manually in ETranslate by following the below steps:

1. Navigate to ETranslate > Translation > Pages and select the page that you want to translate.
   
2. Use the option for Auto translate the content to the corresponding language you set up, as shown below:
   
As you can see, once you translate the page, the ETranslate is changing the HTML elements of the page as well, which is making all it's functionalities unavailable. In order to fix this you would need to follow the below steps:


1. Switch the view of the translated page in ETranslate to HTML by clicking on the Source Code button there. Once you have the HTML view, select the content from the opening till the closing "< style >" tag, and delete it, as shown in the screenshots below:



2. Than navigate to the original Compliance page you are translating from your store admin, and from the HTML view copy the original < style > part to replace the one you removed from the translated page, as shown below:
   

   
   
   
3. The above two steps need to be repeated for the < script > part in the HTML view of the translated page as well. A reference on this can be checked in screenshots below:
   

   

   

   

NOTE: In regards to the above actions, when deleting the old and pasting the original code in the HTML, that should be including the opening and the closing tags.

The GDPR/CCPA Compliance + Cookie Management app will set a link forwarding to the app’s Privacy Policy and Terms of Service document as part of the Compliance pages, in the confirmation message before submitting any compliance requests, and possibly in the footer of the Preferences popup.

This is due to the legal requirement of the app standing between the store customers and the store merchants. But what does this mean for the customers and the store owners?

The Privacy Policy of our app states how data is used and stored and for what purposes. We would suggest adding the Privacy Policy and Terms of Service link of our app to the Privacy Policy page of your store in the section where you list any third-party applications, that are used on your site.

If you are a customer, visiting a store that uses our app for compliance: Our app assures GDPR/CCPA/APPI/PIPEDA Compliance of the respective site, and for this purpose, we do collect IP Addresses and E-mail (only if you are registered) in order to process each acceptance/rejection action done on the Cookie bar, and each request submitted through the Compliance pages.

The Cookie Information Table section, located in the Cookie Bar tab > Cookies Management section, will now show you all of the cookies listed on your site, separated into tables by category for your convenience. There you will be able to copy the table for each cookie group or make a copy of all tables at once and paste it into a page of your choosing. You can check the following tutorial for more information on how to do this:

You can also copy all of the tables at once and paste them into a page of your choosing. You can do this by pressing the "Copy all tables HTML" button, located in the upper right corner. Here is a screenshot of where you can find the button:

At the bottom of the page, you may notice that you can have a table called "List of cookies without description". There you will find the cookies that do not have a set description at the moment. You can set their descriptions, as well as edit the current descriptions and categories of each cookie by navigating back to the main tab page Cookie Bar tab > Cookies Management section > Cookie Information Panel > Select a cookie to modify.
More information regarding this can be found in the following FAQ: 50. How does the Cookie Information Panel work and what does each field do?

When the PageFly app is installed, it automatically creates a file called theme.pagefly.liquid in your store’s theme files. That file contains the content of your theme’s theme.liquid file as well as some additional settings required for PageFly’s features to work correctly.
If you have applied any of our app’s scripts to the theme.liquid file after installing PageFly, those scripts will not be automatically applied to the theme.pagefly.liquid file. In that case, you will need to make sure to copy and paste them manually to the file.
You can check all of the scripts that our app provides in section 30 of our FAQ page.
Note that the theme.pagefly.liquid file is used for the pages that are created with PageFly and have the option Header/Footer unchecked, as well as for the pages that are password protected.

If you need assistance with that, you can always reach out to our support team via email: apps-support@isenselabs.com or from the "We Are Here" button at the bottom right corner of your browser.

If your store is in one language only, and you would like to translate the contents of the Cookie bar and the Preferences popup, you can do that by navigating to the Translation tab -> Set Language For The Cookie Bar & Preferences popup and choose your language from there:

Currently we have predefined translations for the most popular languages worldwide.

If you can not find the language you prefer there, you can refer to our FAQ section "115. How to translate the app if my original/default store language is not English?" to check your options for manual translation.
You can also feel free to reach out to our support team at apps-support@isenselabs.com and request your preferred language.

You can link the Privacy Policy page of your store to the Cookie bar directly from the Cookie Bar tab > Cookie Bar Content section > Privacy Policy Link.

Check the below screenshot and video guide for reference:

Here is a short guide on how you can achieve this:

1. You should start by adding our app's metafields to your theme.liquid file. You can do this by following the steps in our FAQ section "71. How to translate the app by using metafields?"
2. Once the metafields are added, you will need to navigate to the app settings and refresh them from the Translation tab > Refresh Metafields button, as shown HERE.
3. After that, you can navigate to the Transl8 app settings. In the Shop section, you will see the metafields with the text content from our app that you can translate automatically or manually in the fields next to the original texts. Every element needs to be translated separately into the language you selected.



4. As for the Compliance pages generated by our app, they can be found in the Pages section of the translation app and are translated either automatically or manually, depending on your preferences. You can check the reference for this below:



5. In the Transl8 dashboard > Configure languages > Language menu settings, there is an explanation of how the links for all the languages in your store, can be set. You can check the following screenshot:



Also, a reference on how the exact process works can be found below:



6. Lastly, make sure that all the languages you will have the store translated to are also published from the Store Settings > Languages section, as shown in the image below:



If you need help with the translation process, don’t hesitate to contact our support team at: apps-support@isenselabs.com or from the "We Are Here" button at the bottom right corner of your browser.

The blocking will be done with an additional script. The script below will block the UET tag based on its Container ID

Here is how the script works: UET 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 cookie group is currently blocked, either based on the initial state of your cookie bar, or the cookie preferences of your customers. When the initial state is set to block the Marketing cookie group, or the customer opts out, the function which is setting the UET tag will not be executed.

Instructions on how to set UET's blocking script:

1. Open Shopify Admin.
2. Click on Online Store link on the left menu bar.
3. Click on the Actions dropdown button and from there select Edit Code.
4. A new page will open with a list of files on the left side of the screen. Open the theme.liquid file.
5. Locate where you have set the Universal Event Tracking script in the head HTML element - <head>. It should look similar to this:

1. 6. Copy the content of the UET's blocking script provided HERE and paste it under the script tag from step 5, as shown below. Afterwards, follow the next two steps:

Applying the Universal Event Tracking blocking script

Step 1. Copy the content of the Universal Event Tracking script and paste it under the comment “// The content of Universal Event Tracking script goes here”.

Step 2. Comment out or delete the Google Optimize scripts and save the changes.

7. The final result should look like this:

8. That's it!

If you need help with the process, don’t hesitate to contact our support team at: apps-support@isenselabs.com or from the "We Are Here" button at the bottom right corner of your browser.

The Google Optimize service is getting very popular among Shopify store owners and developers, which are using it for optimizing and improving the performance and the impact of their marketing campaigns or to simply check which parts of the store need optimizing in regard to user interface and experience.

Optimize uses the power of Analytics to measure your experiments and leverage your Analytics conversions as experiment objectives. Having said that, the Optimize service is another way of tracking that can be implemented in your store, which to some GDPR laws, is something you will need to get the visitor’s consent for first.

By following the below steps, you will be able to apply proper control on this service, which will work in accordance with the choice the visitor is making via the Cookie bar. Respectively, it will be either fired or stay blocked depending on the configuration of the cookies the visitor decides to accept.

The blocking will be done with an additional script. The script below will block the Google Optimize script based on its tag ID

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

Instructions on how to set Google Optimize blocking script:

1. Open Shopify Admin.
2. Click on Online Store link on the left menu bar.
3. Click on the Actions dropdown button and from there select Edit Code.
4. A new page will open with a list of files on the left side of the screen. Open the theme.liquid file.
5. Locate where you have set the Google Optimize script in the head HTML element - <head>. It should look similar to this:

1. 6. Copy the content of the Google Optimize blocking script provided HERE and paste it under the script tag from step 5, as shown below. Afterwards, follow the next two steps:

Applying the Google Optimize blocking script

Step 1. Copy the link which is inside the src attribute and replace {{ 'Your src link' }} with the copied link.

Step 2. Comment out or delete the Google Optimize scripts and save the changes.

7. The final result should look like this:

8. That's it!

If you need help with the process, don’t hesitate to contact our support team at: apps-support@isenselabs.com or from the "We Are Here" button at the bottom right corner of your browser.

When Transcy’s Auto Switch Language feature is enabled with the option Customer’s Location, it modifies the cookie bar’s buttons, resulting in the click event not being detected. You can see the screenshot below for reference on the option in the translation app:

In order to fix this, you need to add a script to your theme.liquid file. You can do this by following the below steps:

1. Navigate to Online Store > Themes > Actions > Edit Code > theme.liquid, as shown in the image below:

2. There, you need to locate the closing </head> tag, as you can see in the image below:

3. Copy the content of the script file provided below and paste it above the </head>tag.

4. Save your settings.

Here is how the final result should look like:

If you need help with the process, don’t hesitate to contact our support team at: apps-support@isenselabs.com or from the "We Are Here" button at the bottom right corner of your browser.

In case you want to hide the Cookie bar on a specific page/URL of your store, for example, a landing, newsletter or advertisement page to which the visitor is redirected from Facebook or other social media, you can do this by following the guidelines below.

Note: Before you proceed, it is always best to discuss this with a local law advisor or GDPR specialist and if it’s OK not to have the Cookie bar on particular pages of your store.

In order for the Cookie bar to be blocked only on the specific URLs of your store, you need to apply a script that should be added to your theme.liquid file. You can do this by following the steps below:

1. First, you will need to download the script provided below:

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

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