> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/control-panel-overview/forms-overview/map-form-fields.md).

# How to Map Form Fields to CRM Profile or Attribute Group

### Before you begin (Prerequisites)

* **Permissions**: You must be an **Administrator**, **Supervisor**, **Manager**, **Support**, or **Account Rep**. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md).
* **Existing Form**: The form must already exist with at least one question. See: [How to Create a Form](/products/control-panel-overview/forms-overview/create-form.md).

### Instructions

1. Navigate to [**ENGAGE > Survey & Forms > Manage Forms**](https://control.peoplevine.com/surveys).
2. Locate the form and click the **Menu** button (blue) and select **View Questions**.
3. Find the question you want to map and click **Edit**.
4. Under **Map Response to User's Profile**, select the corresponding CRM field from the dropdown (default: No Mapping).
5. Click **Update Question**.
6. Repeat for each question you want to map.

Mapping is set per question when creating or editing questions. See: [How to Create a Form](/products/control-panel-overview/forms-overview/create-form.md) for the full question configuration options.

#### Map a Response to an Attribute Group

To tag a respondent with a custom attribute instead of writing to a standard CRM field:

1. Follow steps 1–3 above to open the question editor.
2. Under **Map Response to User's Profile**, select **Segment into Groups (Attribute)**.
3. In the **Attribute Title** field that appears, enter the exact name of the attribute (e.g., `Dietary Preference`). This must match an existing attribute name exactly.
4. Click **Update Question**.

When the form is submitted, the respondent's answer is saved as an attribute value on their CRM profile, which can be used for segmentation and reporting.

> **Note**: To learn how to create and manage attributes, see: [How to Manage Custom Attributes](/products/control-panel-overview/admin-overview/manage-custom-attributes.md).

### Best Practice

The question type must match the CRM field format for mapping to work correctly:

* **Birthday** and **Anniversary Date** — use the **Pick a date** question type. A free-text field will not map correctly.
* **Opt In To E-mails** and **Opt In To SMS** — use the **Yes or No** question type.
* **Address** fields — use the **Capture Address** question type.

Always include first name, last name, and email fields on guest-facing forms and map them to CRM profile fields so responses write directly to member records.

### What Happens Next

* **On the system side**: Future form submissions automatically write data to the mapped CRM fields. Existing submissions are not retroactively mapped.

***

*Last updated: 2026-05-24*


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.peoplevine.com/products/control-panel-overview/forms-overview/map-form-fields.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.