> ## 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.

# Events

> Inspect the raw activity Datalyr received.

Events is the best place to verify tracking and investigate a specific action. Each row is an event received by Datalyr—not an attributed conversion or a successful ad-platform delivery.

## Find an event

1. Open **Events** and choose a date range.
2. Search by event name, distinct ID, page, or city.
3. Use filters to narrow the event source and other available fields.
4. Select a bar in the volume chart to zoom into that time window. Clear the zoom chip to return to the full range.
5. Expand a row for a quick view, or open it for the complete event record.

The table is ordered by received time by default. Scroll to load more events. The total above the table comes from the complete range, so it can be larger than the rows currently loaded.

## What to inspect

* **Event name** — the stable action name, such as `pageview`, `signup`, or `purchase`.
* **Distinct ID** — the anonymous or known identity attached to the event.
* **Page and referrer** — where the action happened and where the visit came from.
* **Campaign fields** — UTMs and supported click identifiers captured on the journey.
* **Properties** — values supplied with the event, such as plan, product, amount, or currency.
* **Event and received times** — useful when offline queues or server processing delay an event.

You can copy the complete event from its detail panel when debugging an implementation.

## Verify a new event

1. Use a private window or a dedicated test account.
2. Perform the action once.
3. Search for the exact event name and your test identity.
4. Open the row and check the expected properties.
5. If it should become a conversion, verify the matching rule separately in **Conversions**.

<Warning>
  Do not send passwords, access tokens, payment details, health information, or other sensitive values in event names, URLs, or properties.
</Warning>

## No event appears

Check the date range, clear filters, and confirm you are viewing the correct workspace. Then use **Live** to see whether any activity arrives. Browser privacy controls, consent settings, blocked-page filters, and ad blockers can prevent browser events from being collected.