Custom fields
Keep extra details on each person — budget, event date, service wanted — picked up from your forms or added by hand.
Every person has four built-in details: name, email, phone and company. Custom fields hold everything else you want to know about them — budget, preferred date, party size, how they heard about you.
Fields are set up per site. Each site has its own list.
Editing fields is a Pro feature. See Basic and Pro plans.
Three kinds of field
Open the fields editor and each field carries a small caption saying where it came from:
| Caption | What it is |
|---|---|
| Built-in | Name, Email, Phone, Company. Always there. |
| From form | Picked up automatically from a form on your site. The caption also shows the form’s own field name. |
| Custom | Added by you, in the editor or during a CSV import. |
Fields from your forms
You don’t have to set anything up. When you publish a site, PageFork reads its forms and creates a field for each input that isn’t a name, email, phone or company. It uses the label visitors see on the form, and picks a matching type — a date picker becomes a Date field, a dropdown becomes a Select field with the same options, a checkbox becomes Yes/No.
If a submission later arrives with a field PageFork hasn’t seen, a Text field is created for it on the spot, named after the form field.
Tracking and technical values are ignored and never become fields:
anything starting with utm_, click IDs from ad platforms, and captcha
responses.
See Form field schemas for how form inputs map to a person’s details.
Field types
| Type | Holds | Edited with |
|---|---|---|
| Text | Any text | A text box |
| Number | A number | A number box |
| Date | A calendar date | A date picker |
| Select | One choice from a list you define | A dropdown |
| Yes/No | Yes, no, or not set | A dropdown |
| URL | A web address, shown as a clickable link | A text box |
Editing a value
On a person page or a lead record, click a field’s value to change it. Press Enter to save, Escape to cancel. Select and Yes/No fields save as soon as you pick. Choose — or clear the box to empty a field.
A value that doesn’t fit the type — letters in a number field, say — is rejected with a message naming the field.
Each change is recorded on the person’s timeline with the old and new value and who made it.
The fields editor
Owners and admins can change the field list. Members can edit values but don’t see the editor.
Open it with Edit fields — at the top of a person’s details, or from the View settings button in the Leads List view.
| To | Do this |
|---|---|
| Rename a field | Type a new label. Built-in fields can be renamed too. |
| Change its type | Pick from the type dropdown. Built-in fields keep their type. |
| Set Select options | Type them in the box under the field, separated by commas. |
| Reorder | Drag a field, or use the up and down arrows. |
| Show it as a list column | Turn on the Show in list toggle. Built-in fields don’t have one. |
| Hide it | Click the Hide field icon (an eye with a line through it). |
| Bring it back | Find it under Hidden and click Unhide. |
| Add a new one | Click Add field, then give it a label and type. |
Nothing changes until you click Save.
Hiding instead of deleting
There is no delete. Hide field hides a field: it disappears from person pages, list columns and the import mapping, but every value stored in it is kept. Unhide brings the field and its data straight back.
Built-in fields can’t be hidden. A field you’ve just added and not yet saved can be removed outright.
Changing a field’s type
When you change a type, PageFork re-reads every stored value as the new
type. Values that make sense convert — the text 42 becomes the number
42, yes becomes Yes. Values that don’t convert are left exactly as
they were, so nothing is lost; they just stay as text until someone
edits them.
For a Select field, a stored value that isn’t one of the options still shows on the person, as an extra choice in the dropdown.
Show in list
Custom fields with Show in list on are added as columns in the Leads List view and as columns in the CSV export. In the List view you can still switch any field’s column on or off for yourself from View settings.
How values get filled in
From a form submission. When a submission arrives for a person, each field that is empty on the person is filled from the matching form field. Fields that already have a value are left alone — a later submission never overwrites them.
If a submitted value doesn’t fit the field’s type, it is stored as the text the visitor typed rather than dropped.
From a correction. If you correct a submission, the person’s field follows the correction — but only if it still held the old submitted value, or was empty. A value someone has since changed by hand is left alone.
From an import, Zapier or Make. Same rule as forms: empty fields are filled, existing values are kept.
By hand. Editing on the person or lead always takes effect.
Limits
- 40 fields discovered from forms per site, hidden ones included. Past that, new form fields are no longer turned into fields (the submission itself still stores everything).
- 40 fields added by hand or by import per site. Add field switches off when you reach it. Fields discovered from forms don’t count towards this limit.
- Labels up to 60 characters.
- Values up to 5,000 characters.
- Select fields: up to 50 options, 100 characters each, and at least one.
Good to know
A form field isn’t showing on the person. It may have been treated as the name, email, phone or company, or ignored as a tracking value. Or the site has reached 40 form fields.
The same information shows twice under different names. A form field was renamed, so PageFork sees two different fields. Hide the old one.
A field is missing from the import mapping. Hidden fields aren’t offered as import targets. Unhide it first.