Check it works
Open your site in a browser, then look at the checks on the onboarding page (or at Settings → Tracking, which shows what the collector saw in the last 24 hours).
| Check | What it means |
|---|---|
| Snippet installed and reaching Lynq | A request from your site arrived at the collector. |
| Hostname matches this site | The page’s hostname is one of the site’s hostnames. |
| First pageview accepted | A pageview was stored; the Overview has a number. |
| Web Vitals reported | The tag has data-vitals and a page finished loading. |
If a check stays grey
Nothing arrives. View the page source and confirm the tag is in the <head> with the right src. Open the browser’s network panel and reload: you should see a request to lynq.byharsh.com/api/collect about a second after load. A content blocker on your own browser may stop it; try another browser or a private window.
Testing on localhost. Lynq ignores localhost and 127.0.0.1 on purpose. Add data-allow-localhost to the tag while testing, then remove it.
“We received events from …, which is not one of this site’s hostnames.” The page is served from a hostname the site does not claim, often a staging domain or a second domain. Add it under Settings → General → Hostnames, one per line.
“The page path … is on your excluded list.” The path matches an exclusion you set. Remove it or test another page.
“Traffic arrived from an excluded IP range.” Your own address is excluded, which is usually what you want; test from another network or a phone.
“Traffic arrived but all of it was classified as bots.” Automated browsers and known crawlers are dropped at the collector. A real browser will count.
“Events were malformed; is the snippet the current version?” An old lynq-js tag from jsDelivr, or a modified copy, is sending an unsupported format. Replace it with the one-line tag above.
Web Vitals never report. The tag needs data-vitals, and some metrics only finalise when the visitor leaves the page or switches tabs. Load a page, wait, then close the tab.