Skip to main content
Custom properties

Custom properties lets you create fields that collect and store information (e.g. from Journeys flows and integrations).

Updated over 3 months ago

Creating custom properties

Before you can import custom properties via our integrations, you’ll need to setup them up here.

  1. Go to Settings → Custom properties

  2. Depending on where you want the property to appear (e.g. Contact or Product) click into that tab

  3. Select Add property. Another window will open so you can configure the property;

    1. Label (Required) - This is the display name of the custom property.

    2. Technical name (Required)

      • This is the internal name of the custom property and is automatically created as you enter the Label

      • If you want to change it, select the pencil icon

        This is only relevant if you want to match the name of the property technically with the name of any other system or use Webhooks.

    3. Description (Optional) - This is the description of the custom property and it will not display anywhere in the platform

    4. Icon (Optional) - You can assign a unique icon for the custom property and it’ll be displayed alongside the label

    5. Input type (Required) - This defines how and what kind of information you want to collect and store. For the definition of each input type, please see below.

4. Adjust the visibility to decide where it shows up

Deleting custom properties

You can delete a custom property using the Delete button.

Please note that deleting a custom property would remove all the values stored in the system.

Input types

Input type

Description

Useful for

Select

• A list of multiple options where only one option can be selected. • When "Select" is chosen, you will be required to enter data in the field called "Value" for each option you add, which represents the value and internal name of the option. The next column named "Label" is optional, and it is useful if you want to show a different display name for the UI.

Category, income level, gender

Multi-select

• A list of multiple options where agents can select multiple options. • When "Multi select" is chosen, you will be required to enter data in the field called "Value" for each option you add, which represents the value and internal name of the option. The next column named "Label" is optional, and it is useful if you want to show a different display name for the UI.

Preferences, tags

Radio button

• A list of multiple options where only one option can be selected. In terms of functionality, it is similar to "Select" but appears differently. • When "Select" is chosen, you will be required to enter data in the field called "Value" for each option you add, which represents the value and internal name of the option. The next column named "Label" is optional, and it is useful if you want to show a different display name for the UI.

Category, income level, gender

Checkbox

A single checkbox would appear. This is used when the custom property values only contains two options.

True or false type of questions

Text input

A textbox where users can write comments or notes up to 255 characters.

Short comments

Large text input

A larger text box would appear, where users can write long text or comments that would need more than 255 characters.

Descriptions, longer comments

Number input

A field where users can enter numerical data.

Membership ID, score, age

Number with unit input

• A field would appear where users can enter numerical data with a predefined measurement unit. • When this is selected, you will be required to select a measurement unit for the custom property.

Height, weight, storage

Currency input

A field would appear where users can enter numerical data with a predefined a currency symbol. The currency icon is defined in the icon field.

Price, amount, commission

Date input

• A specific date will be defined by the user in the UI. • When this is selected, a calendar picker would open as a drop down when users enter a value in the UI. Please note that we currently only support the following date format: YYYY-MM-DD

Deadline, event, delivery date

Date time input

• A specific date and time will be defined by the user in the UI. • When this is selected, a calendar picker with time would open as a drop down when users enter a value in the UI.

Deadline, event, delivery date

Date range input

• A specific date and time range will be defined by the user in the UI. • When this is selected, a calendar picker with time would open as a drop down when users enter a value in the UI.

Available hours to contact, event dates

Did this answer your question?