Platforms
you already have.
Nineteen platforms on day one. A plugin on WordPress, one line of code on most of the rest, and nothing at all for accessibility monitoring. If your practice website runs somewhere that is not on this page, the scan still works and the install usually does too.
No developer. No theme rebuild. No change to how your site looks.
Accessibility monitoring needs nothing installed.
The accessibility module reads your website from the outside, the way a browser does. There is no script to add, no plugin to keep updated, and no platform requirement at all. It runs on every platform on this page, and on every platform that is not.
Which means you can see what your site is doing before you decide anything.
The free scan works on any site, on any platform, today.
What the install does
Three jobs, wherever your site lives.
The consent module does the same three things on every platform. Only the third one changes shape depending on what the platform lets us reach.
Holds the tags
Non-essential tracking stays off until a patient answers. On WordPress the tags are rewritten server-side, before the browser ever sees them.
Writes the record
Every answer lands in an append-only log with a policy version, a timestamp and a jurisdiction. The database refuses updates and deletes at the permission level.
Signals Consent Mode v2
Google's own tags read the consent state we set, so analytics and ads honour a patient's answer on any platform, not only the ones with a plugin.
Available now
Platforms we install on today.
Every platform below has a documented, supported place to put site-wide code, which is all the consent module needs. The ones marked Plugin go further and hold a practice's existing tags server-side.
Websites and content platforms 8
-
WordPress Plugin Plugin. Any theme or builder, Elementor and Divi included.
-
WooCommerce Plugin Same plugin as WordPress, storefront included.
-
Squarespace Code Injection, site-wide header.
-
Wix Custom Code panel, applied to all pages.
-
Webflow Site-wide custom code in the head.
-
Ghost Code injection, site header.
-
Duda Site-wide header code.
-
Framer Custom code, head.
Funnels and landing pages 6
-
GoHighLevel Head tracking code, sites and funnels.
-
ClickFunnels Tracking code, head.
-
Unbounce Script Manager.
-
Instapage HTML or JavaScript in the head.
-
Leadpages Analytics and head scripts.
-
Kajabi Site header code.
Ecommerce 2
-
Shopify theme.liquid, plus the Customer Privacy API.
-
BigCommerce Script Manager, all pages.
Marketing platforms and code 3
-
HubSpot CMS Site header HTML.
-
Google Tag Manager Custom HTML tag, on any CMS.
-
Next.js and React One script tag, or the npm package.
What you get where
The honest version of "works with".
Consent box, record, and state notice
The patient-facing choice, the append-only consent event, and the state-specific notice where one applies.
Google Consent Mode v2 signalling
Consent state is set before Google's tags read it, so GA4 and Google Ads honour the answer.
Accessibility monitoring
WCAG 2.1 A and AA checks across your real pages, with the conversion path prioritised. Nothing is installed.
Server-side tag holding
Your existing GA4, Meta Pixel and other tags rewritten in the page the server sends, so a tag cannot fire before a patient answers.
Announcing Q4 2026 through Q2 2027
Native apps and modules, quarter by quarter.
Everything above installs today. These go further: a marketplace install instead of a code paste, and server-side tag holding on platforms a script cannot reach on its own. Native marketplace apps for Shopify, Wix and Webflow land in the same window.
Q4 2026
Drupal
Joomla
Cloudflare
Segment
Q1 2027
Adobe Commerce
Craft CMS
Salesforce
Tealium
Q2 2027
TYPO3
Umbraco
PrestaShop
Piwik PRO
What we will not claim on this page
"Works with" is doing a lot of work on most vendors' platform pages, so here is the line. WordPress is the only platform where we hold a practice's pre-existing tracker tags server-side today. On every other platform the consent box, the record, the state notice and Consent Mode v2 all work from day one, and tags installed through the platform's own integrations or through Google Tag Manager are governed by that consent state.
A tag hard-coded into a theme on a platform without a plugin is the gap, and it is the gap the roadmap closes. If you want to know which case your site is in, run the scan. It will tell you what is actually firing and when, which is a better answer than anything on this page.
Consential documents findings and the fix path. It does not apply fixes to your site, and using it does not guarantee compliance with any regulation.
Find out what your site is doing right now.
The scan takes about twenty seconds, needs nothing installed, and names every tracker that fires before a patient has answered anything.
Your platform is not listed? Tell us what you run. It is usually a one-line install.