Consent Setup Available (v1)

Why consent before tracking (the USP)

Visz records zero events, recordings, or fingerprints before the visitor consents. “Do Not Track” overrides everything — if DNT is set, Visz stays off regardless of consent state. This is what makes Visz GDPR-friendly by design.

Method 1 — visz('consent', …)

Call the JS API once your banner resolves:

visz('consent', true);  // visitor accepted → tracking starts
visz('consent', false); // visitor declined → nothing is tracked

Method 2 — Google Consent Mode v2

If you use Consent Mode v2, Visz reads analytics_storage (and respects ad_user_data). Grant analytics_storage and Visz starts; deny it and Visz stays off. No extra wiring beyond your existing Consent Mode setup.

Method 3 — Custom selector (dashboard)

Point Visz at your existing “Accept” button via a CSS selector in the dashboard. A MutationObserver waits for the element and fires consent on click — no code changes on your site.

CMP examples

Common consent management platforms work with Method 1 or 2:

• Cookiebot — accept event → visz('consent', true)
• Usercentrics — consent callback → visz('consent', true)
• Borlabs Cookie (WordPress) — opt-in hook → visz('consent', true)

Detailed step-by-step examples per CMP are coming — the three methods above cover every setup.

Last updated: June 5, 2026