Grip allows participants and exhibitors to interact and connect with the RIGHT people at events. We get this recommendations data from your event participants using the platform, from attendees to exhibitor representatives.
There are a few ways this data can be input, participants can input data when first logging into the platform or this data can be gathered ahead of them logging in (for instance, during the registration process) and either manually input or uploaded through an API.
This data entry uses Custom Profile Fields that you setup when creating an event. These are essentially all the information that you want to know about the people, companies, or items within your event. Our AI then takes that data, learns from it and kickstarts into action, giving you extremely personalised recommendations. To simplify the above, Custom Profile Field data is used to create instant matches, recommendations, all using our proprietary AI.
There are two types of Custom Profile Fields, 'Single-Event' and 'Multi-Event'. Single-Event Fields only exist within a single event. The Custom Profile Field data stays within that single event. Multi-Event Fields exist within multiple events in an event app. The data then pulls across all of your events. More on this in the steps below. Your Grip team needs to enable Custom Profile Fields before you can create them in your event.
In this article we will cover:
- Navigating Custom Profile Fields within a Single-Event
- Understanding the Custom Profile Fields Page
- How to create a Single-Event Custom Profile Field
- FAQs
Navigating Custom Profile Fields within a Single-Event
You can sort and filter all the fields and information within this page.
1. In the dashboard click on 'Event Details' and click 'Custom Profile Fields' at the bottom. This is the 'Custom Profile Fields' page.
2. You can also access Custom Profile Fields by going into the individual data type. In the dashboard click on the 'Data' tab and the click 'Participant' and select which Data Type you would like to go into (for this example we will use 'Attendee').
3. Click 'Custom Profile Fields' at the top of this page (shown in the image below).
4. You will then be taken to the Custom Profile Fields page (in this example for attendees).
5. On this page you will 'Attendee profile fields' which are the default, static profile fields that cannot be changed. Below this, you will see 'Attendee custom profile fields' which are created and assigned to a data type (in this case attendee) in the 'Custom Profile Fields' page we showed you in step 1. You can go back to this page by clicking the button 'Go to event custom profile fields' in the attendee custom profile fields section.
Understanding the Custom Profile Fields Page
1. 'Status in event'. This column will either be 'Active' or 'Inactive'. To make this field active you will need to add 'Types using field in event'. Here you can select the 'Event Data Types' you have setup, this will then make the status 'Active'.
2. 'Name'. This is the name of the Custom Profile Field. Examples below.
3. ‘Field type’. Here you have two options, ‘Single-Event Field’, and ‘Multi-Event Field’. A ‘Single-Event Field’ only exists within a single event. Whereas a ‘Multi-Event Field’ exists within multiple events in an app. You can assign or remove a multi-event field to a Type in this screen, but this change will only impact that Type within this event.
If you are an app admin you can add a ‘Multi-Event Field’ to a Type as a default in the ‘Multi-Event Fields’ page, then whenever that Type is added to an event, it will automatically have that Custom Profile Field assigned to it. Click here to see how you can add this after you have followed the steps below.
4. ‘Input style’. Here you can see what form the data and values within the profile field will take. More on this in the sections below.
5. 'Matching type'. These are data values used by our platform and AI to make recommendations, matches, and for the AI's learning process.
6. ‘Types using field in event’. These are the ‘Event Data Types’ that are using this field within this event. You can easily add or remove a Type using the check boxes in the dropdown from this field.
7. ‘Setting’. This is where you can edit each Custom Profile field. This will take you to the edit page for that Custom Profile Field. Note that for multi-event fields, you can access the edit page, but can only add or remove types from that page. Editing of multi-event fields can only be done by app admins.
How to create a Single-Event Custom Profile Field
Tips for Creating Effective Custom Profile Fields
When it comes to custom profile fields (CPF), we believe in giving you the flexibility to add as many characters as you need. However, we'd like to highlight the importance of testing the visual impact of longer field names. Opting for a shorter, concise version can enhance the overall look and readability of your CPF.
Additionally, we recommend using statements instead of questions for CPFs. This choice ensures seamless integration when using them as filters within your lists. By following these recommendations, you can optimize the feel and functionality of your custom profile fields.
Remember, our goal is to provide you with the best user experience possible, so feel free to explore the possibilities while keeping these suggestions in mind.
1. Click the 'Create new custom profile field' button on the 'Custom Profile Fields' page.
2a. You will then land on the page below. You first have to fill out the 'Single-Event Field Settings' section before proceeding. We have a table below explaining the sections on this page.
| 1. Profile field visible. | This defines whether the Type permissions allow the visible field to be turned on to allow this field to be visible within the event. |
| 2. Profile field editable. | This defines whether the Type permissions allow the editable field to be turned on to allow this field to be editable within the event by that Type. |
| 3. Profile field filterable. | This defines whether the Type permissions allow the Filterable field to be turned on to allow this field to be used as a filter when searching that Type within the event. |
| 4. Profile field can be used in recommendation engine. | This should normally be turned on unless you don't want to use a selection to recommend this profile, e.g. 'vaccination status'. |
| 5. Identifying data check box. | This setting is for GDPR purposes and helps us to identify information that can ID an individual. |
2b. The second half of this page is below.
| 1. Profile field label. | This is the name of the field as it will appear within the event, click the flag to add different translations. |
| 2. Input type. |
You have 4 options here. 1. Pre-defined values: can only be answers from a defined list e.g. 'Industry' you can make this a Parent/Child Field, and a required field if you wish. 2. Freeform: allows anything to be input e.g. 'Name'. Freeform answers cannot be used for recommendations. 3. Pre-defined values and freeform input, and 4. Link: allows text to be hyperlinked to an external page. For pre-defined input types, please add these values in the 'Profile Field Values' tab at the top of the page. |
| 3. How many answers can be selected? | Choose whether this field allows several answers or only one. This will now a 'Required field toggle or a minimum/maximum number of answered required box, more on this in the step below. |
| 4. Use for matchmaking engine as: |
This field has five options. 1. Fact - Facts are metadata values used by our AI for learning purposes. This category helps our AI understand the user more to make the best recommendations.
2. Supply - One group of people will enter supply questions, this for example could be an exhibitor with products. These values MUST match Demand.
3. Demand - The other group of people will enter demand questions, this could be attendees interested in certain exhibitor's products. These values MUST match Supply.
4. Matching fact - Matching Facts act as both Supply & Demand and is used to create immediate matches. For example, the AI will recommend users that have entered the same value for the Metadata questions that they answered. The matchmaking engine will also use the values under this category to learn more about the user’s true interests.
5. Unused - Not using any of the above. |
| 5. Types using field in event. | These are the types where you want this custom profile field to be present, e.g. Company, and Exhibitor representative. |
If you want a step by step guide on how to create Parent/Child Custom Profile Fields, please see our article here.
3. In the 'How many answers can be selected?' filed, if you select 'Can pick one' you will see a required field toggle, which will make this Custom Profile Field mandatory to complete before proceeding in the platform. If you select 'Can pick many', you will see a minimum answers required box, and a maximum answers required box. We have an article here which explains the Required field, Minimum, and Maximum Custom Profile fields.
4. Click 'Create custom profile field' to confirm and create it.
5. To add the values to your newly created Custom Profile Field, click the 'Settings' cog next to the Profile Field.
6. You can then click the Field Values tab at the top of the page.
7. From here you can add your pre-defined answers. Click 'Add rows' and enter your answers. You can copy and paste values from a spreadsheet into these rows. You can paste as many values as you would like without needing to add new rows, simply copy and paste! You can delete rows by clicking the trash button under 'Delete'. Always click 'Save new values'.
When you have a Multi-Event Custom Profile Field, anyone that has selected the values and answered the questions before, in Event A (for example). When attending Event B the Custom Profile Field data (values and answers) will get pulled across so they won't have to fill these in again and all values will be pre-filled. This means they will get even better recommendations with our AI learning more each time.
Navigating and creating a Multi-Event Custom Profile Field
Please note, you must be an App Admin to make to create and edit Multi-Event Custom Profile Fields.
1. Multi-Event Custom Profile Fields exist within 'App Settings'. The steps to create these are the same as the steps for creating Single-Event Custom Profile Fields with a few minor differences outlined in the steps below.
Please note, you can't add 'Types using field by default' from this screen as you can in a Single-Event.
2. To change the 'Types using field by default' field, click the 'Settings' cog on the right.
3. At the bottom of the page you will see the 'Types using field by default' drop down menu. Just like Single-Event Custom Profile Fields, you can add your type. The only difference is this is now application wide, meaning every-time you create a new event and across current events this Custom Profile field and data will pull across saving you time.
Always remember to click 'Save changes'.
FAQs
Can I have multiple Custom Profile fields with the same name?
Yes.
Can I copy and paste data values from an external spreadsheet?
Yes.
Who can create Multi-Event Custom Profile Fields?
Only app admins can create and edit Multi-Event Custom Profile Fields.
In what order do Custom Profile Fields appear in onboarding?
Currently there is no hard rule, but they generally appear in the order in which they are created.
Are emojis supported within custom profile fields?
No, emojis are not currently supported within custom profile fields.
How can I export my Custom Profile Field values once they have been created?
In order to export CPF values, select the Custom Profile Field first. Open the tab ‘Single-Event Field Values’ or ‘Multi-Event Field Values’, and click on the ‘Export Data’ button.
