> 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/zh/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).

# 查看并回复促销代码监控违规评论

<a href="https://pxa.impact.com/student/activity/1117601?sid=0c0e3e5c-54c9-4435-9bee-ebcdccb7f292&#x26;sid_i=0?utm_source=app.impact.com&#x26;utm_medium=owned-platform&#x26;utm_content=pro-350&#x26;utm_campaign=help-center" class="button primary">参加 PXA 课程</a>

合作伙伴可以在未关闭的违规中添加自己的评论，查看时会以线程形式显示。

{% hint style="info" %}
**注意：** 添加评论时，请务必选择 **保存违规** 屏幕底部的，以确保您的评论已保存。
{% endhint %}

1. 在左侧导航菜单中，选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-db1131f1b95ffbfa026aac99b07a7ffe0564b3b6%2F477fa23d9ffe966a6d1191fbd504e9a68f4c3918efe5cee5cb7bbd826e591fea.svg?alt=media) **\[保护]** → **违规**.
2. 在……上 *违规* 在屏幕上，将鼠标悬停在您想查看或添加评论的违规项上，然后选择 **编辑**.
3. 前往 *备注* 部分查看——如果您想回复，请选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-6282f271b7521383385339243690b303086736d9%2F3b5a585dd2895bdf1c30d1236c72ba590dddd18717863b27074c8d313d05ae20.svg?alt=media) **添加评论**.
4. 选择 **添加** 以提交您的评论。
5. 选择 **保存违规** 以保存您的评论并更新该违规项。


---

# 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/zh/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=<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.
