> For the complete documentation index, see [llms.txt](https://guides.fieldedgeapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.fieldedgeapp.com/guide-to-canvassing-and-calls/reporting/tracking-performance-in-hq.md).

# Tracking performance in the HQ Dashboard

The Performance section of the FieldEdge HQ Dashboard is your main tool for understanding what's happening in the field. It has three views, each suited to a different question.

{% hint style="info" %}
You need Campaign Manager access to use the Performance page. Open the HQ Dashboard at [hq.fieldedgeapp.com](https://hq.fieldedgeapp.com) and select **Performance** from the sidebar.
{% endhint %}

## Reports

Reports shows aggregated metrics and charts for a selected time period. Use it after (or during) a campaign push to answer questions like "how many contacts did we make this week?", "what was our door answer rate?", or "which contact statuses are most common?". You can filter by activity type and date range, and drill down by canvasser.

## Stream

The Stream is a live feed of every contact your team logs, updating in real time. Use it while a canvass or phone banking session is actively underway — you can watch activity come in as it's completed, filter by team member or outcome, and spot location anomalies as they happen.

## Team

The Team screen breaks down performance by individual team member. Use it to see who's making the most contacts, who's having quality conversations, and how output varies day by day across your roster.

{% hint style="info" %}
The Team screen is a new feature in [HQ Dashboard V2](/product-tour-or-hq/early-access.md), currently in early preview.
{% endhint %}

For a full breakdown of every metric, filter, and widget across all three views, see the [Performance reference in the Product Tour](/product-tour-or-hq/performance.md).

## What to check if data seems off

**Activity isn't appearing in the Stream**: The Stream only captures contacts logged through the **Canvass** or **Call Time** features in the mobile app. If a team member logs contact via NationBuilder's native Log Contact action — even with Door Knock or Phone selected as the method — it won't appear in the Stream or any field activity metrics.

**Support level stats look low**: Support level is optional in FieldEdge. Avg. Support Level and Confirmed Support Level only reflect contacts where it was recorded.

**A contact status is missing from the Outcome chart**: Only contact statuses enabled in [App Customization](/product-tour-or-hq/app-customization.md) are available to field users, so disabled statuses won't appear here.

## Further reading

{% content-ref url="/pages/81skv3NJj2yndoj1ERkb" %}
[Performance](/product-tour-or-hq/performance.md)
{% endcontent-ref %}

{% content-ref url="/pages/Sf0BrPOsYcKoMxKrFd8k" %}
[User location tracking](/guide-to-canvassing-and-calls/reporting/user-location-tracking.md)
{% endcontent-ref %}

{% content-ref url="/pages/0dlMVObDuqRd3J6ksr6p" %}
[Activity in NationBuilder](/guide-to-canvassing-and-calls/reporting/filtering-activity-in-nb.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guides.fieldedgeapp.com/guide-to-canvassing-and-calls/reporting/tracking-performance-in-hq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.