Skip to Content
Verification & Troubleshooting

Verify & Troubleshoot Available (v1)

The 4-point diagnosis

You find the connection check in the last setup step (Verify connection) and at any time on your website’s detail page under Websites. It runs by itself every few seconds; Check again triggers it right away. It checks four points:

#CheckMeaning
1Snippet loadedThe snippet has reported from your website within the last few minutes.
2cdn.visz.ai is reachableThe script from cdn.visz.ai loads (not blocked).
3Consent allows the measurementNo refusal has arrived that blocks the measurement.
4First event receivedA visit with consent has come in.

Once the first three points are met, the check reports Connected. That is not an error: data arrives as soon as a visitor consents. Once the first event is in as well, it reports You’re live.

”I don’t see any data” · the 3-cause tree

When no data arrives, it’s almost always one of these three causes. The check names the cause that applies and the next step.

Cause 1: Snippet not loaded (correctly)

  • Message: “We haven’t seen the snippet load yet.”
  • Check: Is the snippet line really installed site-wide (theme header or layout), not just on a single page? Did you save and publish, for example on Webflow? Did you clear the cache of your caching plugin? On Shopify: is the app embed switched on and the tracking key entered, see Shopify?
  • Message: “The snippet loads, but the data is being blocked.” The check shows this when a refusal of consent has arrived.
  • Consent: Without consent, Visz deliberately does not track. Make sure your banner triggers visz('consent', true) or your Google Consent Mode sets analytics_storage to granted, see Consent Setup.
  • CSP (Content-Security-Policy): If your site has a strict CSP, allow cdn.visz.ai in script-src and ingest.visz.ai in connect-src.
  • Do Not Track: If DNT is active in the browser, the snippet stays silent. Test in a browser without DNT.
  • Adblocker: Some blockers filter analytics scripts. Test in a browser without a blocker.

Do Not Track, an adblocker, or a CSP that blocks cdn.visz.ai or ingest.visz.ai already prevents the snippet’s first report. The check then shows cause 1.

  • Message: “The snippet loads, we’re waiting for the first consented visitor.” or “The snippet loads, we’re only missing the first page view.”
  • Check: Has the site had any visitors since you installed it? Open it yourself in an incognito window, agree to measurement, and reload the page. The session then appears under Recordings.

Less common causes

  • Address not allowed: The snippet loads, but on an address that doesn’t belong to your website. Visz accepts data from the domain you added, its www. variant, and its subdomains. A website’s domain can’t be changed in the dashboard; if your site runs under a different address, write to info@visz.ai.
  • No source for consent (Shopify): For your shop, neither the Visz cookie banner is switched on nor your own consent tool connected. Without one of the two sources, consent never arrives.
  • Shopify access expired: Connect the shop again with Reconnect store.
  • Adblocker: Reduces the reach you capture, but it’s not a bug. A share of visitors block analytics in general.
  • Consent: In the recommended mode, Visz measures nothing before consent. If you see nothing, often simply no consent has been granted yet.
  • DNT: “Do Not Track” stops the snippet, unless your website explicitly overrides it in code.
  • CSP: Allow cdn.visz.ai (script) and ingest.visz.ai (data endpoint).

Stuck? → Contact / Support.

Last updated: