> 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/surveys/create-custom-fields-for-surveys.md).
# 为调查创建自定义字段
自定义字段与调查一起使用，用于收集有关您的合作伙伴的信息。例如，如果您经常需要收集合作伙伴的出生日期，您可以使用 *日期选择器* 问题类型。
#### 创建自定义字段
1. 从顶部导航栏中，选择  **\[用户资料]** → [**设置**](https://app.impact.com/secure/advertiser/account-settings-flow.ihtml).
2. 在右侧的……下方 **项目**，请前往 *技术* 部分并选择 **自定义字段**.
3. 在右上角，选择 **创建自定义字段**.
4. 填写自定义字段信息：
* **名称：** 添加一个名称，以便在向调查添加字段时轻松识别此自定义字段。
* **描述：** 为您的自定义字段添加描述，以说明该字段所代表的数据。此描述对合作伙伴不可见。
* **显示类型：** 请选择最能收集您所需数据的问题类型。
显示类型参考
| 显示类型 | 最适用于 |
| ----- | -------------------------------------------- |
| 段落 | 允许独特答案的开放式问题。 |
| 多选 | 可能包含多个答案的问题。受访者可以选择1个或多个选项。 |
| 下拉列表 | 要求用户从包含多个答案的隐藏下拉菜单中选择一个选项的问题。受访者可以选择1个或多个选项。 |
| 单选 | 要求受访者仅从列表中选择1个选项的问题。 |
| 日期选择器 | 要求答案为日期的问题。 |
| 数字 | 要求答案为数字的问题。 |
| 文件 | 要求合作伙伴提供附件的问题。 |
5. 选择 **保存**.
* 您现在可以从  **\[下拉菜单]** 在创建调查时选择此自定义字段。
{% hint style="success" %}
**注意：** 您还可以在以下情况下创建自定义字段： [设置新调查](/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/surveys/create-a-partner-survey.md).
{% 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/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/surveys/create-custom-fields-for-surveys.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.
