Importing consent from your previous CMP

Switching consent platforms should not mean re-prompting every visitor who already made a choice. When consent import is enabled for your site, ConsentStack reads the consent record your previous CMP stored in the visitor's browser and honors it: visitors who accepted stay accepted, visitors who declined stay declined, and nobody sees a second banner for a decision they already made.

How it works

1. On the first page load after your cutover, the SDK looks for your previous CMP's first-party consent cookie (for Cookiebot, the CookieConsent cookie).
2. If it finds a valid, explicit decision that has not expired, it maps the categories to your ConsentStack categories and applies them immediately, before any tracking scripts can run. The banner is not shown.
3. The decision is converted into a native ConsentStack record and logged to your consent log with the original evidence attached (the previous CMP's consent ID, timestamp, and region), so your audit trail stays continuous even after you cancel the old vendor.
4. From the second page load on, the native ConsentStack record is used. The old cookie is left in place and simply expires on its own.

What gets imported

Only explicit decisions are imported. Records marked as implied consent, malformed records, and records older than your consent lifetime setting are ignored; those visitors see your banner as normal.

Declines are imported faithfully. A visitor who rejected tracking under your previous CMP stays rejected under ConsentStack, with no re-prompt.

Supported vendors

• Cookiebot

Support for additional vendors is on the roadmap. If you are migrating from a platform not listed here, contact us and we will prioritize it.

Enabling consent import

Consent import is enabled per site by our team during onboarding. Contact support with the name of your previous CMP and we will switch it on before your cutover.