> 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/brand/it/what-would-you-like-to-learn-about/platform-features/submit-and-modify-conversion-data/discover-conversion-data-errors.md).

# Scopri gli errori nei dati di conversione

Un motivo comune per inviare modifiche è perché hai scoperto che a impact.com sono stati segnalati dati di conversione errati. Puoi esaminare i dati di conversione che riceviamo per ciascuna azione per confrontarli con i dati nei tuoi sistemi.

#### Visualizza i pagamenti in sospeso

1. Dal menu di navigazione a sinistra, seleziona ![](https://1043985218-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage] → Transazioni → Payout in sospeso → Azioni**.
2. Da qui, puoi [rivedere i tuoi pagamenti in sospeso](/brand/it/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/payouts/filter-and-download-pending-payouts-list.md).
   * Questa schermata ti mostrerà informazioni su ogni azione in sospeso, come la data e l'ora in cui è stata segnalata l'azione, se è stato utilizzato un codice promozionale e molto altro. Puoi anche selezionare i dettagli dell'azione *ID azione* per visualizzare ancora più informazioni sull'azione, inclusa una cronologia del percorso di conversione (se tali informazioni sono state segnalate).


---

# 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/brand/it/what-would-you-like-to-learn-about/platform-features/submit-and-modify-conversion-data/discover-conversion-data-errors.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.