No data showing
Find out why the dashboard shows no visits after you installed Loomduct.
Use this page when the dashboard still says No events yet after you installed Loomduct. Start by opening your live site with the browser's developer tools, on the Network tab, and look for a request to /l/e.
There is no request to /l/e
Loomduct did not send anything. Check these causes, in this order:
The page runs on localhost
Loomduct skips localhost, 127.0.0.1 and *.local on purpose. Test on your live site, or turn on tracking for local tests: see Don't track in development.
The browser is automated
Loomduct skips Playwright, Puppeteer, Selenium and Cypress. See Test tracking in end-to-end tests.
Your browser has the opt-out flag
Run localStorage.getItem('loomduct_ignore') in the console. If it prints 'true', remove it with localStorage.removeItem('loomduct_ignore').
load() is never called
With npm, check that your app calls loomduct.load() once when it starts. With the script tag, check that the tag has no data-manual-load, or that your code calls loomduct.load().
The script did not load
In the Network tab, look for loomduct.js. If it is missing or blocked, check that the snippet is in the <head> of the page, and that your Content Security Policy allows https://cdn.loomduct.com and https://api.loomduct.com.
An ad blocker blocked it
Turn off your ad blocker and reload. If that fixes it, your visitors with ad blockers are missing too.
To see why Loomduct skipped a page, turn on debug logs: debug: true in your options, or data-debug on the script tag. The console then shows a line like [loomduct] skipped: localhost.
The request to /l/e answers 401
The project token is wrong. Copy it again: in the dashboard, open the project menu, select Project settings, then Copy project token. If you rotated the token, update it on your site.
The request to /l/e answers 202
Loomduct received the event. It shows up in the dashboard within a few seconds. Check that you are looking at the right project, and that the period at the top of the Overview includes today.
The request fails with a network error
The request did not reach Loomduct, for example because of an ad blocker or a network problem. The SDK retries twice, then drops the event. See Handle SDK errors.