Categories and scripts
Every script, iframe, image and request a third party adds to your pages belongs to a category, and the visitor's choice decides each category. ConsentAlly recognises common trackers by their addresses, holds anything else from another site as marketing, and releases what the visitor allows without reloading the page.
Categories
| Category | What it covers |
|---|---|
| Necessary | What the site needs to work. Always on: the visitor cannot turn it off. |
| Functional | Remembering the visitor's choices, such as language or region. |
| Analytics | Measuring how the site is used. |
| Marketing | Advertising and its measurement, and every script ConsentAlly does not know. |
A configuration can hold up to eight custom categories. Give a custom category a purpose (functional, analytics or marketing) and Google Consent Mode and Shopify treat it as that purpose; without one, Global Privacy Control counts it as marketing and it sets no Consent Mode type. Where each category starts before the visitor chooses comes from the rules for the visitor's region.
Vendors
A vendor is a company behind one or more scripts, listed in your configuration under the category it belongs to. The preference centre can show each vendor, so a visitor can allow a category but refuse one vendor in it. This is how a vendor is described in your published configuration:
{ "id": "meta", "name": "Meta Pixel", "category": "marketing", "privacyPolicyUrl": "https://www.facebook.com/privacy/policy/", "saleShare": true, "cookies": ["_fbp", "_fbc"]}-
saleSharemarks a vendor that sells or shares personal data: the visitor's Global Privacy Control signal and an opt-out deny it. -
cookieslists the first-party cookie names the vendor sets; a trailing*matches every name that starts with the rest, as in_ga_*. When the visitor withdraws the vendor, the widget deletes the matching cookies it can see, on your site's host and every parent domain.
How a script is classified
Each address a script, iframe, image or request asks for is checked in this order:
- ConsentAlly's edge always loads.
-
A known tracker is held under its category until the visitor allows it. The built-in list covers Google Analytics, Google Ads, Floodlight, Meta, TikTok, Microsoft UET and Clarity, Klaviyo, Hotjar, Pinterest, Snap, LinkedIn, Reddit, X, Criteo and Shopify's own analytics. Two entries load at once: Google Tag Manager's container and Shopify's platform hosts. Once your configuration arrives, the payment and anti-fraud scripts a checkout needs (Stripe, PayPal, Braintree, Adyen, Klarna Payments, Mollie, Square, Google Pay and Apple Pay) and the captchas (Google reCAPTCHA, hCaptcha and Cloudflare Turnstile) load too, without their analytics or promotional parts.
-
Your own site loads: the page's host and the domains in your configuration, each with its subdomains.
-
Anything else from another site is treated as marketing: it is held until the visitor allows marketing.
A classification (an address and a category) wins over a known tracker only when it is at least as
specific, and a necessary classification never releases a known tracker. A classification that
holds always wins over the entries that load at once, payment and captcha scripts included. An address is matched by its host (a
domain and its subdomains), by host and the start of its path, or by a path on any host.
Held, then released
ConsentAlly holds the scripts, iframes and images added after its script, however the page adds
them: by setting src, by setAttribute, through an HTML string or in the page's own markup. It
holds fetch, XMLHttpRequest and sendBeacon calls too. A held request fails the way an ad
blocker makes it fail, and is not sent later.
When the visitor allows a category, what was held in it loads where it was put, in order, without a page reload, and later requests go through, unknown scripts held as marketing included. When the visitor refuses one of a category's vendors, the category is released vendor by vendor instead: its allowed vendors load, and the refused vendor and anything in that category that belongs to no vendor of your configuration stay held.
Video and map embeds
Before the visitor allows them, YouTube and Vimeo players (marketing) and Google Maps embeds (functional) show a placeholder in their own box: the provider's name, what loading it allows and a Load button, in the banner's language. Pressing Load is the visitor's choice: it allows that category on the site and loads the embed where it is. Any other held iframe stays an empty box until the visitor allows its category.
What is not held
A few kinds of request reach the network without passing through ConsentAlly:
- stylesheet and preload links and media written in the page's own HTML, fonts and CSS
url()and@import, andembedandobjectelements; - images in
srcsetandpicturesources, and static images and iframes the browser fetches before ConsentAlly sees them; - WebSockets,
EventSource, the requests web workers and service workers make, and modules an allowed script imports (import()gives a page no element or request to watch); - form posts, navigation and link pings;
- first-party proxies (a server-side tag manager on your subdomain, Shopify app proxies and app scripts on Shopify's CDN), except Google's standard tag paths (
/gtag/js,/g/collect), which are held as Google Analytics on any host; - any tag that runs before ConsentAlly's script.
The Limitations page lists what ConsentAlly does not do.
Scripts ConsentAlly does not know
Each time the page is hidden or left, the widget reports the unknown third parties it found since the last report: scripts, iframes, images and requests, held or loading after the visitor allowed them. Each goes as its origin and path only (a request or embed by its first folder), never a query, and no visitor identifier, at most 20 at a time. They are added to your store's script list with what they are and the page they were first seen on, and your store's contact gets one email a day listing new ones. Until you classify one, it is treated as marketing: held until the visitor allows marketing.
Tracker data sources
A script the built-in list does not cover can be recognised by ConsentAlly's tracker library, built from open data: the Open Cookie Database (Apache-2.0) and tarteaucitron.js's service list (MIT). Your Scripts screen names a recognised script and its source. The library sets a category on its own only where that holds the script back at least as much as treating it as unknown would, or where the data is confirmed: marketing always, analytics where both sources agree or the entry has been reviewed, functional only once reviewed, and never necessary. Your own category always wins.