Data tab

Before building flows, define the data the campaign works with. The Data tab defines the fields available to the campaign — on the customer profile and on each participant. Fields defined here are used everywhere: imported from CSV files or the API, checked in flow conditions, shown in participant details, and passed to communication actions.

Every field has a Level:

• Customer Profile — fields that describe the customer, such as Email and Phone. Their values are stored on the customer profile: they appear in 360 View and can be reused by other campaigns. Import and Required are still set per campaign.
• Participant — fields that exist only inside this campaign, such as a loan amount or a due date. Use these for campaign-specific data.

A new campaign starts with the predefined system Customer Profile fields — External ID, Email, Phone, Telegram ID, Telegram Username, WhatsApp ID, Web ID, and Full Name — with Import enabled and Required disabled.

Fields table

Column	Meaning
Title	The display name users see in the portal.
Name	Technical name of the field — see Name and Title.
Description	Optional free text.
Type	Data type — see Field types.
Level	Customer Profile or Participant.
Import	Whether this field can be imported from a file. Only checked fields are read from CSV uploads.
Required	Whether this field is required. Rows missing a required field fail during upload.

• Drag the handle at the left of a row to reorder fields. The order is used in the participant details view.
• Unchecking Import automatically unchecks Required — a field cannot be required if it is not importable.
• Rows with a lock icon are system fields: System field — cannot be edited or deleted.

Name and Title

Title is the display name. Name is the machine key:

• CSV column headers are matched against Name (the match is case-insensitive).
• In API uploads, the keys in each participant's attributes object are field Name values.
• Flow conditions and actions reference fields by Name.

Besides CSV uploads, participants can be added with the public API: POST /private/campaigns_v2/{campaign_id}/participants is a synchronous endpoint for enrolling batches of participants from your backend or CRM. See Bulk Add Flow Participants in the API reference.

Field types

Type	Example	Validation
string	Gold	Leading and trailing spaces are removed.
integer	42	Must be a whole number.
numeric	19.99	Must be a number.
boolean	true	Accepts true/false, 1/0, and yes/no.
date	2026-07-05	ISO format YYYY-MM-DD.
datetime	2026-07-05T14:30:00+02:00	ISO 8601. The timezone is optional — a value without one gets the participant's timezone, then the tenant timezone, then UTC.
enumeration	bronze	Must match one of the allowed values defined when the field is added.
email	anna@example.com	Trimmed, lowercased, and validated against a standard email pattern.
phone	+1 (415) 555-0100	All non-digit characters ("+", spaces, parentheses) are removed; the value must contain at least one digit. The example is stored as 14155550100.

The type controls which operators a Field Check condition offers and how uploaded values are validated.

Add a field

1. Click Manage fields.
2. In the Manage fields dialog, click Add field.
3. Fill in Title and Name (both required), optionally a Description, and pick a Type. Fields created here have the Participant level. If you leave Name empty, it's generated from Title: lowercased, spaces replaced with underscores, other special characters removed.
4. Save the new row and close the dialog. The field appears in the table on the Data tab.

Change or delete a field

After a field is created, its Name, Type, and Level can't be changed — you can edit the Title and Description. Keep this in mind when you plan the fields:

• System fields (lock icon) can't be edited or deleted.
• A custom field can't be deleted while any campaign uses it — the error message lists those campaigns. Remove the field from them first.
• Deleting a field also removes its stored values from customer profiles and participants.

Best practices

• Use Participant fields for campaign-specific data; reuse the Customer Profile fields for data that describes the customer.
• Settle the field types before you upload data — a type can't be changed after the field is created, and it decides how uploaded values are validated and which comparisons are available in conditions.
• Keep Name values stable once flows and CSV files reference them.

Related pages

• Workflow — use fields in conditions and actions
• Uploads — import data into these fields
• Participants — review everyone in the campaign
• 360 View — the customer profiles behind Customer Profile fields