Serving the script yourself

Lynq does not support this. Some sites want to load the script and post events through their own domain, to keep one origin or to get past content blockers. Lynq’s tracker only needs two paths for that, /js/lynq.js and /api/collect, but a reverse proxy in front of the collector does not work today, and this page exists so you do not spend an afternoon finding that out. Keep the tag pointing at lynq.byharsh.com.

Why not

A visitor’s number is computed from the address the request arrives from, read from the hosting platform’s own headers and never from X-Forwarded-For, which a client could set to anything. Behind your proxy every request arrives from the proxy, so every visitor becomes one visitor per day and every country becomes the proxy’s country. The numbers would be wrong rather than missing, which is worse.

What to do instead

The script is 2.1 kB, loads deferred and never blocks the page, so there is no performance reason to proxy it. Content blockers that stop it are respecting a choice the visitor made; Lynq does not try to route around that.