Short answer
External CMP monitoring lets a site keep its chosen third-party CMP as the only visitor-facing banner while GDPRChecker checks for provider presence, live-site protection signals, tracker changes, coverage, scans, alerts, and evidence. It prevents a duplicate GDPRChecker banner.
It does not grant GDPRChecker the external provider’s account access, CMP ID, vendor-list authority, TCF registration, or legal responsibility. A successful static detection is not the same as proving every consent interaction or vendor declaration is correct.
What to check
- Whether a recognizable external CMP script or marker is present on the site.
- Whether GDPRChecker’s own banner is suppressed to avoid two consent dialogs.
- Whether scans, coverage, cookie changes, and pre-consent tracker signals remain visible.
- Whether the provider CMP is installed where the monitored templates are scanned.
Practical steps
- Select External CMP as the consent source in GDPRChecker.
- Install and publish the external CMP according to its provider instructions.
- Verify the live site and confirm only one banner is visible.
- Run a GDPRChecker scan and Page Coverage scan across representative URLs.
- Review alerts and Evidence Center after provider, tag, or template changes.
Common mistakes
- Expecting External CMP mode to configure vendor lists inside the provider account.
- Reading provider detection as a TCF or certification guarantee.
- Leaving GDPRChecker’s own consent source enabled alongside an external banner.
- Skipping a live interaction test after changing provider settings.
Important boundary
Know the scope
GDPRChecker can detect and monitor external CMP integration but cannot certify the provider, generate a TC String, or inspect private provider account settings without a separate approved integration.