I need a full CMP (banner + consent logs + scanner)
You probably need HubSpot. CookieInspector doesn't replace your banner — but you can layer us on top for independent audit evidence. See "How to layer CookieInspector on top of HubSpot" below.
Honest comparison
HubSpot Scanner Alternative: CookieInspector Compared
HubSpot's cookie banner comes free with your subscription and does a good job of gating HubSpot's own tracking. What it does not do is tell you what else fires on your pages. HubSpot has no cookie scanner, so the banner is configured from a list you maintain by hand — and anything added outside HubSpot stays invisible to it. CookieInspector is the audit layer: it loads your site in a real browser, records every request and cookie before consent, and shows you what your banner is actually holding back.
Last reviewed · August 2026
Pick the path that fits
Which case describes you?
I only need scanning, auditing, and monitoring
Many teams pay for HubSpot just to use the scanner. If you don't need a TCF-certified banner or consent logs, CookieInspector replaces the scanning component at a fraction of the cost.
Pricing at a glance
HubSpot
Included with your HubSpot subscription — there is no separate CMP fee. The banner is available from the free tier up; region-specific banners and finer customization sit on higher tiers. HubSpot itself is priced per hub and per seat, which is out of scope here.
CookieInspector
Free: 1 scan per domain, 1 page, 45s, summary-only. Pro/Team: $9.99/mo billed annually (or $11.99/mo monthly) — unlimited domains, AI insights, scheduled monitoring, up to 5 monitored sites, Notion/Confluence exports. Agency: custom.
Feature-by-feature
Where each product focuses, without pretending we do the same job.
| Feature | HubSpot | CookieInspector |
|---|---|---|
| Serves a consent banner / CMPWe audit banners; we don't serve them. Keep HubSpot's banner in place. | Yes — bundled with HubSpot | No — scanner only |
| Scans your site to discover cookiesThis is the gap. HubSpot can only govern what you told it about. | No — categories are maintained by hand | Yes — headless browser, full network and cookie log |
| Gates HubSpot's own trackingHubSpot's cookies (__hstc, hubspotutk, __hssc) respond to the banner correctly. | Yes — that's what it's built for | We verify it, not replace it |
| Gates third-party tags you added elsewhereTags loaded via GTM or pasted into a template are not blocked automatically. | Only if you wire each one up yourself | We show you which ones fired before consent |
| Evidence of what fired before consentThe record you need when someone asks you to prove it. | Not offered | Per-page timeline with request-level evidence |
| Scheduled recurring scansCatches trackers that slip in between releases. | Not offered | Daily/weekly, up to 5 sites on Pro |
| Third-party verification badgeExternal proof of audit rather than self-attestation. | Not offered | Public verification badge per domain |
| Works if you leave HubSpotWe detect HubSpot's banner by name, and 15+ other platforms too. | Banner goes with the subscription | CMP-agnostic |
Choose CookieInspector when…
- You run HubSpot's banner and want to confirm it's actually holding trackers back.
- Your marketing team adds tags through GTM, and you're not sure they're gated.
- You need per-page evidence of pre-consent activity for a legal or client review.
- You want to be told when a new tracker appears, instead of finding out later.
Choose HubSpot when…
- You need a consent banner in the first place — HubSpot's is included and solid.
- Your site is entirely HubSpot-hosted and every tag is managed inside HubSpot.
- You want consent state to flow into HubSpot contact records automatically.
How to layer CookieInspector on top of HubSpot
Most teams keep their CMP and add us for evidence, monitoring, and external audit proof.
- 1
Keep HubSpot's banner exactly as it is
CookieInspector does not replace your consent banner. Nothing about your HubSpot setup changes.
- 2
Run a baseline scan
See what loads before anyone clicks Accept — including tags HubSpot's banner never knew about.
- 3
Wire up whatever the scan surfaced
For each third party that fired early, gate it behind HubSpot's consent events or your tag manager's consent mode.
- 4
Re-scan to confirm
Verify the fix from the outside rather than trusting the configuration screen.
- 5
Schedule weekly monitoring
New tags arrive with new campaigns. Weekly scans tell you when one slips past the banner.
Frequently asked questions
Does CookieInspector replace HubSpot's cookie banner?
No. HubSpot's banner is a consent management platform and a decent one — keep it. CookieInspector is a scanner that audits it from the outside, which is the part HubSpot doesn't offer.
Does HubSpot have a cookie scanner?
No. HubSpot's Privacy & Consent settings let you define cookie categories and customize the banner, but they don't crawl your site to discover what's actually loading. That inventory is yours to maintain by hand.
HubSpot's banner is enabled — why did your scan still find trackers before consent?
Because HubSpot's banner reliably governs HubSpot's own tracking, not everything else on the page. A Meta pixel, a LinkedIn insight tag, or a script added through Google Tag Manager will fire on page load unless you've explicitly gated it. That's the most common finding on HubSpot sites we scan, and it's a configuration gap rather than a HubSpot defect.
Do you detect the HubSpot banner by name?
Yes. Reports name HubSpot as the consent platform when its banner is present, so you can confirm we found the right thing. HubSpot's banner infrastructure is treated as consent tooling and never counted against you — while HubSpot's analytics and advertising pixels are still measured like any other tracker.
Will scanning interfere with my HubSpot tracking or contact records?
No. Scans run in an isolated headless browser against your public pages. Nothing is written to your HubSpot account, and scan traffic isn't tied to a contact record.