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

# Check your events

> Confirm that events are arriving in Data → Events and that they carry what RevBridge needs to identify each person.

Every purchase, sign-up or abandoned cart reaches RevBridge as an **event**: from your store connection, from Eduzz, from the [Events API](https://docs.revbridge.ai/developer/ingesting-events.md) or from the [Web SDK](https://docs.revbridge.ai/developer/web-sdk.md). **Data → Events** shows what arrived, so you can confirm a new integration works before you build audiences or campaigns on it.

## Check that an event is arriving

**1. Open Data → Events**

The **Received events** tab lists every event name your workspace has received: its share of all events and of people, its revenue, its identification score and when it was last received.

**2. Find the event**

Search by name, for example `purchase` or `checkout_abandoned`. Totals can take up to 5 minutes to reflect new events; click **Refresh list** if you just sent one.

**3. Open its details**

Click the event to see **Total Events**, **Unique Users** and **Total Revenue**, and three tabs: **Properties**, **Identification** and **Activity**.

## Check the data inside an event

On the **Properties** tab you see every property sent with that event, how often it is filled and up to 3 examples received in the last 90 days. Use it to confirm that fields like the order value or the product IDs arrive in the format you expect.

The **All properties** tab lists properties across every event, with their value format (Text, Number, Boolean or Object / JSON). Open a property to see its most frequent values and the events that use it.

## Check that people are identified

An event is only useful if RevBridge can tell who it belongs to. The **Identification** tab gives each event an **Identification coverage** score from 0 to 10, based on how often the event carries an email, a phone, a user ID and a first and last name. Email, phone and ID count the most.

Under **Where identification can improve**, RevBridge shows which identifier to fill, on how many events, and how much the score would rise.

> [!NOTE]
>
> The score measures whether identifiers are present, not whether they are valid. A wrong email still counts.

## If an event is missing

* Check the source: [Data → Overview](https://docs.revbridge.ai/integrations/data-overview.md) for store connections, the [Eduzz card](https://docs.revbridge.ai/integrations/eduzz.md) for Eduzz.
* For events sent by your developers, see [Ingesting events](https://docs.revbridge.ai/developer/ingesting-events.md) and [Event types](https://docs.revbridge.ai/developer/event-types.md).

> [!TIP]
>
> **Ask the assistant.** With the [RevBridge MCP](https://docs.revbridge.ai/assistant/overview.md) connected, try:
> "Check this event payload before our backend starts sending it."


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