Snippet not firing
What to check when Luria records nothing on a site that uses the script tag.
If your site uses the script tag and Luria is recording nothing, one of six things is usually true. Work through them in order.
On Shopify you do not use this tag. Serving and tracking come from the Luria app embed, so go to Install on Shopify instead.
What you'll need
- The tag Luria gave you, with your site ID already filled in.
- Access to the template that renders your
<head>. - A private browser window with extensions off.
Steps
Step 1: Check the tag is in the head, exactly as issued
<script async src="https://luriart.com/snippet.js" data-luria-site="YOUR_SITE_ID"></script>It must sit in <head>, not in the footer or the body. If data-luria-site is missing or empty, the snippet stops immediately and does nothing.
The dashboard does not display your site ID yet. Luria gives you the tag with your site ID filled in during onboarding, or by email from hello@luriart.com.
Step 2: Confirm the page you are testing is the live one
A tag added to a draft template, a staging domain, or a page your CMS has not republished will never run. Load the public URL and view source.
Step 3: Test in a private window with blockers off
Luria collects nothing at all when the browser sends Global Privacy Control or Do Not Track. In the EU, the UK and Switzerland, and whenever the country cannot be determined, the snippet shows its own small banner ("We use analytics to measure and improve this site. May we?") and tracks nothing until you choose Accept. If you chose Decline earlier, that choice is remembered in that browser.
Ad blockers and privacy extensions also stop the request. A clean private window rules all of this out.
Step 4: Watch the network panel
Open developer tools, go to the network panel, and reload the page. You should see snippet.js load from luriart.com, then calls to /api/events and /api/patches on the same host. In the console, window.luria should be defined once tracking is allowed.
Step 5: Check your Content Security Policy
If your site sets a CSP, it must allow luriart.com for both loading the script and connecting to it. A blocked request shows as a CSP violation in the console.
Verify it worked
Reload the public page in a private window. snippet.js loads, /api/events is called within a couple of seconds, and window.luria exists in the console. Sessions from that visit then feed the numbers in your dashboard.
Common failures
- Tag in the footer. The snippet loads asynchronously and never blocks your page, but it still belongs in
<head>so variants apply before the visitor reads the page. - Site ID typo. One wrong character means the snippet talks to no site. Copy and paste the tag rather than retyping it.
- Two installs on one page. A second copy is ignored on purpose, so a duplicate tag does not double-count, but remove it anyway to keep things clean.
- Automated browsers. Headless and crawler user agents are filtered out, so a scripted check will not show up.
- Single page apps. The snippet runs once per full page load and does not hook route changes.
- Nothing broke, nothing happened. Luria fails open. On any error the page behaves exactly as if Luria were not there, which is why a broken install is silent rather than loud.