> For the complete documentation index, see [llms.txt](https://docs.uppromote.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uppromote.com/guide-for-affiliate/affiliate-admin/affiliate-admin-dashboard.md).
# Affiliate Admin - Dashboard
In **Dashboard**, affiliates find their **affiliate link** or **coupon(s)** to share and send to customers. Any order resulting from the link/coupon will lead to a possible commission.
They can also use the **Get Product link** function to promote specific products. It allows affiliates to search for a product on the store and generate an affiliate link for that product. The affiliates can also add a source to the product link to track from which source the conversion comes.
Additionally, affiliates can use the **Get link with source** function to track where the traffic comes from *(such as Facebook, Twitter, or Instagram)*. The source will then be shown on the graph and the table below as well as on the **Commission** and **Payment** tab. The affiliates would know which channels are leading the conversion.
Affiliates can see all important data including Commission total and status according to graphs through periods. They can also adjust the period to show specific data.
---
# 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://docs.uppromote.com/guide-for-affiliate/affiliate-admin/affiliate-admin-dashboard.md?ask=&goal=
```
`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.