Consent management
Your website is telling ad platforms who's asking about a procedure.
Not your booking system. Not your EHR. Your public website.
A request to that URL is not a neutral page view.
What happens between the click and the page
One page load, watched in real time.
By the time your cookie notice renders — if you have one — the disclosure has already happened.
Why the usual fix isn't one
Most cookie banners announce the problem. They don't stop it.
It's a notice, not a gate
Display-only banners tell a visitor that tracking exists. They don't hold the scripts. The tags fired while the banner was still rendering, and the click changes nothing about what already left.
It doesn't know your pages carry health intent
General-purpose consent tools were built for retail and publishing. They treat a treatment page and an About page identically, because in every other industry they are identical.
It leaves no record you can produce
A cookie set in the visitor's own browser is not documentation. If someone asks what a specific visitor was shown and what they chose on a specific date, a browser cookie cannot answer — and the visitor cleared it in March anyway.
Google Consent Mode v2 is the mechanism a linked Google Ads account uses to interpret consented and non-consented traffic. Google Signals stopped acting as a backstop on 15 June 2026. Before that date, a missing consent signal degraded your reporting. After it, the platform has nothing to model from — the compliance-correct configuration and the performance-correct configuration are now the same configuration.
The honest test
Three questions most practices can't answer.
What is firing on my site right now?
Not at launch — right now. Sites drift. A plugin update adds a pixel, a new landing page ships with a stray tag, someone installs a chat widget on a Friday. The ad platforms, analytics and call tracking tools a practice runs each arrive by their own route. The list you approved and the list that runs are two different lists, and nothing tells you when they diverge.
What did this visitor see, and what did they choose, on this date?
A defensible answer is a timestamped row with the banner version, the categories offered, and the choice made. Not a screenshot of what the banner looks like today.
When a patient withdraws consent, does anything downstream actually change?
In most setups the pixel stops and the CRM keeps going. The record that started life as a consented lead stays in the nurture sequence, because nothing told the CRM the answer changed.
The identical page, with Consential installed
One gate on the way in. One record on the way out.
Non-essential tags are held before they execute, not asked to behave afterward — and the choice is written to a log where UPDATE and DELETE are revoked at the database permission level.
Two more things per scan cycle
The configuration stays honest on its own.
A consent layer is only accurate on the day it's configured. Two checks ride the regular scan cycle so it stays accurate afterward — neither requires anyone to remember anything.
Banner covers six trackers. Scan finds nine.
Every cycle observes the scripts, pixels and cookies actually loading and compares them against what your consent configuration declares. The gap appears in the report.
When no configuration has been supplied it says so, rather than reporting all clear. A false all-clear never gets investigated.
Read the policy, check the date, name the gaps.
The same cycle reads your policy page and flags when it hasn't been revised in over a year, when it names vendors no longer on the site, when vendors are on the site but absent from the policy, and when state privacy laws have taken effect since its last revision date.
These are recorded as observations. Whether any of them is a legal problem is your counsel's call, not ours.
Consential is consent infrastructure. It is not a law firm, it does not provide legal advice, and installing it does not by itself satisfy HIPAA, any state privacy law, or any other regulation. What it does is make your posture real and documented instead of assumed, within limits we publish rather than bury. Your counsel should review your consent language before it goes live.
No signup
Find out what your site is actually doing.
The scanner loads your site fresh in a real browser and reports what fires before any consent interaction — named tags, named cookies, with timestamps. It tells you where you stand before anyone tries to sell you anything. You can also watch the consent box work on this site, or read what it costs per practice.