People reporting

Export People Records

You can easily export a CSV report of all people in the event. The Export tool allows you to filter the data based on any combination of the following options:

• People who have or have not had their badge printed
• People who belong to different categories
• People who attended different sessions

Generate a People report

To generate a People report, follow these steps:

1. Log in to the Jomablue Portal, and then click on People in the left-hand menu
2. Click on Export at the top-right of the screen
3. Set the filters you wish to apply to your export (Badge printed, Categories, Sessions)
4. Select the columns you want to include in your report by checking the relevant boxes
5. Click on Generate Export to start the generation of your export
6. Wait for the export generation process to complete.
7. Once the process is complete, the export is ready for you to download. Click the Download CSV icon next to the right of the report to download the CSV file containing your People report.

Filters And Columns

The Export tool allows customisation of the data included in your export. You can filter the people that will be present in the report and choose which columns of data to include.

Available Filtering options

• Badge Printed: Include people who have had their badge printed, those who have not, or everyone
• Categories: Select people from specific categories to include in your export. If left blank, people from all categories will be included
• Sessions: Select people who attended specific sessions. If left blank, all people will be included.

Columns included by default

• Organisation UID - the unique identifier attached to that person, usually generated by your own CRM before the event. This can be used to feed the data obtained from your event back into your own
• CRM.
• First Name - First name of the attendee
• Last Name - Last name of the attendee
• Job Title - Job title of the attendee
• Company - Company of the attendee
• Mobile - The mobile number of the attendee
• Email - The email address of the attendee
• QR UID - The Unique Identifier for a person (Jomablue use only)
• NFC UID - Another Unique Identifier for a person (Jomablue use only)
• Status - The registration status of this person within the event. This can be either 'Registered' or 'Cancelled.’
• Import Type - The method by which the person was initially entered into Jomablue. This can be via a site, import, manual addition etc.
• Mobile Suppressed - A Y field indicates if a person has not consented to have communications sent to them via their mobile number e.g., "SMS Opt Out"
• Community Member - Indicates if the person has logged into the Community.

Filter & optional columns

In addition to the default columns, the export tool allows you to:

• Limit the results with filters
• Select additional data to be included in the report as columns, as shown below.

Data available 

Select any of the following options to include in the people export CSV file:

Categories - denoted by: CATxxx [name]

This option includes one column per Category enabled in the event. Each person row will contain a 'Y' for each category they are a member of.

Vendors - denoted by: VENxxx [name]

This option includes one column per Vendor in the event. If an attendee taps their Smart Badge on a Vendor's Lead Capture Device, the timestamp will be in the corresponding column in the CSV. The first interaction timestamp is recorded.

Vendor Journey

This option includes a single column named “Vendor Journey,” which contains the Vendor Journey that each attendee has undergone. This is a somewhat structured string that can be uploaded to your CRM if your fields are limited. For additional information, see the section below: Vendor Journey Legend.

Item Entitlements- denoted by: ITMxxx

This option includes one column per item. When a person is entitled to an item they will be represented with a Y, once collected the Y is replaced with a timestamp.

Session Related Content - denoted by: SESxxx - Related Content

This option includes one column per Session in the event. If an attendee attends a Session and then requests the Session Related Content, the column will contain the timestamp of when they requested the Session Related Content.

Session Attendance - denoted by: SESxxx - Attended

Y will appear if the person has attended the session. This could be either by a session check-in or inferred.

Session Check-in - denoted by: SESxxx [name] - Check In

This option includes one column per Session in the Event.  If a person attended a Session, the timestamp of when they checked in to the Session will appear in the corresponding column

Session Check-out - denoted by: SESxxx - Check Out

This option includes one column per Session in the event. Each column header takes the form "Check OUTxxx", where xxx is the Session number. If a person checks out of a Session, the timestamp of when they checked out of the Session will appear in the corresponding column

Session Allow Entry - denoted by: SESxxx - Allow Entry

This option includes one column per Session in the event and indicates if a person is entitled to attend a Session with a Y in the corresponding column.

