# Switch from iubenda to Cookiequiet

> Move a site from iubenda to Cookiequiet: map purposes 1 to 5 to four categories, convert _iub_cs_activate tags and suppressedsrc embeds, swap the snippet.

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

## Steps

1. **Add the site and scan it** Create the website in Cookiequiet and run the scan to fill the cookie table and list the trackers.
2. **Convert blocked scripts** On each _iub_cs_activate script, replace the class and data-iub-purposes with data-cq-category, and move suppressedsrc back to src. Map 2 and 3 to functional, 4 to analytics, 5 to marketing.
3. **Convert blocked iframes** Remove src about:blank, move suppressedsrc to data-cq-src and add data-cq-category.
4. **Rewire the preferences link** Replace the iubenda-cs-preferences-link class or openPreferences call with data-cq-show-preferences.
5. **Swap the snippets in one release** Remove the iubenda snippet or plugin and paste the Cookiequiet snippet first in the head, before the Google tag.
6. **Verify** Check the three paths in a private window, run a scan, and update policy links.

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](/vs/iubenda) has the details, and the [cost calculator](/tools/cookie-banner-cost-calculator) compares totals for your traffic.

## How do iubenda's purposes map?

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

| iubenda purpose | Cookiequiet category |
|---|---|
| 1, Necessary | necessary (leave the tag unmarked) |
| 2, Functionality | functional |
| 3, Experience | functional |
| 4, Measurement | analytics |
| 5, Marketing | marketing |

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](/guides/block-scripts-until-consent) 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](/guides/google-consent-mode-v2).
- **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](/pricing) lists what each plan adds.

## Questions

### Does Cookiequiet understand iubenda's _iub_cs_activate markup?

No. It reads its own data-cq-category attribute and a few attributes other banners use, but not iubenda's class, purposes attribute or suppressedsrc. Each manually tagged script or iframe needs the edits described above.

### How do iubenda's five purposes fit into four categories?

Necessary stays necessary and unmarked, functionality and experience become functional, measurement becomes analytics, and marketing stays marketing. A tag with several purposes takes the strictest one.

### Will visitors have to consent again?

Yes. iubenda stored the choice in its own cookie, which Cookiequiet does not read, so each returning visitor sees the banner once. The new consent log records each new choice.

### Does the pageview count matter after switching?

No. Cookiequiet has no pageview or banner-view limit on any plan, including the free plan for one website. Plans differ by features such as log retention, weekly rescans, AI brand match and the AI design agent.

## Sources

- [iubenda pricing page (checked 20 October 2026)](https://www.iubenda.com/en/pricing)
- [iubenda Help, Prior blocking of cookies: manual tagging](https://www.iubenda.com/en/help/1229-manual-tagging-blocking-cookies/)
- [iubenda Help, Privacy Controls and Cookie Solution: custom website installation guide](https://www.iubenda.com/en/help/36226-cookie-solution-custom-website-installation-guide/)
- [iubenda Help, How to configure your Privacy Controls and Cookie Solution (advanced guide)](https://www.iubenda.com/en/help/1205-how-to-configure-your-cookie-solution-advanced-guide-2/)
- [iubenda Help, How to disable the iubenda privacy widget and add a footer link](https://www.iubenda.com/en/help/164180-how-to-disable-the-iubenda-privacy-widget-and-add-a-footer-link/)