> 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/actions-and-payouts/actions/system-reattributed-actions-explained.md).

# 系统重新归因动作说明

您可以 [可以撤销或修改操作](/brand/zh/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/payouts/approve-reverse-and-modify-pending-payouts-for-actions.md) 在它们锁定之前。不过，某些操作会由 impact.com 系统撤销，这些操作被称为系统重新归因操作。

当您 [查看已撤销操作列表](/brand/zh/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/actions/view-a-list-of-reversed-actions.md)时， *撤销原因* 筛选器中可以包含撤销原因 `系统重新归因订单`，这可能有以下两种原因之一：

1. **用户发起的重新归因：** 您请求在锁定前重新归因某项操作。
   * impact.com 可以更正归因，以确保尚未锁定的操作仍可计入。系统重新归因操作并非在平台中发起。请 [联系支持团队](https://app.impact.com/support/portal.ihtml?createTicket=true&&) 如需对任何操作重新归因，请寻求帮助。
2. **系统发起的重新归因：** impact.com 因数据质量原因执行了重新处理。
   * impact.com 更正归因，以确保正确的合作伙伴能够获得原本会归因于媒体渠道或其他合作伙伴的操作的佣金。此更正可能因数据质量原因而发生，例如数据处理过程中的问题影响了事件关联。

用户发起和系统发起的重新归因均由 impact.com 处理，因此这两种类型始终都会有 `系统重新归因订单` 作为撤销原因。

**具有重复 OrderId 的操作**

当 impact.com 因以下原因撤销某项操作时 `系统重新归因订单`，会创建一个新的 `待处理` 操作，其 orderId 相同。只有该 `待处理` 操作才被视为可支付。


---

# 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/actions-and-payouts/actions/system-reattributed-actions-explained.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.