Skip to main content

Types of Custom Fields Available

Understand the different custom field types and when to use each one.

Written by Wes Byrne
Updated over a month ago

Lingo offers several custom field types to match different kinds of information. Choose the type that best fits the data you want to track.

Text

A freeform text field for any string value.

Best for:

  • Notes or descriptions

  • Campaign names

  • Product SKUs

  • Any unstructured text

Example uses:

  • "Campaign Name" → "Summer 2024 Launch"

  • "Product SKU" → "WDG-4521-BLU"

Number

A numeric field that only accepts numbers.

Best for:

  • Quantities

  • Version numbers

  • Dimensions

  • Any countable value

Example uses:

  • "Version" → 2

  • "Sort Order" → 15

Date

A date picker field for calendar dates.

Best for:

  • Expiration dates

  • Publication dates

  • Review deadlines

  • Event dates

Example uses:

  • "Expiration Date" → December 31, 2024

  • "Last Reviewed" → January 15, 2024

Single-select (Dropdown)

A dropdown menu where users choose one option from a predefined list.

Best for:

  • Status tracking

  • Categories with mutually exclusive options

  • Any "choose one" scenario

Example uses:

  • "Status" → Draft / In Review / Approved / Archived

  • "Department" → Marketing / Sales / Product / Engineering

  • "Region" → North America / Europe / Asia Pacific

Multi-select (Checklist)

A checklist where users can select multiple options from a predefined list.

Best for:

  • Multiple categories that can overlap

  • Feature tags

  • Use cases or applications

Example uses:

  • "Channels" → Web, Print, Social, Email (select all that apply)

  • "Languages" → English, Spanish, French, German

  • "Use Rights" → Internal, External, Commercial

Choosing the right type

If you need to track...

Use this type

Free-form text

Text

Numbers only

Number

A specific date

Date

One option from a list

Single-select

Multiple options from a list

Multi-select

How custom fields appear in the inspector

Users with edit access can modify custom field values directly in the inspector panel:

Custom fields as seen by editors

Users with view-only access see custom field values in read-only mode:

Custom fields as seen by viewers

Learn more

Did this answer your question?