Session Journey

This option will include a single column named Session Journey which contains the Session Journey that each attendee has undergone. It consists of a series of [square brackets] containing the names of each Session they attended, in the order that they attended them.

Touchpoints - denoted by: TPTxxx

If an attendee taps their Smart Badge on a Touchpoint during the event, the most recent time they did so will appear as a timestamp in the corresponding column.

Block Metrics

This option includes a column per metric, per block. It shows the calculated value for that metric based on a person's interactions with that block. (Note that this will add a significant number of columns to the report if your event has many blocks)

Each column will have a header containing the block type followed by the block ID # followed by the block name followed by the metric name. e.g., Block Type: live_chat | ID: 1590 | Session 1 | Participated

If no block names are provided it will be difficult to identify where the metric comes from e.g Block Type: live_reaction | ID: 1561 | keynote_session_reactions | Reacted: Love

It is recommended to have a consistent block naming convention that will help you sort the data easily.

e.g., [Canvas Name] + Block type + Unique ID ( video name /  file name  / integer)

Block metrics available below:

Canvas Views

This option includes two columns per Canvas: one column containing a view count (e.g., the number of times that Person has viewed the Canvas), and the second column containing the "first viewed" time (the first time that Person viewed the Canvas, in the event timezone).

Each Column has a header containing:

• The Canvas ID
• The Canvas type
• The name of the Session/Vendor/Page the Canvas is attached to (or the Event Name in the case of the Lobby Canvas)
• "Views" or "First Viewed" for the view count and first viewed columns respectively

Vendor Journey Legend

The vendor journey is designed as a somewhat structured free-text field. It can be used if you have limited fields available in your CRM.

For example, if you can only update a single text field such as 'description' on a person record but want to load more information, the vendor journey might be useful for you.

Legend

[Vendor Name]{tag}{{email}}(notes)

Understanding the Layout

Records will only appear if they exist. So if a tag, email, or note wasn't included during the lead capture, you will only see [Vendor Name]

The order is the order of vendors visited (chronological)

Examples

[Coca-Cola]{Warm}{{Introduction Email}}{Prospect}[Schweppes]{Hot}(Interested in the new product line)

In this example, the person had the following Journey:

• Visited Coca-Cola
• Coca-Cola tagged them with Warm and Prospect tags
• Coca-Cola sent the email titled "Introduction Email"
• Visited Schweppes
• Schweppes tagged them with Hot
• Schweppes added a note stating “Interested in the new product line”

Explore People - Presets

Presets allow you to create and save filtered views of people. This saves you time in building a filter each time. 

Create a new Preset

1. Within your event, select People from the left navigation
2. Select the Explore People button
3. Apply the required filtering options
4. Select Filter Preset and Save as new Preset
5. Apply a Name and Description to your new Preset
6. Select Save

Load a Preset

Within your event:

1. Select People from the left navigation
2. Select the Explore People button
3. Select Filter Presets and Load Preset
4. Click on the dropdown and select the required Preset
5. Select Load to load the Preset filters
6. Select Load to view the results

Update a Preset

Once a Preset has been loaded, you can modify the criteria and save these changes to your Preset.

To do this:

1. Select Load to load the Preset filters
2. Apply the changes to the criteria
3. Select Load to view the results (to confirm your changes)
4. Select Filter Presets > Update current Preset
5. Select Update

Note: We recommend adding a note in the Description referencing the updated criteria.

Delete a Preset

Within your event:

1. Select People from the left navigation
2. Select the Explore People button
3. Select Filter Presets and Load Preset
4. Click on the dropdown and select the required Preset
5. Select Load to load the Preset filters
6. Select Filter Presets > Delete current Preset
7. Select Delete to permanently delete the selected Preset

Export a Preset

The Menu icon (top right of results table) provides an option to export all data or a customised view of fields (see below).

Additional Options

The Menu icon (top right of results table) offers options to include different fields in the view.

Notes:

Saved Presets are available to all users within your instance who have the appropriate role.