Configure and publish the consent banner

When to use this

Configure the consent banner after Step 2 · Install Script completes and before later setup steps. On Growth you continue to Step 4 · Tracker Blocking; on Pro you can skip the optional tracker-blocking step and continue to Step 5 · Legal Pages after publish. The banner is your visitor-facing GDPR interface: it must offer accept, reject, and granular preferences where required, with clear category labels for necessary, analytics, marketing, and preferences storage. GDPRChecker’s consent workspace walks through appearance, banner content, categories, privacy entry, and publish.

Pro unlocks full banner editing and publish; Free accounts may preview locked controls but cannot deploy to a managed site. Growth adds multi-language strings, advanced appearance (radius, density, shadow), and customizable floating privacy entry buttons.

Draft changes are not live until you publish. The setup wizard’s Step 3 stays incomplete until cmpPublishedAt and published JSON exist, which runtime verification later confirms as config loaded and UI rendered.

Category labels should mirror language in your cookie policy to avoid visitor confusion—if marketing calls a stack “Performance,” map it to analytics or marketing honestly in both banner and policy.

Accessibility matters: sufficient contrast, keyboard reachable buttons, and readable font sizes reduce regulatory risk beyond automated scanner checks.

Step-by-step instructions

1. Open Dashboard → Consent and select your verified site if prompted.
2. Start with Categories: enable only stacks you truly use; disable marketing if no ads pixels are present.
3. Configure Banner content: headline, description, button labels including an equivalent reject path—not only accept.
4. Set Appearance: position (bottom bar or corner), color mode, accent color; Growth users can tune density and shadow.
5. Optional Growth step: add localized strings and privacy entry icon/placement for returning visitors.
6. Under Categories, review Google Consent Mode v2 settings (enabled by default): Basic/Advanced mode and outside-EEA defaults. Mapping is analytics → analytics_storage and marketing → ad_storage / ad_user_data / ad_personalization. GDPRChecker supports Consent Mode v2 integration and diagnostics, but is not currently a Google Certified CMP or IAB TCF CMP.
7. Use the live preview pane to confirm readability on mobile and desktop breakpoints.
8. Click Publish and wait for confirmation; note the published timestamp in configuration summary if available.
9. Load your live site in a private window to see production banner, not dashboard preview chrome.
10. Return to Setup wizard and confirm Step 3 · Consent Banner shows completed before continuing—on Growth, open Step 4 · Tracker Blocking next; on Pro, continue to Step 5 · Legal Pages.

Expected result

Published consent configuration is stored for your site id and delivered to the runtime on the next page load. Visitors see the banner on first visit according to your frequency rules. Step 3 completes in setup, and runtime health begins reporting UI mounted after a real visit.

Reject and accept choices should persist consent state in the mechanism GDPRChecker configures—verify in browser storage or consent logs if your process requires audit trails.

Localization on Growth requires publishing all required locales before go live in those markets—partial locale sets can pass English-only scans while failing visitor expectations in regulated regions.

Troubleshooting