Skip to main content
Use one controlled test and follow it from the device to Events.

​
1. Confirm the test environment

  • The latest code is deployed to the URL or app build you are testing.
  • The installation uses the workspace ID or server key from the active workspace.
  • You are looking at a date range that includes now.
  • Browser privacy tools, content blockers, and consent settings are not suppressing the test.
Test in a clean private session with blockers disabled. Do not use production traffic as your first diagnostic.

​
2. Check the installation

For web tracking, load one page and inspect the browser console and network activity for a blocked script, content-security-policy error, or initialization error. Confirm Datalyr initializes once. For server or mobile SDKs, enable the SDK’s debug logging, send one simple event, then flush before the process exits or the app is closed.

​
3. Compare automatic and manual tracking

Send a simple manual event.
  • Manual and automatic events are missing: initialization, credentials, consent, network access, or workspace routing is wrong.
  • Manual works, automatic does not: review page or screen tracking configuration and framework lifecycle hooks.
  • Events appear only after a delay: review queue and flush behavior, especially in serverless jobs and short-lived scripts.

​
4. Find it in Datalyr

Open Events, search for the exact event name, and widen the date range. Check the source and identifiers to make sure the event did not arrive under a different environment or workspace.

​
Still missing

Capture the workspace ID prefix, SDK name and version, environment, event name, test timestamp with timezone, and the relevant debug error. Do not include a full secret API key.
Reinstalling repeatedly can create duplicate tracking. Change one thing at a time and remove abandoned snippets before retesting.