When to use this
Verify installation when you have pasted the runtime snippet but the dashboard still shows Step 2 · Install Script incomplete, or when you want independent confirmation before handing off to a developer. Verification is lighter than full runtime verification (Step 6): it focuses on whether the script is reachable on your public site and whether GDPRChecker has recorded an install or ping event tied to your site id.
This check matters because consent banner preview in the dashboard does not prove anything runs on your origin. Only a live load against your registered domain counts. Teams that edit only GTM preview containers often stall here until production publish happens.
Repeat verification after major site launches, theme migrations, or headless replatforming—even if you previously went live—because template regressions can remove the tag silently.
Step-by-step instructions
- Open Setup → Step 2 · Install Script and read the current status (Not configured, detected, or verified).
- In another tab, open your live homepage using https and the same host you registered.
- Use view-source or DevTools → Network filtered by your GDPRChecker host to confirm the script request returns 200.
- Disable ad blockers for this test session so heartbeat beacons are not stripped.
- Click any Run check or Refresh status control on the install panel to pull latest telemetry.
- If available, follow the guided link to open your site with a verification query parameter that forces a setup ping.
- Wait up to two minutes for heartbeat aggregation; status should flip to installed or online.
- Document the timestamp shown as last seen for future incident comparison.
- When Step 2 shows complete, proceed to Step 3 · Consent Banner—Step 3 stays locked until Step 2 is complete.
Expected result
Install verification succeeds when the dashboard records script detection or a fresh setup heartbeat from your production domain. Copy in the UI should state that the snippet is detected or runtime is connected. You can move to consent configuration without waiting for full runtime verification (Step 6)—that comes after banner publish, legal pages, and on Growth, tracker blocking.
Protection overview may still show warnings until later steps publish config; that is normal. The key outcome here is proof the tag is on real pages visitors load.
Record which environment you verified—production versus staging—to avoid false confidence when staging has the tag but production does not yet deploy from pipeline.
Troubleshooting
Script visible in HTML but status missing
Ensure the site query parameter matches your Site ID. Mixed www/non-www hosts may ping a hostname GDPRChecker does not attribute to your site—align DNS canonical host with registration. Clear full-page caches and edge workers that serve stale HTML without the new tag.
Works on homepage but not inner pages
Install via global layout, not a single page template. SPA frameworks need the tag in index.html or root layout. Subroutes that lazy-load without the head snippet will not count toward site-wide protection.
Verification succeeded then reverted
A deployment may have removed the tag. Compare last heartbeat timestamp with your last release. Enable deployment checks that fail CI if the GDPRChecker script string is absent from built HTML.