> 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/event-risk/view-validation-patterns-for-conversion-events.md).

# 查看转化事件的验证模式

以下步骤将引导您查看我们为您的订单 ID 和转化页面 URL 设置的验证规则。

{% hint style="warning" %}
**重要：** 如果您想修改这些规则中的任何一项并设置其他规则，请 [联系支持团队](http://mailto:tech-support@impact.com/?subject=Conversion%20Spoofing%20Validation%20Rules%20Request%22%20target=%22_blank).
{% endhint %}

1. 从左侧导航菜单中，选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage]** → **报告** → **更多报告**.
2. 在 *类别* 筛选，选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-9fd92d4378edf839f6a1f6fc0beaa1660b3892b5%2F69842c54f03332c1e2eed608d72b25ad10248384a914164a7255a1e94dc76ee2.svg?alt=media) **\[未选中复选框]** **保护**，然后选择 **转化欺诈规则**.
3. 查看每种事件类型的转化欺诈验证规则：

   | 列名             | 说明                                                          |
   | -------------- | ----------------------------------------------------------- |
   | 事件类型名称         | 该事件类型的名称。                                                   |
   | 状态             | 该事件类型的状态，例如， *有效*.                                          |
   | 类型             | 转化事件的类型，例如线上销售或潜在客户。                                        |
   | 订单 ID 正则表达式    | 用于验证您的订单 ID 的正则表达式。不匹配的事件将被移至 *有风险* 选项卡，并且除非明确批准，否则将被撤销。    |
   | 转化页面 URL 正则表达式 | 用于验证您的转化页面 URL 的正则表达式。不匹配的事件将被移至 *有风险* 选项卡，并且除非明确批准，否则将被撤销。 |


---

# 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/event-risk/view-validation-patterns-for-conversion-events.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.