Get started
Verify tracking
After you install the tracker, confirm that page views reach usage.io and appear in your dashboard.
In-app confirmation
When a site has never received a valid page view, the app shows a waiting for first ping (or similar setup) state with your snippet.
Once usage.io accepts a page view for that domain:
- The setup state clears and you can open the full analytics view (subject to an active trial or subscription).
- Live Now may show visitors before longer-range charts finish aggregating.
Visit a real page on your production hostname—the same domain you registered—not only localhost, unless your local environment uses that registered host.
Browser DevTools check
- Open your site in Chrome, Firefox, or Safari.
- Open Developer Tools → Network.
- Reload the page.
- Filter for
pingor forusage.io. - You should see a POST request to
/pingthat completes successfully.
If your site is a single-page app, navigate to another client-side route. You should see an /exit followed by a new /ping.
Ad and privacy extensions
Browser extensions that block analytics or third-party requests can prevent pings during testing. Try a clean profile or temporarily disable blockers.
Dashboard check
Open Dashboard → your site and select a range that includes today.
- Page views and Live Now are the fastest signals that ingest works.
- The chart and path breakdowns can take a few minutes to populate after the first visits.
If Live Now updates but the chart is still empty, wait a few minutes and refresh.
Common problems
| What you see | What to check |
|---|---|
| No network requests | Snippet missing from the layout, wrong script URL, or CSP blocking the script |
| Requests fail (4xx) | Page URL host does not match a site domain in usage.io; Origin/Referer mismatch (see Tracker reference) |
| Requests succeed but no dashboard data | Trial or subscription inactive; path or IP exclusion discarding hits |
| No data for DNT browsers | Enable Collect Do Not Track traffic or test with DNT off |
| Staging vs production | Register and test against the hostname visitors actually use |
Domain matching
usage.io attributes traffic by matching the host of the page URL in each ping to a site you created. Register www.example.com if that is what appears in the browser address bar, or register the apex domain if you standardize on that—example.com and www.example.com are handled as related hosts, but your live URLs must resolve to a registered site.
Still stuck?
Contact support with your site domain, the page URL you tested, and whether /ping appears in the network tab.