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

# Use the Events Log

> Use the Cometly Events Log to confirm that an event arrived, read its raw data and find the error message when an event fails.

A lead or sale is missing from your reports, or you sent a test event and cannot tell whether it arrived. The Cometly Events Log is where you check. An event is an action Cometly tracks, such as a form submission, a lead or a purchase.

When an event does not show up as expected, it usually either never reached Cometly, or it arrived with a field that is missing or in the wrong format. The Events Log shows the events Cometly receives, with the raw data of each one. Use it to monitor, verify and troubleshoot events as they arrive.

To open it, click **Events Manager** in the sidebar, then open the **Events Log** tab.

## What the Events Log is for

The Events Log is not designed for data analysis. It is the place to confirm that events are sent to Cometly correctly and contain accurate fields and data. If you send a test event to Cometly and need to confirm whether it was received correctly, check the Events Log.

Use it to:

1. **Verify incoming events.** Confirm when an event was sent to Cometly and that the raw data is accurate.
2. **Troubleshoot issues.** Inspect the payload fields of each event to find and fix problems.
3. **Monitor data flow.** See the events Cometly received, with their status.

## Choose a source: Server or Browser

Use the **Source** dropdown at the top of the log to choose which events you see:

* **Server** (the default): events sent to Cometly from a server, such as integrations, webhooks and the Cometly API. They all appear in one list.
* **Browser**: events the Cometly pixel fires on your website. The pixel's `init` event is not listed.

## What each column shows

| Column | What it shows |
| - | - |
| **Datetime** | When the event was received, in your account timezone. |
| **Event Name/Description** | The name of the event and, when it has one, its description. |
| **Source** | The integration or source that sent the event. |
| **Status** | The processing status of the event. |
| **Details** | **SUCCESS**, or the error message when something went wrong. |

The log shows 15 events per page, newest first. Use the arrows below the list to move between pages.

## Filter the server log

When **Source** is set to **Server**, you can narrow the list:

1. Under **Date**, pick a day.
2. Optional: under **Search payload**, type a value to look for in the raw data (for example an email address or an order ID). You need to pick a date first.
3. Click **Apply**.

## Status indicators

* **Green badge:** the event was received and processed without issues. The **Details** column shows **SUCCESS**.
* **Gray badge:** the event has not finished successfully yet, for example because it is still processing. Check the **Details** column.
* **Red badge:** there was an issue with the event. The **Details** column shows the error message, which you can use to troubleshoot the problem.

## View event details

> [!NOTE]
>
> When an event is sent to Cometly, it can take up to 15 minutes for it to appear in the reporting areas, such as the Report Builder or Ads Manager. However, **the event shows in the Events Log within 60 seconds**, so you can quickly verify that it was received and troubleshoot if needed.

Click a row to expand it and view the raw payload. It includes all the fields sent with the event, so you can:

* Verify the accuracy of the data.
* Check that all required fields were included.
* Diagnose and fix any data inconsistencies or errors.

In the expanded row, use **Search JSON...** to highlight a value in the payload, or click **Copy** to copy the whole payload.

## Troubleshoot with the Events Log

1. **Locate the event.** Set **Source** to **Server** or **Browser**, depending on the type of event you are investigating. For server events, filter by date and search the payload to find the specific event.
2. **Check the status.** Look at the **Status** column to see whether the event was processed or ran into an error.
3. **View the payload.** Click the row to expand it and inspect the raw data. Make sure all fields are correct and formatted as expected.
4. **Address errors.** If the event shows an error, read the message in the **Details** column. It helps you pinpoint the issue and take corrective action.

## Confirm the event is fixed

Send the event again, then find it in the Events Log. It is fixed when the row shows a green badge and the **Details** column shows **SUCCESS**. The event shows in the Events Log within 60 seconds, and can take up to 15 minutes to appear in the reporting areas.

## Frequently asked questions

### Why does the Events Log say "No events found"?

Cometly has no events to list for the **Source** and filters you selected. With **Server** selected, check the **Date** and **Search payload** filters, then confirm that your integration, webhook or API call is sending data. With **Browser** selected, the list fills once the Cometly pixel (the tracking script on your website) fires events.

### Why is my event in the Events Log but not in my reports?

Reports update later than the log. An event shows in the Events Log within 60 seconds, but it can take up to 15 minutes to appear in the reporting areas, such as the Report Builder or Ads Manager. If the row shows a red badge, read the error message in the **Details** column first.

### Can I filter or search browser events in the Events Log?

No. The **Date** and **Search payload** filters appear only when **Source** is set to **Server**. With **Browser** selected, use the arrows below the list to page through the events, newest first.

## Next steps

* [Learn how Cometly events work](https://docs.cometly.com/guides/events/how-events-work.md)
* [Send event data to Cometly with webhooks](https://docs.cometly.com/integrations/webhooks.md)
* [Test your pixel and events with the Cometly Pixel Helper](https://docs.cometly.com/guides/tracking/pixel-helper.md)
* [Check your whole setup with Tracking Health](https://docs.cometly.com/getting-started/tracking-health.md)
* [Browse all troubleshooting guides](https://docs.cometly.com/support/troubleshooting/overview.md)

Still have questions or need a hand? We're happy to help. Reach our team at [support@cometly.com](mailto:support@cometly.com).


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