> 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/product-marketplace-and-catalogs/set-product-catalog-feed-preferences-as-a-partner.md).
# 作为合作伙伴设置产品目录偏好
当你 [下载产品目录](/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/marketing-content/product-marketplace-and-catalogs/download-product-catalogs-as-a-partner.md) （也称为商品信息流）在 *Impact 格式*，你可以选择文件类型以及是否压缩。只需设置一次偏好设置，之后每个 *Impact 格式* 你下载的目录都会使用这些设置。
## 设置文件偏好
1. 在顶部导航栏中，选择  **\[用户资料] → 设置**.
2. 在 *技术* 部分，选择 [**数据馈送**](https://app.impact.com/secure/mediapartner/accountSettings/view-edit-daily-feeds-flow.ihtml).
3. 选择  **\[编辑]** 旁边的 *商品信息流* 来编辑该部分。
4. 选择 **文件格式**。你可以选择 XML、CSV 或 TAB。
* CSV 和 TAB 都是纯文本格式；CSV 使用逗号分隔，TAB 使用制表符分隔。
5. 选择是否将文件压缩（gzip）。对于较大的产品目录，建议进行压缩。
6. 选择 **保存**.
* 请参见 [示例电子表格](https://docs.google.com/spreadsheets/d/11zZAPcufBSb-cH_uVwI4xtUtB_uTC6nPEzptNgL_Sgo/edit) 下方可查看所有参数的说明列表以及产品目录示例。
{% hint style="success" %}
**注意：** 要打开压缩的产品目录，你需要使用解压软件，例如 [WinZip](https://www.winzip.com/en/) , [WinRAR](https://www.rarlab.com/) ，或 [7-Zip](https://www.7-zip.org/) .
{% endhint %}
---
# 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/product-marketplace-and-catalogs/set-product-catalog-feed-preferences-as-a-partner.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.
