Custom fields store workspace-specific contact information in Noticestry One. Use them for relevant personalization after the field and its contact values have been configured.

Create a field

1. Check the workspace selector.
2. Open the account menu, then Account settings → Custom Fields.
3. Enter a human-readable Name, such as Membership Level.
4. Enter a stable Key, such as membership_level. Keys use lowercase letters, numbers, and underscores and start with a letter. Check the normalized value shown in the form.
5. Select the supported type: text, number, url, or json.
6. Choose Add Field and confirm it appears in Existing fields.

Keys must be unique in the workspace. Choose a key that can stay consistent across imports and email designs.

Create fields in Settings → Custom fields. Choose a stable key and the correct type before adding contact values.

Add contact values

Open Contacts and edit the relevant records, or map a CSV column to the existing custom field during import. Check that values match its type. Creating a field does not populate every contact automatically.

Insert personalization

In the visual email editor, use the available merge-field controls. Built-in fields include First Name, Last Name, Full Name, Email, and Organization Name. Your workspace fields appear with their display names.

The supported custom-field form is {{ custom.membership_level }}, where membership_level is the actual saved key. Insert the field from the editor where possible to avoid spelling or syntax errors. Do not invent unsupported fallback syntax.

Check both filled and missing values

Preview and send a test before delivery. The editor can show sample values; a sample does not prove every recipient has that data. Review the underlying contact record and test the message with representative data. Write surrounding text that remains readable when an optional value is absent.

For example, use a general greeting when your audience does not consistently have first names. Review personalized links as well as visible text.

Maintain fields carefully

Check templates, campaigns, automations, imports, and integrations before removing a field. Deleting a custom field also deletes its stored values. Do not delete and recreate a field merely to change its label without reviewing those dependencies.

If a field is missing, confirm the workspace, saved definition, exact key, and editor session. Save your work and reopen the editor if it was opened before the field was created. If a token remains visible in a delivered test, correct it before sending to subscribers.