/ /

Copying Configurations in Cookie Consent

Updated 3 months ago

Osano makes it easy to duplicate an existing Cookie Consent configuration. Use the Copy Config button to save time by reusing Settings, Customizations, and Classifications from an existing configuration.

When to Use This:

Use the Copy Config feature when:

  • You need a fast starting point for a new config, based on existing classification rules, privacy settings, and customizations.

  • You want to apply the same consent settings to a new, unrelated domain.

  • You’re managing multiple websites with similar privacy requirements.


How to Copy a Configuration

  1. Navigate to Cookie Consent

Go to Cookie Consent → Configurations.

  1. Locate the Configuration You Want to Copy

Find the configuration you’d like to replicate.

  1. Click the “Copy Config” Button

On the right-hand side of the configuration, click the Three Dot Menu, then the Copy Config button.

image.png

  1. Enter New Configuration Name and Domain

A prompt will appear where you’ll enter:

  • New Configuration Name (a label to help identify it)

  • New Domain (the domain this new configuration will apply to)

  1. Save and Review

After submitting, Osano will create a new configuration with:

  • The same Settings

  • The same Customizations

  • The same Classifications (excluding Ignored items)

Note: This new configuration will also require a new script URL specific to the new configuration.


Customize As Needed

After copying, you can edit the new configuration without affecting the original one. This is especially useful when:

  • Branding or language needs to differ by region or domain

  • You need to tailor classification rules for different data uses

  • You want to test changes in a staging environment


Things to Keep in Mind

  • The copied configuration is completely independent from the original, including the script URL.

  • You can repeat this process for as many domains as needed.

  • Only the core elements (settings, customizations, classifications(excluding Ignored items)) are copied — other data such as consent records, compliance mode, or version history are not carried over.

Was this article helpful?
Subscribe to receive updates on this article