# Switch from CookieYes to Cookiequiet

> Move a site from CookieYes to Cookiequiet in about 30 minutes: map the categories, keep the script markup, keep Consent Mode working, remove the old script.

Source: https://cookiequiet.com/guides/switch-from-cookieyes
Published: 2026-10-20
Publisher: Cookiequiet

## Steps

1. **Create the site and scan it** Add the website in Cookiequiet, run the scan, and review the detected providers and cookie categories. Map performance to analytics and advertisement to marketing.
2. **Copy your texts and colours** Reproduce any custom wording, the layout and the brand colours in the banner designer, in each language you need.
3. **Export the CookieYes records** Download the consent records and the cookie table from the CookieYes dashboard and keep them with your compliance files.
4. **Check the script tags** Tags with data-cookieyes keep working as they are; mark inline tracking snippets that CookieYes did not require marking with type text/plain and data-cq-category.
5. **Update custom code and tag manager triggers** Replace CookieYes event listeners with the cq:consent event or Cookiequiet.on, and point tag manager triggers at the cq_consent event.
6. **Swap the scripts in one release** Remove the CookieYes plugin or script and add the Cookiequiet snippet with Consent Mode and auto-blocking enabled, first in the head.
7. **Point the settings link at the new centre** Give the footer link the data-cq-show-preferences attribute so visitors can reopen their choices.
8. **Verify and regenerate the policy** Check the three paths in a private window, run a scan to confirm no other consent tool remains, and regenerate the cookie policy from the scan.

Switching from CookieYes to Cookiequiet is a half-hour job for a typical site: one script tag replaces another, the scripts you marked for CookieYes get a different attribute, your Google tags keep receiving Consent Mode signals, and the footer link that reopened the CookieYes banner points to the new preferences centre. Visitors will be asked for their choice once more, because the stored consent lives in a different cookie, and that is fine. The order of the steps matters only to avoid showing two banners at the same time.

## Why people switch

CookieYes prices by pageviews. On its pricing page (checked on 20 October 2026) the Free plan allows 5,000 pageviews a month on one domain, Basic costs $10 per domain per month for 100,000 pageviews, Pro $25 per domain per month for 300,000 pageviews, with geo-targeting starting at that tier, Ultimate $55 per domain per month for unlimited pageviews, and extra traffic is billed at $0.30 per 1,000 pageviews. Cookiequiet has no pageview or banner-view limit on any plan: Free for one website, Starter at €3 per website per month or €29 a year, Pro at €9 per website per month or €99 a year, geo-targeting included on every plan. The [comparison page](/vs/cookieyes) has the feature table; [the pricing argument](/blog/why-pageview-pricing-is-wrong-for-consent) explains why a per-pageview meter is a poor fit for a legal requirement.

## What carries over

**Categories.** CookieYes uses necessary, functional, analytics, performance and advertisement. Cookiequiet has four: necessary, functional, analytics and marketing. Map performance to analytics and advertisement to marketing; functional and necessary keep their names. If you assigned cookies to categories in the CookieYes dashboard, the Cookiequiet scan rebuilds the table from the site itself and lets you adjust categories by hand.

**Banner texts.** Copy the wording you customised, if any. Cookiequiet ships 24 languages picked from the visitor's browser, every string editable per language.

**Consent records.** Export what your CookieYes dashboard offers before you close the account. Choices made under the old banner are proven by the old records; the new log starts at the switch.

## What changes: the script markup

CookieYes documents two blocking methods: a `data-cookieyes` attribute on external script tags, with values such as `cookieyes-analytics`, `cookieyes-functional` or `cookieyes-performance`, and URL patterns entered in its dashboard. Cookiequiet reads the `data-cookieyes` attribute too: cookieyes-analytics and cookieyes-performance map to analytics, cookieyes-functional to functional, cookieyes-advertisement to marketing, so those tags keep working without changes. Its marking is the `text/plain` convention:

A tag marked for CookieYes:

```html
<script async data-cookieyes="cookieyes-analytics"
  src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXX"></script>
```

The same tag marked for Cookiequiet:

```html
<script type="text/plain" data-cq-category="analytics" async
  src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXX"></script>
```

