> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/dashboard/brand-dashboard-widgets.md).
# Brand Dashboard Widgets
The dashboard widgets on the [Home](https://app.impact.com/secure/advertiser/engage/aview.ihtml?t=u) screen provide an overview of your impact.com account as a brand.
{% hint style="danger" %}
**Important:** The brand dashboard widgets will only be populated with data if you have the required feature or add-on enabled in your account. If you want to be included in a feature, [contact support](https://app.impact.com/support/portal.ihtml?createTicket=true&).
{% endhint %}
#### To Do List widget
The *To Do List* widget lists all your pending tasks that are ready to be actioned. This widget helps you keep track of pending tasks straight from the dashboard and ensures you complete all pending tasks. These tasks can be actioned by selecting the relevant buttons next to each listed item.
#### Program Health widget
The *Program Health* widget shows your campaign trends over a period of time. It can be customized to show a range of different metrics.
Customize the Program Health widget
* Above the widget, select the date range to change the displayed data.
* Select **Show Compare** to apply a date range for comparison (e.g., *Previous Month*).
* Select **Edit** to modify the widget.
* Use the first  **\[Drop-down menu]** to select the metric you want to customize.
* Select your preferred chart style (*Line Chart*, *Area Chart*, or *Bar Chart*) to visualize your data.
* Select  **Enable monthly goals** to enter specific targets for each measure.
* Use the  **\[Drag handles]** to reorder your metrics, or select  **\[Remove]** to delete a measure.
* Select one of the metrics (*Clicks*, *Actions*, *Action Cost*, *Revenue*, *Total Cost*, *Conversion Rate*) to see the related performance metric appear in the chart.
* Hover over any peak or summit on the chart to see the total recorded amount of the selected metric for that day.
#### Partners you'll love widget
The *Partners you'll love* widget shows a curated selection of potential partners that you can recruit. View essential partner details without leaving your dashboard, including:
* **Tier status:** Displays the [partner's size](/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/partner-management/partner-size-rating-criteria.md).
* **Content categories:** Displays the partner's specific content expertise.
Select **Go to Discover** to access the [Partner Marketplace](/brand/what-would-you-like-to-learn-about/platform-features/find-partners-and-creators/look-for-specific-types-of-partners.md).
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/dashboard/brand-dashboard-widgets.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
