Troubleshooting
Installed the pixel but something isn’t right? Walk through these common issues.
Data is not showing up in the dashboard
1. Check the pixel is installed.
Open your website, right-click → View Page Source, and search for in.glinto.eu. You should see the script tag in the <head> section.
2. Check the browser console.
Open DevTools (F12) → Network tab → filter by in.glinto.eu. You should see:
- A request for
p.js(the pixel script) — should return200. - A POST request to
/e(the event) — should return204.
If p.js returns a 404, double-check your data-site attribute matches the ID in your dashboard.
3. Check Do Not Track.
If your browser has Do Not Track (DNT) enabled, the pixel will not fire. This is by design. Disable DNT temporarily to test.
4. Check ad blockers.
Some ad blockers (uBlock Origin, Brave Shields) may block the pixel. See “Pixel is blocked by ad blockers” below.
5. Wait a few seconds.
Data typically appears in the Realtime view within 2–5 seconds. Aggregated dashboard views may take up to 60 seconds to update.
Pixel is blocked by ad blockers
Ad blockers use filter lists that may include analytics domains. Options to mitigate this:
- Custom domain proxy (recommended). Set up a CNAME record like
a.yoursite.compointing toin.glinto.eu. Then change the pixel’ssrctohttps://a.yoursite.com/p.js. This makes the pixel a first-party resource and bypasses most blockers. - Accept the ~15% gap. Industry data shows ad blockers affect 10–20% of visitors. Glinto’s numbers will be consistent relative to themselves — trends and comparisons remain accurate.
Script loads but no events are sent
- Wrong
data-siteID. Make sure the value matches exactly what’s shown inDashboard → Setup. It’s case-sensitive. - Content Security Policy (CSP). If your site has a strict CSP, add
https://in.glinto.euto bothscript-srcandconnect-srcdirectives. - Page loaded via
file://. The pixel only works onhttp://orhttps://origins.
Numbers don’t match Google Analytics
Differences between Glinto and GA are expected and normal:
- Glinto counts unique visitors per day (hash rotates daily). GA uses persistent cookies that can track across 30+ days. Glinto will show higher “unique” counts over long periods.
- Ad blockers block GA more aggressively than Glinto (GA is in every filter list). Glinto may show more traffic from privacy-conscious visitors.
- Bot filtering differs. Glinto drops known bots server-side. GA may count them differently depending on your settings.
Heatmap data looks wrong
- Heatmap clicks are recorded as a percentage of the viewport, not absolute coordinates. If your site layout changes significantly between screen sizes, the heatmap may look different on desktop vs mobile.
- Click events are rate-limited to 50 per page load to prevent abuse. If a page has very high click activity, some clicks may be dropped.
Core Web Vitals are not showing
Web Vitals (LCP, CLS, INP) are sent when the visitor navigates away from the page or the tab becomes hidden. They require:
- A Chromium-based browser (Chrome, Edge, Opera). Safari and Firefox don’t support all Web Vitals APIs.
- The visitor to spend enough time on the page for the metrics to be computed.
- At least a few page loads — the dashboard requires a minimum sample size to display vitals.
Still stuck?
Email contact@glinto.eu with your site ID and a description of the problem. We typically respond within 1–2 business days.