> 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/partner/what-would-you-like-to-learn-about/platform-features/dashboard/submit-leads-as-a-partner.md).
# Submit Leads as a Partner
B2B brands on impact.com may offer payouts for qualified leads — these can be submitted via the *Submit a Lead* widget. If you're a B2B partner working with one of these brands, this widget will appear on your impact.com partner dashboard.
In most cases, a brand accepting leads will have a third-party integration with impact.com to collect those leads, such as Hubspot or Salesforce CRM. The *Submit a Lead* widget acts as a portal to that brand's lead-submission system.
## Submit a lead
1. On the partner dashboard, find the *Submit a Lead* widget.
2. Use the  **\[Drop-down menu]** to select the brand that will receive your lead, then select **Create Lead**.
3. In the modal, fill out the required fields for this lead, then select **Submit**.
## View my leads
The *My Leads* report shows leads that you've submitted to brands.
{% hint style="warning" %}
**Important:** A brand has to grant you access to this report. If you don't see this report, it's because you have not been granted access to it by the brand.
{% endhint %}
1. From the top navigation bar, select **Reports →** **More Reports**.
* Alternatively, from the top navigation bar, select **Reports** **→ More → More Reports**.
2. From the *Category* filter next to the search bar, select **Performance**.
3. Select **My Leads**.
---
# 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/partner/what-would-you-like-to-learn-about/platform-features/dashboard/submit-leads-as-a-partner.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.
