> 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/protect-and-monitor-your-performance-program/promo-code-monitoring/view-and-respond-to-promo-code-monitoring-violation-comments.md).
# Afficher et répondre aux commentaires sur les violations de surveillance des codes promo
Suivez la formation PXA
Les partenaires peuvent ajouter leurs propres commentaires à une violation ouverte, qui apparaîtront sous forme de fil de discussion lors de sa consultation.
{% hint style="info" %}
**Remarque :** Lors de l’ajout de commentaires, veillez toujours à sélectionner **Enregistrer la violation** en bas de l’écran pour vous assurer que votre commentaire est enregistré.
{% endhint %}
1. Dans le menu de navigation de gauche, sélectionnez  **\[Protéger]** → **Infractions**.
2. Dans la *Infractions* écran, survolez la violation que vous souhaitez consulter ou à laquelle vous souhaitez ajouter des commentaires, puis sélectionnez **Modifier**.
3. Accédez à la *Commentaires* section pour consulter — si vous souhaitez répondre, sélectionnez  **Ajouter un commentaire**.
4. Sélectionnez **Ajouter** pour soumettre votre commentaire.
5. Sélectionnez **Enregistrer la violation** pour enregistrer votre commentaire et mettre à jour la violation.
---
# 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/protect-and-monitor-your-performance-program/promo-code-monitoring/view-and-respond-to-promo-code-monitoring-violation-comments.md?ask=&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.