> 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/tracking/credit-policies/last-to-cart-credit-policy-explained.md).
# 最后加入购物车归因政策说明
“最后加入购物车”政策类似于 [最后点击](/brand/zh/what-would-you-like-to-learn-about/platform-features/tracking/credit-policies/last-click-credit-policy-explained.md) 该政策，因为它会根据客户的行为来确定哪个合作伙伴获得转化的归因和分成。不同于由客户的最后一次点击决定结果，客户最后一次 *将商品加入购物车* 将决定获胜的合作伙伴。
在“最后加入购物车”政策下，在结账前引导客户将最后一件商品加入购物车的合作伙伴通常将获得该转化 100% 的归因和全部分成。不过，归因和分成的金额可能会受到你的 [参与奖励](/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/participation-bonuses-explained.md) 设置。
{% hint style="warning" %}
**兼容性要求：** 最后加入购物车需要手动 [通用跟踪标签（UTT）](/brand/zh/what-would-you-like-to-learn-about/platform-features/tracking/javascript-tag-tracking/tracking-with-universal-tracking-tag-utt.md) 设置和 [UTT `trackCart` 实施](/brand/zh/what-would-you-like-to-learn-about/platform-features/tracking/javascript-tag-tracking/tracking-with-utt-javascript-functions.md) 在你的加入购物车操作上。应用和插件集成不支持“最后加入购物车”，包括 Shopify、WooCommerce 和 BigCommerce。要使用“最后加入购物车”，你必须使用手动 UTT 集成，而不是应用或插件集成。如果你需要帮助迁移到手动 UTT 集成， [请联系支持团队。](https://app.impact.com/support/portal.ihtml?createTicket=true)
{% endhint %}
示例场景
ACME Corporation 经营一家在线直面消费者（DTC）的油漆店。由于合作伙伴的反馈，他们希望将政策从“首次点击”改为“最后加入购物车”。在与客户成功经理（CSM）讨论后，ACME Corporation 决定将重点放在客户何时将商品加入购物车。
尽管有这一变化，ACME Corporation 的转化路径并没有改变。客户仍然是在点击家居装修博客的横幅广告后购买油漆刷，在点击赞助搜索结果后购买防水布，并在点击赞助 Instagram 帖子后结账。采用新政策后，负责赞助搜索结果的合作伙伴现在获得了所有转化，因为是他们引导客户在结账前将最后一件商品（防水布）加入购物车。
{% hint style="info" %}
**我该如何申请此归因策略？** 联系你的 CSM（或 [联系支持团队](https://app.impact.com/support/portal.ihtml?createTicket=true)）以讨论启用“最后加入购物车”归因政策。你需要说明你为什么想使用此政策，以及是否所有合作伙伴都会采用“最后加入购物车”（如果不是，在一个旅程中出现多个政策时，应由哪种政策优先）。
{% endhint %}
---
# 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/tracking/credit-policies/last-to-cart-credit-policy-explained.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.
