Switch from iubenda to Cookiequiet

Switching from iubenda to Cookiequiet means replacing iubenda's snippet in the head with one Cookiequiet script tag, converting the tags you blocked manually (class _iub_cs_activate with data-iub-purposes) to Cookiequiet's data-cq-category attribute, moving suppressedsrc URLs back to src on scripts and to data-cq-src on iframes, and pointing the "Your Privacy Choices" link at the new preferences centre. For most sites that is half an hour. Visitors are asked once more, because iubenda stored their choice in its own format.

Why people switch

iubenda prices by pageviews. On its pricing page (checked on 20 October 2026), Essentials costs €5.99 per site per month, or €4.99 billed yearly, for 25,000 pageviews; Advanced €21.99, or €19.99 yearly, for 50,000; Ultimate €89.99, or €79.99 yearly, for 150,000, then €0.05 per extra 1,000 pageviews. Geo-targeting and every language start at Advanced. Cookiequiet has no pageview limit on any plan, geo-targeting and 24 banner languages on the free plan for one website, and Starter at €3 per website per month. The comparison page has the details, and the cost calculator compares totals for your traffic.

How do iubenda's purposes map?

iubenda's manual tagging uses purpose IDs in data-iub-purposes:

When a tag lists several purposes (for example "4, 5"), choose the stricter one, marketing, because Cookiequiet uses one category per tag.

What changes in the markup?

iubenda's guide to manual tagging tells you to change type to text/plain, add the class _iub_cs_activate, add data-iub-purposes, and optionally move src to suppressedsrc or data-suppressedsrc. Cookiequiet reads neither the class nor the purposes attribute nor suppressedsrc, so each tag needs three edits.

An external script blocked for iubenda:

html
<script type="text/plain" class="_iub_cs_activate" data-iub-purposes="4"
  suppressedsrc="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXX"></script>

The same script for Cookiequiet:

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

The browser does not execute a script whose type is text/plain; Cookiequiet activates it when the category is granted. Inline scripts work the same way: keep type="text/plain", replace the class and purposes with data-cq-category.

An iframe blocked for iubenda has src="about:blank" and the real URL in suppressedsrc. For Cookiequiet, remove the about:blank source and put the real URL in data-cq-src:

html
<iframe data-cq-src="https://www.youtube-nocookie.com/embed/VIDEO_ID"
  data-cq-category="marketing" width="640" height="390" title="Video"></iframe>

Tags that iubenda's automatic blocking held without any markup are covered by Cookiequiet's auto-blocker when the host is among the about 80 trackers in its provider database; mark anything else by hand. The script blocking guide has the four methods.

What else needs rewiring?

• The preferences link. iubenda reopens preferences from elements with the class iubenda-cs-preferences-link or the openPreferences() API method. Give the footer link data-cq-show-preferences instead, or point it to #cq-preferences. Keep the "Your Privacy Choices" label if you show it to US visitors.
• Google Consent Mode. If iubenda sent Consent Mode signals, the Cookiequiet snippet from the dashboard does the same with data-consent-mode="1"; keep the Google tag after it. See the Consent Mode guide.
• Tag Manager triggers. Replace triggers on iubenda events with the cq_consent dataLayer event and its cq_analytics, cq_marketing and cq_functional flags.
• Policies. If iubenda hosts your privacy and cookie policies, keep them until replacements are ready. Cookiequiet generates privacy, cookie and terms pages from a questionnaire prefilled by the scan, in English and French; they are templates, not legal advice.
• Consent records. Export what iubenda's dashboard offers before closing the account; choices made under the old banner are proven by the old records.

Removing iubenda

iubenda's installation guide asks for its snippet to be pasted into the head as the first element. Remove that snippet, or deactivate and delete the iubenda plugin on WordPress and other CMSs, in the same release that adds the Cookiequiet snippet in the same place. Running both shows two banners and lets two tools fight over the same tags.

After the switch

In a private window, check that no analytics or advertising request leaves the browser before a choice, that nothing new appears after Reject all, and that everything loads after Accept all. A scan should list Cookiequiet as the only consent tool and detect Consent Mode. Setup is one script tag before your other scripts, with Reject all on by default, the cookie table filled from the scan, and about five minutes from sign-up to a live banner; pricing lists what each plan adds.