Verify your install

The one-minute check

1. Open your site in a normal browser tab.
2. Open Realtime in sonex.
3. You should appear as an active visitor within a few seconds.

If that works, you are done. The Overview’s install panel disappears by itself once the first pageview lands, and there is a Check again button on it if you want to force a re-check after deploying.

When nothing shows up

Work down this list. It is ordered by how often each one is the real cause.

The tag is not on the page you opened

View source on the live page, not your editor, and search for sonex.js. If it is missing, the deploy did not include it, or it went into a layout that page does not use.

The src points at the wrong host

It must be https://api.trysonex.com/sonex.js. trysonex.com and app.trysonex.com return HTML, so the browser loads a page where a script should be and nothing runs.

data-website-id is missing or wrong

No id means no events, silently. Compare it against the id in the app’s Install dialog, character for character.

data-domains excludes the hostname you are on

If you set data-domains, only those exact hostnames report. Testing on localhost or a preview URL while the list says example.com produces exactly zero events, correctly.

You disabled tracking in this browser

If you ran the exclude-yourself snippet, this browser is quiet on purpose. Undo it with:

localStorage.removeItem("sonex.disabled");

Do Not Track is on and you honor it

With data-do-not-track="true", visitors sending a DNT signal are skipped. Your own browser may well be one of them. Test in a browser without DNT, or drop the attribute.

An ad blocker or extension is eating it

Privacy extensions block analytics domains by pattern, and yours is not exempt just because it is not surveilling anyone. Check the browser console and network tab for a blocked request to api.trysonex.com. Try a clean profile or a different browser to confirm.

The site never loaded the script at all

In the network tab, filter for sonex.js. No request means the tag is missing or malformed. A request with a non-200 status means the src is wrong.

Confirm events, not just pageviews

Firing a custom event but seeing nothing in Events? Check the date range first. Events land in the range they happened in, so a fresh event will not appear inside a range that ended yesterday. Then confirm the call actually ran:

window.sonex.track("signup");

Run that in the console on your own site. If window.sonex is undefined, the tracker is not loaded, and this is an install problem rather than an event problem.

Next: Concepts, so the numbers you now have mean what you think they mean.