This guide covers a controlled replacement of CookieYes on a website. Work in staging first; the time required depends on your tags, integrations and policy setup.
Treat this as a new consent setup. Do not assume that a CookieYes consent cookie or exported log can be imported into QookieQloud or used to authorize tracking. Plan for visitors to make a new choice. Keep historical records separately according to your retention policy.
Inventory and save
Record every place that loads CookieYes: the site template, a CMS plugin, Google Tag Manager and any platform integration. Save the current configuration, tag-container version, banner texts and records you need before closing the old account.
Check provider-specific dependencies
Check whether CookieYes is installed through a CMS plugin, a dashboard snippet or GTM. Look for getCkyConsent(), cookieyes_consent_update listeners and CookieYes consent variables in tag triggers. Review the cookieyes-consent cookie, policy embeds and the control that reopens preferences; these are not QookieQloud interfaces.
Prepare QookieQloud on staging
Add the domain, choose a plan for the features you need and configure languages, categories, regional behavior and policy links. Connect your CMS or use the installation snippet provided for your site. Review scan findings and map each tag to the appropriate category; a scan alone does not prove correct blocking.
Replace consent-dependent code
Replace old event listeners, consent checks, tag triggers and the link that reopens cookie settings. Use the current QookieQloud integration instructions. Do not merely remove blocking attributes: that can turn a blocked tracker into an unrestricted script. Review Google Consent Mode defaults and updates if you use Google tags.
Test the entire choice flow
Use a clean browser session and test before any choice, reject all optional categories, accept all, a partial selection and withdrawal. Inspect cookies, local storage and network requests against your intended consent mode. Reload, navigate between pages and test a returning browser with an old CookieYes preference. Check mobile, language versions and regional rules. Google advanced consent mode can send cookieless pings; assess those separately from cookies.
Switch over and verify
Deploy the prepared replacement and disable the old loader in every installation location so only one CMP controls the site. Clear CMS, page and CDN caches, then repeat the tests on production. Update cookie-policy embeds and preference links. Confirm new choices appear in QookieQloud before cancelling the old service.
Keep a rollback ready
Retain a deployable copy of the previous setup and tag-container version. If the new setup fails, remove its loader and restore the old configuration together, clear caches and retest. Avoid leaving two active CMPs during rollback.
