You installed the tracker, opened your site, waited a minute… and your website is still Unverified. Here are the five most common causes, in order of frequency.
1. The script isn't actually on the page
Open your site, view source (Cmd+U / Ctrl+U), and search for netaj.io. If you don't find it, the snippet either didn't save, was added to the wrong template, or got stripped by a security filter.
Fix: re-paste the snippet from the Websites page in the dashboard, save the theme, and hard-refresh (Cmd+Shift+R).
2. Your tracking ID is wrong
The tracker URL contains your org's public ID — something like nj_a1b2c3d4. If you copy-pasted from somewhere old (or someone else's account), it won't match your dashboard.
Fix: re-copy the snippet directly from Websites → Setup in your current dashboard.
3. The domain doesn't match
The tracker only counts events from the domain you registered. If you registered example.com but your store actually serves on shop.example.com, events get dropped.
Fix: in the dashboard, edit the website and change the domain to match exactly what's in the address bar of your storefront. Subdomains count separately — www auto-matches, but other subdomains don't.
4. An ad blocker or privacy extension is blocking it
uBlock Origin, Privacy Badger, and similar tools sometimes block analytics tags. The tracker is safe, but extensions don't always know that.
Fix: open your store in incognito mode with extensions disabled. If it verifies there, the issue is local to your browser. Real users won't all have the same extension.
5. The browser is loading a cached page
If you've been editing the theme and your browser cached the old version (without the snippet), you'll think you installed it but the live page hasn't updated.
Fix: hard-refresh (Cmd+Shift+R / Ctrl+Shift+R) or open in a private window.
Still stuck?
Open DevTools → Network → filter by netaj. You should see tracker.js (200) and /api/events (202). If you don't see any netaj request, the tracker isn't loading. If you see tracker.js but no /api/events, it loaded but isn't firing — usually a JS error from earlier in the page broke it.