Consent, GPC and why a visit was not tracked
Why a visit can be missing on purpose, how the consent banner behaves by region, and how to tell a privacy signal apart from a broken install.
Most "the scan says zero sessions" reports are not a broken install. They are a privacy signal doing its job. Check these before you check anything else.
Global Privacy Control or Do Not Track
If the browser sends globalPrivacyControl or doNotTrack, Luria collects nothing: no visitor id, no events. The page renders exactly as normal, and there is nothing to see in your dashboard.
Many privacy-focused browsers and extensions send this by default, including the browser you probably test in.
How to tell: open a plain private window with extensions off and load the page again.
The consent banner
In regions where consent is required, the snippet shows its own small banner before tracking anything:
We use analytics to measure and improve this site. May we?
with Accept and Decline. Nothing is tracked before that choice. If you declined once, your browser remembers, and every later visit from that browser is silent.
How to tell: clear the site data for your own domain and reload.
Which regions ask is decided by the country the request arrives from. The EEA, the UK and Switzerland require consent. When the country cannot be determined, Luria fails closed and asks anyway.
On Shopify
The store's own Customer Privacy settings govern. Assignment still runs, because a visitor has to see a consistent page, but marketing extras wait for consent.
Ad blockers
Some blockers stop requests to any third-party analytics host. Luria's requests go to luriart.com. If a blocker catches them the page still behaves normally, and the visit is simply not recorded.
What this is not
If tracking is silent for every visitor, including a clean private window with blockers off, this page is not your problem. Go to Snippet not firing.