Consent Setup Available (v1)
Why consent before tracking
In the recommended mode, Visz collects no events, no recordings, and no fingerprint before consent. This is not an after-the-fact filter: the snippet holds back until consent is there. Beforehand it only sends a technical sign of life without visitor data, so the connection check can see that it loaded. If a visitor declines at the Visz cookie banner, Visz only stores a record of the refusal, without a visitor and without a session.
“Do Not Track” (DNT): If the browser sends DNT, the snippet stays silent,
regardless of the consent state. This can only be overridden in your
website’s code, with window.viszConfig = { dntOverride: true } before the
snippet.
The consent mode
When Visz waits for consent is set per website, during setup or later under Settings → Privacy in the Data collection tab:
| Mode | Behavior |
|---|---|
| Wait for consent (recommended) | Visz only measures after consent via one of the methods below. |
| Google Consent Mode v2 | Visz follows the signals of your Google Consent Mode (method 2). |
| No consent required | Visz measures right after loading. |
You connect Visz to your visitors’ consent in one of three ways.
Method 1: visz('consent', …)
The most direct path. Call the API as soon as the visitor accepts or declines:
// visitor accepted → tracking starts
visz('consent', true);
// visitor declined → no tracking
visz('consent', false);Attach the call to the accept and decline buttons of your cookie banner. Visz
stays silent before the true call. If you call visz('consent', false)
after consent was given, the consent counts as withdrawn: Visz sends one last
record of the withdrawal and stops measuring.
If your banner runs before the snippet has loaded, first set up the small buffer from the JavaScript API. The snippet runs the buffered calls on start.
Method 2: Google Consent Mode v2
If you use Google Consent Mode v2 (for example via GTM), Visz reads its
signals in the dataLayer. Tracking starts as soon as a consent call
(default or update) sets
analytics_storage=granted
This also applies to entries that were already in the dataLayer before the
snippet. Without granted, Visz stays silent. You don’t have to change your
existing setup for this.
Method 3: The Visz cookie banner
If you don’t have a banner of your own, Visz can show one on your website. Switch it on under Settings → Privacy in the Cookie banner tab with Show banner. There you also choose position and language and see a preview.
When the banner is on, only the visitor’s choice at the banner decides, even if the mode is set to No consent required. The browser remembers the choice for your website. If you already use your own consent tool, leave the Visz banner off.
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)
Where in the dashboard
Settings → Privacy applies per website. In the Data collection tab you set the consent mode, in the Cookie banner tab the Visz banner.
Last updated: