Skip to main content
Every browser and server event goes to https://ingest.datalyr.com, and the status on that request names the failure. Start there before you change any code.

Read the status first

Open devtools, select the Network tab, and reload the page. Filter on ingest. The SDK treats any 4xx except 408 as permanent, so it drops that batch instead of retrying. Fix the cause above, then send the event again.

Server SDK statuses on /track

No request leaves the browser

Run these four in the console on the page you are testing.

The SDK loaded but sends nothing

Tracking stops in five cases. Run window.datalyr.isOptedOut() first. Do Not Track is off by default, so a DNT browser is tracked.
An ad blocker stops requests to ingest.datalyr.com for real visitors, not only for you. Set up first-party tracking so the requests go to your own hostname.

Server and mobile SDKs send nothing

The SDK batches. It sends after 10 events or 5 seconds, whichever comes first. It retries 5 times and queues 100 events offline.
Call flush() before a serverless function returns. The process exits before the 5-second timer fires, and the batch never leaves.

Verify

  1. Open Live.
  2. Reload the page you are testing.
  3. Confirm your visitor appears within 30 seconds.
If Live stays at watching for events, contact support. Send the workspace public ID, the X-DL-SDK-Version header value, and the status code.