GDPR · revFADP · Consent Mode v2
A banner that does not only talk to Google. Meta Pixel, TikTok, Clarity and anything without a consent API stay put until the visitor decides — and all of them start the instant they accept.
Consent Mode is a conversation with Google and nobody else. If the notice says _fbp waits for consent and the pixel ignores it, the document is describing the breach. QS Cookies uses three mechanisms, chosen service by service.
| Mechanism | For whom | What happens |
|---|---|---|
| Consent Mode v2 | GA4, Google Ads, Floodlight, DV360 | The signals go out before any tag, with the defaults denied. |
| The provider's API | Meta Pixel, Clarity, Microsoft Ads, Matomo | The banner calls the vendor's own API on every decision, revocation included. |
| Blocking | TikTok, LinkedIn, Pinterest, Hotjar, YouTube, Maps | The script never runs and the iframe has no address at all: nothing reaches the vendor. |
The banner is the part you see. Underneath are the documents and the proof.
Tick the services the client actually uses and out come the cookie policy, the privacy notice and the record of processing, in Italian and English, under the GDPR or the Swiss revFADP. Change a service and the version goes up: the banner asks again on its own.
Every choice leaves a receipt with the date, the categories and the notice version, exportable as CSV. With no IP addresses: a visitor's consent should not leave more behind than it has to.
Each client has their own details, their own banner and their own public pages. You can give them a login too: they see their own dossier and their own receipts, and can change nothing.
The script goes in <head>, as high as it will go: it is the line that tells everything else to wait.
<script src="https://qscookies.mgquantumsystems.com/embed/CHIAVE.js"></script>
The controller's details and the third-party services they use. The catalog knows 96, Swiss ones included.
On WordPress there is a plugin: origin and key, and you never touch the theme.
The panel tells you which ones must be blocked, and hands you ready-made code for the common ones.
Signing in is for whoever manages the clients. If you are a client and were given a login, this is the way in.
Sign in