Custom Fields
Collect structured data from users with configurable form fields
Custom Fields
Custom fields let you add structured form inputs to your feedback widget, so users can provide specific information — like their name, plan tier, or a support reference number — when they submit feedback.
Custom fields require a Pro or Pro Max plan.
Two kinds of fields
Every project has two categories of custom fields.
Default Fields
Four built-in fields are available on every project, regardless of plan:
| Field ID | Label | Type |
|---|---|---|
df_name | Name | Text |
df_email | ||
df_phone | Phone | Tel |
df_company | Company | Text |
Default fields are pre-configured. Enable or disable them per widget from the Widget Builder — no creation step needed.
Values from df_name, df_email, and df_phone are automatically promoted to the feedback item's user info and appear in the Context card in the dashboard.
Project-Defined Fields
Beyond the defaults, you can create your own fields in Project Settings > Custom Fields. Each field gets an auto-generated ID with a cf_ prefix (e.g. cf_a8k2m1p5).
Seven field types are supported — see Field Types for the full reference.
Where fields appear
| Surface | Details |
|---|---|
| Widget form | Fields you enable appear as inputs when the user submits feedback |
| Create Ticket dialog | Fields marked required at creation are shown when an agent creates a ticket manually |
| Feedback detail panel | All project fields are visible and editable by agents |
| Exports | Field values are available as columns when exporting feedback to CSV or Excel |
Custom Fields vs Custom Metadata
UserHero has two ways to attach structured data to feedback. They serve different purposes:
| Custom Fields | Custom Metadata | |
|---|---|---|
| Set by | End user via the widget form, or developer via the API | Developer, via setMetadata() |
| When | When the user fills out the feedback form | Before the widget opens (e.g. on login) |
| Visible to user | Yes (form inputs) | No |
| Use case | Collecting user input — name, email, or custom answers | App context, user identity, internal IDs |
| Dashboard location | Custom Fields card | Custom Data card |
Priority rule: If both a custom field and custom metadata provide the same user info (e.g. both set an email address), the custom field value takes priority.
See Custom Metadata for details on setting developer-side context data.