> For the complete documentation index, see [llms.txt](https://wpmaps-docs.mapster.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wpmaps-docs.mapster.me/pro-sections/user-submission/adding-custom-fields.md).

# Adding Custom Fields

You may want to collect more information from users than just a title, a geography, and a description. If so, you can easily integrate [Advanced Custom Fields](https://www.advancedcustomfields.com/) into Mapster WP Maps and the fields will appear immediately in your frontend forms.

At the *very* least, you should have a custom field that will let you identify the post the user submits (a title field).

Create the field set however you like in ACF, and then set it to conditionally display on the **Location** and the **User Submission** post types. It must be set to be visible on **both** of these post types to work properly.

![](/files/2xIdTNBm0CsiKlaDMA6q)

These fields will now appear as part of your front-end form, and will collect data from users. You can then user the data from these fields in other areas of your site -- output their data in a custom popup, or use them as part of the [Advanced Category Filter](broken://pages/N11qbgvuayN7PaRtbYee)!

{% embed url="<https://www.youtube.com/watch?v=rU_y6v0Hq4g>" %}


---

# 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://wpmaps-docs.mapster.me/pro-sections/user-submission/adding-custom-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.