> 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/it/di-cosa-vorresti-saperne-di-piu/platform-features/marketing-content/requests/requests-overview-for-partners.md).

# Panoramica delle richieste per i partner

Questo articolo offre una panoramica per aiutarti, in qualità di partner, a capire come creare e gestire le richieste. Le tipologie di richieste disponibili includono asset, valori di tracciamento o fondi per lo sviluppo del marketing. Creare e gestire queste richieste in modo efficace garantisce una collaborazione più fluida e una maggiore visibilità sulle interazioni con il brand, in corso e completate.

## Tipologie di richieste disponibili

* **Asset** - Richieste per uno specifico [asset creativo](https://help.impact.com/partner/it/di-cosa-vorresti-saperne-di-piu/platform-features/marketing-content/requests/request-assets/submit-and-manage-asset-requests-as-a-partner.md), ad esempio: *Richiesta di asset e-mail*, da parte di un brand.
* **Fondi per lo sviluppo del marketing** - [Richieste di fondi](https://help.impact.com/partner/it/di-cosa-vorresti-saperne-di-piu/platform-features/marketing-content/requests/submit-and-manage-marketing-development-fund-requests-as-a-partner.md) stanziati da un brand per sostenere iniziative di marketing.
* **Valore di tracciamento** - Richieste relative alle metriche di monitoraggio delle prestazioni, ad esempio: [*Richiesta di codice promozionale*](https://help.impact.com/partner/it/di-cosa-vorresti-saperne-di-piu/platform-features/marketing-content/promo-codes/view-and-request-promo-codes-as-a-partner.md), da parte di un brand.

  <div data-with-frame="true"><figure><img src="https://1708986086-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2FRam9LVAvDYxGNaWCkqTc%2FScreenshot%202026-05-22%20at%2018.02.51.png?alt=media&amp;token=95ce9faa-c486-4b87-9d8e-a4db2e90143d" alt="" width="563"><figcaption></figcaption></figure></div>

## Consulta gli stati e gestisci le richieste

Dopo aver inviato una richiesta a un brand, [puoi seguirne lo stato](https://help.impact.com/partner/it/di-cosa-vorresti-saperne-di-piu/platform-features/marketing-content/requests/request-assets/check-asset-request-status.md). Dopo l'invio, lo stato della richiesta sarà **Aperta**. Il brand potrà quindi **approvarla** o **rifiutarla** . Una volta soddisfatto dell'esito, il brand contrassegnerà la richiesta come **Completata**. Quando visualizzi una richiesta, potresti anche vedere i relativi dettagli e commenti.


---

# 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/it/di-cosa-vorresti-saperne-di-piu/platform-features/marketing-content/requests/requests-overview-for-partners.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.
