> 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/marketing-content/brand-assets/access-widgets-created-by-partnered-brands.md).

# 访问合作品牌创建的小组件

您合作的某些品牌可能会分享自定义组件，供您用于创建高度定制化的内容。这些组件可提供各种工具，让您完全自定义店面、创建图像素材、查询应用程序编程接口 (API) 等。您可以使用哪些组件，取决于与您合作的品牌。

{% hint style="success" %}
**注意：** 合作品牌向您提供组件后，顶部导航栏中才会显示“内容组件”选项。
{% endhint %}

## 访问组件

组件可能托管在 impact.com 内，也可能托管在品牌网站上；如果托管在品牌网站上，您将从 impact.com 平台跳转至该网站。

1. 在顶部导航栏中，选择 **管理** → **更多** → [**品牌组件**](https://app.impact.com/secure/mediapartner/tools/view-mp-tools-flow.ihtml).
2. 选择要使用的自定义组件。
   * 您将跳转到提供该组件的品牌页面

     **或**
   * 该组件将在 impact.com 平台中显示。
3. 此时，您可以按需使用该组件，或按照合作品牌的说明使用。

<div data-with-frame="true"><figure><img src="https://1152657667-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2Fgit-blob-b5edba322ab078a4eabfeed203a14f6444dfde2a%2Ffc58dcd512e16414422dc61a838449c685efb7bb51baf5903b8795af945b4eef.png?alt=media" alt=""><figcaption></figcaption></figure></div>


---

# 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/marketing-content/brand-assets/access-widgets-created-by-partnered-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.
