> For the complete documentation index, see [llms.txt](https://track360.gitbook.io/track360/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://track360.gitbook.io/track360/section-3-deals-and-loyalty-programs/editor/3.2-manage-deal.md).

# 3.2 Manage Deal

* On the Sidebar Menu go to **Deals**
* On the upper bar will be presented the **Filters**, where it is possible: **Filter by Name** of a deal; **Deal Status** between enabled (still active deals), disabled or both; **Types** of deal (e.g. CPA, CPI, RevShare); **Created by** “Me” in case you want to show deals only created by you, “Everyone” in case you want to show deals created by everyone
* On the right top, click on **Download** button to export all deal details into an Excel file for external analysis or record-keeping
* Use the **Reset Filters to Default** button to reset all filters chosen to default options

<figure><img src="https://4110691288-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1iHXZgeTSXZwHDnWa5S8%2Fuploads%2FHVqqvWzoH2j2bD5kCxgw%2Fimage.png?alt=media&amp;token=33fc05d0-16bc-46db-9f78-26f0f1d169ee" alt=""><figcaption></figcaption></figure>

* The listed deal shows information of each deal by row where:
  * **Deal ID**, the ID given to each unique deal
  * **Detail icon**, provides an overview of the deal’s configuration, condition and formula
  * **Name**, given name to describe each deal
  * **Default Role**, displays which role this deal is attained to
  * **Type**, presents the type of deal
  * **Period**, displays that certain terms, such as payments, are recurring on a set timeframe basis
  * **Currency**, gives information on the type of currency used in the deal
  * **Enabled?**, states whether the deal is active or not
* On the right side of each deal, it provides an **Actions Menu** with a distinct function:
  * **Create Deal based on this one,** creates a new deal with the selected deal as a template, allowing alterations to conditions and formulas. You will be able to modify the deal and only save it as a new deal
  * **Deals Settings,** allows you to alter some specific deal details. Modifying the deal's name, type of the deal (e.g., Hybrid, CPA), and affiliate role.
  * **Deals Asigned,** displays all affiliates who were ever assigned this deal (whether currently active or in the past)
  * **Formula,** displays the formula used to calculate the deal, ready to copy to clipboard
  * **Deals Details,** provides an overview of the deal’s configuration, condition and formula

<figure><img src="https://4110691288-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1iHXZgeTSXZwHDnWa5S8%2Fuploads%2FIV2gbwtQAMScuIN4SPAg%2Fimage.png?alt=media&amp;token=a484b0a0-1764-44e1-a3db-99ea9b065dd4" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Once saved, deals can only be modified for name, type, and role. If the structure is modified, the deal will be saved as a new deal
{% endhint %}


---

# 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://track360.gitbook.io/track360/section-3-deals-and-loyalty-programs/editor/3.2-manage-deal.md?ask=<question>&goal=<user_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.