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

# Découvrir les erreurs de données de conversion

Une raison fréquente de soumettre des modifications est que vous avez découvert que des données de conversion incorrectes ont été signalées à impact.com. Vous pouvez consulter les données de conversion que nous recevons pour chaque action afin de les comparer aux données de vos propres systèmes.

#### Voir les paiements en attente

1. Dans le menu de navigation de gauche, sélectionnez ![](https://57104473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage] → Transactions → Paiements en attente → Actions**.
2. À partir d’ici, vous pouvez [consulter vos paiements en attente](/brand/fr/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/payouts/filter-and-download-pending-payouts-list.md).
   * Cet écran vous montrera des informations sur chaque action en attente, comme la date et l’heure auxquelles il a été signalé que l’action s’était produite, si un code promo a été utilisé, et bien plus encore. Vous pouvez également sélectionner l’ *ID de l'action* pour consulter encore plus d’informations sur l’action, y compris une chronologie du parcours de conversion (si cette information a été signalée).


---

# 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/fr/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.