> ## Documentation Index
> Fetch the complete documentation index at: https://docs.datalyr.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Start at the first missing stage and follow one known record.

Most tracking problems become simple when you trace one event instead of comparing a large total.

## Choose the first broken stage

1. **Nothing reaches Datalyr:** start with **No events**.
2. **Activity arrives, but a purchase or subscription does not:** use **Missing revenue**.
3. **The conversion exists, but has no campaign journey:** use **Missing attribution**.
4. **A source card shows an error or stale state:** use **Integration errors**.
5. **Both systems have data, but totals disagree:** use **Different numbers**.
6. **The conversion exists but did not reach an ad platform:** use **Conversion not delivered**.

## Use a controlled test

Record the workspace, environment, event or transaction ID, source, timestamp with timezone, and expected result. Change one thing, repeat the test once, and check the same record through each stage.

Avoid reconnecting sources, rotating keys, or reinstalling SDKs before locating the failure. Those actions can create new variables or duplicate tracking.

## What to collect for support

* workspace name and public ID
* affected page, source, or SDK and version
* one event or transaction ID
* test timestamp and timezone
* exact error text or delivery status
* what you expected and where the record last appeared

Remove secrets, payment details, and sensitive customer data from screenshots and logs.