WooCommerce
WordPress GDPR Cookie Consent
WordPress og WooCommerce GDPR cookie compliant plugin som gør det nemmere for din virksomhed at overholde reglerne.

WooCommerce

WordPress GDPR Cookie Consent

WordPress og WooCommerce GDPR cookie compliant plugin som gør det nemmere for din virksomhed at overholde reglerne.

Med WordPress GDPR Cookies Consent plugin kan din hjemmeside eller webshop blive GDPR Cookie compliant med fuld gennemsigtighed.

Dette plugin gør det nemlig muligt at få brugeren til at afgive de nødvendige tilladelser det kræver for eksempelvis at analysere adfærd via Google Analaytics, eller Facebook. Endvidere er der right mulighed for at tilpasse plugin’et efter jeres behov.

Cookie grupper/sektioner

Pluginet tilbyder support af følgende cookie sektioner/grupper:

  • Nødvendige
  • Funktionelle
  • Statistikker
  • Marketing
  • Kommunikation
  • Uklassificeret

Alle sektioner kan blive navngivet efter eget ønske. Det eneste man skal holde i mente er, at de events som bliver skudt af sted til Google Tag Manager stadig hedder det oprindelige navn.

Ikke 100% automatiseret

Plugin’et er ikke en 100% automatiseret løsning og kræver både forståelse af Google Tag Manager og at alle 3-part scripts som sætter cookies/indsamler data bliver flyttet til Google Tag Manager.

Installationskrav – Læs inden køb

Det du skal vide inden du køber dette plugin:

  • Plugin’et er ikke en 100% automatiseret løsning og kræver forståelse af Google Tag Manager og indsættelse af script her i (se dokumentation) og gerne kendskab til JavaScript.
  • Plugin kræver en aktiv Google Tagmanager konto på tagmanager.google.com (gratis)
  • WordPress 5.x eller nyere

Du kan altid kontakte os og forespørge om en kort GDPR Cookie snak for at se, om dette plugin er den rigtige løsning for jer. Angiv venligst en adresse til din hjemmeside/webshop.

Installation

  1. Download the plugin from either a) the download link in the confirmation email or b) your account page on the website
  2. Upload and activate the plugin on your WordPress website
  3. Go to “Customizer > Rommel GDPR Cookie Consent” and activate the sections/groupings you wish to use
  4. Go to Google Tag Manager and setup triggers that you can now use to activate GTM scripts (read more below)

Google Tag Manager setup

The concept in Google Tag Manager is fairly simple. We trigger a custom event whenever a guest accepts a cookie group which your setup triggers for i Google Tag Manager (see the screenshot below for a trigger example). The plugin can send the following events based on the users actions – please notice that the “necessary” grouping is not actually a thing but purely used for communication to your guests:

  • cookies_consent__functional
  • cookies_consent__statistic
  • cookies_consent__marketing
  • cookies_consent__communication
  • cookies_consent__unclassified

The last part you have to do is use the triggers on your tags. These tags can also be used in groups to ensure that a tag is only executed once per page load. This is relevant to note since an event could potentially be executed multiple times on if a guest opens and closes the cookie settings modal multiple times and keep changing their preferences.

WordPress GDPR Cookie Consent features (roadmap)

Alt starter et sted – hvor syntes du vi skal hen? – Skriv til os på support@rommel.dk hvis du har nogle forslag til forbedringer/udvidelser.

Installation

  1. Download the plugin from either a) the download link in the confirmation email or b) your account page on the website
  2. Upload and activate the plugin on your WordPress website
  3. Go to “Customizer > Rommel GDPR Cookie Consent” and activate the sections/groupings you wish to use
  4. Go to Google Tag Manager and setup triggers that you can now use to activate GTM scripts (read more below)
  5. To skip the setup you can download the example file and import it into your Google tag manager container.

Google Tag Manager setup

The concept in Google Tag Manager is fairly simple. We trigger a custom event whenever a guest accepts a cookie group which your setup triggers for i Google Tag Manager (see the screenshot below for a trigger example). The plugin can send the following events based on the users actions – please notice that the “necessary” grouping is not actually a thing but purely used for communication to your guests:

  • cookies_consent__functional
  • cookies_consent__statistic
  • cookies_consent__marketing
  • cookies_consent__communication
  • cookies_consent__unclassified

The last part you have to do is use the triggers on your tags. These tags can also be used in groups to ensure that a tag is only executed once per page load. This is relevant to note since an event could potentially be executed multiple times on if a guest opens and closes the cookie settings modal multiple times and keep changing their preferences.

To make it all much easier you can download and import this file in Google Tag Manager which will add all the triggers. We’ve also added a Google Analytics script in the file (make sure you don’t override) if one already exists.

Insert link to re-open the settings

Add this to the page in order to trigger the settings panel.
<a href=”#open-cookie-settings”>Click here to change cookie settings</a>

Datalayer

Unless you are all about datalayer and Google Tag Manager we recommend that you use the plugin Google Tag Manager for WordPress to get your data from the website/webshop to Google Tag Manager.
When installed you will need to let the “Google Tag Manager for WordPress” plugin that it should only add the Data layer to the page source.
See screenshot below:

1.3.7:
Fix: Internet Explorer issues

1.3.1:
CSS: Smaller improvements.

1.3.0:
* Feature: support updating the plugin through the WordPress interface.

1.2.2:
* Fix: start the pop-up logic in a “DOMContentLoaded” event to allow the JavaScript to be included both in the head or footer of the HTML.

1.2.1:
* Fix: correct issue where the English description would be used for all languages.

1.2.0:
* Feature: Rename all elements and styling to be more specific to avoid conflicts with existing themes and plugins.

1.1.1:
* Feature: improved code documentation.

1.1.0:
* Feature: refactor the code to use localStorage instead of cookies to register options but keep the cookie solution as a fallback if the browser do not support localStorage.
* Support Polylang multilingual plugin (i18n).

1.0.0:
* Feature: Initial release of the plugin.