Testing Your CMP on Non-Production Environments (Test Domains)

Overview

You can now safely test your cookie banner in non-production environments, without impacting your live setup or analytics.

This feature allows you to preview and validate your banner's design, blocking behavior, and user experience on a staging or localhost domain that mirrors production, without needing to implement the CMP script on the production domain itself.

Why use Test Domains?

Previously, banners could only appear on domains listed in Domain Management, which made it difficult to run quality assurance on test sites. With Test Domains, you can display your banner on a staging or localhost domain and review its behavior before deployment, without requiring additional configuration or risking production data.

How it works

When your banner loads on a registered test domain, it will:

• Mirror the appearance and blocking behavior of the referenced production domain
• Display a "draft" label on the banner for easy identification
• Act as an allowed domain for scanning and configuration purposes
• Not log consent or analytics — so test interactions never affect your reports

This means you get an accurate, realistic testing experience — completely isolated from your live data.

How to set up Test Domains

1. Add a Test Domain

Go to Configuration → Setup and scroll down to the Test Domains section. Click Add domain.

2. Enter your staging URL and select a reference domain

In the dialog, enter your staging or localhost URL (e.g. staging.domain.com or localhost:3000) and select the production domain it should mirror from the Choose reference domain dropdown.

Once added, make sure to save and publish.

3. View and remove test domains

After saving, all registered test domains appear in a table under the Test Domains section, showing the staging URL and its linked reference domain. Click Remove to delete an entry at any time.

 

Notes and limitations