Configuration

The plugin’s settings are split into ten tabs:

• General
• Cookies
• Translations
• Modals
• Floating Button
• Consent Mode
• Blocked Scripts
• Consent Records
• Logs
• About

Under the “General” tab, you’ll find all the basic configuration options, toggleable features, color palette, etc.

• “Autorun” will show the cookie consent as soon as possible. If disabled, you’ll have to manually call the .show() method of the global pressidiumCookieConsent object.

  // Manually show the cookie consent modal
  window.pressidiumCookieConsent.show();

  For more information about the pressidiumCookieConsent object, refer to the Control programmatically section of this wiki.

• “Auto-clear cookies” will clear any cookies set on the Cookies tab when the user opts-out of a specific category.

• “Page scripts” will manage third-party script tags. For more information on how to block them, refer to the Blocking Scripts section of this wiki.

Select one of the fonts that you have installed via the Font Library (WordPress 6.5+).

Choose one of the three predefined themes:

• Light
• Dark Blue
• Dark Turquoise

Then, adjust any color you wish individually.

List all of your analytics, targeting, and preferences cookies.

For each cookie, fill its:

• Name (e.g. ^_ga)
• Domain (e.g. example.com)
• Expiration (e.g. 2 years)
• Path (e.g. /)
• Description (e.g. Google Analytics to count pageviews)

Note that the cookie names can be either exact matches or regular expressions (if you select the “Is Regex?” toggle).

The cookie tables will be displayed on the settings modal under the “Analytics”, “Targeting”, “Preferences” or cookies respectively. They will also be used by the “Auto-clear cookies” feature, which will clear these cookies when a user opts-out of their category.

On the “Translations” tab, you can select the language auto-detection strategy:

• Browser — Read the user’s browser language
• document — Read value from <html lang="..."> of current page

Then, add languages and fill their translations.

By default, the English (🇬🇧) translation will be prepopulated for you.

Adjust the settings of the consent and settings modals. Select the layout, position, transition, and adjust the buttons of the consent modal. Select the layout, position, and transition of the settings modal.

At any point, you can click the “Preview Consent” or “Preview Settings” buttons to preview the modals with the currently selected settings. Note that your changes won’t be saved until you click the “Save” button.

On the “Floating Button” tab, you can enable a floating settings button that allows users to change their cookie preferences at any time.

You can adjust the button’s size, position, icon, and transition.

On the “Consent Mode” tab, you can enable Google Consent Mode v2 (GCM) and integrate with:

• Google tag (gtag.js)
• Google Tag Manager (GTM)

If you’re using Google tag, you can configure everything directly from the plugin’s settings page.

If you’re using Google Tag Manager, you can get our Google Tag Manager template via the Community Template Gallery (or import it manually by downloading the template.tpl file from the GitHub repository).

Selecting Google Tag Manager (GTM) template as the Implementation will show a panel containing step-by-step directions that will guide you through:

• Importing the Google Tag Manager template
• Create a new tag
• Configuring the Pressidium Cookie Consent tag

For more information about how to integrate with Google Consent Mode, refer to the Google Consent Mode section of this wiki.

On the “Blocked Scripts” tab, you can block third-party scripts from loading until the user has given consent. That way, they won’t set any cookies that the user hasn’t explicitly consented to.

For this feature to work, you’ll have to enable the “Page Scripts” option, under the General tab.

Script blocking may not always be effective due to variations in script loading methods. To make sure that you’re GDPR-compliant, you should double-check that the scripts you’ve configured are actually getting blocked. If you experience any issues, please let us know by opening an issue.

To block a script, you just need to copy-paste the URL of its src.

For example, to block the following script until the user has given consent for the “analytics” cookies:

<script src="https://www.google-analytics.com/analytics.js" type="text/javascript"></script>

You would enter the following:

You could also use a regular expression. For example, to block any script on the *.google-analytics.com domain, you could use:

^(?:https?:)?\/\/(?:www\.)?google-analytics\.com

For more information about how to block scripts from running, refer to the Blocking scripts section of this wiki.

Under the “Consent Records” tab, you’ll find all the consent records that have been collected by the plugin.

To enable the consent recording, you’ll have to turn on the “Record consents” option, under the General tab.

You can also export all recorded consents into a CSV file by clicking the “Export CSV” button, or permanently delete all recorded consents by clicking the “Clear Records” button and then “Delete records” in the confirmation modal.

Note that the “Location” information is only recorded if the server responds with one of the following headers:

• MM_COUNTRY_CODE
• GEOIP_COUNTRY_CODE
• HTTP_CF_IPCOUNTRY
• HTTP_X_COUNTRY_CODE

Under the “Logs” tab, you’ll find logs and other information, useful for debugging.