#### プロモーションコード通知を設定する
プロモーションコード違反が発生したときに通知されるよう、通知を設定できます。
1. 上部のナビゲーションメニューから を選択します  **\[通知]**.
2. パネルの右上隅で を選択します **設定**.
3. までスクロールします *プロモーションコード違反* セクション。
4. 次の *プロモーションコード違反* ドロップダウンリストで、通知の配信方法を選択します。
* **イベント発生時にメールを送信**
* **毎日のダイジェストメールを送信**
* **毎週のダイジェストメールを送信**
* **SMSを送信**
* **個別設定（詳細）**：このオプションでは、新しい違反と違反の更新に対して個別の通知設定を選択できます。
---
# 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/ja/what-would-you-like-to-learn-about/platform-features/protect-and-monitor-your-performance-program/promo-code-monitoring/review-promo-codes.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.
