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

# Event logs

> Inspect raw events as they arrive, to confirm tracking works.

Event logs shows every event the property received, from every source, newest
first. It is a diagnostic screen rather than an analysis one: the question it
answers is "what is this property actually receiving".

Because it spans sources, it has a source column and a source filter that the
per-source log tabs do not need.

## What it tells you

The distinction that matters is between an event that arrived and was rejected,
and an event that never arrived:

* **Present but rejected.** It reached Soran and something about it was wrong.
  The log says what, and the fix is in the payload or the configuration.
* **Absent entirely.** It never reached Soran. The snippet is missing, blocked,
  or sitting below another script that failed first.

> [!NOTE]
>
> A disabled source is a third case worth knowing. The snippet keeps firing and
> Soran discards what it sends, so nothing is stored — and nothing arrives here.

## Related

> **[Install the tracker](/docs/get-started/install-the-tracker)**
>
> Get events flowing in the first place.

> **[Events and persons](/docs/concepts/events-and-persons)**
>
> What an event is and how events group into people.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.