For each tag: keep `data-cookieyes="cookieyes-<category>"` as it is, or replace it with `type="text/plain" data-cq-category="<category>"` if you prefer one convention, mapping performance to analytics and advertisement to marketing. Inline scripts can be marked the same way; CookieYes did not require marking them, so check your inline snippets (the gtag config block, the Meta Pixel init) and mark those too. Trackers you blocked through URL patterns in the CookieYes dashboard are covered by Cookiequiet's auto-blocker when the host is in its provider database (about 80 trackers), and by marking otherwise. The [script blocking guide](/guides/block-scripts-until-consent) covers the four methods in detail.

**Custom code that listened to CookieYes.** The documented CookieYes events are `cookieyes_banner_load` and `cookieyes_consent_update`, with the accepted categories in the event detail. The equivalents are the `cq:consent` event on `window`, whose detail carries the granted categories, and `window.Cookiequiet.on(callback)`; `window.Cookiequiet.get()` returns the stored choice.

**Google Tag Manager.** If CookieYes set Consent Mode defaults for you, Cookiequiet does the same when the snippet carries `data-consent-mode="1"`: all types denied before the container runs, updated on every choice. Triggers that fired on a CookieYes dataLayer event should fire on `cq_consent` with the matching flag (`cq_analytics`, `cq_marketing`, `cq_functional`) instead. See [the Consent Mode guide](/guides/google-consent-mode-v2).

**The "Cookie settings" link.** A footer link that called the CookieYes revisit function becomes an element with `data-cq-show-preferences`, or a link to `#cq-preferences`.

## Order of operations

Do the markup changes on a staging copy or behind a feature flag first, then swap the script tags in one deployment. If both scripts are live together, visitors see two banners and the two tools fight over the same tags. Remove the CookieYes WordPress plugin or script tag in the same release that adds the Cookiequiet snippet.

## What visitors will notice

Returning visitors see a banner once more, because their previous choice was stored in a CookieYes cookie that the new script does not read. The new banner shows Accept all and Reject all at the same size on the first screen; if your CookieYes banner showed a smaller reject option or none on the first layer, expect your acceptance rate to settle lower and your compliance risk to settle lower with it. [The consent rate article](/blog/cookie-consent-rates-what-to-expect) has the published numbers. Visitors outside consent countries stop seeing a banner at all if you set geo-targeting to regulated countries only, which CookieYes gated behind its Pro tier.

## A rollback plan

Keep the CookieYes account open for a week. If something is wrong, the switch reverses in one deployment: remove the Cookiequiet snippet, restore the CookieYes tag, and the old marked scripts, if you kept them in version control, work again. In practice the usual fix is smaller: a tag that was not marked, or a Tag Manager trigger still pointing at the old event.

## After the switch

Open the site in a private window: no analytics or marketing request before a click, nothing new after Reject all, everything after Accept all. Run a scan: it should report Cookiequiet as the consent tool, Consent Mode detected, and no other CMP. Regenerate the cookie policy from the scan so the table matches the new categories, and replace the CookieYes policy link. Keep the exported CookieYes records with your compliance documents.

## Questions

### Will visitors have to consent again after the switch?

Yes. CookieYes and Cookiequiet store the choice in different cookies, so returning visitors see the new banner once. Asking again when the consent tool changes is normal, and the new log records the new choice.

### Can I run both tools during a transition?

Avoid it. Two banners confuse visitors and both tools try to control the same tags. Prepare the markup changes first, then replace the script in a single deployment.

### I used the CookieYes WordPress plugin. What changes?

Deactivate and remove the plugin, then add the Cookiequiet snippet through your theme or a header script option, as described in the WordPress platform guide. Scripts the plugin blocked by URL pattern are handled by the auto-blocker or by marking.

### Do my pageviews matter on Cookiequiet?

No. There is no pageview or banner-view limit on any plan, including Free. Plans differ by features such as log retention, CSV export, weekly rescans and languages for the policies.

## Sources

- [CookieYes documentation, How to implement prior consent and cookie auto-blocking](https://www.cookieyes.com/documentation/implement-prior-consent-using-cookieyes/)
- [CookieYes pricing page (checked 20 October 2026)](https://www.cookieyes.com/pricing/)
- [Google, Set up consent mode on websites](https://developers.google.com/tag-platform/security/guides/consent)