Overview
Custom attributes are fields you create to store information the platform does not ship by default — for example, a tax ID, the subscribed plan, the lead source, an order number or any data relevant to your operation.
Each attribute is defined once (with a name, a key and a type) and then appears in the conversation side panel and/or on the contact record. You can use attributes as criteria for segments, in automations, in campaigns and during CSV import.
Prerequisites
- An active ConversaLabs account.
- Administration permission to create and edit attribute definitions.
- Decide the type of each field before creating it (text, number, date, list, etc.).
Step by step
- Go to the account Settings and open the custom attributes section.
- Create a new definition and choose where it applies: contact or conversation.
- Enter a display name (what the team sees); the system generates a stable key.
- Select the field type (see the table below).
- For lists, enter the possible values; save the definition.
- Open a contact or conversation and fill the new attribute in the side panel.
Settings & options
The platform offers these attribute types:
| Type | What it is for |
|---|---|
| Text | Free text (notes, codes) |
| Number | Numeric values |
| Currency | Monetary values |
| Percent | Percentages |
| Link | Clickable URLs |
| Date | Dates |
| List | Choose from predefined values |
| Checkbox | True/false |
- Attribute model: contact (applies to the person) or conversation (applies to that interaction).
- Unique key: each key is unique per model and cannot conflict with standard fields.
- Optional validation: some fields accept a pattern (regex) to enforce the format.
- ConversaLabs also uses custom attributes in other modules (CRM, catalog, tasks, calendar and more), each in its own settings area.
Use cases
- Store the customer's tax ID or document number on the contact.
- Mark the lead source (ad, referral, website) as a list.
- Record an order number or ticket number on the conversation.
- Build segments like "Pro plan customers" using a list attribute.
Tips, limits & best practices
- Choose the right type from the start — changing the type later may require re-editing data.
- Use lists instead of free text for fields with few options (avoids variants like "WhatsApp" and "whats").
- Standardize key naming before importing large bases via CSV.
- Contact attributes follow the person; conversation attributes apply only to that interaction.
Troubleshooting
- I cannot create the attribute: the key may already exist or conflict with a standard field — use another name.
- The value does not appear on import: check that the CSV header uses exactly the attribute key.
- The field rejects the value: there may be a format validation (regex) set on the definition.