Managing Versions in Cookie Consent

What is the Versions feature in Osano's Cookie Consent module?

The Versions feature, available exclusively to Premier users, allows you to view and manage current and previous published versions of your Cookie Consent Management Platform (CMP) scripts. It provides the ability to roll back to a previous version, including all associated configurations, for comprehensive reversion.

How do I access the Versions feature?

1. Log in to Osano using your account credentials.

2. Navigate to Cookie Consent from the main menu.

3. Select the configuration you wish to manage.

4. Click on the Versions tab.

What happens when I revert to a previous version?

Reverting to a previous version will restore all elements of that version, including:

• Source code.

• Styling configurations.

• Classification settings.

This full reversion ensures your CMP setup is exactly as it was at the selected version.

When should I use the Versions feature?

The Versions feature is particularly useful in the following scenarios:

• Breaking Changes: If recent updates to your CMP introduce issues that affect functionality or performance.

• Compatibility Problems: If new features or updates cause conflicts with your site's existing infrastructure.

Rolling back can quickly restore stability while you investigate or resolve any issues.

Does the Versions feature support collaborative workflows?

Yes! All published versions are listed chronologically, allowing team members to track changes, identify issues, and revert to a stable version as needed.

How do I revert to a previous version?

1. Access the Versions tab as described above.

2. Review the list of published versions and select the version you want to restore clicking the reversion icon on the left-hand side of the entry.

3. Confirm the reversion to apply the changes.

Can I recover my current configuration after reverting?

Reverting replaces the current configuration with the selected version. To preserve your current setup before reverting, we recommend publishing first to persist any recent changes and then reverting once those updates have been published. This will allow you to "restore" the current version at a later date.