> 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/seller-program/beta-seller-for-retailers/im-a-brand/seller-explained-for-brands.md).

# 面向品牌方的 Seller 详解

作为通过 零售商[^1]销售产品的品牌，您可以亲自推动销售增长。impact.com 的 Seller 解决方案可让您激励合作伙伴推广产品，从而增加产品在零售渠道的流量，为您提供一种可衡量的收入增长方式。

借助 Seller，您可以在一个平台上管理所有合作伙伴关系需求，包括发现合作伙伴、报告和付款。

## Seller 为像您这样的品牌提供哪些服务

* **全面掌控您的计划** — 您可以管理自己的计划，直接与合作伙伴互动，并自行设定佣金费率。
* **获取更深入的洞察** — 通过详细的报告，全面了解绩效，并清晰洞察客户在购买前接触过的触点。
* **拓展选择** — 掌握战略增长的主动权，而非完全依赖零售商的营销工作，并新增一种可靠的营销资源。
* **以低风险扩大规模** — 您只需为产品在零售渠道成功转化的情况付费，因此这是一种具有成本效益的增长方式。

<div data-with-frame="true"><figure><img src="https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FcNzhJux44U4xgLuszgXy%2Fundraw_holding-flowers_jc03%20(1).png?alt=media&amp;token=560442cc-331c-4aad-840e-edad0b13e250" alt="" width="563"><figcaption></figcaption></figure></div>

## 运作方式

1. 您会收到零售商提供的注册链接。
2. 您可以设置专属的 Seller 计划，以便与该零售商合作。
3. 零售商会审核并批准您的计划。
4. 获批后，您即可发现合作伙伴、设定佣金费率、发起营销活动、管理付款、跟踪绩效并优化策略。
5. 您可以针对每家希望合作的零售商重复此流程。

## 为什么要为每家零售商分别创建计划

您的 Seller 计划会关联一家零售商，以确保追踪准确，并让您轻松了解哪些做法有效。当计划中的所有点击、潜在客户和转化都与特定零售商的平台相关联时，您就无需猜测是哪家零售商的网站为您带来了成效。单独创建计划还可以让零售商审批您的计划，并确认他们愿意与您分享敏感的客户数据。

## 开始使用时的预期体验

* **引导式设置** — 借助分步帮助文档的指导，只需几分钟即可创建自己的计划。
* **强大工具** — 利用 impact.com 的功能轻松与合作伙伴互动、自动处理付款并跟踪绩效。
* **持续合作** — 通过产品推广或效果营销活动，与零售商发掘更多机会，实现共同增长、互利共赢。

<a href="https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/seller-program/beta-seller-for-retailers/im-a-brand/sign-up-for-a-seller-program-as-a-brand.md" class="button primary">立即开始！</a><br>

[^1]: 一种在线商店，为卖家品牌或商家提供向更多客户销售产品的机会。例如，WayneMart.com 向客户销售来自 Dynamite Labs、Anvil ForgeMasters 和 Bats 'n Things 等制造商的产品。


---

# 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/seller-program/beta-seller-for-retailers/im-a-brand/seller-explained-for-brands.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.
