Fields let you save and manage the information you need for each friend as custom fields. Give friends the information your marketing needs — such as job title, membership rank, or number of visits — and use it to narrow down segments and branch workflows. This article explains how to create fields and put them to use.
What is a Field?
A field is a custom field tied to each individual friend. In addition to the basic information available from LINE, such as the display name, you can freely define the information you want to manage yourself.
Whereas a tag is a marker for whether it is "attached or not," a field can hold a value like "Job title = Manager" or "Visits = 5." Fields suit cases where you want to manage friends in detail by the kind or level of a value; tags suit simple classification.
The field list starts out empty. You add the fields you need yourself with "Create field".
Opening the Fields screen
The Fields management screen opens from "Customer data" in the side menu of your LINE Official Account.
- Open the target LINE Official Account
- Click "Customer data" in the side menu
- Open the "Fields" card to see the list of fields
Reading the field list
Fields appear in the list with the Label, Memo, Type, Friends, Last updated, and Mapping columns. "Back to Customer Data" at the top takes you back. The header buttons are "Create field", "Create folder", and "Default view settings".
Creating a Field
Use "Create field" to define a new custom field.
| Setting | Details |
|---|---|
| Label | The name shown on screen (e.g. Job Title) |
| Key | The system identifier. It's generated automatically from the label (e.g. job_title). You can rewrite it while creating the field, but it cannot be changed after saving |
| Type | The kind of value. Choose from Text, Number, Date, Date & time, Email, Phone, Select, External ID, or LINE User ID. Date stores the date only, while Date & time stores the time as well |
| Options | For the Select type, defines the selectable values. Turn on "Set codes" to give the options an order and compare stages in segments (the list shows it as "Select (ordered)") |
| Folder | Pick the folder the field belongs to, at the top of the form |
| Memo | Leave a note about what the field is for. It shows in the "Memo" column of the list |
A field's account cannot be changed after creation.
Setting Field values
Field values can be set by editing them directly on the friend's details, by automatic updates from a workflow, and by data import.
- Edit directly on the friend's details: Enter values in the "Fields" card on the friend's details screen. When you edit, a bar appears at the bottom of the screen — click "Save" to confirm. The clock icon "View change history" on each input shows when the value changed and how (Manual, Workflow, Data import, or ID Link Import)
- Automatic updates from a workflow: The workflow action "Set Field" automatically updates a friend's field. You can automate operations like "increase the number of visits for friends who used a coupon"
- Bulk setting by data import: Import a CSV to set and update the values of many friends at once. The steps for choosing which field each column feeds are covered in the data import article
Identity fields and Data Import
A field with "Use to match friends during data imports" turned on becomes the key for matching friends during a CSV import (for example, identifying and updating a friend by membership ID). This checkbox is available for the Email, Phone, External ID, and LINE User ID types.
What happens when you import a CSV containing the same friends again is decided per field, under "Data import". An identity field is only used to find the friend, so an import never changes its value.
Data import behavior
In the "Data import" section of the field's create and edit form, choose the update rule for re-imports per field.
| Option | Behavior |
|---|---|
| Update on re-import (last write wins) | Always updates with the new value |
| Keep existing — log conflict | Keeps the value already in place and records the difference as a "Conflict" in the import results |
| Manual only — imports skip this | Imports never change the value |
A field with "Use to match friends during data imports" turned on is fixed to "Manual only".
Matching on LINE User ID
A field of the "LINE User ID" type is there to match friends directly against a LINE User ID column in your CSV. Even when a CSV coming from another tool has nothing but LINE User IDs, creating a field of this type lets you import it.
- The "Use to match friends during data imports" checkbox is always on. Because the type exists purely for matching, you can't turn it off
- The value itself is not stored. It is only used to find the friend
- In a CSV that has both an email address column and a LINE User ID column, the LINE User ID column is matched first
Putting Fields to use
The values you set can be used to narrow down friends and as conditions for automation.
| Where used | Details |
|---|---|
| Friends list | Fields with display turned on appear as columns. Drag a column header to change the order and width (saved per browser) |
| Inbox | Check the current friend's values in the "Fields" card on the right-hand panel of the conversation |
| Segment | Choose "Field" as the criterion, and narrow down the delivery target by value |
| Workflow | The "Set Field" action updates values automatically |
"Where this field is used", on the field's edit screen, shows which segments and workflows it is used in. Check the scope of impact before deleting a field that is in use.
Choosing which fields show on friend details
The fields shown on the "Fields" card of a friend's details, and their order, can be set at two levels: a shared default and per friend.
Setting the default for all friends
Open "Set the default field view" from "Default view settings" in the field list. Set which fields show on every friend's details and in what order. Add with "Add a field", remove with "Remove from view", and confirm with "Save view settings". Friends with their own display settings aren't affected.
Changing it per friend
"Display settings" at the top right of the "Fields" card on a friend's details changes which fields show for that friend only. "Reset to default view" returns it to the default.
Setting import sources and write-back destinations together
Select several fields in the field list and click "Map fields" to open the "Map fields" dialog. It sets the data import source column for each field in one place, and the HubSpot destination as well while HubSpot is connected.
| Setting | Details |
|---|---|
| Data import source column | Switch between "Import" and "Do not import", and pick the source column |
| HubSpot destination | Switch between "Write back" and "Do not write back", and pick the destination property (only while HubSpot is connected) |
Save with "Save mapping". Changing the mapping doesn't change existing data — the new setting applies from the next data import. The matching key's column can't be changed. You can check the result in the "Mapping" column of the list.
Organizing with Folders
Once you have many fields, you can organize them with folders.
- Create a folder with "Create folder"
- Select fields and organize them with "Move to folder"
- Even if you delete a folder, the fields inside are not deleted — they move to the top level
When things don't work
When a field doesn't behave as expected, check the key, type, and where it is used.
- You want to change the key: The key cannot be changed after saving. Create a new field and migrate the values
- Values are not updated by import: Check whether the field has "Use to match friends during data imports" turned on, or whether its data import behavior is set to "Manual only". An identity field is only used to match friends, so an import puts no value in it. If you want the value too, create a separate field and split the column
- Cannot delete, or worried about impact: Check the usage in segments and workflows under "Where this field is used" on the edit screen before deleting
- You can't create or change a field: Ask an administrator to check that the "Use Fields" member permission is granted. Without it the buttons stay clickable, but the save is rejected