> 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/contracts-and-template-terms/contracts/dynamically-pay-partners-with-the-shared-id.md).
# 使用共享 ID 向合作伙伴动态付款
参加 PXA 课程
Shared Id 可区分每个行为的流量来源，使您能够根据网站流量的来源调整转化佣金。合作伙伴可以将 Shared Id 作为额外参数添加到您的营销内容中。无论营销内容何时被纳入转化路径（例如，当客户点击横幅广告时），该参数都可以包含任意值，并会被 impact.com 跟踪。
1. 与您的合作伙伴讨论他们计划托管您的营销内容的网站域名。
* 确定合作伙伴计划托管您的营销内容的网站域名，对于使用 Shared Id 进行动态支付至关重要。如果不进行充分的调研，您的实际支付金额可能与预期不符。
2. [创建模板条款](/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/create-template-terms.md) ，用于根据……调整转化的支付金额 *推荐 SharedId*。这应与合作伙伴提供给您的域名保持一致。
* 所有会影响转化支付的网站域名都需要进行调整或限制。要更新某个域名的支付，请使用 [*支付组*](/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/set-payout-rules-using-payout-groups.md) 或 *支付调整*。要阻止支付，请使用 *支付限制*.
3. 您的合作伙伴会通过向营销内容中添加 Shared Id 来更新内容，然后将其托管在与 Shared Id 值匹配的网站域名上。
* 传递的 Shared Id 值必须与 *推荐 SharedId* 您与合作伙伴签订的合同中的支付规则完全匹配。如果不匹配，则支付不会动态更新。
* 对您添加到模板条款中的每个网站域名重复此步骤。
4. 转化会被跟踪。支付会根据传入的 Shared Id 值动态更新。
{% hint style="info" %}
**请与您的 CSM 仔细核对您的设置：** 如果您想在执行计划前再次确认动态支付设置，您可以联系您的 CSM，或者 [联系支持团队](https://app.impact.com/support/portal.ihtml?createTicket=true).
{% endhint %}
#### 其他资源
* [面向合作伙伴的 Sub ID 和 Shared ID 参数说明](/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/tracking/tracking-links/link-parameters/sub-id-and-shared-id-parameters-explained-for-partners.md) — 说明该参数如何工作，以及合作伙伴如何将其附加到您的营销内容中。
* 了解如何 [查看 Shared Id 绩效数据](/brand/zh/what-would-you-like-to-learn-about/platform-features/multi-program-reports/performance-reports-for-brands/view-shared-id-performance-data-as-a-brand.md).
---
# 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/contracts-and-template-terms/contracts/dynamically-pay-partners-with-the-shared-id.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.