Your landing page will have two types of cookies:
- Essential cookies - mandatory Instapage cookies that are essential for pages and variations being served, and conversions being tracked;
- Optional cookies - all other cookies that you have installed with integrations or were added to a page with custom code. Only these cookies will be blocked by this solution.
You need to make sure all of your landing pages provide your visitors with proper consent and the opportunity to opt out of non-essential cookies.
In the case where you have more than one processing scope for the data that you are collecting, as per GDPR Article 7, you will need to offer the possibility to your visitors to consent for each and every scope you are collecting the data for. In order to be fully compliant with the GDPR law in the case you are collecting data for multiple scopes, please make sure to collect consent for each case.
In conclusion, please make sure to collect the consent for each case by using a separate method from our cookie bar, such as checkbox fields in your form, in order to be fully GDPR compliant.
NOTE: We do not recommend placing any other scripts in this section of the page besides Javascript tracking ones that you need to have blocked. Any code added with <script> tags will be ignored by the cookie bar and will fire on the page regardless of the cookie bar being accepted or not. HTML code will result in errors.
What does the cookie bar block?
It will block the native integrations from the Marketing Tags & Pixels section in the Integrations part of the slideout, along with any scripts placed in the Scripts & Privacy section. The scripts from the Javascript and HTML/CSS section in the editor can be blocked if they are wrapped in a code found at the bottom of this article.
Under the Scripts & Privacy section of each page you have an option that will allow you to postpone the cookie delivery until a visitor accepts it. When you enable that feature for a specific page, that page will show a small cookie notification on the bottom of the browser window where the page visitor can accept or decline cookies from the page.
If the visitor clicks on the Yes, I accept button, he will give his consent that all cookies that are on that particular page can be added to his browser. On click, ALL cookies will be installed and the notification will disappear. If the same visitor accesses the page again later, the browser will remember his choice and the cookie bar will not show up again.
If the visitor clicks on the I do not accept button, he will deny all the optional cookies that are on that particular page. On click, only OPTIONAL cookies will NOT be installed and the notification will disappear. Essential cookies will still be added to his browser.
If the visitor clicks on the Learn more link, he will be sent to a page on your website where your company explains which cookies are being used and why. You can see where to place this link in the instructions below.
1. Click on the name of the page and go to the Scripts & Privacy tab
2. In the screen that opens, you need to enable the Cookie Bar toggle and input the link to your terms of service into the designated field;
By default, this input field is empty, and if it is left empty after enabling this feature, the default value will be an empty link.
3. After you switch the toggle to ON, you will see a modal that notifies you that you need to read and confirm reading this article before you can continue.
When you enter a code snippet into the Scripts & Privacy section, it will be applied to all the variations that you are using to A/B test the page, unlike the code in the HTML/CSS and Javascript section in the builder, which are variation-specific.
If the cookie bar is OFF, the code will run automatically, on all the variations. If the cookie bar is ON, the code will run only after the visitor accepts the cookies.
Important notes!
In order for the scripts placed in the builder in the Javascript or HTML/CSS sections to only run after the visitor accepts the cookies, you will need to wrap all the code in the following function:
The codes placed in the Scripts & Privacy section do not need this function to be blocked by the cookie bar, only the ones in the page builder do.
Instapage app sections that were made for JavaScript code ("JavaScript" in the page editor, "Scripts & Privacy" in the slideout) will add <script></script> tags to the code by default.
If you need to use <noscript></noscript> tags, as is needed for some GTM snippets and other cases, then please add a <!-- disable <script> autowrap --> comment before the first <noscript> tag.
Example:
<!-- disable <script> autowrap -->
<!-- Google Tag Manager (noscript) -->
<noscript> <iframe src="https://...[add the rest of the code as usual]
_________
If you want to translate or change the text on the cookie bar, you can refer to this guide here: https://d.pr/0tEJLn.
_________
If you would like to learn more about the Workspace Scripts feature that is present in the same section, please refer to this article here: https://d.pr/afatJM.
Google's Consent Mode
We do not have a native integration at this time, but it is doable trough custom code. Please see Google's documentation here: https://support.google.com/google-ads/answer/10000067?hl=en and the code that they provide for this can be found here: https://developers.google.com/tag-platform/security/guides/consent?sjid=10192954601016830509-EU&consentmode=advanced