velaro. CMP Widget Test
Cookie Consent Guide KB 781

Does your CMP block the Velaro widget?

Enter your site ID and optionally your CMP's script-blocker URL to instantly test every consent scenario — no guesswork, no waiting. Works with OneTrust, Cookiebot, TrustArc, Osano, Termly, and any other CMP.

Your configuration

Find this in your Velaro dashboard or in your GTM embed code.
Only set if you're routing to a specific queue. Leave blank for site-default routing.
Paste the URL your CMP uses to auto-block scripts — OneTrust: Scripts / Auto-Block → script src; Cookiebot: the Cookiebot.js tag src; others: the equivalent blocking script. Without this, the blocking scenarios use a simulated blocker. Scenario A (baseline) and D (deferLoad) always run with your real site ID regardless.
Works with a full page-source paste too — the tool only looks for the parts it needs and ignores everything else. Nothing is sent anywhere; parsing happens entirely in your browser.
🎉

Path 2 confirmed — chat for everyone

The button appeared with Strictly Necessary-only consent and zero visitor data sent on page load. This means all visitors — regardless of their cookie choice — can reach your chat. Data is sent only after they click the button.
Next: add deferLoadUntilInteraction: true to your GTM embed and you're done.

Enter your site ID above and click Run All Tests.

On v20 / Velaro Messenger instead? Test Auto Mode v20

Everything above tests the classic Velaro widget (v10). If your embed code loads embed.js instead of the v10 shim, you're on v20 / Messenger and use a different mechanism entirely: data-consent-mode on the script tag, not a script-blocker. This test loads the real production embed.js with Auto Mode (data-consent-mode="auto") and confirms the pre-consent launcher renders before any CMP category is granted — using the same site ID you entered above.

What goes on your page (v20 Auto Mode)