Troubleshooting
Encountering deployment operational hitches? Review the most frequent failure states and their resolution routines.
Zero Metric Ingestion inside Dashboard
If you appended the tracking fragment but the analytics grid records no active events, walk through these system validations:
- Verify that the Website ID variable specified within the tracking script exactly references your property token.
- Ensure client-side tracking assets are not intercepted by local AdBlocker tools (deploy an incognito session window to verify).
- If running validation tests inside local development workspaces, confirm the inclusion of the 'data-allow-localhost="true"' attribute parameter.
- Examine your web inspector console logs (F12) to trap prospective 403 Forbidden or 404 Not Found routing errors.
AdBlocker Interception Barriers
Rigid client-side filtering systems might throttle payload dispatches heading towards our collection clusters. To enforce telemetry accuracy, we recommend mounting a dedicated reverse proxy routing custom subdomain.
Proceed to Proxy Architecture GuideClient Inspector Trace Errors
403 Forbidden (Domain mismatch)This network state signifies that the origin header of the telemetry payload drops out of alignment with the domain target initialized within your dashboard settings. Adjust your workspace parameters.
404 Not Found (Invalid Website ID)The provided Website ID parameter token could not be mapped inside the configuration index. Re-extract the payload signature block from your workspace portal.
Are operational bottlenecks persisting?
Our technical engineering desk is available to review your target infrastructure deployment.