Magento 2 Cookie Consent Mode V2

User Guide & Documentation

Installation from Command Line

This extension can be installed in a few minutes, by going through the following steps:

• Download/purchase the extension
• Unzip the file in a temporary directory
• Copy directory contents and paste it in your Magento installation root directory. This extension will not replace existing code or file structure
• Enter the following at the command line:
  
  php bin/magento setup:upgrade
  php bin/magento setup:static-content:deploy (only if site is in production mode)

Installation and updating with Composer

You can install this extension via Composer only after purchasing a Composer support package

• Run the following Composer commands
  
  composer require anowave/package
  composer require anowave/consent
  
  bin/magento setup:upgrade
  bin/magento setup:static-content:deploy (only if site is in production mode)

Cookie Consent Configuration

Google Consent Mode V2 configuration

If you use Google Consent mode for your tags and/or have Additional Consent Checks you need to edit your GA4 Configuration tag (Google Tag) and change it's trigger from All Pages to Event Equals Cookie Consent Granted. This will allow this tag to fire whenever consent is granted. Otherwise, the tag will fire on all subsequent requests therefore you will lose the initial HIT.

Testing Consent Mode / GDRP features involves the following steps:

1. Hit F12 in your browser, then go to Console -> Storage and remove any cookies  prefixed 'cookie' e.g. 'cookieConsentGranted' etc.
2. Go to Console -> Local Storage and remove 'consentMode' value
3. Once done, put GTM in Preview mode and refresh your site.
4. Accept cookies and check if GA4 Configuration (Google Tag) is firing.
5. Optionally (as a developer) you can check Console -> Network requests for any requests to https://region1.google-analytics.com/g/collect?v=

Also when checking browser requests in the F12 -> Console -> Network tab, you can inspect 1 important parameter:

gcs - Encodes the current state of the user’s consent. The gcs parameter always begins with “G1” and is followed by two other digits, either 1 or 0. The G1 is a constant that indicates that the parameter is a GA4 consent mode parameter, so the first 1 doesn’t tell us anything.

G100     No consent has been granted.
G110     Google Ads has consent, Google Analytics does not.
G101     Google Analytics has consent, Google Ads does not.
G111     Both Google Ads and Google Analytics have consent.

3rd PARTY Consent Configuration

The feature provides a mechanism to include third party script into consent mode compliance. To do so, you need to add some data-* attributes tagging to those scripts. The following changes are required:

1. Remove 'async' attribute
2. Change 'type' attribute from 'text/javascript' to 'text/template' e.g. type='text/template'. If type attribute is missing, add it as 'text/template'
3. Add data-consent="cookieConsentGranted" attribute to SCRIPT tag. Attribute values may include: cookieConsentGranted, cookieConsentMarketingGranted, cookieConsentUserdata, cookieConsentPersonalization, cookieConsentPreferencesGranted, cookieConsentAnalyticsGranted

Review granted permissions

You can review all granted permissions in a separate menu in admin panel under Admin -> Reports -> GDRP Consent (see below)

Cookie Classification

The module will automatically detect and collect cookies set in browsers. These cookies will appear in administration panel under Reports -> Consent Cookies V2 listed  as grid. By default all cookies are presumed Unclassified, you can click on any row contaning a cookie and assignt that cookies to specific segment. From then on this cookie will get set when customers allow the segment in the cookie consent widget in frontend.

You can also put manual text description of the cookie which can be seen in the widget when customers click 'Learn more' next to each cookie segement. The cookie segments correspond to those in the frontend thus effectively allowing cookie classification.