Short answer
consentmanager is an external CMP with formal advertising-ecosystem capabilities, including TCF support and Google CMP partner positioning. GDPRChecker is designed to make SMB protection, verification, monitoring, and audit evidence straightforward, and can monitor a site that chooses consentmanager as its visitor-facing CMP.
For a normal SMB site, GDPRChecker can be the simpler default. For a publisher or a customer that requires formal TCF/Google CMP capabilities, consentmanager should own the CMP while GDPRChecker supplies independent operational controls.
What to check
- Whether your site needs a registered TCF CMP and vendor list.
- Whether the main need is a simple three-step setup and ongoing verification.
- Whether an agency needs cross-provider monitoring and evidence across sites.
- Which product will own the single visitor-facing banner.
Practical steps
- Classify the site’s advertiser versus publisher requirements.
- Select GDPRChecker or consentmanager as the consent source in GDPRChecker.
- If external CMP is selected, install the provider code first and verify it on the live site.
- Run GDPRChecker’s external CMP scan, Page Coverage, and change monitoring.
- Review evidence and responsibilities after each material vendor or tag change.
Common mistakes
- Loading both consentmanager and GDPRChecker banners.
- Selecting a provider only because it has TCF when the site is not a publisher.
- Assuming external CMP mode disables monitoring; it only prevents the duplicate GDPRChecker banner.
- Not documenting the owner of vendor configuration, policy text, and incident response.
Important boundary
Know the scope
GDPRChecker does not claim consentmanager’s CMP ID, TCF registration, or Google certification. External CMP mode prevents double banners while retaining monitoring and evidence functions.