> 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/reporting-for-partners/declined-insertion-orders-report-for-partners.md).

# Report sugli ordini di inserzione rifiutati per i partner

Il **Report sugli ordini di inserzione rifiutati** mostra tutti i contratti che sono stati rifiutati nel corso del tuo tempo con impact.com. Questo report mostrerà il programma, il contratto (precedentemente noto come *ordine di inserzione*), la data di rifiuto e il motivo del rifiuto.

1. Dalla barra di navigazione in alto, seleziona ![](https://1708986086-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2Fgit-blob-3c5971fb7b03a98375488e97a4317afd60621298%2Fd0fbb4c2c189cdc83bc0eb8e906fa3cb66818d0a9daa1491ea48042160714ed2.svg?alt=media) **\[Cerca]**, quindi inserisci "Ordini di inserzione rifiutati."
2. Sotto il *Report* colonna, seleziona [**Ordini di inserzione rifiutati**](https://app.impact.com/secure/mediapartner/viewReport.report).
3. Da qui puoi vedere informazioni sui contratti che sono stati rifiutati.

   <table><thead><tr><th width="229.63671875">Colonna</th><th>Descrizione</th></tr></thead><tbody><tr><td><strong>Campagna</strong></td><td>Visualizza il programma per cui era previsto il contratto rifiutato.</td></tr><tr><td><strong>Ordine di inserzione</strong></td><td>Visualizza il nome del termine del modello seguito dal contratto rifiutato.</td></tr><tr><td><strong>Data di rifiuto</strong></td><td>Visualizza la data in cui il contratto è stato rifiutato.</td></tr><tr><td><strong>Motivo del rifiuto</strong></td><td>Visualizza il motivo per cui il contratto è stato rifiutato (se è stato fornito un motivo).</td></tr></tbody></table>

<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%2Fsigmn1QJ9WRtGZVfwhBD%2FScreenshot%202026-05-22%20at%2011.06.58.png?alt=media&amp;token=cb91e051-e3db-4339-9550-b63d3afbcb40" alt="" width="563"><figcaption></figcaption></figure></div>


---

# 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/reporting-for-partners/declined-insertion-orders-report-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.