Migrating to OptinStack from another CMP
By OptinStack Team - Jul 1, 2026 - 2 min read
Use this hub when you are moving from another consent management platform to OptinStack and your site uses Google Tag Manager. Most migration issues are caused by leaving old CMP templates, events, variables, or category triggers in the GTM container.
Your tags may stop firing, fire too early, or send the wrong Consent Mode signals if you publish OptinStack while old CMP triggers and variables are still controlling GTM tags.
The migration model
- Remove the old CMP as the consent authority. Keep only one system setting Google consent defaults and updates.
- Install the OptinStack runtime early so it can control direct trackers outside GTM.
- Import the official downloadable OptinStack template under Templates > Tag Templates > New > Import. It is not currently published in the Community Template Gallery. Fire the OptinStack tag on Consent Initialization – All Pages.
- Replace old CMP event names and variables with OptinStack category events and GTM Additional Consent Checks.
- Test with GTM Preview, Tag Assistant, DevTools, and an OptinStack scan before publishing.
| Old concept | OptinStack replacement |
|---|---|
| Old CMP GTM template | OptinStack GTM template on Consent Initialization - All Pages |
| Old CMP category event | optinstack_necessary_accepted, optinstack_analytics_accepted, optinstack_marketing_accepted, optinstack_preferences_accepted |
| Old CMP consent variable or first-party cookie condition | GTM Additional Consent Checks using Google consent types |
| Old per-vendor gating | OptinStack category gating unless the tag truly needs vendor-specific logic |
Start with the guide for your current CMP
- Migrate from Cookiebot to OptinStack
- Migrate from CookieYes to OptinStack
- Migrate from OneTrust to OptinStack
- Migrate from Axeptio to OptinStack
Related articles
Migrate from Cookiebot to OptinStack
Move a Cookiebot GTM setup to OptinStack by replacing the Cookiebot template, cookie_consent_update triggers, and category mappings.
Migrate from CookieYes to OptinStack
Move a CookieYes GTM setup to OptinStack by replacing the CMP template, consent cookie conditions, and trigger wiring.
Migrate from OneTrust to OptinStack
Move a OneTrust GTM setup to OptinStack by mapping OnetrustActiveGroups, OptanonConsent, and category IDs to OptinStack.
Migrate from Axeptio to OptinStack
Move an Axeptio GTM setup to OptinStack by replacing vendor-based triggers with OptinStack category events and consent checks.
Integrate OptinStack with Google Tag Manager
Configure OptinStack with Google Tag Manager from start to finish, including the GTM template, Consent Mode v2 signals, defaults, triggers, consent settings, and testing.
Basic vs Advanced Google Consent Mode
Compare Basic and Advanced Google Consent Mode, including tag loading, cookieless pings, GTM settings, verification, and when each mode makes sense.
How helpful was this article?