How to upgrade to CookieHub version 2.8

This guide explains how to upgrade from an older CookieHub version to 2.8, including changes to the widget and updates required for your implementation.

Why upgrade?

Version 2.8 introduces changes to Consent Mode behavior to comply with Google CMP requirements:

  • Consent Mode defaults are now set without custom code.
  • Consent update signals are only sent after user interaction, not on page load.
  • Regional defaults must now be configured in the GTM template (if using GTM).
  • Updated mapping of ad_storage signals to TCF purposes.
  • Enhanced Preference Center with service lists, links, and cookie details.

For a complete list, see the Change Log.

Upgrade process overview

Upgrading involves two steps:

  1. Upgrade CookieHub to version 2.8 in the dashboard.
  2. Update your site’s implementation (HTML code, GTM template, or WordPress plugin).

Step 1: Upgrade in CookieHub dashboard

  1. Log in to your CookieHub dashboard.
  2. Select the domain you want to upgrade.
  3. In the Overview tab, check if an update is available.
  4. Click Upgrade to 2.8.x and confirm.
  5. If you see Publish pending changes, click it.

Your domain is now on version 2.8.

Step 2: Update your implementation

If using HTML (manual code)

  • Go to the Implementation tab in the dashboard.
  • Select Manually insert the code.
  • Copy the latest production code and replace the old code on your site.
  • Place the code at the top of <head> .

See full HTML installation guide.

If using WordPress plugin

  • Make sure you have the latest version of the CookieHub WordPress plugin installed.
  • No further changes are required.

See WordPress plugin guide.

If using Google Tag Manager

  • Replace the old CookieHub template with the CookieHub GTM community template.
  • Configure region defaults in the GTM tag if your domain uses multiple regions.

See GTM upgrade guide.

Important notes

  • Old HTML snippets included code to set Consent Mode defaults. This is no longer required.
  • CookieHub now sets defaults automatically and sends the update signal only after user consent.
  • If you customized category descriptions (especially Marketing), update them to comply with Google’s EU consent policy.