When to use this
Teams often arrive with a PDF or dashboard from another scanning vendor. This article helps you map foreign categories to GDPRChecker without expecting identical scores. External tools may count cookies differently, treat tag managers as single domains, or ignore consent Mode signals GDPRChecker evaluates.
Use mapping when procurement asks why GDPRChecker reports differ, or when migrating off another CMP and you need a joint remediation backlog.
After mapping, run a fresh GDPRChecker scan as the source of truth for actions inside this product.
Procurement sometimes attaches Cookiebot or OneTrust PDFs to security questionnaires. Respond with a mapping table plus GDPRChecker scan link dated the same week so reviewers see active remediation rather than stale third-party exports.
When external tools grade cookie banner cosmetics higher than functional reject paths, prioritize GDPRChecker critical findings—regulators increasingly test behavior, not color contrast alone.
Security questionnaires sometimes ask for SOC2 reports from scanners—GDPRChecker evidence is technical behavior; attach scan plus runtime diagnostics when you control the site.
Step-by-step instructions
- Export or list critical findings from the external tool with URLs and severity.
- Run the same canonical URL through /scanner.
- Create a three-column table: external finding, GDPRChecker finding, status match or gap.
- Align tracker domains—external cookie names may map to network hosts in GDPRChecker.
- Map consent issues: missing banner, no reject, dark patterns, to consent banner help tasks.
- Map policy issues to legal pages verification in dashboard.
- For blocking gaps, install the runtime and configure the consent banner on Pro; upgrade to Growth when you need dashboard-managed tracker blocking rules rather than only a banner swap.
- Close gaps that exist only in external tool by documenting false positives; close GDPRChecker gaps with setup work.
- Rescan both tools after deployment with the same timestamp window for fair comparison.
- Store mapping spreadsheets with version numbers when auditors revisit annually.
- Escalate unmatched critical gaps to legal when external tool is silent but GDPRChecker is not.
- Version the mapping table filename with scan dates and owner initials.
Expected result
Stakeholders see a reconciled plan owned in GDPRChecker. Duplicate work is avoided when findings already pass here. True gaps get setup wizard assignments.
Migration projects gain a single dashboard for go forward monitoring even if legacy vendor reports are archived.
When auditors ask why two tools disagree, attach the mapping table and note methodology differences in the cover memo—transparency reduces repeated scan requests.
Troubleshooting
External tool shows more cookies
Passive cookie databases count storage GDPRChecker attributes to script requests. Focus on pre-consent network activity for enforcement parity.
GDPRChecker stricter on consent
We weight reject parity and category granularity. Cosmetic banners that external tools pass may still fail here—improve UX per cookie banner guides.
Scores incomparable
Present finding counts by severity instead of normalizing scores. See Cookiebot vs GDPRChecker article for vendor-specific notes.
External pass but GDPRChecker fail on same day
Re-run both tools on identical URL and timestamp. Clear CDN cache. Confirm external tool tested post-login page without realizing paywall blocked crawler. Attach HAR export to engineering ticket if mismatch persists after two rescans.