Title: Custom map fields
Last modified: August 27, 2017

---

# Custom map fields

 *  Resolved [kveelenturf](https://wordpress.org/support/users/kveelenturf/)
 * (@kveelenturf)
 * [8 years, 9 months ago](https://wordpress.org/support/topic/custom-map-fields/)
 * In MailPoet 2 and in the new beta version, the subscribers only have two separate
   fields for first and last name. In Dutch a lot of people have a – as we say –
   tussenvoegsel (or in English a surname prefix). It would be nice to have a separate
   field for that. Is it possible to create it e.g. with the function.php functionality
   or is it maybe something for a feature request?
    I’m using Gravity Forms to automatically
   map subscribers to my lists in MailPoet, but I’m missing the surname prefix in
   a couple of names. 🙂

Viewing 1 replies (of 1 total)

 *  [Wysija](https://wordpress.org/support/users/wysija/)
 * (@wysija)
 * [8 years, 9 months ago](https://wordpress.org/support/topic/custom-map-fields/#post-9447937)
 * You can add that field as a custom field: [http://beta.docs.mailpoet.com/article/159-how-to-add-custom-fields-to-your-forms](http://beta.docs.mailpoet.com/article/159-how-to-add-custom-fields-to-your-forms)

Viewing 1 replies (of 1 total)

The topic ‘Custom map fields’ is closed to new replies.

 * ![](https://ps.w.org/mailpoet/assets/icon-256x256.png?rev=3284564)
 * [MailPoet - Newsletters, Email Marketing, and Automation](https://wordpress.org/plugins/mailpoet/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/mailpoet/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/mailpoet/)
 * [Active Topics](https://wordpress.org/support/plugin/mailpoet/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/mailpoet/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/mailpoet/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Wysija](https://wordpress.org/support/users/wysija/)
 * Last activity: [8 years, 9 months ago](https://wordpress.org/support/topic/custom-map-fields/#post-9447937)
 * Status: resolved