Skip to content
Installation
Upgrade guide

Upgrade Guide (Version 2.8)

This guide will instruct you on how to upgrade to CookieHub 2.8 from earlier versions and covers both the upgrade process in the CookieHub dashboard and changes required to the CookieHub implementation on your website.

Changes in Version 2.8

We have made various changes related to consent mode to fulfill Google CMP requirements. These changes apply both to the widget core code and the Google Tag Manager implementation, making it necessary to manually update the Google Tag Manager implementation for those who don't use the CookieHub GTM community template.

Notable Changes

  • Consent mode defaults are now sent in a codeless way, both when using the latest CookieHub GTM community template and with manual HTML code implementation.

  • The consent mode update signal is now only sent after users have interacted with the CookieHub dialog, either allowing or denying all or certain categories. Previously, CookieHub sent a consent update signal with the default consent to make sure the initial consent reflected the consent settings for the detected region. Due to this change, domains with multiple regions and implementing in GTM will now have to specify the regional defaults in the GTM template.

  • A list of services belonging to each category, along with links to their privacy policies and lists of cookies, is shown in the Category section of the Preference Center.

  • Mapping of consent mode signals for ad_storage to TCF 2.2 purposes & features was changed to Google's recommended setup.

A full list of changes is available in the Change Log.

How to Upgrade?

The upgrade to CookieHub 2.8 is done in two steps. First, you'll have to upgrade the CookieHub service, which activates the latest CookieHub widget, and then upgrade the implementation, which either involves replacing the HTML implementation code or upgrading the CookieHub template in Google Tag Manager.

Upgrading CookieHub

Follow these steps to upgrade to CookieHub 2.8:

  1. Log in to the CookieHub dashboard (opens in a new tab).
  2. Select the domain you wish to upgrade.
  3. In the Overview tab, you will see a box with information about the current version and if there's an update available.
  4. If you are not using the latest version, you will see a message similar to this: Upgrade needed
  5. Click the "Upgrade to 2.8.0" button and then confirm in the dialog shown with detailed information about the update.
  6. After the upgrade has been completed, you should see the message "You are using the latest version of CookieHub." in the box previously indicating that an upgrade was available. Latest version in use
  7. The changes should be published automatically, but if you see a button at the top "Publish pending changes," click it to publish the changes.

Upgrading Implementation

When you have upgraded CookieHub to the latest version, you may need to upgrade the implementation as well. Refer to the following list of implementation methods to find the next steps.

Tag Installation

If you implemented CookieHub on your website by inserting the HTML implementation code, you may be using an old code with outdated consent mode default settings. Follow the Tag Installation Instructions to find out how to locate the correct implementation code and replace the current code with the new one.

Please Note: Previous tag installation codes included code to set the consent mode defaults. CookieHub now provides a codeless way to set the consent mode defaults, which also sets regional defaults if you have multiple regions active.

WordPress Plugin

If you are currently using the CookieHub WordPress plugin (opens in a new tab), you don't have to do anything except make sure you have the latest version of the WordPress plugin installed.

Google Tag Manager

If you are currently using Google Tag Manager to implement CookieHub, follow the Google Tag Manager Upgrade Instructions to make sure you have the latest CookieHub GTM community template installed.

Please Note: CookieHub does not set consent mode defaults using a consent update command anymore. Due to this, you may need to set regional defaults manually in the CookieHub GTM template as instructed in the upgrade guide.

Getting startedConsent mode