> For the complete documentation index, see [llms.txt](https://help.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.whaly.io/recipes/marketing/create-a-partner-dashboard.md).

# Create a partner dashboard

**Objective**

In every partnership, it is important to share, be it in life, in love or in business. For example, if your company outsources part of its lead acquisition process to external partners, it is important for them to have an overview of how successful you are with converting their leads into deals.

In this guide, you will learn how to structure and configure a partner dashboard that enables you to securely share this information back with your partners. 

### High level plan

* Understanding our partner dashboard
* Making our dashboard partner-ready
  * Adding a partner filter to our dashboard
  * Adding a sharing link
  * Hiding the partner filter from the report

### Understanding our partner dashboard

For this guide, we will assume that we have already built our Partner Dashboard, which gives us information about:

* Our leads conversion funnel
  * Number of new leads received
  * Number of qualified leads
  * Number of converted leads
* Our partners based generated revenue 
* Our partners commission 

You can take a look at our example dashboard below: 

![](/files/GeU4RWDJtvLv7LCBvvyE)

### Making our dashboard partner ready

#### Adding a partner filter to our dashboard

To make our dashboard partner ready, we will firstly need to be able to breakdown our view per partner. This steps essentially consists in adding a "Partner" filter to our dashboard, and will allow us to restrict the leads to the partner they are generated from. 

Let's get to work. On Whaly, open your partner dashboard, then: 

* click on Edit
* click on Add a filter
* select you partner identifier in the "Fields to filter from" list (in this example we will use `partner_name`) and give your filter a name
* in the "Tiles to update" tab, verify that the filter is applied to all the tiles you need

![](/files/p9XNyj58KfRknP6glx6K)

### Adding a sharing link 

We will use the sharing link feature to create a pre-filtered view of our dashboard that we will be able to send to our partners.

In order to do so: 

* Click on share
* Click on new sharing link
* Give it a name (we will use "Partner: Duff"), a password if you need to, and select set partner filter value to your partner's name. 

![](/files/VFSeNOPY55rNHPao6u35)

### Hiding the partner filter from the report

Great, now we have a sharing link. But before sending it, we will probably want to prevent our partner to filter on our others partners. To do so, we will hide the partner filter from the dashboard: 

* Click on edit
* Click on the partner filter settings
* Check "Hide your filter from the report" and save

![](/files/UUoSM0rbPhsUoAGYWD3r)

That's it, now we can send our sharing links to our partners. They will be able to view the dashboard to gain insights of how the partnership is performing :tada:


---

# 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://help.whaly.io/recipes/marketing/create-a-partner-dashboard.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.