Custom fields can be added for extended functionality when it comes to categorising and filtering profiles, along with adding rules and logic gateways to Track, Capture and Smart Redirect elements. Some common examples of these custom fields are; gala dinner attendance, address, post code or an alternate contact number.
The creation and management of these fields is located within the Profiles section under the Project Configuration tab, not to be confused with the Profiles element. Within this section, you will notice a number of sub-sections dedicated to fixed, identification and customisable fields. Customisable fields are those focused on in this article.
In order to create a custom profile field, click the icon located in the customisable field sub-section. This will direct you to the profile field creation page. From here, you will need to create you field by providing the details prompted.
Name: This will be the title of your profile field and what users will see within their in-app profiles.
Key: The key acts as a unique identifier for each profile field within the Core backend. A key is required for each profile and must be unique, containing no spaces and cannot start with a number. The unique key requirement only applies to a single given project as keys make be duplicated across various different projects.
Type: This is the type of response gathered for a given profile field. Short or long text, social media, location and multiple choice responses are all available options. Note; a maximum of 10 custom fields are allowed for short or long text, location or social media responses. However, you may utilise as many multiple choice custom fields without limitation.
Required: Setting a profile field to required dictates whether or not a response is necessary for the field. If this is the case, a default option will need to be set in the event that a response is not provided. This will also mean that the field will need to be set to mandatory when placed into a registration form.
User Access: If set to hidden, users will be unable to edit or see their personal field/s within their in-app profile. If set to visible, they will be able to view the field and their response. If set to editable, they will be able to view the field and alter their response freely at anytime. As this option is seperate to Profile Visibility, other users viewing attendee profiles will not be restricted by the changes made to this option.
Profile Visibility: If set to hidden, users will be unable to view this field on other users profiles. If however, it is set to visible, users will be able to see the field and response provided.
Once you have provided the relevant details, click Save. Depending on the chosen type, a secondary option will present itself; Selectable Options. With particular reference to the Multiple Choice type, this is where the set of selectable options will be defined.
As is shown above, an option has been defined for the 'Will you be attending the Gala Dinner?' custom field. The option shown dictates that an attendee will be in attendance and has been labeled 'Yes, I will be in attendance' purely for display purposes.
Let's assume a fictional scenario - the data provided by the client, in an excel spreadsheet format, has included this field. The responses for each attendee provided varies between 'Yes, I will be in attendance', 'Yes' and simply 'Y'. The Import Keywords option allows for a given field's data to be captured regardless of what variation of the response has been provided, so long as the keyword/s is/are defined. Note that the responses are not case sensitive, meaning that 'Y' will capture all responses regardless of whether they are upper or lower case. This makes data imports easier and less time consuming than going through the spreadsheet and updating all responses to be uniform.
In particular for fields set as required, it is considered best practice to provide a default option in the event that a user/s does not provide a response. To set a Selectable Option as default, click on the line items corresponding dropdown icon and select Make Default, as shown below.
At any point in time you may edit your created custom fields, altering options as you desire. Custom fields may also be deleted freely. However, ensure that there are no other features such as Smart Redirects or Track that will be disrupted as a result of the fields deletion.