Create one
In the portal, open Custom Fields. The section describes itself plainly: "Define the fields your team captures when scanning a lead."
Add a field, name it, and choose its type.
The field types
Type | Use it for |
|---|---|
Single-line text | Short free text, a referrer's name, a booth number |
Long text | Anything that runs on |
Dropdown | One choice from a fixed list |
Multi-selection | Several choices from a fixed list |
Toggle | An on or off switch |
A field can be marked required, so it can't be skipped.
Prefer a dropdown to free text wherever you can. Free text gives you "Lead", "lead", "LEAD " and "warm lead" in the same column, and none of it filters or reports usefully. A fixed list stays analysable a year later.
What you can capture
Where you met: the event or channel. Dropdown.
What they want: the product or interest. Dropdown.
Next step: send pricing, book a demo, no action. Dropdown.
Required fields, carefully
Marking a field required guarantees you get it. It also blocks saving a lead without it, which at a busy event means people either invent a value or stop capturing.
Make a field required only when a lead is genuinely useless without it.
Getting them into your CRM
Custom fields are only worth capturing if they land somewhere. Map them so they arrive in the right CRM field rather than vanishing. See Map custom fields to your CRM.
They appear everywhere your leads do
Once a field exists, it follows your leads through the portal without any further setup:
A column of its own on the Leads table, in the order you defined the fields.
A filter in the Filters panel, matched to the field type.
A column in the CSV export, headed with your label, with dropdowns exported as the option's label and toggles as
YesorNo.