Custom fields

Five field types, one screen

Create a field from the Contacts settings, give it a label, and pick a type. MailerPress builds the field key from the label, so you never have to invent one.

Types: text, number, date, checkbox and select.

Select fields hold a fixed list of options you define.

The field key is what you use everywhere else: merge tags, segments, API and webhooks.

No limit on the number of fields.

Values cleaned on the way in

MailerPress validates every value against the field type, whatever the source. A number is stored as a number, not as a string. A checkbox accepts 1, true, yes, on or enabled and is stored as 1 or 0. A date is parsed and normalised. A select value is matched against your options, ignoring case.

The same rules apply to imports, forms, webhooks and the API.

Values that do not fit the type are rejected instead of being stored as junk.

Fill them from anywhere

Map a column during a CSV import.

Map a Contact Form 7, Gravity Forms, Fluent Forms, Elementor, Bricks, Divi or WPForms field.

Map a WooCommerce checkout or order field, including your own custom checkout fields.

Map a WordPress user field or user meta key when you sync users.

Send them in an incoming webhook, as a custom_fields object or with the cpt: prefix.

Set them from an automation step, or write them through the REST API.

Personalise with merge tags

Every custom field is available in the email editor as {{field_key}}, without declaring anything. Add a fallback with {{field_key default="there"}} so an empty value never leaves a hole in your copy. Values are resolved per recipient when the campaign is sent, so each subscriber gets their own.

Segment on your own data

Custom fields are full segmentation conditions.

Use equals, does not equal and contains on text, greater than and less than on numbers, and before, after or on for dates.

Combine them with lists, tags, opens and purchase history using AND/OR logic, then send to the segment.

Search, sort and automate

Search your contacts by custom field value, alongside names, emails, list and tag names, opt-in sources and contact IDs. Sort the contact table by any field. Start an automation from the Contact custom field updated trigger, branch a workflow on a field value, or push a contact.custom_field.updated webhook to your own systems.