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

# Liveview

> Debug Branch objects with legacy Liveview. In new Branch, Liveview lives under Testing and Monitoring.

> **Warning**
>
> Please note that this article explains the [legacy Branch experience](https://help.branch.io/marketer-hub/branch-dashboard-overview.md) for Liveview, which is slated for deprecation.  
>
> In the [new version of Branch](https://help.branch.io/account-hub/liveview-new.md), attribution windows are configured under **Testing & Monitoring** → **Liveview**.

## Supported objects

Liveview enables you to debug the following objects:

1. Events
2. Webhook records

`Events` and `Webhook records` allow advanced filtering on a number of dimensions, including per-event and per-device dimensions not surfaced elsewhere on the Dashboard. Access to this data is determined by the [Sensitive Data access level](https://help.branch.io/account-hub/default-access-levels-users-roles-permissions.md#access-levels).

## Getting started

### 1. Choose an object

Choose among the supported objects using the tabs at the top of the screen.

![](https://help.branch.io/img/7a3ce28-liveview-objects.png "liveview-objects.png")

### 2. Choose event type

If you are viewing `Events`, then be sure to choose the appropriate event type from the dropdown, e.g. `commerce event`.

![](https://help.branch.io/img/99c8b94-liveview-events-filter.gif "liveview-events-filter.gif")

### 3. Add advanced filters (optional)

Add advanced filters. Some of the most useful include `name` (e.g. `PURCHASE`), `feature`, `channel`, `campaign`, and device identifiers like `IDFA`.

![](https://help.branch.io/img/c5e5ea3-liveview-add-filter.gif "liveview-add-filter.gif")

> **What does it mean if the OS is "Robots" in Liveview reports?**
>
> This means that one of these conditions are true:
>
> 1. The link clicks are not from a true iOS, Android, or other platform user agent
> 2. The link clicks are from a bot like a Google scraper

### 4. Viewing Webhook Records

To see the webhook request and response for debugging, you can use the webhook records tab. 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).

![](https://help.branch.io/img/dbe6778-Screen_Shot_2023-01-26_at_11.51.52_AM.png "Screen Shot 2023-01-26 at 11.51.52 AM.png")

> **Caution**
>
> **If you are trying to view Webhook Records going to a Data Integration**
>
> You will 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, etc. If you don't add this filter the webhook records for those DIs will not show.

## FAQs

> **Why is my link showing the same campaign name even though I’m sending dynamic values via query parameters?**
>
> We do not 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 will only see the data in Liveview, and the same data will not populate the Dashboard.
>
> For more information, please refer to our documentation on [Tracking Commerce, Content, Lifecycle and Custom Events](https://help.branch.io/developer-hub/track-branch-events.md).