Everything you need to get ConsentMonitor working for your sites.
Four steps from sign-up to your first automated check.
Sign up
Create your account at consentmonitor.com. Magic link or Google — no password needed.
Create an organization
An organization is your workspace — it groups your domains, team members, and billing. You can belong to multiple organizations, which is useful if you manage several clients.
Add a domain
Add the root domain you want to monitor (e.g. example.com). If you signed up with a business email, ConsentMonitor may suggest it automatically. You can always add it manually.
Add a page
A page is a specific URL to check — a homepage, a checkout, a product listing. Give it a name and paste the full URL (https://example.com/checkout). That's what gets monitored.
ConsentMonitor visits your pages using a headless browser — no cookies, no session, exactly like a first-time visitor. Nothing is installed on your site. Checks run automatically at your plan's frequency.
Each check follows five steps, in order:
Each check produces a pass or fail verdict, with a breakdown of what was found.
The six summary cards at the top give you a quick read:
Below the cards, violations are grouped by vendor — requests and cookies in separate sections. Expand a vendor to see which exact hostnames fired and when. At the bottom of a failed check, ConsentMonitor generates a suggested remediation your analytics or dev team can act on directly.
A screenshot is taken at check time so you can confirm the banner was actually visible when the check ran.
When a check finds violations, organization members receive an email alert with a direct link to the check result.
To stop receiving alerts for a specific page, pause it from the Pages list. Pausing stops both the automated checks and the alerts — the page won't be monitored until you resume it. Useful during a deployment when you know things are temporarily broken and don't want noise.
You can resume a page at any time. Historical check data is preserved either way.
You don't need to track every URL on your site. Consent issues surface most on landing pages — the URLs where visitors arrive for the first time and see the consent banner. Those are the pages that matter for compliance.
The quickest way to get that list: open Google Analytics 4 → Reports → Engagement → Landing page, sort by sessions. The top 10–20 typically cover the vast majority of your traffic and give you solid coverage without going overboard.
Not sure where to start? Email [email protected] and we'll help you put the list together.
Standard plans run checks weekly (Free), daily (paid tiers), or hourly (Enterprise). Page limits follow the same tiers — Free comes with a handful, paid plans scale up from there.
If you're managing a large number of pages across multiple client domains, or need a frequency that doesn't fit the standard options, we can put together something custom. Agencies monitoring dozens of sites tend to need this kind of arrangement.
Get a quoteA check error means ConsentMonitor couldn't complete the check at all — not that a violation was found. These are infrastructure-level failures, not compliance results.
Page load failed
The page was unreachable or timed out. Common causes: the URL changed, the page requires authentication, or a firewall is blocking our checker's IP range.
If you suspect a firewall issue, contact [email protected] — we can provide the IP range to allowlist so checks go through cleanly.
Browser crashed
An internal error occurred during the check. This is usually transient — the next scheduled check will likely succeed on its own.
If it keeps failing on the same page, send the check ID (visible at the top of the check detail page) to [email protected] and we'll dig in.