# Debug Analytics

Validate instrumentation with debugging and user lookup tools.

Source: https://amplitude.com/docs/analytics/debug-analytics

---

On this page

- [Before you begin](#before-you-begin)
- [Ingestion debugger](#ingestion-debugger)
- [User lookup](#user-lookup)
- [Step 1: Find yourself](#step-1-find-yourself)
- [Step 2: Analyze the event stream](#step-2-analyze-the-event-stream)
- [Instrumentation Explorer](#instrumentation-explorer)
- [View your triggered events](#view-your-triggered-events)

# Debug Analytics

Data validation is a critical step in the instrumentation process.

## Before you begin

Before you debug, you must instrument your events. If you haven't instrumented any events, Amplitude's servers don't receive data, and Amplitude has no data to display. Create a test app to test and validate your first event data.

## Ingestion debugger

Use the Ingestion Debugger in Amplitude to check requests, events and identify counts, and throttled users or devices:

1. Log in to Amplitude.
2. Click **Data** in the top nav bar and select [**Sources**](https://data.amplitude.com/amp-dev-docs/sources) from the left nav bar.
3. Click the **Ingestion Debugger** tab.

The ingestion debugger shows three charts: successful requests, events and identify counts, and error requests for the endpoints you specify. You can specify a timeframe of one hour or one week.

Below the ingestion debugger, Amplitude lists throttled users and devices from the last 30 minutes, plus silenced device IDs.

## User lookup

### Step 1: Find yourself

After you instrument your events, trigger some of those events on your own device. Then open Amplitude Analytics and navigate to [*Users > User Profiles*](http://analytics.amplitude.com/amp-dev-docs/activity). Search for yourself by user ID or device ID.

### Step 2: Analyze the event stream

In the user profile, the [event stream](/docs/analytics/user-data-lookup#activity) displays a user's entire event history, grouped by session. The most recent activity appears at the top of the list, and events populate the stream in ten seconds to one minute.

Clicking an event gives you detailed information about it, including the user property and event property values **at the time of that event**.

Because the event stream can update in real time, you can use it to make sure you're capturing new events correctly, or to troubleshoot or debug instrumentation errors. For example, if you trigger an event only one time but the event stream consistently displays two instances of the event, there could be an instrumentation error.

Click *Raw* to see more information and the event's raw data.

## Instrumentation Explorer

The Amplitude Instrumentation Explorer is an extension in the Google Chrome Web Store that helps you examine and debug your Amplitude Browser SDK instrumentation by interacting with your product. It captures each Amplitude event you trigger and displays the event in the extension popup. [Download the Instrumentation Explorer](https://chrome.google.com/webstore/detail/amplitude-event-explorer/acehfjhnmhbmgkedjmjlobpgdicnhkbp).

### View your triggered events

In the Instrumentation Explorer, the **Events** tab is where you can find detailed insights into the parameters of each event you trigger on your website. This includes `user_id`, `device_id`, `event_properties`, and `user_properties`.

Was this helpful?

<!--$-->

<!--/$-->