Subscriber Details

Custom Fields

Custom Fields store subscriber details that need a specific value, not just a label.

  • Store text, number, date, and yes-or-no details about subscribers.
  • Use field values in forms, imports, subscriber profiles, segments, and personalization.
  • Define fields clearly before a large import or email send.
Mailrith custom fields page showing field names and types.

Practical Use

What This Feature Helps You Do

See the everyday task this feature supports and the small decisions it helps you avoid handling by hand.

Better Personalization

Fields can store subscriber details that help you write more relevant emails, such as plan, company, city, or renewal date.

Cleaner Imports

Create the field before import so each CSV column has a clear destination.

Smarter Segments

Segments can use field values to find subscribers who match specific conditions.

When To Use This Feature

  • You need to store a value that can be different for each subscriber.
  • The value should be used for personalization, segments, forms, or automations.
  • You want a clear place for each subscriber detail before you import or collect information.

When This May Not Be The First Thing To Set Up

  • A simple yes-or-no label is enough. A tag may be cleaner.
  • You will never use the value for choosing subscribers, personalization, reporting, or support.
  • The information is sensitive, and you do not have a clear reason or consent to store it.

Setup Steps

Simple Setup Steps

Follow these steps before you add more complex setup or automation.

  1. 1

    List the subscriber details you actually need.

  2. 2

    Choose the right field type for each subscriber detail.

  3. 3

    Create the field before you collect the value in forms or imports.

  4. 4

    Use clear field names so teammates understand what each field means.

  5. 5

    Review fields before major sends, then remove fields that are no longer useful.

Avoidable Problems

Common Mistakes To Avoid

Watch for these mistakes because they can make basic email setup and sending harder to troubleshoot.

Choosing The Wrong Field Type

A date should use a date field, a number should use a number field, and a yes-or-no value should not be stored as free text.

Collecting Nice-To-Have Data

Every field should have a clear purpose. Extra fields make forms longer and subscriber data harder to maintain.

Changing Meaning Later

If a field called plan means product plan today and pricing tier tomorrow, old segments can become unreliable.

Works With Other Features

How This Connects With The Rest Of Mailrith

Email work often uses several Mailrith screens. Use this section to see where Custom Fields connects to related Mailrith features.

  • Forms and landing pages can collect custom field values.
  • Segments can filter by custom fields.
  • Broadcasts and sequences can personalize with field values.
  • Automations can use fields in conditions.