Termly Compliance Checker Verify Your Setup Is Working
Termly is a trusted consent management platform popular with US businesses, agencies, and content publishers. Installing Termly was the right first step - but site changes, new plugins, and GTM deployments can introduce tracking gaps that Termly cannot detect from inside your configuration.
We work alongside Termly - not against it
Termly manages your consent banner and cookie categories. We independently verify the outcome in a real browser - finding what breaks between Termly scans as your site evolves.
What we verify that Termly alone cannot confirm
Six checks that require independent browser-based observation to confirm your Termly implementation works in practice.
| Check | Why Termly alone cannot confirm it |
|---|---|
| Pre-consent cookies | Termly auto-blocks scripts it has scanned and categorized. Scripts added to your site after Termly's last scan, or scripts loaded via tag manager rules without consent triggers, can fire before consent. |
| Google Consent Mode v2 signals | Termly supports Consent Mode integration. Verifying the signals initialize correctly before GTM loads, include all 4 v2 signals, and update correctly after each consent action requires external browser testing. |
| Reject All enforcement | A theme update, new plugin installation, or GTM tag added after Termly's last cookie scan introduces unblocked tracking. Termly's scan schedule may not catch it immediately. |
| GPC signal handling | Testing GPC compliance requires a real browser session with navigator.globalPrivacyControl = true - a configuration review of Termly's settings cannot confirm runtime behavior. |
| Dark pattern checks | Termly's banner builder offers multiple layout presets. Whether the final deployed banner presents Accept and Reject with equal prominence and avoids pre-ticked boxes requires visual inspection in a real browser. |
| Multi-region behavior (up to 15 regions) | Termly can show different banners to EU vs US visitors. We test from actual jurisdiction IPs to confirm geo-targeting works as configured and the correct banner displays in each region. |
How we detect Termly on your site
Four fingerprint signals confirm Termly is present and active.
JavaScript globals
displayPreferenceModal, Termly
DOM elements
#termly-code-snippet-support, .termly-styles-container, #termly-consent-banner
Consent cookies
termly-consent (stores category Accept/Reject state)
Script domains
app.termly.io, embed.termly.io
See all 40+ supported CMPs: Supported CMPs
Verify your Termly configuration works end-to-end
Cookie Compliance Checker is launching soon. Join the waitlist for early access and be among the first to scan your site.