Migrate from v1 to v2
This guide explains how v1 users can continue using their existing setup in v2 and how to migrate to unlock all new v2 features.
I am a v1 user continuing with the v1 banner
For users coming from v1 who already have their banners configured, no action is required when they open the app in v2. Everything will continue to work as before. However, features such as logs, auto-categorization scripts, and similar functionality will not be available until the migration to v2 is completed.
I am a v1 user who wants to use v2 features
Any modification made in the app to use V2 features, such as geolocation, the new banner structure, or AI categorization, will trigger a script update and require the banner to be replaced.
To complete the migration, the user must:
- Create a new banner or replace the existing banner.
- Add the new Consent Pro script to the custom code
<head>section. - Remove the legacy Consent Pro code block in the Code Added by Apps section.
- Scan the website and review the instructions in the Actions tab.
After publishing the project, the new banner will function properly, and the user will have access to all v2 features, such as scan to detect trackers and consent logs.
Do not worry. When you replace or create a new banner, you will see all the instructions to complete the migration in the Actions tab.
Legacy Attribute Override
When a project has legacy fs-consent-categories attributes on its tracking scripts, Consent Pro V2 will always prioritize the category assigned by the app over any manually added attribute values.
How It Works
When Consent Pro V2 scans your project and assigns a category to a script, that app-assigned category takes precedence over the value set in the fs-consent-categories attribute.
If a script has no category assigned in the app, Consent Pro V2 will fall back to the value in the fs-consent-categories attribute.
| Scenario | Category Used |
|---|---|
| Script has an app-assigned category | App-assigned category |
Script has no app category, but has fs-consent-categories | Value from fs-consent-categories |
| Script has neither | Not blocked |
Example
Consider a script that was manually tagged as essential via the fs-consent-categories attribute:
<script type="fs-consent" fs-consent-categories="essential" src="https://example.com/analytics.js"></script>Despite the essential value set on the attribute, if the app has identified and categorized this script as analytics, the script will be treated as an analytics script. The app's category always takes priority.
This means the script will only load once the user has accepted the analytics category — not by default as an essential script.
Why This Matters
This behavior ensures that the app's knowledge of what a script actually does is always respected, even if a legacy attribute was added manually with an incorrect or outdated category. It prevents trackers from being inadvertently classified as essential and loading without explicit user consent.
What Changed from V1 to V2
Below, you will see all the changes and improvements we made from v1 to v2 to help you decide if you want to migrate your current project to use Consent Pro v2 features.
Auto-Blocking Scripts
v1: It was required to manually update the scripts in the custom code section.
v2: Scripts are blocked automatically. No action is required.
Store Consents Automatically
v1: A manual and boring Cloudflare server setup was required to store users' consents.
v2: Consents are saved automatically on our servers and displayed to the user in the Logs tab.
Geolocation Feature
v1: One global banner for all regions.
v2: Custom banners per region using the geolocation feature.
Tracker Info in the Preferences Panel
v1: No tracker information in the preferences panel.
v2: All trackers are listed by category in the preferences panel.
Fill with AI
v1: Not available.
v2: Generate content to fill tracker information and categorize them with one click using AI.
More Banner Options
v1: Opt-in, Opt-out and informational banners available.
v2: Opt-in, Opt-out, Do Not Sell, and Informational banners available.
Improved Website Scanner
v1: Simple scan to detect scripts found in the project.
v2: Advanced scan to detect trackers and automatically categorize and populate them based on our knowledge database.