Snippet not firing

Step-by-step diagnosis when the dashboard shows no green dot or no sessions after installing Luria.

Work through these in order. Stop at the first step that fails and apply its fix. Most installs are fixed by step 3.

Step 1: Wait 60 seconds, then use a private window

Open a fresh private or incognito window with extensions disabled, and load your site's homepage. Luria can take about 60 seconds after install to start reporting.

Pass: the dashboard shows a green dot or at least one session within a couple of minutes. You are done. Fail: still nothing. Continue.

Step 2: Confirm the tag is on the live page

In that private window, right-click the page and choose View Page Source. Search (Ctrl+F / Cmd+F) for snippet.js.

Snippet installs: you should see https://luriart.com/snippet.js inside <head>.
Shopify: search for luria instead; the app embed injects it.

Pass: the tag is there. Continue to step 3. Fail: the tag is missing. You are looking at a site or theme that does not have it. Re-add it following your platform guide, for example Install on a custom site, and make sure you saved and published.

Step 3: Check the Site ID matches

Compare the data-luria-site="..." value in the page source with the Site ID in your dashboard (Settings > Install). They must match exactly, including case.

Pass: they match. Continue. Fail: they differ (common when you copied from a staging site or a second account). Replace the tag with the one from your dashboard.

Step 4 (Shopify): embed is on for the LIVE theme

App embeds are per theme. Go to Online Store > Themes. On the theme marked Current, click Customize > App embeds (the puzzle-piece icon) and confirm Luria is switched on, then Save.

Pass: it is on for the current theme. Continue. Fail: it was off, or it was on for a different theme. Switch it on for the live theme and save. Wait 60 seconds.

Step 5 (Google Tag Manager): container published and tag fired

In GTM, open Preview mode and load your site. Confirm the Luria tag shows under "Tags fired" on page load. Then confirm the container version containing the tag is actually published (Submit > Publish).

Pass: fired in Preview and published. Continue. Fail: fix the trigger (it should be All Pages, or your consent trigger), then publish. See Install with GTM.

Step 6: Your own browser may be blocking Luria

Luria honours Global Privacy Control and Do Not Track (collects nothing), and ad blockers often block analytics scripts. If you declined Luria's consent prompt earlier, that is remembered too. So your own browser is the worst place to test.

Pass: in a private window with extensions off, you appear in the dashboard as a session. Fail: still nothing. Continue.

Step 7: Look for errors in the console

In the private window, open developer tools (F12 or right-click > Inspect) and open the Console tab. Reload. Look for red errors mentioning luriart.com, "Content Security Policy", or "Refused to load".

Pass: no Luria-related errors. Continue. Fail: a CSP error means your site's security headers block third-party scripts. Add https://luriart.com to your script-src and connect-src directives (or ask your developer or platform support to).

Step 8: Confirm requests are leaving the page

In developer tools, open the Network tab, reload, and filter by luriart. You should see snippet.js load with status 200, and after a second or two a request to /api/events.

Pass: both appear. Luria is firing; if the dashboard still shows nothing after five minutes, contact support with a screenshot of this tab. Fail: snippet.js is blocked or returns an error. Screenshot the Network tab and write to support.

Why you might not see yourself

Even on a perfect install, you personally may never show up: GPC/DNT, an ad blocker, a declined prompt, or simply being in the control group for a test. That is expected. Judge the install by the dashboard, not by your own screen.