# Switch from Termly to Cookiequiet

> Move a site from Termly to Cookiequiet in about 30 minutes: remove the resource blocker, re-mark data-categories scripts and data-src embeds, rewire the link.

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

## Steps

1. **Add the site and scan it** Create the website in Cookiequiet and run the scan; it fills the cookie table and lists the trackers to check.
2. **Re-mark blocked scripts** On each script with data-categories, replace that attribute with data-cq-category, using the mapping: performance to functional, advertising and social networking to marketing.
3. **Rename embed attributes** On blocked iframes, rename data-src to data-cq-src and add data-cq-category.
4. **Rewire the preferences link** Replace the termly-display-preferences class or displayPreferenceModal call with data-cq-show-preferences.
5. **Swap the scripts in one release** Remove the Termly resource blocker tag 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 Termly to Cookiequiet takes about half an hour on a typical site. You remove Termly's resource blocker script, add one Cookiequiet script tag in its place, change the `data-categories` attribute on any scripts you blocked by hand to `data-cq-category`, rename `data-src` to `data-cq-src` on blocked embeds, and point the "Cookie preferences" link at the new preferences centre. Returning visitors see the banner once more because their choice was stored by Termly. Do the markup changes first and swap the scripts in one release, so visitors never see two banners.

## Why people switch

Termly limits banner views. On its pricing page (checked on 20 October 2026), the free plan includes one policy, 10,000 banner views a month and quarterly scans; Starter costs $14 per website per month, or $10 billed yearly, for 50,000 banner views; Pro+ costs $20 per website per month, or $15 yearly, for unlimited views, and Consent Mode v2, logo removal and regional rules are only on Pro+. Cookiequiet has no pageview or banner-view limit on any plan: free for one website with geo-targeting and Consent Mode v2 included, Cookiequiet's Starter at €3 per website per month or €29 a year. The [comparison page](/vs/termly) has the feature table, and the [cost calculator](/tools/cookie-banner-cost-calculator) works out the difference for your number of sites.

## How is Termly installed?

Termly's documentation says its consent banner embed must be loaded before all other scripts, so that its Auto Blocker can intercept them. The embed loads a resource blocker from `app.termly.io/resource-blocker/` followed by your website's ID, with `?autoBlock=on` when automatic blocking is enabled. On WordPress it is often installed through Termly's plugin; with Google Tag Manager, Termly recommends placing the script on the page before the container. That is the tag (or plugin) you remove.

## How do categories map?

Termly's manual blocking uses six categories: essential, performance, analytics, advertising, social networking and unclassified. Cookiequiet has four:

| Termly category | Cookiequiet category |
|---|---|
| essential | necessary (leave the script unmarked) |
| performance | functional |
| analytics | analytics |
| advertising | marketing |
| social networking | marketing |
| unclassified | classify it, or marketing to be safe |

Termly describes its "performance and functionality" cookies as improving the site without being essential, which is Cookiequiet's functional category; its "analytics and customization" category maps to analytics. Social media embeds and share widgets that track visitors belong in marketing.

## What changes in the markup?

Termly's manual blocking sets `type="text/plain"` and adds a `data-categories` attribute. Cookiequiet does not read `data-categories`, so add its own attribute:

A script blocked for Termly:

```html
<script type="text/plain" data-categories="analytics"
  src="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 `type` stays `text/plain`, so only the attribute changes. For embeds, Termly renames `src` to `data-src`; Cookiequiet uses `data-cq-src`:

```html
<iframe data-cq-src="https://www.youtube-nocookie.com/embed/VIDEO_ID"
  data-cq-category="marketing" title="Product video"></iframe>
```

Scripts that Termly's Auto Blocker 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) covers all four methods.

## What else needs rewiring?

- **The preferences link.** Termly opens its preference modal from elements with the `termly-display-preferences` class or a call to `displayPreferenceModal()`. Replace them with an element carrying `data-cq-show-preferences`, or a link to `#cq-preferences`.
- **Google Consent Mode.** Add `data-consent-mode="1"` to the Cookiequiet snippet (the dashboard's snippet includes it) and keep the Google tag after it. See [the Consent Mode guide](/guides/google-consent-mode-v2).
- **Tag Manager triggers.** Triggers that waited for Termly's consent should wait for the `cq_consent` dataLayer event with the matching flag (`cq_analytics`, `cq_marketing`, `cq_functional`).
- **Policies.** If Termly hosted your privacy or cookie policy, generate new ones from the Cookiequiet scan and update the footer links, or keep the Termly policy until the new ones are reviewed.

## The migration, step by step

The numbered steps below are the whole job. Keep the Termly account open for a week in case you need to roll back, and export what Termly offers of your consent records before closing it: choices made under the old banner are proven by the old records.

## After the switch

Open the site in a private window: no analytics or advertising request before a choice, nothing new after Reject all, everything after Accept all. Run a scan to confirm Cookiequiet is the only consent tool detected and that Consent Mode is present. Setup itself is one script tag before your other scripts, with Reject all on by default and the cookie table filled from the scan; the [pricing page](/pricing) lists what each plan adds.

## Questions

### Will my Termly-marked scripts work with Cookiequiet without changes?

Not quite. They already have type text/plain, but Cookiequiet does not read Termly's data-categories attribute. Replace it with data-cq-category and the matching category, and rename data-src to data-cq-src on embeds.

### Do visitors have to consent again?

Yes. Termly stored their choice in its own format, which Cookiequiet does not read, so returning visitors see the new banner once. That is normal when the consent tool changes, and the new log records each new choice.

### Is geo-targeting included on Cookiequiet's free plan?

Yes. Every plan, including the free one for one website, can show the banner only in regulated regions and an opt-out notice in US states with a privacy law. Termly lists regional rules on its Pro+ plan.

### Can I keep my Termly privacy policy?

You can keep it while you prepare a new one, but it may stop being updated once you cancel. Cookiequiet generates privacy, cookie and terms pages from a questionnaire prefilled by the scan; they are templates to review, not legal advice.

## Sources

- [Termly pricing page (checked 20 October 2026)](https://termly.io/pricing/)
- [Termly Help Center, Auto Blocker implementation guide](https://support.termly.io/hc/en-us/articles/30710482292881-Auto-Blocker-implementation-guide)
- [Termly Help Center, Blocking JavaScript third-party cookies manually](https://support.termly.io/hc/en-us/articles/30710536446993-Blocking-JavaScript-third-party-cookies-manually)
- [Termly Help Center, How can I let my users manage their cookie preferences?](https://support.termly.io/hc/en-us/articles/30710537528977-How-can-I-let-my-users-manage-their-cookie-preferences)
- [Termly Help Center, How to use Termly with Google Tag Manager](https://support.termly.io/hc/en-us/articles/30710480660881-How-to-use-Termly-with-Google-Tag-Manager)
- [Termly Help Center, Understanding the different types of cookies (the six categories)](https://support.termly.io/hc/en-us/articles/30710498728849)