> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/forms/push-to-customer-metafields.md).

# Push to customer metafields

Store form submissions in a customer metafield when the customer is identified.

Use this when form data should be available as customer data later.

This is useful for reporting, theme logic, and downstream workflows.

### What this setting does

When **Save submissions to customer metafield** is enabled, Roadmap stores the form submission under:

`customer.metafield.roadmap.form_<formId>`

This happens when the customer is identified.

> **Screenshot placeholder:** Form settings with **Save submissions to customer metafield** enabled inside **Advance Settings**.

### Enable customer metafield saving

{% stepper %}
{% step %}

#### Open the form settings

From **Forms**, open **Settings** for the form.
{% endstep %}

{% step %}

#### Open Advance Settings

Expand the advanced options for the form.
{% endstep %}

{% step %}

#### Enable metafield saving

Check **Save submissions to customer metafield**.
{% endstep %}

{% step %}

#### Save and run a test submission

Submit the form once and confirm the customer metafield is updated.
{% endstep %}
{% endstepper %}

### When to use it

Use this when you want to:

* keep a structured record of the submission per customer
* reference form data later in Shopify
* persist answers from onboarding or qualification forms

### Important behaviour

* the metafield key is specific to the form
* the customer must be identified
* you should re-test after changing field names or structure

### Troubleshooting

#### Nothing was written to the metafield

Check these first:

* the setting is enabled
* the form changes were saved
* the customer was identified during the submission

#### The saved data looks outdated

Run a new test after any form structure change.

### Related guides

* [Building with forms](https://docs.roadmap.so/forms/building-with-forms.md)
* [Save into a customer profile](https://docs.roadmap.so/forms/save-into-a-customer-profile.md)


---

# 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://docs.roadmap.so/forms/push-to-customer-metafields.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.
