Verify your installation

Test in order#

1. Confirm the correct site is selected and its project ID matches the snippet.
2. Confirm collection is enabled and a valid HTTPS privacy URL is saved.
3. In browser developer tools, check weeveo.js loads successfully once.
4. Make a manual visit on a public deployed page and grant analytics consent.
5. Confirm window.weeveo exists and getConsentRecord().status is granted.
6. Check a POST to /api/v1/collect on your configured host and inspect its response.
7. Open Realtime, then Overview with a date range including today and matching traffic filters.

When nothing is sent#

DNT, GPC, webdriver, localhost exclusions, disabled local storage flags, domain restrictions, private paths, missing consent or a blocked script can stop the tracker. A browser extension or CSP can also block the request. Test with a normal browser and inspect the specific cause; do not remove privacy controls to inflate counts.

When requests fail#

Check the collector host, TLS, CORS origin, project existence and payload response. A successful script load does not prove the collection endpoint is reachable. A custom domain can be pending HTTPS even after DNS resolves.

When reports disagree#

Compare the same site, timezone, traffic type, filters and date range. Realtime covers recent activity; historical reports use their selected window. Payments, pageviews, sessions and unique visitors are different measures.

Share a useful bug report#

Include the affected report, site ID, timeframe, filters, sanitized browser error and HTTP status. Remove API keys, OAuth tokens, raw visitor details and provider credentials.