> 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/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/tracking/piggyback-pixels/manage-partner-piggyback-pixels-as-a-partner.md).

# 作为合作伙伴管理旁路像素

通常，当发生转化时，数据会从品牌的网站传到 impact.com 的内部系统，然后再传给你。这个两步传输过程可能会导致你所推动的转化在报告中显示前有轻微延迟。Piggyback 像素可作为捷径，直接从品牌网站拦截这些数据。 [了解更多](/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/tracking/piggyback-pixels/partner-piggyback-pixels-overview.md).

## 管理你的 piggyback 像素

1. 在顶部导航栏中，选择 **发现 →** [**品牌**](https://app.impact.com/secure/mediapartner/marketplace/new-campaign-marketplace-flow.ihtml#joinState=joined\&sortBy=salepercent\&sortOrder=DESC).
2. 选择你要管理 piggyback 像素的品牌，然后选择 ![](https://1152657667-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2FAdEhp3l0LUFmpTmLdgZK%2F%5BMore%5D%20vNext%202.svg?alt=media\&token=def8ea40-8fca-4be5-ad36-8d5bb4bb4b6b) **\[更多]** → **跟踪集成**.
3. 对于你要管理 piggyback 像素的事件类型，在 *操作* 列下，选择 ![](https://1152657667-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2Fgit-blob-df93ac0f80fc5cece7983980a5ce3fbcf19aabce%2F3ef9d737089bc07dbb7e4fd41a97edfbaec261e4f55ab3a1666f3daf957f69c3.svg?alt=media) **\[下拉菜单]** → **编辑**.
4. 阅读通知并选择 **我已了解，继续**.
5. 选择跟踪像素类型。
6. 添加跟踪像素代码或图片源 URL。
7. 如果你想向 piggyback 像素添加更多参数，请选择 **显示/隐藏可选参数**。请参照 *可选 URL 参数* 以获取更多信息。
8. 选择 **保存**.
   1. 当包含 piggyback 像素的确认页面加载时，像素会通过浏览器 cookie 将其已跟踪的数据发送到跟踪软件，并将你关联到订单确认。
   2. 请记住，piggyback 像素只需要浏览器 cookie 即可触发，因此你可能会遇到假阳性和假阴性。这可能导致模板条款未达成、最后点击未被记录，以及其他错误报告。

{% hint style="success" %}
**注意：** 如果在操作锁定周期结束前未更正，假阳性操作可能会失效。其他失效情况包括使用重复的订单 ID 注册、超出操作重复次数的模板条款，以及品牌与合作伙伴之间缺少有效的模板条款，这通常是由于 piggyback 像素误触发造成的。
{% endhint %}

### 可选 URL 和商品级参数参考

URL 可以包含可选参数值。URL 加载时，这些参数会动态替换为实际值。

所有 URL 参数都基于同一个 URL 模板，即 `https://www.domain.com?[Parameter]={Example}`。当调用该 URL 时， `{Example}` 将填充 `[Parameter]` 所请求的数据。

<details>

<summary>URL 参数参考</summary>

<table><thead><tr><th width="200.3046875">URL 参数</th><th>描述</th></tr></thead><tbody><tr><td>{CampaignId}</td><td>你的合作品牌 ID。</td></tr><tr><td>{ActionTrackerId}</td><td>你要为其添加 piggyback 像素的操作跟踪器 ID。</td></tr><tr><td>{MediaPartnerId}</td><td>合作伙伴（即你）的 ID。</td></tr><tr><td>{SaleAmount}</td><td>该操作的销售金额，以品牌偏好的货币表示。此项仅可用于销售操作跟踪。</td></tr><tr><td>{Currency}</td><td>该操作的原始货币，即用于购买产品或服务的货币。</td></tr><tr><td>{Network_SaleAmount}</td><td>该操作商品的金额，以品牌偏好的货币表示。此项仅可用于销售操作跟踪。</td></tr><tr><td>{PromoCode}</td><td>该操作的促销代码。</td></tr></tbody></table>

</details>

* 也可以向 piggyback 像素添加商品级参数。它们能让你更详细地了解具体售出了什么、售出数量多少等信息。
* 与 URL 参数类似，商品级参数也基于一个模板。在这种情况下，格式为 `{join(items,i,"[Function]{i}={i.[Function]}","&","?")}`。你希望跟踪的任何商品级参数都需要替换 `[Function]`.
* 例如，如果你想跟踪售出商品的 sku 编号，你的参数将是 `{join(items,i,"sku{i}={i.sku}","&","?")}` 并会生成 `?sku1=[sku 1 number]&sku2=[sku 2 number]...` 并持续到该操作中售出的商品数量为止。


---

# 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/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/tracking/piggyback-pixels/manage-partner-piggyback-pixels-as-a-partner.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.