> For the complete documentation index, see [llms.txt](https://help.branch.io/llms.txt).

# Liveview (New)

> Access Liveview for advanced event monitoring and webhook debugging.

## Get started

To access Liveview, go to **Configuration** **>** **Testing & Monitoring**, then select the **Liveview** tab. To use Liveview, you need **View** access to **App-level Settings** and **Sensitive Data**.

Liveview remembers your event type and filters in your current browser, and runs them again the next time you open the tab.

> **Attention**
>
> Branch's new experience is rolling out in phases, so your interface may differ. This article covers the Testing & Monitoring page in the new experience. To learn more, see [New Branch Overview](https://help.branch.io/account-hub/new-branch-overview.md).

### 1. Choose an event type

Select the event type you want to view from the dropdown menu in the upper left, then select **Update Query**. If no query is running, the button reads **Run Query** instead.

### 2. Add filters (optional)

Select **Build Query** to open the query builder modal. If you already have filters, the button reads **Edit Query**. Here you can:

- Change the **Event Type** from the dropdown.
- Add filters by selecting a field, an operator, and a value. The operators are equals, does not equal, contains, and does not contain.
- Select **+ Add filter** to add additional filters.

Select **Save**, then select **Update Query** to apply your filters. Saving the filters alone doesn't change the results.

Some of the most useful filters include `name` (for example, `PURCHASE`), `feature`, `channel`, `campaign`, and device identifiers like `IDFA`.

### 3. Customize columns (optional)

Select the **Columns** dropdown to show or hide columns in the results table. You can search for available columns and check or uncheck them to customize your view.

To go back to the default columns, event type, and filters, select **Restore default view** from the three-dot menu next to the query button.

Select any row in the results table to see that event's details.

### 4. View Webhook records

To see the webhook request and response for debugging, select webhooks from the event type dropdown. This allows you to see what information is getting sent and whether it was successful (200 status code) or not (400 or 500 status code).

> **Note**
>
> If you're trying to view Webhook Records going to a data integration, you'll need to filter by `webhook_partner_key` and specify the value in the format `di_partner_name`. For example, Adobe Analytics Processing Rules is `di_adobe_analytics_pr`, Mixpanel is `di_mixpanel`. If you don't add this filter, the webhook records for those data integrations will not show.

## Supported event types

Liveview enables you to debug the following event types:

- click
- branch cta view
- sms sent
- open
- install
- reinstall
- web session start
- pageview
- content event
- commerce event
- custom event
- user lifecycle event
- webhooks

Liveview allows advanced filtering on a number of dimensions, including per-event and per-device dimensions not surfaced elsewhere in Branch. Using Liveview requires **View** access to **App-level Settings** and [Sensitive Data](https://help.branch.io/account-hub/default-access-levels-users-roles-permissions.md#access-levels).

## FAQs

> **Why is my link showing the same campaign name even though I'm sending dynamic values via query parameters?**
>
> We don't allow you to override default values set for analytics parameters ('~channel', '~tags', '~campaign', '~feature') at the link level via query parameters. This is done to prevent spam.

> **Why am I able to see revenue data on Liveview but not on the analytics page?**
>
> Revenue data will only populate for `PURCHASE` events. The event must be a standard Branch Commerce Event with the type `PURCHASE`, as outlined in the Commerce table in this [section](https://help.branch.io/developer-hub/track-branch-events.md#track-commerce-events).
>
> If you use a different type of event other than a `PURCHASE` event, you'll only see the data in Liveview, and the same data will not populate the dashboard.
>
> For more information, refer to our documentation on [Tracking Commerce, Content, Lifecycle and Custom Events](https://help.branch.io/developer-hub/track-branch-events.md).