> 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/blocking-and-redirect-rules/test-a-redirect-rule.md).
# 测试重定向规则
您可以使用 A/B 测试来确保您的重定向规则带来的效果优于原始目标 URL。impact.com 建议您在为计划使用的重定向链接创建正式重定向规则之前，先对它们进行 A/B 测试。了解更多关于 [重定向路由规则](/brand/zh/what-would-you-like-to-learn-about/platform-features/blocking-and-redirect-rules/redirect-routing-rules-overview.md).
#### 设置 A/B 测试
您首先需要设置一个 [重定向规则](/brand/zh/what-would-you-like-to-learn-about/platform-features/blocking-and-redirect-rules/create-a-redirect-rule.md) 并设置一组特定条件。请按照以下步骤，确保您的规则设置正确。
{% hint style="success" %}
**注意：** 您将需要 `广告 ID` 您想要进行 A/B 测试的广告的。此信息可在 [管理广告](https://app.impact.com/secure/advertiser/engage/ads/manage-all-ads-flow.ihtml) 界面中进行设置。
{% endhint %}
1. 从顶部导航栏中，选择  **\[用户资料] → 设置**.
2. 在右侧，位于 *技术*，选择 **屏蔽与重定向**.
3. 在右上角，选择 **配置规则**.
4. 为您的规则添加一个 \*\*名称\*\*。
* 考虑使用一个能将此规则标识为 A/B 测试的名称。
5. 在 \*条件\* 部分，使用  **\[下拉菜单]** 按如下方式配置您的 A/B 测试：
* 将第一个条件设置为 *广告 ID* + *为* + {Ad ID}。
* 选择  **\[添加]** **和**.
* 将第二个条件设置为 *概率* + *小于* + *50*.
* 您必须完全按照描述设置这些条件。设置不同的条件（例如，选择  **\[添加]** **添加另一个** 而不是  **\[添加]** **和**）会使您的测试结果产生偏差。
6. 在……中 *操作* 部分，使用  **\[下拉菜单]** 将您的重定向规则配置为 *重定向* +（重定向链接协议）+（目标 URL）。
7. （可选）选择  **\[开启]** **安排规则** 以定义此重定向规则必须处于活动状态的时间段。
8. 设置 *排名* 将重定向规则的 **高**.
9. **保存** 您的规则。
#### 跟踪您的 A/B 测试
如果您想跟踪重定向规则的成功情况，可以使用 [汇总 A/B 性能报告](/brand/zh/what-would-you-like-to-learn-about/platform-features/multi-program-reports/operations-reports/aggregate-ab-performance-report.md)。该报告通常在用于测试特定着陆页 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/blocking-and-redirect-rules/test-a-redirect-rule.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.
