> 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/reach-out-to-partners/partner-management/partner-size-rating-criteria.md).

# 合作伙伴规模评级标准

合作伙伴规模评级通过外部来源和 impact.com 数据来确定。这些因素相互作用，并以不同方式反映每个合作伙伴各自的业务。创作者层级按社交关注者或订阅数进行划分。请参见 *创作者层级规模* 了解创作者层级的定义方式。

<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%2Fgit-blob-54cc75799167be20786198bdd5aad98ee9e13bb7%2F3b524d671a73e1462d3997c38eb510fc57858bf3d5dbfc9ad9f2c22e3de3a3bc.png?alt=media" alt=""><figcaption></figcaption></figure></div>

#### impact.com 数据如何使用？

对于在 impact.com 上有活跃行为的合作伙伴，合作伙伴规模将反映近期合作伙伴活动的每日汇总：

* 带来的操作/销售数量以及赚取的支付金额
  * 内部 impact.com 评级受以下因素影响 **每个项目的支付金额** 和 **项目总数**.
* 有效合作关系数量以及活动量

#### 外部来源如何使用？

对于提供一个或多个有效媒体资产的合作伙伴，合作伙伴规模将反映从外部来源按月查询的数据，以确定合作伙伴规模：

* **企业实体：** 估计年收入和员工人数
* **网站域名：** 每月网站流量
* **网红账号：** 跨所有平台的受众规模
* **应用：** 下载量和评分

#### 合作伙伴规模等级

这些评级数字可作为估算合作伙伴规模的参考。

| 大小 | 关注者     | 网站访问量   | 应用下载量   | 企业年收入  | 每个项目的 impact.com 年度支付金额 |
| -- | ------- | ------- | ------- | ------ | ----------------------- |
| 超小 | 50      | 100     | 200     | $1,000 | $50                     |
| 小  | 3,000   | 5,000   | 10,000  | $100万  | $1,000                  |
| 中  | 100,000 | 250,000 | 500,000 | $5000万 | $10,000                 |
| 大  | 500万    | 1000万   | 2000万   | $5亿    | $500,000                |
| 超大 | 2.5亿    | 5亿      | 10亿     | $50亿   | $500万                   |

#### 创作者层级规模

| 大小     | 关注者/订阅者          |
| ------ | ---------------- |
| 纳米创作者  | < 15,000         |
| 微型创作者  | 15,000 - 75,000  |
| 中级创作者  | 75,000 - 250,000 |
| 大型创作者  | 25万 - 100万       |
| 超大型创作者 | 100万以上           |


---

# 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/reach-out-to-partners/partner-management/partner-size-rating-criteria.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.