Every Foleon Doc has cookies, and according to GDPR regulation, you need to inform your readers about these cookies. In this article, you learn why this is important, and how to set up the cookie consent pop-up.
💡 Are you looking for more detailed information on GDPR regulation? Check out our article All about Foleon and GDPR.
In this article
General Data Protection Regulation (GDPR)
On May 25, 2018, the General Data Protection Regulation (GDPR) came into effect. The GDPR is a set of laws aimed at enhancing the protection of EU citizens’ personal data and increasing the obligations of organizations to deal with that data in transparent and secure ways. More information about the GDPR can be found here.
Foleon uses these GDPR laws as the basis of the cookie consent settings.
Setting up the cookie consent
Go to your Foleon Doc settings and scroll down to the Marketing tab. Here you’ll see a switch to turn on cookie consent. Once you enable the feature, you will be able to set up your consent modal. You can:
- Change the title
- Change the description
- Add your privacy policy link
- Allow your audience to change their cookie preferences
⚠️ The cookie consent option is off by default.
-
Title
This is where you can enter the title of the message. We recommend keeping it clear and to the point.
-
Description
Add some information about why the message pops up and/or what happens with the information you’re gathering.
-
Privacy policy
When your company has set up a privacy policy that is added to the website, the link can be added to the cookie consent. By default, the link label says “Read our privacy policy” which is also editable in this section.
-
Allow your audience to change their cookie preferences
When you check this box, the cookie consent will show an extra button for the reader to decide if they want to allow the analytical and targeting cookies.
In the preview, you can check what this will look like for your audience.
💡 The text styling of the cookie consent pop-up is based on the brand settings. The title — here, "Cookies for a better site experience" — is based on the header 3 setting. The body text is based on the paragraph text setting.
If your audience clicks on accept all, they accept functional, analytical, and targeting cookies.
Clicking on cookie settings will bring up the options in the example below.
If your audience clicks on "cookie settings", only functional cookies are selected. Analytics and targeting cookies are opt-in.
💡How long your audience's cookie preferences are saved depends on your browser. For example, Firefox and Google Chrome don't have an expiration date, while Safari removes data after seven days. Learn more about Foleon cookies in our article All about Foleon and GDPR.
-
What happens when a visitor declines cookies
When your visitor selects "Accept all", they accept functional, analytical, and targeting cookies.
When you've allowed your audience to change their cookie preferences, they can prevent you from tracking them with analytics and targeting cookies.
-
Analytics cookies
If a visitor declines analytics cookies, this prevents Google Analytics and Foleon Analytics from tracking the user.
⚠️ If a visitor declines these cookies, their data won't show up in your Google Analytics or Foleon Analytics report.
-
Targeting cookies
If a visitor declines targeting cookies, this prevents cookies from being used for advertising.
Because video platforms such as YouTube and Vimeo also place targeting cookies, videos will be blocked when a visitor declines these cookies.
If this is the case, YouTube and Vimeo show visitors a message that lets them manage their cookie preferences or directly accept targeting cookies to view a video.
-
Scripts in the remarketing code
Scripts placed in the remarketing code field do not listen to updates in the Foleon cookie consent modal automatically. To be GDPR compliant, we have to make sure that they only work when they are allowed to work.
Therefore we need to tell the script that it can only fire when a specific cookie is allowed. We can do this by updating your script with two attributes.
First add type="text/plain" to your script element.
Next, add data-cookieconsent="statistics" to your script element to only allow this script to be fired once the statistics cookie is accepted.
-
<script type="text/plain" data-cookieconsent="statistics">
For targeting cookies and preferences you can use the same concept:
-
<script type="text/plain" data-cookieconsent="preferences">
-
<script type="text/plain" data-cookieconsent="marketing">
That’s it. The scripts in your remarketing field now listen to the user’s cookie preferences.
Allow your audience to update consent at any time
You can link any button or text to the Foleon cookie consent modal, allowing your audience to update their cookie preferences at any time.
First, make sure that you’ve enabled the checkbox in your Doc settings that allow your audience to change their cookie consent preferences.
Add or edit a button or a text link on your Doc and open the link-to dropdown. Here you’ll see an option to link to your cookie consent modal.
Cookie consent and MAP tracking
If you're working with one of our Marketing Automation Platform (MAP) integrations and use their tracking features, it's good to know how they work together with cookie consent. Foleon has four native MAP tracking integrations:
- Tracking Foleon Doc engagement in HubSpot
- Tracking Foleon Doc engagement with Eloqua
- Tracking Foleon Doc engagement with Marketo
- Tracking Foleon Doc engagement with Salesforce Pardot
Depending on if you have cookie consent set up, this is how MAP tracking works:
- When cookie consent is not set up, MAP tracking will work automatically — tracking visitors.
- When cookie consent is set up, MAP tracking only works if the visitor accepts cookies.
To set up your Foleon Docs in compliance with GDPR, you must activate Foleon's cookie consent feature if you use any tracking scripts. Alternatively, you can implement a Consent Management Platform (CMP).