> 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
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=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.