The trackers are not on your site until someone agrees
Most cookie banners work by stepping in front of code that is already sitting in your website, trying to hold it back at the last moment. Consentify does something simpler: your analytics and advertising tools are not in the page at all until a visitor accepts. There is nothing to hold back, because there is nothing there yet.
Why the usual approach leaks
If a tracking script is written into your HTML, it wants to run the moment the browser reaches it. A cookie tool that tries to stop it is in a race, and it does not always win. A slow connection, a script that loads a fraction earlier than expected, or a tag added by a colleague who did not know about the rules, and the tracker fires before anyone was asked.
That is also why those tools need to crawl your website every month. They cannot know what is on your pages, so they go and look, and your cookie declaration is only as current as the last crawl.
What we do instead
You give us the measurement ID for your analytics or advertising tool once, in your dashboard. We keep it. Your website only ever loads one script, ours. Nothing about Google Analytics or Meta exists in your page until the visitor accepts, and at that point we add it.
Turn a tool off, or a visitor declines, and the code is simply never written. Not blocked, not delayed, not there.
What this changes for you
No race to lose
A tracker that has not been added cannot fire early. There is no timing to get right and nothing that can slip through on a slow connection.
No crawler guessing at your site
We know what is configured because you told us, so your cookie declaration is built from fact rather than from a monthly visit that may have missed a page.
Colleagues cannot undo it by accident
Someone pasting a tag straight into the site is the most common way consent setups break. If the tools live with us, there is nothing in the page for them to paste next to.
One script instead of many
Your pages load our script and nothing else until consent, which is usually faster than loading a cookie tool plus every tracker it is trying to hold back.
Where this does not reach, and what we do about it
Gated consent covers anything you configure through us. It cannot cover code you paste into your own pages, because we never see it. If you add a tracking pixel directly to your HTML, it is yours to manage.
There is one case where you have no choice. A YouTube video or a booking widget has to sit in your markup, because it belongs in a particular place on a particular page and we cannot know where. For those we do block, in the browser, the way other tools do. That is the one exception, and it is deliberate.
How embedded videos and widgets are handledFor developers
The gateway builds a per-domain script and caches it. Integration IDs are encrypted at rest and decrypted only while the bundle is generated. The bundle carries the tracker snippets as inert strings and evaluates them in activateScripts() once the stored consent covers their category, so nothing is appended to the document before that.
Google tags are the one thing that can start earlier, and only if you switch on advanced Google Consent Mode. That is off by default. When it is on, the tags load in cookieless mode with every consent signal denied, which is what makes conversion modelling work without storing anything.
Embedded content is handled separately by the embed guard, which watches the document as it parses and pulls matching iframes before the browser fetches them.
Does any of this apply to your site?
Find out in ten seconds. The scan shows which trackers fire before your visitors have agreed to anything.
- Results in about 10 seconds
- No account needed
- Shareable report link
See what is loading on your site right now
Our scanner checks any site for trackers that fire before consent. It takes a few seconds and needs nothing installed.
- 1 domain
- 5,000 pageviews/mo
- All integrations
- GDPR, CCPA and ePrivacy