Profiles FAQs

Table of contents:

  1. When would you use external references?
  2. When is it best to use a text field over a multiple choice field?
  3. Are there length restrictions of Profile data fields?
  4. How do we enable the digital event ticket, including QR code?
  5. What is a unique reference?
  6. Can you have duplicate emails in Profiles?

 

FAQ: When would you use external references?

A: External references are a unique string of characters (not limited to numbers) that are populated by an event organiser when profiles are imported. These are used to identify profiles in the Core and may include Staff ID, registration number, ticket number etc.

External references can be very useful when importing profile lists. Using external references when uploading profile data minimises the risk of duplicating your profile list by mistake, as this number can be used to separate those existing profiles from ones yet to be created. This is also important when bringing attendee data from a third-party system with pre-existing registration or ticket numbers, as to keep the data clean and trackable.

While a primary function of an external reference is as profile identification, it can also be used to log into the event App. It is particularly useful to use an external reference as a login method when the reference is something the attendee is already familiar with (e.g. staff ID or member number), as this limits confusion and required attendee communication.

 

FAQ: When is it best to use a text field over a multiple choice field?

A: As customisable fields are limited to an additional 10 text fields, it is important to plan ahead with which fields will be what type.

Customisable Multiple Choice Fields

It is recommended to use multiple choice fields where possible as there can be an unlimited number with as many choices as required. Multiple choice fields are also the most versatile when working with elements in the system, and increase flexibility with personalisation and data collection. Multiple choice fields can be used to:

  • Show/hide information on badges
  • Create smart redirects
  • Create Track Rules for sessions and events
  • Track Interactive Sessions demographic data
  • Create leaderboard teams
  • Display more in-depth and segmented profile statistics
  • Display information on attendee profiles
  • Be completed by attendees

Customisable Text Fields

Text fields vary in size, however, have no character limit. The size (short, medium and long) refer to the size of the textbox provided on a registration form or when updating a profile in-app. Text field size can be used to encourage attendees to provide longer answers etc.

Each project is limited to 10 text fields, in addition to pre-existing Fixed and Identification fields (e.g. Type, First Name, Last Name etc.). Text fields draw the text that has been input directly into another place. For example, an attendee’s office street address may need to appear on their profile in the list. The address will pull as it has been loaded into the profile.

Text fields can be used to:

  • Populate text on badge
  • Display information on attendee profiles
  • Be completed by attendees

 

FAQ: Are there length restrictions of Profile data fields?

A: No, there are no character limits for text fields. The short, medium and long text fields are purely visual and only affect the physical size of the text box, not the character limit. For example, you may wish to use a long text field to promote a longer answer from attendees, or a short text field if you are only expecting a short answer. 

 

FAQ: How do we enable the digital event ticket, including QR code?

A: In-App Badges are already enabled when the App element is activated, to use them, first you must create an In-App Badge. Navigate to App > In-app Badge to create your badge. In-app badges have a QR code by default, and other elements can be added as required. Once your badge has been setup, it will need to be added to the main menu as an icon.

 

FAQ: What is a unique reference?

A: Unique references are those which are specific to each attendee profile. They are predominately used for profile management between external registration systems and the Core, and attendee logins. Attendees can have one internal reference and one external reference.

Internal references are a unique string of numbers that are generated by the Core for each attendee. These are automatically determined when a profile is created and cannot be changed as they are used to identify profiles in the Core.

External references are a unique string of characters (not limited to numbers) that are populated by an event organiser when profiles are imported. These are used to identify profiles in the Core and may include Staff ID, registration number, ticket number etc. If not populated, this will remain blank.

 

FAQ: Can you have duplicate emails in Profiles?

A: Yes you can permit duplicate emails in your profile data.

To enable duplicate emails in your profile data go to:

Project Configuration > Profiles > Profile Fields

Click the drop down menu for Email and click Allow Duplicates.