# Jomablue
## Documentation
# Inferred Sessions
In many events, Sessions occur back-to-back with limited or no opportunity to gather check-in data from people who remain seated in the room.
By using Jomablue Session Entry (Check-in) and Session Exit (Check-out) features, we can intelligently infer which sessions attendees participated inbetween these two data points. For additional information, see the article: [Managing Sessions](https://jomablue.bolddesk.com/kb/article/149/managing-sessions) under the section: **Create a Location**.
When Inferred Sessions are enabled, Jomablue employs an algorithm that determines attendance using various factors. The most significant factor is the Minimum Stay Percentage, which you can adjust (more details on this later).
#### **When is Inferring Useful**
- When there is limited changeover time between sessions
- When attendees generally remain seated for several sessions in a row
- When attendees must stay in a session for a specific duration to be considered as “attending” (e.g., CPD points)
## How it works
The following rules must apply:
- If a Person entered (checks in) to a Session at a Location
- AND that Person has exited (checked out) from the same Location
- AND if that Person was in the Session for longer than the Minimum Stay Percentage
- AND if that Person has no interactions (check-in or check-out) at any other Location during that time
We can then infer that they remained in the room for the entire duration and therefore attended all sessions between the two data points.
**Visual example**
## Minimum Stay Percentage
The Minimum Stay Percentage is a feature of Inferred Sessions, ensuring that attendance calculations are meaningful. If Session A and Session B are back-to-back and Session A runs over time, People checking out immediately after Session A (e.g., 10 mins into Session B) should not be counted as having attended Session B.
The Minimum Stay Percentage indicates the minimum duration required for a Session to be considered attended. By default, the value is set to 60%, but you can adjust it after enabling Inferred Sessions (see Enable Inferred Sessions section below).
The algorithm is designed to be more lenient towards attendance (vs. non-attendance), since false negatives for attendance are generally more problematic than false positives.
Using the above example, if Session A and Session B are each 100 minutes long and a Person checks in at the beginning of Session A, they will be inferred as having attended Session B if they check out after the 60-minute mark of Session B. However, if they check out before the 60-minute mark, they will not be inferred as having attended.
## Enable Inferred Sessions
- Navigate to **Event Configuration > Settings > Event Settings Tab**
- Select **Yes**
****
## How do I see Inferred Sessions?
Inferred sessions are displayed whenever session information is displayed. After enabling this feature, you can assume that any session-related data reflects inferred attendance. For Example:
- In the Person Detail section under the Interactions and Session Attended Tab
- Visible in Exports
- Event App users see "Attended" icons in their agendas
- Networking recommendations in Community will consider inferred attendance
Attendees will receive survey questions for the Inferred Session if dynamic Surveys are in use
- Insights charts will reflect inferred counts
**Notes:**
- Jomablue recalculates inferred session attendance on an ongoing basis during a live event: approximately every 10 minutes. If you're monitoring Session Check-in counts, expect updates on this cadence.
- Separately, if you change the Minimum Stay Percentage or other Inferred Session settings, it may take up to 10 minutes for that specific change to be reflected in Jomablue.
- If you use Inferred sessions, the counts for "Checked in to session" may appear understated, as Jomablue can only infer attendance once the session exit interaction is logged. If sessions run back-to-back, the check-out data may not be logged for some time after the first session starts.
- Jomablue will not infer attendance for a restricted session unless the person is entitled to access it
- Inferred Sessions can be enabled or disabled retrospectively
If changes are made to the Minimum Stay Values or inferred session settings, it may take up to 10 minutes to see the updated results in Jomablue
- People who have checked into a location and have not checked out, or interacted elsewhere, will be marked as attending the session they entered (as long as they meet the Minimum Stay Percentage)
## Referenced articles
[Managing Sessions](https://jomablue.bolddesk.com/kb/article/149/managing-sessions)
# Release 9.57.0
## Improvement
### Improved Trait Management for Sessions & Vendors
- Traits on Session and Vendor records are grouped by Trait type, with a simpler picker for adding and removing them. This makes it easier to see what's assigned and update it without digging through a long list.
- When editing a session or vendor, any requirements on a trait type, such as a trait being mandatory or having a maximum number of selections, are checked when you save. If a requirement isn't met, an inline message tells you exactly what to fix.
****
### Traits List Sorted Alphabetically
The Traits list within a Trait type opens in alphabetical order and can be sorted by name, ascending or descending. As your list of traits grows, this makes it faster to find the one you're looking for.
****
### Saved View Presets Sorted Alphabetically
Preset views in the external viewer, including People Advanced Search and the Views and Actions page, are listed alphabetically wherever presets appear. This gives a consistent, predictable order and makes it easier to locate the view you need.
## Known Defect
### Mandatory Traits Can Now Be Met When Creating Sessions or Vendors
- Mandatory Trait requirements can now be met while creating a Session or Vendor, rather than only after the record has been saved for the first time.
- Previously, the Trait picker for mandatory Trait types wasn’t available until after initial creation.
- If you try to create a session or vendor without meeting a mandatory trait requirement, an inline message tells you what's missing before the record is created.
- This behaviour is now consistent across both sessions and vendors.
### Filter Preset Reliability Improvements
- Creating and updating filter presets works reliably across roles. Eligible roles can create and manage shared presets without unexpected errors.
- Other users can update a preset's name, filters, and columns as expected.
- If a save fails, you'll see a clear, readable message explaining what went wrong, rather than a raw technical error.
# Managing Sessions
## Session Locations
Before setting up Sessions in Jomablue, you need to create Locations. Locations indicate where a Session will take place, whether online or at a physical location for in-person events.
### Create a Location
1. Navigate to **Locations** via the left navigation menu
2. Select the **New Location** button at the top right
3. Populate the fields as follows:
**Location Name** (required)
- For Online/Community events, use the Stream/Track name, or simply "Online"
- For in-person events, use the name of the Theatre or Meeting Room
**Description** (optional)
- Friendly description, not displayed anywhere in Community
**Log Exits** (required)
- This feature applies only to in-person events using Jomablue Smart Badge, Name Badge & Name Label solutions. For Community Events and Badgeless solution, toggle the button to **No**.
- For in-person events and Jomablue Smart Badge, Name Badge & Name Label solutions, toggle the button to **Yes** if you want to enable **Session Check-Out** mode and Inferred Sessions using the Jomablue Session Attendance Management feature
- For additional information see the article: [Inferred Sessions](https://jomablue.bolddesk.com/kb/article/138/inferred-sessions).
**Community Schedule Settings**
These settings are related to Community/Virtual Event. For an in-person ONLY event, this is not applicable. These options refer to the Community Schedule, which provides an alternative view of the Agenda.
For additional information see the article: [Session Canvases](https://jomablue.bolddesk.com/kb/article/145/session-canvases).
**Schedule Colour**
- Apply a custom colour for the Location in the Schedule view
**Schedule Sort Order**
- Enter a number to determine the order of the Location in the Schedule view
**Search a Location**
- Type the Location Name in the search bar to pull up the location information you need
### Delete a Location
You can delete Locations that are no longer needed. However, a Location cannot be deleted if it has any existing relationships, such as:
- Location interactions (e.g., a Person has checked into that Location)
- Sessions (e.g., a Session is using that Location)
**To delete a Location:**
1. Navigate to **Locations** via the left navigation menu
2. Select the **Delete** button next to the respective Location
If a user attempts to delete a Location with existing relationships, a pop-up will display appropriate messages.
****
If a Location is eligible for deletion, clicking the Delete button will prompt a confirmation modal before proceeding.
****
## Create and Delete a Session
To create a Session in Jomablue, you will need the following:
- Session Name
- Session start date and time
- Session end date and time
- Session Location
### Create a Session
1. Navigate to **Sessions > Add a Session**
2. Populate the following fields:
a. **Session Name** (191 character limit)
b. **Start and Finish Date/Times**
c. **Location**
d. **Description** (HTML supported)
3. It's optional to add Session promotional text and images. Session promotion image supports transparency, allowing the upload of images without a white background.
4. If you are using Traits, click the blue plus **(+)** icon to add Traits to the Session.
5. If the Session is intended to be a Restricted Session, select the **Yes** option under Restricted Session (default is set to No). For additional information, please see the section: **Manage a Restricted Session** below.
**Note:** Line breaks are not supported in the Session name. If required, use the “Session Promotion” line within the session to add additional copy to the session listed in the agenda.
#### Session Organisation UIDs
Session Organisation UIDs are unique identifiers assigned to each Session in Jomablue. They enable you to correlate the records to your own source data. Session Organisation IDs are imported with other Session data. The UIDs are visible in the Session Detail View.
If you need to make a change to a Session Organisation UID, please contact Jomablue. Editing an Organisation UID carries system-wide consequences, such as integration or event reporting.
#### Modify check-in parameters
Once a Session is created, you can adjust the Check-In experience for Attendees by clicking on the
**Check-In** tab. Below are descriptions of each option:
- **Entry Buffer:** Sets a buffer time (in minutes) for how early an Attendee can check in before the Session starts (default is 10 minutes)
- **Upon Entry, Send:** Select an Email and/or SMS Template to be sent to the Attendee upon check-in
- **Feed - Live Engagement App:** Create a Card for the Community that will be sent to an Attendee's Feed when they check into the Session. For more on publishing Sessions, see Publishing Sessions in Community.
#### Set Related Content
After creating a Session, you can add Related Content to be distributed via a Touchpoint device during or after the Session. To select the available content, click on the **Related Content** tab, then set the following fields to appropriate values:
- **Exit Buffer:** The time (in minutes) after a Session's end date/time during which an Attendee can still download Related Content from a Touchpoint device (default is 0 minutes).
- **Upon Request for Content:** Use the three drop-down menus to select an Email, SMS, or Card template to be sent to the attendees when they use their Smart Badge on a Touchpoint device. You can combine any of these options (e.g., send an Event App Card and an SMS).
### Edit Session Buffer Times
1. Navigate to **Sessions** in the left navigation menu
2. Select the **Grid View** tab and slide through the timeline to your preferred session
3. Click on the Session you want to adjust the buffer time for
4. Adjust the value under the **Entry Buffer** field to control how early attendees can access the session
5. Adjust the value under the **Exit Buffer** field to control how long attendees can continue to download related content from a Session device
6. Click **Save**
### Delete a Session
To delete a session, you can do the following:
1. Navigate to **Sessions**
2. Click on the Session you want to delete
3. Go to the **Details** tab
4. Click the **Delete** button at the top right-hand side
5. A pop-up window will appear with a confirmation asking, ‘Are you sure you want to delete this session?’
6. Finally, click on the **Delete** button
**Note:** A Session can’t be deleted if a Session Canvas is attached.
## Import Sessions
The Jomablue Import Tool allows users to import new Sessions and update existing Sessions.
#### Preparation:
- Ensure that your data file is clean and properly formatted
- Ensure that all Locations have been created in the event
- If using the Session Template, ensure that the second line in the template (that contains dummy/placeholder values) is removed before import
#### Session Import Tool
To get started, navigate to the **Sessions section** and click the **Imports** button. A list of previous imports will be displayed. To start a new import, click the **New tab** or the **New Imports** button at the top right of the page. The Session Import tool will take you through 7 steps:
**Step 1: Upload CSV File**
Use the file uploader to choose your Session import file. Also available are download buttons on the right-hand side, which provide several downloads. These include:
- **Starter Template:** An empty Session import file that serves as a template for creating your import file
- **Update Existing Sessions:** This option downloads a list of all existing Sessions, including basic Session fields (e.g., Name, Description, Location, Start/End times, and Session IDs), so you can edit it and re-import to update existing Sessions
- **Advanced Session Export:** A comprehensive export of all Sessions and their Session-related fields
**Step 2: Validate Columns**
In this step, you will need to select the format for the dates included in your import file. By default, the Session Template asks for dates in the YYYY/MM/DD hh:mm datetime format (in the event’s timezone), but other formats are also available.
For example, if your dates are formatted as DD/MM/YYYY hh:mm, choose the Day/Month/Year Time format.
**Step 3: Validate Rows**
The import tool will validate all rows in the file to check for any errors, such as missing required values, invalid dates, missing locations, and non-existent session IDs
**Note:**During row validation, the importer proactively checks for potential scheduling conflicts. If any imported sessions overlap in the same time slot for a given location, a warning will be displayed. This early conflict detection helps prevent accidental double-booking of locations and saves you from needing to manually review and resolve these issues after import.
**Step 4: Fix Errors**
If any errors are identified in Step 3, the affected rows will be displayed with the erroneous fields identified, allowing you to manually correct or remove them.
If no errors are found, then Step 4 is skipped, and Step 5 commences.
**Step 5: Review and Submit**
Once all row validation has been completed, the tool will display the total number of rows to be imported and summarise how many Sessions will be created or updated
**Step 6: Run Import**
In this step, the Sessions are queued for import.
**Step 7: Results**
Once all records have been queued for import, the import will finish in the background, and the page can be safely closed. A button to view the Import Progress will redirect the user to the list of recent session imports, where the progress will be displayed.
## Manage a Restricted Session
Restricted Sessions can be used during Session Check-in to either allow or deny entry to attendees. For example, you might want to prevent staff from entering a popular Session to ensure a good experience for your audience.
If a Session is restricted, the entry conditions are based on:
- Individual person entitlement
- The Category of a person
In Community, Restricted sessions will appear with a padlock:
- Green padlock if the attendee is entitled to attend the session
- Red padlock if the attendee isn’t entitled to attend the session
### Person level Entitlement
This is generally used if you are selling a session or workshop that requires registration or payment for attendance. In Jomablue, this is generally managed through a People import, but can also be manually edited in the person record.
To enable a Restricted Session:
1. Navigate to the **Session** in the left menu
2. Select **Yes** for **Restricted Session**
3. Press **Save**
To manually adjust an attendee’s entitlement to the Session:
1. Navigate to the person record
2. Select **Entitlements** tab
3. Click the (+) icon and select the Sessions they should be entitled to
4. Press **Save**
### Category level Entitlement
This is generally used if you want to allow or prevent certain Categories of people from attending particular Sessions. You can either include or exclude Categories based on your selections.
To enable Category-based entitlement restrictions on a Session:
1. Navigate to the **Session**
2. Select **Yes** for **Restricted Session**
3. Press (+) next to the **Allowed Categories**
4. Toggle the Categories you wish to allow entry for
5. Press **Save**
If a person belongs to any of the allowed Categories, they will be allowed entry to the Sessions.
**Notes:** You can allow entry to an unentitled person at the door if the Allow Override option is enabled in Session Details. This setting can be used if an organiser’s representative is managing Session entry and is authorised to make this decision.
## Log Exits (Session Check Out)
Log exits are used to track the time spent in a location, which can help infer session attendance (see [Inferred Sessions](https://support.jomablue.com/kb/article/138/inferred-sessions)) or capture the exact time spent in a location or session for CPE/CPD requirements.
**Understanding how Log exits work**
Firstly, logging is enabled by location, not by session. This means event staff have the option to toggle the device between Entry and Exit modes for every session within that location.
In either mode, tapping a Smart Badge will record an Entry (Check-In) or Exit (Check Out) for whichever session is currently displayed on the screen.
**Understanding which sessions are displayed on the screen**
Jomablue devices automatically keep track of which session is being displayed based on the session data entered. The devices held by event staff will automatically change to new sessions without intervention from the event staff.
**Entry Buffers**
Entry buffers allow a device to begin capturing data for a session before the scheduled start time. This is often necessary when you want to start letting people into a session before the actual start time.
**Example:** If a session is scheduled for 10:00 AM to 11:00 AM with a 15-minute entry buffer, event staff can check in attendees (Entry) or check them out (Exit) for this session between 9:45 AM and 11:00 AM.
**Notes:**
Exit buffers apply only to Session Related Content and do not affect Entry or Exit interactions.
**Scenario:** Consider a person who checks in for Session A but does not check out until after Session B has started (or even Session C or D).
In this case, the person would receive:
- Entry (Check-in) timestamp for Session A
- Exit (Check Out) timestamp for Session B (or optionally for Session C or D)
**Impacts of this scenario:**
- If you're using the Inferred sessions feature, the person will be considered to have attended both Session A and Session B
- If you're not using inferred sessions and are doing time-based reporting for CPE/CPD or similar, you will need to calculate the time spent by reviewing all sessions at that location and matching Entry (Check-in) and Exit (Check-out) timestamps.
## Promote Sessions in Agenda View
The Community Agenda allows for Session promotion directly within the Agenda. You can add an image and a short text description to be displayed alongside the Session listing in the Agenda.
#### **Promoting a Session in the Agenda**
To promote a Session in the Agenda, navigate to the Session in Jomablue and scroll to the bottom of the Session configuration page. Here, you will see a field to add Promotion Text and a place to upload an image. See below for an example configuration:
****
#### **How it looks in the Agenda**
In the Agenda view, this promotional content is displayed below the Session information, with the image on the left and the text beside it. See below for an example of how the previous configuration looks in the Agenda:
****
#### **Recommendations and limitations**
When using this feature, we have a few recommendations:
- **Limit usage:** Use this feature sparingly for Sessions that truly need it. If all Sessions are promoted, the value of each promotion diminishes; focus on select Sessions to make them stand out.
- **Keep Text concise:** Limit the length of the Promotion Text to 150 characters. While more characters are supported, excessive text can clutter the Agenda view, especially on mobile devices.
- **Image Specifications:** The Promotion Image will always display as a square. The recommended size is 100x100 pixels. You can upload larger images, but they will be resized to fit the square format, while non-square images will be padded.
## Identify Sponsored Sessions in Session Views
Jomablue indicates sponsored Sessions across key Session views, allowing users to easily recognise sponsored content while browsing the schedule.
### Agenda View
Sponsored Sessions within this view display a Sponsored flag within the Session listing
****
### Grid View
Sponsored Sessions are visually distinguished by a dotted (barber-pole) style line at the bottom of the Session block. Non-sponsored Sessions use a solid line.
****
### List View
List view includes a Has Sponsor column. Sponsored Sessions display a tick in this column for quick identification.
****
To focus specifically on sponsored Sessions, use the **Only Sponsored** filter. This filters the list to show only Sessions with an assigned sponsor, and reveals a sortable Sponsor Name column so you can review and validate sponsor-to-session assignments at a glance, without needing to open each Session individually.
When a Session has multiple sponsors, the sort order prioritises by sponsor count first, then by sponsor name alphabetically.
**Notes:**
- Selecting a Session opens a pop-up view. If the Session is sponsored, a Sponsored flag is displayed.
- For information on how Sponsored Session attendee data is delivered to Vendors, see [View Attendee Data in a Lead Export](https://jomablue.bolddesk.com/kb/article/83/managing-vendors#view-attendee-data-in-a-lead-export "https://jomablue.bolddesk.com/kb/article/83/managing-vendors#view-attendee-data-in-a-lead-export") in Managing Vendors article.
## Session Attendance FAQ
#### **How does a Person check into a Session?**
Prior to the Session commencing, staff at the entrance will use Jomablue Session Check-In devices. As Attendees arrive, they will tap their Smart Badges onto the Check-In devices, recording their arrival time, which is then uploaded to Jomablue.
#### **Can a Person check out of a Session?**
The Jomablue Session Check-In devices can be configured to check attendees out of the session, too, which is useful for recording attendance for CPD/CPE accreditation.
#### Can session attendance be manually added or backdated after a Session has already occurred?
No. Session check-in is the source of truth for on-site attendance, so Jomablue does not support manually marking a Person as attended after the fact, even if you know they were there. Attendance can only come from check-in/check-out data captured at the time (see [Session Check-in using Jomablue Omnia App](https://support.jomablue.com/kb/article/492/session-check-in-using-jomablue-omnia-app "https://support.jomablue.com/kb/article/492/session-check-in-using-jomablue-omnia-app")) or, where applicable, from Inferred Sessions, see [Log Exits (Session Check Out)](https://support.jomablue.com/kb/article/149/managing-sessions#log-exits-%28session-check-out%29 "https://support.jomablue.com/kb/article/149/managing-sessions#log-exits-(session-check-out)") above and the [Inferred Sessions](https://support.jomablue.com/kb/article/138/inferred-sessions "https://support.jomablue.com/kb/article/138/inferred-sessions") article. If neither captured it, there's no way to add it retrospectively.
#### **Can I send content to a guest upon checking in to a Session?**
Yes! When an attendee checks in to a Session, you can configure Jomablue to send them an email, SMS, and/or a Card in their Event App Feed. For more information on how to configure this, see What is a Session Related Content?
## Referenced Articles
[Inferred Sessions](https://jomablue.bolddesk.com/kb/article/138/inferred-sessions)
[Session Canvases](https://jomablue.bolddesk.com/kb/article/145/session-canvases)
# Jomablue Privacy Policy
At Jomablue, we are committed to protecting your personal information and respecting your privacy. This Policy explains when and why we collect personal information from people who visit our website or use our products and services; how we use it; the conditions under which we may disclose it to others; and how we keep it secure.
By providing personal information to us (or allowing another person to do so on your behalf), you agree to the terms of this Policy regarding how we handle the personal information. You consent to our collection; use; and disclosure of your personal information as detailed in this Policy. If you do not agree with any part of this Policy, you must not provide your personal information to us, as this may affect the services we can provide.
In this Policy, the term ‘disclose’ includes transferring, sharing, sending, or otherwise making your information available or accessible to another person or entity.
We may occasionally change this Policy, so please check this page occasionally to ensure that you are happy with any changes. By using our website, products or services, you agree to be bound by this Policy.
### Who are we?
We are Jomablue Pty Ltd ACN 109 385 079 (in this Policy referred to as ‘Jomablue’, ‘we’, ‘ours’ or ‘us’), an Australian proprietary company limited by shares, with its registered office at Suite 73, 330 Wattle Street, Ultimo NSW 2007, Australia. We provide software to assist event organisers in delivering the event and allowing them to better understand how event attendees engage with these events.
### What personal information do we collect?
Generally, the personal information we collect is needed to facilitate your attendance and enhance your experience before, during and after an event organised by a third party. For example, we may collect details such as your name, professional address, and contact details (e.g., telephone number and email address) to provide you with a Smart Badge, which allows you to access the event and exchange your personal information with other delegates or exhibitors electronically. We may also collect details about the exhibitors you have chosen to provide your details to, the areas of the event you visit, and the times of your arrival and departure. We do not collect sensitive information such as religious beliefs or affiliations, criminal records, or health information. Any credit card information you provide as part of a purchase is collected by a third party, not by us.
### How do we collect personal information?
We collect personal information directly from you or from someone providing it on your behalf. This information is usually collected when you buy a ticket or register to attend an event or when you request information from us.
In some cases, we may need to collect your personal information from a third party, such as when you register for an event with a third party. Where this occurs, we will assume you have consented to your personal information being collected and handled in accordance with this Policy. If you become aware that your personal information has been provided to us by another person without your consent, please let us know immediately.
### How do we use personal information?
We mainly use your personal information to facilitate the provision of goods and services concerning your attendance at an event, both before and after the event. We may also use your personal information for the following purposes:
- Regulatory reporting and compliance where that is integral to your attendance at the event
- Developing, improving, and marketing our products and services to event organisers
- Conducting research and gauging customer engagement and participation in event activities
- Analysing trends in attendance at events
- Other purposes required by law (e.g. prevent a threat to life, health, or safety)
We are only allowed to store your personal information for as long as necessary having regard to the purpose for which it was collected. Therefore, we may delete or destroy your personal information after a reasonable time. If you have not used our services for some time, you may be required to re-enter or provide your personal information so that we can continue to deliver our services or those services of a third-party organiser.
### Is personal information disclosed to third parties?
Your personal information may be disclosed by us to third parties in the following circumstances:
- In each of the circumstances set out in the previous section ‘How do we use personal information?’
- As permitted or required by law
- To third-party suppliers of IT-based solutions that assist us in providing services to you (e.g., email and SMS delivery engines)
- To third parties for the purpose of analysing trends in participation in conferences, seminars, and exhibitions
Aside from these situations, we will not disclose your personal information without your consent, unless we reasonably believe such disclosure is necessary to prevent a threat to life, health, or safety, or for certain actions to be undertaken by an enforcement body (e.g., prevention or punishment of criminal offences). Disclosure may also be authorised or required by law or disclosure or permitted under applicable privacy laws.
### Third-party websites
Our website may contain links to other websites run by other organisations. This Policy only applies to our website, products, and services‚ so we encourage you to read the privacy statements on the other websites you visit. We cannot be held responsible for the privacy policies and practices of other sites, even if you access them using links from our website.
In addition, if you reached our website through a third-party site, we are not responsible for the privacy policies and practices of the owners and operators of that third-party website, and we recommend reviewing their privacy policies.
### Transborder Data Flows
As part of the products and services offered through this website, the information you provide may be transferred to our servers located in Australia and possibly to other countries both inside and outside the European Union (EU). These countries may not have similar data protection laws to the EU. By submitting your personal information, you consent to this transfer, storage, or processing. If we transfer your information outside the EU in this way, we will take steps to ensure that appropriate security measures are in place to protect your privacy rights as outlined in this Policy. If you have any objections to your personal information being disclosed to overseas recipients, please let us know, noting that this may affect our ability to provide our products and services to you.
### Information Tracking
We use Cookies, Analytics, Web Beacons/GIFs, and Third-Party Tracking to assist us in providing a better service to you and future customers. Cookies save data about individual visitors to our website, such as the visitor’s name, user name, pages visited, and preferences chosen. When the visitor revisits the website, we may recognise the visitor through the cookie.
You can remove persistent cookies by following the directions provided in your Internet browser's ‘help’ file.
### Security of Information
We have implemented various physical, electronic, and managerial security procedures in order to protect against unauthorised access, modification, disclosure, and interference. We regularly review these security and encryption technologies and conduct ‘penetration tests’ to ensure the safety of your personal information.
Additionally, we regularly educate our staff about their responsibilities regarding the safe and secure collection, storage, and destruction of your personal information and their compliance with the relevant privacy laws.
### Access to and correction of Personal Information
Subject to any exceptions under applicable privacy laws, we invite you to access any personal information we hold about you. If that information is inaccurate, incomplete, outdated, or irrelevant, you may request a correction within a reasonable timeframe. We reserve the right to confirm the identity of the person seeking access or correction to the personal information. If we deny access or correction, we will provide you with the reason for such denial. If you wish to access or see the personal information held by us about you, please refer to the **Feedback/Complaints/Contact** section below.
You must always provide accurate information and you agree to update it when necessary. Additionally, you also agree that the personal information submitted to us is correct. You have the right to ask for a copy of the information we hold about you. We may charge AUD180 for each information request to cover our costs in providing you with details of the information we hold about you.
### Your choices
You have a choice about whether or not you wish to receive information from us. If you do not want to receive direct marketing communications from us about our products and services, then you can select your choices by ticking the relevant boxes located on the form/s on which we collect your information.
We will not contact you for marketing purposes by email, phone, or text message unless you have given your prior consent. We will not contact you for marketing purposes by post if you have indicated that you do not wish to be contacted. You can change your marketing preferences at any time by contacting us by email (please see the **Feedback/Complaints/Contact** section below).
### Changes to our Policy
From time to time it may be necessary for us to review and revise this Policy. We reserve the right to change our Policy and any revised version will be posted on our website.
### Feedback/Complaints/Contact
Email us at privacy@jomablue.com or write to the attention of the Privacy Officer at P.O. Box 174, Annandale, NSW, 2028, Australia.
# Data Security Review Requests
At Jomablue, we invest heavily in providing a secure product for our customers. This investment begins the moment we start working on a feature, using a ‘secure by design’ methodology. This approach ensures that data security is at the front of our processes and not an afterthought.
While many of the things we do to deliver a secure environment are published in this article, there are additional steps we take that are considered confidential and/or commercially sensitive, which we do not publicly disclose.
### Request a Security Review from Jomablue
If you wish Jomablue to assist you with a security review, we ask you to be aware we follow a process to manage the engagement.
1. Any requests for engagement around security reviews are to be sent to privacy@jomablue.com. If Jomablue team members receive a request directly they are trained to forward requests to the Privacy team.
2. Team members outside our Data Protection & Privacy requests cannot commit to timeframes for completing any review requests.
3. Engagement with security reviews will only be undertaken with the end customer or final data owner, not any intermediary or agencies. Communication must be directly with security review personnel rather than via other parties.
4. Upon receipt of a security questionnaire and contact details of the end customer security reviewer, we will confirm receipt of the request via email.
5. Customers requesting a security review will be provided with a Jomablue-issued mutual NDA.
6. Jomablue will provide a comprehensive 120-point Q&A document at no charge.
7. Any requirement to provide custom responses will be a paid engagement at AUD240.00 (excluding GST) per hour with a minimum of 2 hours, billed on actual hours spent on engagement. Contract values greater than AUD20,000.00 per annum will receive 3 consulting hours FOC. Custom responses must be requested earlier than 1 month prior to the instance/subscription live date.
8. If the information requested is considered by our team to be sensitive or confidential, we may require a secure transfer method (rather than a plain text email). In these cases, we will ask for a PGP key to be issued by the security reviewer within the receiving organisation. This is at our discretion to ask for a PGP key. This is the only method of secure transfer we support.
**Notes:**
Penetration tests commissioned by Jomablue are run by external consultants and performed regularly. Extracts or a summary may be provided in some circumstances at the discretion of our team.
1. The Table of Contents from internal Jomablue articles may be shared in some cases, however complete internal documents are not.
2. PGP is an industry-standard for signing and encrypting sensitive data. Jomablue requires customers PGP public key in order to share sensitive or corporate information.
3. Password protection is not the same as encryption using PGP keys. Passwords can easily be shared and distributed without consideration. PGP provides protection of the files in transit as well as defines receipt and ownership of the contents. From a trusted perspective, this provides Jomablue with a single person responsible within our customers' organisation for the protection of the data contained within.Additionally, the PGP must be created from the customer email domain using a non-generic account. For example, max.piper@acme.com will be accepted; hello@acme.com or max@gmail.com won’t be accepted.
If you are sharing any sensitive data, such as lists of data with Jomablue, we strongly encourage the use of PGP.
Our Public Key can be found here: [https://keys.openpgp.org/search?q=privacy%40jomablue.com](https://keys.openpgp.org/search?q=privacy%40jomablue.com)
# Touchpoints
Touchpoints are effective tools for delivering content, facilitating call-to-actions, providing entry to competitions, and generating interactions with Attendees. They can be stand-alone units or statically mounted in strategic locations around your Exhibition space, or attached to Vendor/Exhibition stands. Here are some typical use cases for Touchpoints:
- Sending an SMS link to download the event app at the information counter
- Sending an SMS or email with a link to view an event map
- Offering a tap-to-subscribe for the event or company newsletter
- Providing a tap-to-download function for content within your exhibition hall or attached to a specific Vendor for Vendor-related information
- Enabling a tap-to-enter draw for prizes or competitions
- Providing a tap-to-donate option for select charities
- Sending Session-Related Content to attendees after a Session
- Facilitating the tracking of Item Collection
Free-standing or static Touchpoints encourage attendees' interaction with your event, helping you gain insights into individual attendees' journeys. They improve insights into your event for follow-up sales and marketing strategies and add value for attendees by extending the lifespan of event content beyond the event itself and providing additional ways to engage.
Touchpoints attached to Vendor/Exhibition stands provide an inviting and easy-to-use method of delivering Vendor-related content.
### Build Features
Features include:
- Self-contained unit
- Ability to integrate into built structures, such as countertops, walls, benches, and coffee tables
- Can be attached to fixtures, walls, signage, or be handheld
- The device must be plugged in to operate
- Front-facing Smart Badge reader with animations and icons indicating where the Smart Badge should be tapped
- Attention-grabbing screen elements designed to attract users from afar
## General and Vendor-Specific Content
Touchpoints serve as an excellent means to offer additional content to attendees. After tapping their Smart Badge on a Touchpoint, attendees can receive SMS messages, Emails, or Event App Cards with relevant content.
Content Download can be used in a Static/Freestanding configuration (for general event-related content) or attached to Vendor/Exhibitor stalls (for Vendor-specific content).
Some screenshots of the Touchpoint screens can be seen below:
****
## Session Related Content
One of the most valuable uses of Touchpoints is delivering content related to sessions. This content can be delivered via email, SMS, or Cards provided through a person's Feed in the Event App. Touchpoint content captures deeper engagement from attendees, providing rich data points throughout their journey.
To encourage demand for content, we recommend the following:
- Ensure free-standing Touchpoints are well-advertised with clear instructions on how to tap a badge to receive content
- Include a holding slide from each speaker, indicating to the audience that content is available for their session
- Ensure staff delivering content via Touchpoints are vocal and visible to the audience during and after the session
- Inform attendees via SMS upon entering the first session of the day that they will receive related content in their app feed. All related content will be sent to their feed upon entry into the relevant sessions.
**Note:**If you are not using the Live Engagement App, we recommend delivering related content via Email upon session entry.
## Item Collection with Touchpoints
- Touchpoints can also facilitate physical item collection at your event. Our Item Collection allows for the following:
- Monitoring and controlling inventory levels, such as T-shirts and tote bags
- Ensuring only entitled attendees receive their gifts
- Preventing 'double-dipping' through real-time updates of a person's record after collection
- Improving budget allocation and reducing waste through accurate stock level monitoring
To set up Touchpoint devices for item collection, relevant information must be included in the event data (e.g., T-shirt sizes for each attendee record and the number of 'gifts' a particular attendee is entitled to)
## Touchpoint Hardware
#### Hardware Specifications
The Touchpoint devices are similar in size to an iPad mini, lightweight, and can be mounted flush against a wall or stand or angled.
#### Device Size
212mm High x 122mm Wide x 9.9mm thick
#### Screen Size
172 x 106mm
#### Weight
350 grams
#### Smart Badge Reader Position
Bottom of screen
#### Power
Touchpoints must be connected to a power source to operate. Ensure each device has continuous access to power for the full duration of your event.
#### Mounting Options
- Flush against the surface using double-sided tape
- With a universal tablet holder or other mounting solutions
- Connect the Touchpoint to a power source for the duration of use
**Note:**
- The back of the device must not be flush against conductive materials such as metals or alloys, as this can interfere with the Smart Badge reader
- Because the device must stay connected to power, plan cable management as part of your mounting solution so the power cable can run neatly to the device and remain connected throughout use. The mounting solution should also allow for the removal and replacement of the device if needed. For example, by removing and replacing the double-sided tape.
## Examples of Touchpoints
****
## Touchpoint configuration
Touchpoints can be configured to optionally send an SMS, email, or insert a card into the Feed of their Community. Additionally, when a person taps their badge, the interaction date and time are recorded, which can be used for real-time engagement scoring or post-event reporting.
#### **Some Touchpoint use cases include:**
- Tap your badge, and a business analyst will give you a call tomorrow
- Tap to subscribe to our weekly newsletter
- Tap if you would like to receive more post-event information
- Get a 90-day free trial by tapping your badge
- Tap to get our latest white paper and case study
### Configure a Touchpoint
To configure your Touchpoints, follow the steps below:
1. Log in to Jomablue and navigate to **Touchpoints/Card Templates**
2. **Click New Touchpoint to create a new Touchpoint**
**Required Fields**
The minimum required fields for configuring a Touchpoint are:
- **Name** - This is the internal label for the Touchpoint and is not customer-facing (maximum of 30 characters)
- **Title:** Displayed on the device (maximum of 30 characters)
- **Description:**Displayed on the device (maximum of 170 characters)
- **Success Message:** Displayed after the badge is tapped (maximum of 80 characters)
- **Background Colour:**Must be a hex value and must contrast with white text
**Additional Fields**
The following fields are optional:
- **Image:** Recommended size is 700 x 700 px, in a square aspect ratio (png/jpg image)
- **Card ID:** Select the card template to insert upon tapping
- **SMS Content ID:** select the SMS template to send upon tapping
- **Email Content ID:** select the email template to send upon tapping
**Important to note:**
- To select a Card ID, SMS Content ID, or Email Content ID, you must first create a Card Template, SMS Template, or Email Template, respectively
- The font on each Touchpoint is not currently customisable (including colour and style); all text is left-justified
- Touchpoints feature on-screen elements designed to catch the attention of passersby and guide them to tap their Smart Badge in the correct location. The corners of the device flash and change colour to draw attention from a distance, while the Smart Badge read zone features a pulsing animated circle that indicates where the device should be tapped. Both of these attention-grabbing features cycle through a predetermined colour palette.
# Custom Fields
Custom Fields allow you to collect information from attendees beyond Jomablue's standard fields. They can be used across registration forms, exports, campaigns, and more.
The standard fields in Jomablue include:
- First Name
- Last Name
- Job Title
- Company
- Email
- Mobile
Custom Fields are additional questions or data points you can add beyond the standard fields listed above. Examples of Custom Fields might include:
- Dietary Requirements
- Postcode
- State
- Country
- Office Phone Number
- Marketing Campaign ID
Jomablue accepts Custom Fields through Jomablue Registration, bulk import, or manual entry.
When using the **Select** type, there are a few commonly used options you can choose from:
- Country
- Australian States
- Dietary Requirements
- Yes/No
## Plan your Custom Fields
Custom Fields are a powerful tool for collecting and structuring data from your attendees. To maximise their effectiveness, it is important to carefully plan how you will use them before creating them in the Portal.
You have the option to select which custom fields are allocated to a specific product. For example, in a Student Admission, you may want to request a Student Number; however, this custom field would not apply to a Delegate Admission. Additionally, you could remove the Title and Company fields from the Student Admission.
#### Clean, Structured Data
One of the key considerations when planning Custom Fields is ensuring that the data collected is as structured as possible. Structured data simplifies the event planning process and makes the data collected at the end of the event more meaningful.
When structuring your data, it’s vital to keep it clean and consistent, especially if you plan to feed the data collected by Jomablue back into your organisation's CRM or similar system. We recommend structuring your Custom Fields to align with your CRM for easy importing and interpretation.
Wherever possible, use single selection fields or radio selectors, and only resort to free text entry where absolutely necessary. Jomablue supports an "Other" option with single selection fields, which is advisable for fields where most attendees will fall into one of a few defined options.
#### Event Logistics Fields
Custom Fields can be used to gather and organise data related to event logistics. Examples of Event Logistics-related fields include:
- **Special Dietary Requirements**: A Custom Field can be used to collect attendees’ dietary requirements
- **Accessibility Requirements**: A Custom Field can gather information on attendees’ accessibility requirements, such as spatial/physical access or hearing induction loop requirements
- **State/Country**: A Custom Field can collect information regarding where your Attendees are coming from to better accommodate them
- **Item collection**: If attendees are entitled to receive a t-shirt, this field can present a list of styles, sizes, and colours for selection
#### Sales and Marketing Fields
Custom Fields can also capture data useful for your Sales and Marketing teams to better target attendees with relevant materials. These fields can be used to capture information about Attendees, including:
- **Areas of Interest**: Custom Fields can help gather information about Attendees’ interests during the registration process
- **Industry, Organisation Size, Employment Level, etc.**: Custom Fields can collect information related to Attendees’ organisations to create tailored sales and marketing content
#### Intelligent Networking Fields
Custom Fields can be configured to enhance the Intelligent Networking algorithm within the Networking feature of the Event App. For example, a Custom Field asking attendees to select their areas of professional interest can help the algorithm recommend relevant connections to each attendee during the event.
For additional information, please see the article: [Community Networking and Messaging](https://support.jomablue.com/kb/article/133/community-networking-and-messaging).
###
Define Custom Fields
While you can add Custom Fields in Jomablue via Registration or bulk import without defining them, defining Custom Fields allows for more robust interaction. Once a Custom Field is defined, you can:
- Make it editable by Jomablue users
- Filter Campaigns for specific groups of attendees
- Include it in Vendor Lead Exports
- Add pre-defined values to each field
#### Create a new Custom Field or review an existing Custom Field:
1. Navigate to **Settings** within the Event Configuration group in the left navigation pane
2. Go to the **Custom Fields** tab and select the **New Custom Field Definition** button to add a new Custom Field, or select an existing Custom Field to review
3. Follow the guide to populate the definition
#### Copy fields from another event
This option allows you to replicate the settings of an existing Custom Field definition from another event in your instance. Click to choose a definition to add to the current event.
**Note:** If a custom field has label sets configured, those can also be copied across events. See Custom Field Aliasing below for details.
#### Attributes of Custom Fields
**Key**
An identifier for the Custom Field. It can't contain spaces or special characters. (e.g., job\_role or dietary\_requirements). This field is limited to 191 characters in length.
Custom Field keys must be unique and must not match the keys or names of built-in system fields (such as First Name, Last Name, Email, or Company). This safeguard applies across all methods of creating, updating, or importing Custom Fields and prevents custom data from overwriting system-managed fields.
**Label**
This is what will be displayed to users in Jomablue (e.g., Job Role or Dietary Requirements). This field is also limited to 191 characters in length.
**Validation Rules**
By default, no validation is applied (blank). If you want to restrict what a person can enter into the field, you can add one or many validation rules. For additional information, see the **Creating Validation Rules for Custom Fields** section below.
**Available in Vendor Lead Export**
If set to Yes, this Custom Field will be included in Vendor Lead Exports. This is useful for fields like State or Postcode, assuming the data was collected initially.
**Allow the field to be edited**
If set to Yes, a Jomablue user can see and edit the Custom Field values on a Person record. If set to No, the Custom Field will be read-only.
**Display by default and require this field in the portal person record?**
This option indicates whether the field is required for portal users (not paid Registration pages).
**Type**
This determines what kind of Custom Field it is. Options include:
- Short answer
Enables text input
- Radio Select
Recommended only for limited values (e.g., Yes/No; Option 1/Option 2/Option 3).
- Checkboxes
Allows multi check values
- Dropdown Select
Recommended if more than three values to be offered. This can be used for a list selection, such as dietary requirements (e.g., Vegetarian, Pescatarian, Gluten Free, Dairy Free)
**Field Options**
This is accessible for Radio, Select Values and Checkbox type Custom Fields.
1. Select **Edit Values**, and a dialogue box will pop up
2. You can click on **Generate with AI** button to produce a list of values based on your Label
3. Press on **Prompt Again?** button if you want to generate a new list, or you can manually add to the value list. Press **Save**
**Note:** Custom Field Aliasing allows you to control what a registrant sees on the form versus what is saved to their record. This is available for custom fields with pre-defined values. See Custom Field Aliasing below.
**Default Value**
Available for Radio, Select Value, and Checkbox type Custom Fields. Select one value from your options to set a default for users. For example, you may have a Select field for "Country" and you could set the Default Value to the country of the event as it's likely most of your audience will be selecting this anyway.
**Show in the list of merge tags available in the email or SMS template editors**
This setting determines whether a Custom Field will be available as a Merge Tag in the Email Template Editor.
## Custom Field Aliasing
Custom Field Value Aliasing allows you to separate what a person registering sees on a form from what is saved to their record in Jomablue. For any custom field with pre-defined values (Radio, Select, or Checkbox types), you can define one or more sets of display labels, each of which maps to an underlying base value that is stored in the system.
This is particularly useful for multilingual events, international audiences, or any situation where you want to standardise the data saved in the system, regardless of how options are presented to registrants. For example, without aliasing, a German-language registration form might save "Deutschland" to the person record. With aliasing, the same field can display "Deutschland" to the registrant while saving the standardised value "Germany" to the system, keeping your data consistent regardless of which language the form is presented in.
**Note:** Existing custom fields that do not have aliasing configured are not affected and will continue to behave as before.
### Label Sets
Before using label sets, it helps to understand the two key terms:
- Base value - The standardised value that Jomablue stores on the person record. It is what your system, CRM, or exports will always receive, regardless of what the registrant sees on the form.
- Label - The display version of a base value shown to the registrant during registration.
A label set is a named collection of display labels, where each label corresponds to one of the field's base values. A single custom field can have multiple label sets. For example, "UK Sizing," "EU Sizing," and "US Sizing" for a shoe size field, each presenting the same underlying base values in a different way to different audiences, while saving a single standardised value to the system.
When the person submits the form, the base value is saved to their record, not the label they selected. The label is what they see on the form and on their confirmation page.
### Custom Field Builder
The Custom Field Builder is a visual editor available in **Event Configuration > Custom Fields**. It displays your Field's base values and label sets in a table layout, allowing you to enter and review display labels for each value across multiple label sets in one view.
The text-based custom field editor remains available alongside the builder. Both views reflect the same field data, changes made in one are reflected in the other. The text editor is particularly useful for copying large sets of values across events. See Copy Fields from Another Event above for details.
#### Configure Label Sets
The Custom Field Builder displays your field's base values in rows and your label sets in columns. For each base value, enter the corresponding display label in the column for each label set.
To configure label sets for a custom field with pre-defined values:
1. Navigate to **Event Configuration > Settings > Custom Fields**
2. Select the Custom Field you want to configure, or create a new one with pre-defined values (Radio, Select, or Checkbox type)
3. Open the Custom Field Builder for that field
4. For each base value in your field, enter the display label you want to show for each label set in the corresponding column
5. Name each Label Set clearly so it is easy to identify when configuring registration forms
6. Press **Save**
**Note:** When duplicating an Event, any Custom Field Aliases (label sets) configured for Custom Fields in that Event are duplicated along with the Custom Fields themselves. The duplicated Event will retain the same label sets and base value mappings as the original, so there is no need to reconfigure aliases after duplication.
#### Apply a Label Set to a Registration Site
When a Custom Field with Label Sets is added to a Registration Site, a Label Set dropdown appears alongside the field in the form configuration. This allows you to select which Label Set to display to registrants. Different Admissions within the same event can use different Label Sets for the same Custom Field. For example, one Admission displaying Deutschland and another displaying Germany, while both save the same standardised base value to the system.
For step-by-step instructions on adding fields to a Registration Site and configuring it, see the article: Registration Sites.
#### Delete Label Sets
A label set is considered in use if it is currently applied to a Registration Site, or if registrant responses have already been recorded against it. If you attempt to delete a label set or value that is in use, the system will notify you that the deletion cannot proceed, or prompt you to confirm before continuing, depending on the context.
If responses have already been recorded using a label, deleting it will not remove those responses; the base value will remain on the person record. However, the label will no longer be available for display on registration forms.
### AI-Generated Custom Field Values
You can use AI to generate suggested values when creating or editing a Radio select, Checkboxes, and Dropdown Select custom field type. To do this:
1. Select Custom Field Type of **Radio Select, Checkboxes,** or **Dropdown Select**
2. In Field Options click **Edit Values**
3. The Values overlay will be displayed. Select **Generate with AI**to generate a new set of values.
4. Review and manually refine the list to your liking, or select **Prompt Again**to let AI generate a different set of values
5. Once satisfied with the list, click **Save**
**Note:**OpenAI integration and the use of this feature are available to all customers but can be disabled per instance for data privacy reasons.
### Set Fallback Values for Custom Fields
When personalising your campaign with merge tags, it's wise to set default values for recipients who have not provided data (values) for a custom field.
**Setting Fallback Values**
1. Navigate to **Settings > Custom Fields Tab**
2. Select the **Custom Field**
3. Add the fallback value
****
**Example of Fallback Values:**
Consider two different people receiving an SMS. In this case, the Merged field was "Role Type," with a fallback value of "people".
James had a Role Type of "Marketers"
Sarah did not have a value set, so the fallback was used:
### Create Validation Rules for Custom Fields
Custom Fields can have specific validation applied to ensure that Paid Registration users enter the desired values during activation.
Examples include:
- Limiting a Custom Field called "Member Number" to 11 numeric characters only
- Asking for a link to a LinkedIn profile and validating it to ensure it is a valid URL
- Ensuring a valid email address is entered in the "Alternate Email" field
#### Add Validation
Validation is added under **Event Configuration > Settings > Custom Fields**.
A blank field means no validation rules are being applied.
****
**Validation Rules**
Validation rules can be applied individually or combined in the Validation Rules field. If combined, they must be separated by a pipe (|). For example: “between:1,11|numeric”
To use validation rules, simply paste the validation rule (e.g., "alpha" or "alpha\_dash" into the Validation Rules field of the Custom Field.
**Available validation rules:**
- alpha -****Must only contain alphabetic characters.
- alpha\_num - Must contain alphabetic characters or numbers (no spaces or special characters).
- alpha\_dash - Must contain alphabetic characters, numbers, dashes or underscores.
- between:x,y - Must have a numeric value within a specified range between values x and y. (e.g., ‘between:1,11’)
- digits:x - Must be numeric and have the specified number of digits defined by the value x. (e.g., 'digits:11')
- email - Must be a valid email address.
- max:x - Must not exceed the specified length value x. (e.g., ‘max:11’)
- max\_value:x - Must not exceed the specified maximum value x.(e.g., ‘max\_value:500’).
- min:x - Must not be less than the specified length value x. (e.g., ‘min:3’)
- min\_value:x - Must not be less than the specified value x. (e.g., ‘min:100’)
- numeric - Must only consist of numbers.
- url - Must be a valid URL.
### Country and State Custom Fields
Custom fields can be defined with a Type of ‘Country’ and ‘State’ (see **Attributes of Custom Fields** section above). These fields are linked and used in Registration to reveal a State selection field if the selected Country has states. For example, when you select ‘Australia’, a dropdown will offer New South Wales; Victoria, etc. The registrant will see the Country and State selections in detail. The data for Country will be saved to the person record as [ISO-3166](https://en.wikipedia.org/wiki/ISO_3166 "https://en.wikipedia.org/wiki/ISO_3166") (including subsections). For example, Country is a 2-ch code as shown below.
To use these field types, first create a new Custom Field and apply the Country type, and then another one using the State type. The State Custom field must be linked to the Country field).
Next, add these fields to an Admission (recommend adding the State field directly after the Country field).
When the registration form is being populated by the registrant, initially only the Country field will be visible. Once a country is selected that has states associated with it, the State field will be displayed offering the states of that country.
**Note**: After the registration process is complete and the person record has been created, these fields are not longer linked. If the Custom Field(s) is enabled for editing, values should be updated with the relevant ISO codes.
## Copy Custom Fields
If you have multiple Events, you may have Custom Fields that are common to more than one Event. Rather than re-creating each Custom Field in every Event, you're able to copy a Custom Field from one Event to another.
To copy a Custom Field from another Event:
1. Create a new Custom Field in the target Event
2. Use the **Copy field from another event** drop-down menu
3. Select the field you wish to use, and it will instantly fill out the Custom Field information
4. Click **Save** to save your work
## Custom Field Event Presets
Custom Fields can be exported as an Event Preset, allowing you to create new events and replicate pre-defined Custom Fields.
Within an event containing the defined Custom Fields, go to **Settings > Custom Fields**, then click the **Export Event Preset** button on the upper right hand of the page.
When applying a Custom Field Event Preset during event creation, you can deselect any Custom Fields you do not wish to import.
## Update Custom Field Values after registration launch
During the active sales period for your event, you may want to update some Custom Field values (this option is available in a dropdown box). This usually occurs when you notice that a portion of your audience is selecting "other" options during registrations, and you want to gain more insight into their preferences.
**Pro Tip:**To view a breakdown of responses in a friendly pie chart, navigate to **Insights > Audience.**
#### **Can I remove values?**
While it is technically possible to remove values, we do not recommend it. Values may have already been submitted by people when activating their Registrations. If a person record contains a removed value, then that field will appear blank.
We always suggest not removing values but rather adding values and refining the list for the next event you launch.
#### **Can I add values?**
Yes, adding values has no impact on existing or new Registration Activation. Once new values are added, there will be an available option for Registration Activation from that point forward.
**Note**: Field Labels, Field Descriptions, the order of fields and the inclusion of fields or not (set under Admissions) can be updated at any time without any impact on users.
## Delete a Custom Field Definition
A Custom Field definition can be deleted if it has not been applied to other records or functions within Jomablue. To delete a Custom Field:
1. Select **Settings** in the left navigation menu
2. Select the **Custom Fields** tab
3. Click the **Delete** button on the right side of the relevant field
****
If the Custom Field has been applied to a person record or functionality, a pop-up will appear, indicating how it has been applied. To proceed with the deletion, you must resolve each relationship prevention, which may include:
- Applied to a CX Badge Layout
- Applied to a Smart Badge or Kiosk Badge Layout
- Applied to a Person record
- Used in a Registration Admission
- Used in an Engagement Scoring segment
If none of these relationships exist, a confirmation popup will appear. The Custom Field will be deleted upon selecting the **Delete** button on the pop-up.
**Note:** To delete a custom field from a person record, see the article: [Importing People](https://support.jomablue.com/kb/article/69/importing-people) under the section **Delete a Custom field**.
## Order Custom Fields (track marketing campaigns)
Jomablue supports the use of tracking parameters in both Online Free Registration and Online Paid Registration. Using these parameters allows you to identify the source of each Registration/Order, which can help assess the effectiveness of your marketing campaigns, sales representatives, and more. This is achieved via invisible fields in an Admission named 'Order Custom Field (hidden)'.
This is the result of a registration site having URL parameters. For example, **?referrer=ref\_id&uniqueid=unique\_id\_value**, the Registration Form can be configured to create:
- the Custom field **referrer** with the value of the **ref\_id**
- the Custom field **uniqueid with the value of the unique\_id\_value**
To map URL parameters to custom fields, the key of the URL parameter needs to be entered into the **Order Custom Field** (hidden) field.
****
In the above example, the **referrer** and **uniqueid** fields have been added, so values for those fields in the registration URL will map to Custom Fields with matching keys and values in the Person record.
For additional information, please see the article: [Managing Campaigns](https://support.jomablue.com/kb/article/135/managing-campaigns).
**Note**:
- If multiple URL parameters with identical keys are in a registration site URL, multiple Custom Fields will be created in the Person Record
- If a URL parameter with an empty value is in the registration site URL, no Custom Field will be created
- If a URL parameter does not have a matching Order Custom Field (hidden) field, it won't be mapped to a Custom Field on a Person record. This can be leveraged to map certain Order Custom Fields to People Custom Fields, depending on which Admission type is registered.
There is no need to define the custom fields (in portal settings) when doing marketing parameters to custom field mapping.
### Add 'Order Custom Field' to Custom Field Mapping
When registering, Order Custom Fields can be directly passed to Custom Fields on a Person record via invisible fields in an Admission.
For example, if a registration site has URL parameters (e.g., ?edm=edm01&sales\_rep=rep02), the Registration Form can be configured to create Custom Fields ‘edm=edm01’ and ’sales\_rep=rep02’.
#### **Configuration**
A field is available for addition to a Registration form: "Order Custom Field (hidden)". To map URL parameters to custom fields, the key of the URL parameter must be entered into the **Order Custom Field (hidden)** field.
For example, if “edm” and “sales\_rep” tracking fields have been added to the registration URL, the values for those fields will map to Custom Fields with matching keys and values in the Person record.
#### **Features of Custom Field Mapping**
- If multiple URL parameters with identical keys are present in a registration site URL, multiple Custom Fields will be created in the Person Record.
- If a URL parameter has an empty value in the registration site URL, no Custom Field will be created.
- If a URL parameter does not have a matching Order Custom Field (hidden) field, it won't be mapped to a Custom Field on a Person record. This can be leveraged to map certain Order Custom Fields to People Custom Fields based on the Admission type being registered.
## Requirements when using the People Import Tool
When using the Import Tool, Custom Fields will appear in the dropdown menu in two groups:
1. **Pre-defined**: Fields defined under Settings > Custom Fields
2. **Existing but not pre-defined**: These are a result of previous imports (see below)
You can create a new custom field key during the import process (using letters, numbers and underscores only). These will be categorised as “Existing but not pre-defined” fields. You may define these later, but it is not mandatory.
During import, Custom Field keys are validated against built-in system fields. If a key matches a system field, it cannot be created or updated as a Custom Field.
To remove a custom field from a person’s record, see the article: [Managing People](https://support.jomablue.com/kb/article/70/managing-people).
**Note**: Custom Field definition is not a required setting. Custom Fields can be added to Jomablue via Registration, or bulk import without defining them.
## Referenced articles
[Community Networking and Messaging](https://support.jomablue.com/kb/article/133/community-networking-and-messaging)
[Importing People](https://support.jomablue.com/kb/article/69/importing-people)
[Managing Campaigns](https://support.jomablue.com/kb/article/135/managing-campaigns)
[Importing People](https://support.jomablue.com/kb/article/69/importing-people)
# Setting up Zoom Meetings to Live Stream
## User Requirements
- Jomablue Enterprise with Community Plus edition
- Active Zoom account (with support for Live Streaming)
- The Host/ Co-hosts has a Zoom Webinar add-on
- Zoom desktop client version 4.0 or higher on PC or a Mac
- Zoom mobile client version 5.4.0 or higher on Android or iOS
- Custom Live Streaming service is enabled on your Zoom account
You can live stream your content via Zoom and streaming service into a Jomablue Community Plus site. Here is the short guide on how to set up Zoom to live stream your session.
## How to live stream your Zoom meeting
Note: The following steps need to only to be completed once:
1. Sign in to your organisation’s Zoom account through a web browser (https://zoom.us/signin) and click settings and then click In Meeting (Advanced).
2. Ensure “Custom Live Streaming Service” is activated.
Note: The following steps need to be completed for each session:
Note: If you are unable to locate this setting, it may mean you are not an admin in Zoom. Please contact your organisation’s IT Department to enable this setting for you.
1. Schedule the Zoom meeting 30 minutes prior to the actual scheduled session start time.
2. As the meeting host, select More > “Live on Custom Live Streaming Service.”
3. There are two options to enter the live streaming details:
- Option 1: Enter the Details as provided, and press Go Live
- Streaming URL: (A rtmp:// address – provided by Jomablue).
- Streaming Key: (supplied by Jomablue).
- Live streaming page URL: (this link will take to the Client's Community Page).
- Note: Jomablue will be providing these details to the client in advance.
- Option 2: Enter the details in the backend of Zoom by following the steps below:
- Click into your Zoom meeting.
- Scroll down to the end and click ‘Configure Custom Streaming Service’.
- Enter the following stream details (no need required to tick any checkboxes).
4. Please wait while Zoom prepares your live stream.
5. You will see a confirmation page appear and zoom meeting will now indicate it is live streaming. You can see the status and control the stream from your zoom meeting window.
6. Click save to save your live streaming settings.
## Troubleshooting
- In-case the details are entered incorrectly - the user will need to log in to the Zoom Web Portal (https://us02web.zoom.us/signin). Click Meetings, select the relevant Meeting, scroll down to Live Streaming and click edit to re-enter the correct streaming details.
# Release 9.47.0
## New Feature
### Instance Level Ingest API
A new Instance Level Ingest API is now available, providing a single ingest point for third-party systems to send People records into Jomablue.
This API uses a unique identifier within each request to automatically route people records to the correct event within the instance. The Global Ingest API is configured at the instance level under Settings and can only be managed by users with the appropriate role.
This is a new way for Jomablue to programmatically accept new people records. It is configurable to align with the data structures you already use, meaning your systems can send webhook or API requests without reshaping data beforehand. Jomablue handles the mapping so incoming data matches the required structure.
****
### Program and Member Support for CRM Campaigns
Jomablue now supports managing CRM campaign data directly in the platform through a new feature called Programs.
Instead of relying on custom fields, Jomablue can now store Salesforce Campaign IDs and Campaign Member Statuses. These member statuses can be mapped to operational event interactions such as Interacted Day or Session Attended. This significantly broadens support for enterprise-level campaign data structures.
The feature is called Programs because Jomablue already uses the term Campaigns for email and SMS communications. In many marketing stacks, Programs and Campaigns are used interchangeably, such as in Marketo, which refers to campaigns as Programs.
Programs can now also be defined directly within the Portal.
****
****
### Updates API - Retrieve Event Data from Jomablue
A new Updates API has been introduced to make it easier to retrieve data from Jomablue and integrate it with your own systems. This API supports accessing data such as People, Sessions, Leads, and Vendors.
The Updates API includes portal-based mapping, allowing you to map Jomablue fields to your preferred data structure. For example, a field like ‘first\_name’ can be mapped to ‘First’ if that matches your internal system. With this approach, Jomablue adapts data to your requirements, reducing the effort needed on your side to integrate.
API documentation for this feature will be published in the Jomablue API documentation.
An Updates API Endpoints tab has been added to the Integrations section within Events:
****
Individual update endpoints can have any of the 5 endpoint types applied:
****
Mapping can be added to an endpoint type, with basic validation to ensure the mapping format is acceptable:
****
A new tab has also been added to the instance-level organisation settings, where integration consumers and their authentication tokens are managed:
****
##
Improvement
### Updated New Category Workflow
The New Category workflow has been updated to improve usability. Categories are now created in a dialogue box rather than on a separate page.
Additional detection has been added so that if you attempt to create a Category that is similar to an existing one in the instance, you will receive a warning. You must then confirm before proceeding. This does not prevent duplicate Categories from being created; it simply ensures you are aware before doing so.
****
### System-Defined Fields Available for Advanced Search and Campaigns
When Event Day Interactions are activated for an event, system-defined fields are now displayed and can be used as filters in both Advanced Search and Campaigns.
### Refreshed Locations UI with Pagination
The Locations interface has been refreshed to improve navigation and usability. Search functionality and pagination have been added, and you can now filter the list to show only locations with logging exits enabled.
### ****
### Refreshed Items and Item Groups UI
The Item Groups and Items interface has been refreshed. Item Groups and Items now appear in separate tabs, and both lists are searchable.
### ****
### Daily Badge Printing Stats and Clearer Dashboard Refresh Times
Event dashboards now include a new Badges Printed Per Day section, showing how many unique people had badges printed on each day of the event.
The existing People With Interactions Per Day widget now clearly shows how often data refreshes, which is every 15 minutes, and when it was last updated. This helps clarify whether displayed numbers are current.
On the Community dashboard, the widget name has been updated for consistency. Counts are always live for the current day, while data for past days is cached once finalised.
### ****
### Survey Session Editing Requires Confirmation
When editing survey-enabled sessions, a new orange banner and tooltip explain that survey sessions are configured at the event level, not per individual survey.
You must now check a confirmation box before saving changes. This ensures you understand that updates apply to all surveys within the event.
### ****
### Search Added to Advanced Search Lists
A search box has been added to Advanced Search selection lists, including Category, Sessions, Item Allocation, Referring Store, Import Type, Touchpoint Interactions, and Custom Fields.
Checked items remain selected even when hidden by search results. The search function only hides items visually and does not change your selections.
### Event Preset Option Retired
The Event Preset feature has been removed to streamline event setup. The Duplicate Event tool now provides a simpler and more effective way to reuse event configurations.
### e-Ticket Scanner Management Permissions Updated
Super and trusted-support users can now add and edit e-Ticket scanners directly in the Portal. This change aligns permissions across roles for more consistent scanner management.
### Video Tables Block Retired from Community
The Video Tables block is no longer available for new use in Community. Any existing Video Tables blocks have been marked as Discontinued.
Allow Defining Programs via Portal
We’ve added the ability for Programs to be defined within the Portal.
****
# Jomablue Smart Badge
The Jomablue Smart Badge is a physical PVC card embedded with an NFC chip. Once printed and issued to attendees, it acts as their digital business card for use during the event. At the time of printing, the badge is encoded and linked to the attendee, serving as an identifier. Importantly, no personal information is stored on the Smart Badge, so there’s no privacy risk if it is lost or stolen.
This data collected helps map the individual journeys of attendees as well as the overall flow of all participants. Some uses of the Smart Badge include:
- **Identification** **:** Upon check-in, the badge is used to identify attendees, displaying their first name, last name, and company.
- **Lead Capture:** Exhibitors can capture leads by tapping an attendee’s Smart Badge on a Jomablue Lead Capture Device
- **Session Check-In:** Event staff can check attendees into sessions by tapping their Smart Badge on a Jomablue Session Check-In Device
- **Access to Content**: Attendees can tap their Smart Badge on a Jomablue Touchpoint to access Session-Related Content, download posters or whitepapers, enter competitions, complete surveys, and obtain any other materials you wish to provide
- **Item Distribution Management:** Event staff can manage physical item distribution by tapping an attendee's Smart Badge on a Jomablue Item Collection device
## Smart Badge Specifications
The Jomablue Smart Badge measures 85.6mm x 54mm with rounded corners. By default, it is white, but it can be customised with printed artwork or produced in a solid colour. If you choose a non-standard option, please allow 5 weeks from the order date until the event date for custom manufacturing. Consult your Project Manager to determine the best option for your event.
**Lanyard slot:**
- Dimensions: 15mm wide x 3mm high
- Distance between the top edge of the badge and the top edge of the slot: 3mm
**Long Edge Slot**
**Short Edge Slot**
****
**Artwork and Printing**
Attendee information can only be printed on one side of the Smart Badge. This information is printed in black ink. Badge printing supports inverted printing of specific fields, allowing white text to be displayed inside a black box on a white Jomablue Smart Badge.
There is an option for printing custom colours or artwork on one or both sides of the Jomablue Smart Badges. The artwork must meet the specified requirements and include a 5mm bleed. Note that custom artwork or colours may incur an additional fee. Please consult your Jomablue Project Manager.
**Important:** Please leave at least 60% of the front face of the Smart Badge clear to ensure sufficient space for printing the Attendee's details. This assumes 3 lines of information (e.g., First Name, Last Name, Company). Additional space is recommended if more lines are needed. A background can occupy this area if it is uniform and suitable for printing.
**Notes:**
- Printing image-based elements such as logos during Smart Badge printing is currently not supported. If a logo is required on the badge, it must be included in the pre-printed badge artwork rather than added through the Smart Badge Layout configuration in the Portal.
- Customer-provided or externally-sourced QR codes cannot be imported or printed on Smart Badges. Customer-provided or externally-sourced QR codes cannot be imported or printed on Smart Badges, as Jomablue does not have visibility or control over data generated outside the Jomablue platform.
## Configure Jomablue Smart Badge Layouts
Jomablue Smart Badge layouts (e.g., the positioning, size, and style of all text elements on your Smart Badge) can be configured via the Portal.
To access the Smart Badge Layout configurator:
1. Navigate to **Event Configuration > Settings**
2. Click on the **Printed Badge Layout** tab
3. Click the **New Smart Badge Layout** button to start configuring your Smart Badge layout. You'll be presented with a screen where you need to fill out the following fields:
****
- **Copy template from another event:** You can select a badge layout from a drop-down menu list of existing events (see **Copy a Smart Badge Layout** below)
- **Name:** Enter a meaningful name for the Smart Badge Layout. This will make it easier to locate, especially if you have many Badge layouts for a single event.
- **Layout Type:** Select the orientation of the Smart Badge Layout. The options are Horizontal and Vertical. Choosing the Vertical option will change the preview on the right to a Vertical orientation.
- **Category:** This option allows you to apply the Layout to all People in your Event or restrict it to a specific Category. If you choose "Apply Layout to specific category," a drop-down menu will appear for you to select the desired Category.
- **Priority:** This option applies to Layouts that correspond to a specific Category. Since People may belong to multiple Categories, this field allows you to prioritise Layouts.
- **Print Preview Badge Size:** The selected badge size will be displayed as well as a preview of the configured layout.
After completing these fields, click **Save** to save the Layout, and then proceed to edit the Layout itself.
### Using the Smart Badge Layout Editor
To edit the Layout, click on the **Edit Layout** button and you'll see this screen:
****
On the left, you can see the preview area displaying the elements you have positioned. On the right, there are several panels for the following purposes:
- **Sample text:** Enter sample text that appears in the currently selected field
- **Elements:** Add, select, or remove text elements to the Layout. Click the plus (+) sign next to an element to add it, or click on its name to select it. To remove an element, select it and then click the red cross icon.
- **Dimensions:** With an element selected, this panel allows you to view and edit its Width, Height, X Position, and Y position. The X and Y positions refer to the top-left corner of the field. For example, if both X and Y are set to 0, the field will be in the top-left corner of the Layout. Note that these dimensions reflect the bounding box of the element, not necessarily the printed text.
- **Font:** With an element selected, this panel lets you view and edit options like font size, style, family, case, and overflow method. Additionally, it includes an option to enable inverted printing for the selected element.
- **Alignment:** With an element selected, this panel allows you to adjust the text alignment within the element itself. You can align it horizontally (left, centre, right) and vertically (top, middle, bottom).
**Note:** A Custom Field always prints its stored value. To print a shortened version (e.g., "AI, Data and NGDE" instead of "AI, Data, and Next Generation Developer Experience"), create a second Custom Field with the shortened text and add that field to the Layout instead.
#### Smart Badge Font Options
Each field has independently customisable font options, enabling you to design your Smart Badges as desired. The options are:
- **Size:** The font size. Depending on the selected overflow option, fields may print at a smaller size to fit the text within the bounding box.
- **Style:** Choose between Regular or Bold font
- **Family:** Select the font family. The built-in options are Corbel, Open Sans, and Helvetica (with Corbel set as default). The option [Custom] allows you to manually enter a font family, but please note that custom fonts require additional setup. Consult your Jomablue Project Manager for your options.
- **Case:** Choose the case of the font. The options include:
- **Default:** No adjustment to the case
- **Sentence Case:** Capitalises the first letter of the badge
- **Upper Case:** Capitalises the first letter of each word
- **Overflow:** The method used when the text in a field cannot fit within its designated area.
There are two methods to handle this: Resize and Wrap:
- - **Resize:** Reduces the text size to fit within a single line inside the box, and it's indicated by a red exclamation mark when the text has been resized.
- **Wrap:**Keeps the text size constant while allowing the text to flow onto new lines. However, using the Wrap method may eventually result in the text overflowing from the top and bottom of the field.
- **Invert:** When this option is enabled, the selected element will be printed in an inverted style. For example, on a white badge, the text will appear white with a black background.
An example of the two methods is illustrated below:
On the left, you will see the Resize method (indicated by the red !), and on the right, the Wrap method (which shows text overflowing from the box):
****
### Copy a Smart Badge Layout
When creating a new Smart Badge Layout, you have the option to copy an existing Layout from another Event. To do this:
1. Click on the drop-down menu under the title **Copy template from another event**
2. Select a Smart Badge Layout from the list in the next drop-down menu
**Note:**To copy a Smart Badge Layout that contains Custom Fields, the current Event must include Custom Fields with matching keys. If they don't exist, a warning will appear with a link to the Custom Fields section of the Event, where you can create the necessary Custom Fields. Alternatively, you can use the Custom Field copying functionality to copy Custom Fields directly.
## Lanyard Options
The Jomablue Smart Badge is typically attached to a lanyard using the method below:
- **Direct Attachment:** The Smart Badge can be clipped directly to a lanyard, provided it has one or two slots or circular holes on one of its edges, depending on the lanyard type and desired orientation. This can be used with a backing card that clips to the lanyard behind the Smart Badge.
If lanyards with backing cards are used, they should be assembled before the event based on the expected number of attendees in each Category. This assembly can be arranged by Jomablue or by the client if preferred.
Some examples of Smart Badges attached to lanyards via these methods can be seen below.
****
**What gets printed on a Jomablue Smart Badge**
You can have any necessary data printed on the Jomablue Smart Badge. Custom fields and layouts are available; however, the standard fields we use are:
- First Name
- Last Name
- Job Title
- Company Name
- Badge Category Codes
The default typeface used on a Jomablue Smart Badge is Corbel. While custom fonts can be requested, they must undergo testing before approval. Please note that using custom fonts incurs an additional cost for setup and testing, which requires at least 5 business days.
## Configure Category Settings
The Jomablue Smart Badge settings allow you to add Category Codes to a person’s badge and an optional Category priority.
For example, you might want to use different lanyard colours to identify attendees at an event:
- Delegates = Black Lanyard
- VIP = White Lanyard
Instead of printing the full words on the Smart Badge, you can print category codes: "BLK" for black and "WHT" for white.
**What if someone belongs to more than one category?**
This is where Category Priority comes into play. For example, if a person is assigned to both Delegate & VIP, only the category code with the highest priority will be printed on their Smart Badge.
Example:
Delegates will receive a black lanyard
- Category Code = "BLK"
- Priority = 1
VIP will receive a white lanyard.
- Category Code = "WHT"
- Priority = 2
****
In this case, if a delegate has both Delegate and VIP categories, “WHT" will be printed on their badge since it has a higher priority (2).
If a person belongs to multiple categories with the same priority value, the category code for the first category they belong to will be printed. This is undesirable and uncontrollable, so it's advised not to assign the same priority to multiple categories.
**Note**: The prioritised Category must be active on one or more Smart Badge printers.
### Edit Category code
To edit the Category code, follow these steps:
1. Navigate to the **Portal > Event Configuration > Categories**
2. Click on **Event Settings** for the desired Category
3. You can now set or edit the Category Code and Priority in Badge Settings
#### Insights Settings
Toggling this option will include the category in the insights reporting. For example, if you want to exclude the crew from all insight charts and data tables, set the Crew Category to "No".
**Note:** This setting only affects the Organiser Insight dashboard
****
## Use Categories to apply different Smart Badge layouts
The badge for a person who belongs to multiple Categories will be based on the layout with the lowest priority value. For example, if a person is categorised as a VIP with a priority of 3 and as a Speaker with a priority of 2, the Speaker layout will be selected when their Smart Badge is printed.
# Release 9.34.0
Release Date: 27th February 2025
##
## New Feature
### Re-added Custom Domain Support for Free Registration
We have reintroduced custom domain support into a different feature. This allows for specific custom scripting that customers may want to embed on their registration sites. It still supports free registration custom domains, and includes groundwork for future custom domains for pages and other features.
### ‘Change Password’ Functionality in Portal
Users can now reset their passwords directly within the Portal while logged in, eliminating the need to go through the ‘forgot password’ workflow. Users are guided through the process via step-by-step instructions with an intuitive UI. The process also ensures that organisation-specific policies, such as minimum password length and multi-factor authentication (MFA), are enforced.
## Improvement
### Enhanced “View Countries Status” Modal in Event Settings
The width of the “View Countries Modal” in Event Settings has been increased for easier readability of the countries and their respective statuses.
## Known Defect
### Registration Billing Address Validation Issue
A validation issue with the billing address field has been fixed
### Registration Error Message Display
An issue causing an empty red box to appear on the Registration Page when a field validation failed has been resolved
# Release 9.31.0
**Release Date:** 20th December 2024
## New Feature
### Improved Portal Settings UI
The Settings User Interface has been redesigned to be more intuitive. Organisation settings now appear in the top Menu Bar instead of in a modal, making access easier.
### Google Tag Manager Integration
Google Tag Manager (GTM) can now be integrated into paid and free registration sites through the Integration tab in Registration configuration. Google Tag Manager allows the addition of third-party tags such as Google Analytics, Facebook, or LinkedIn pixels on Jomablue registration sites.
For compliance reasons, the Tag Script will only execute if the configuration is correctly set up. Currently, we are not passing any eCommerce data (like order values) or custom attributes to GTM; therefore, it can only be used for tracking page progress and default button clicks.
The GTM configuration validation has been updated to support the correct range of container ID formats. Previously, the configuration required eight characters after the *GTM-* prefix, which prevented some valid container IDs from being accepted. GTM container IDs that contain seven characters (a combination of letters and numbers, for example, *GTM-5ZMJBXW*) are now supported and can be successfully configured.
### Custom Domains for Free Registration Sites
Free Registration Sites now support custom domains. For example, a free registration site associated with the lep.jomablue.com instance could appear on a sonicconference.com domain.
Please note that implementing this feature requires action from the product team, and DNS configuration by the customer
### Event Level Permissions
A new user role has been introduced that allows the allocation of users to individual events–one or many–restricting their access to particular events. This feature is especially valuable when working with agencies or during Jomablue professional services events.
### Customisation of Registration Field Validation Error Colours
The colours for all registration error notifications are now customisable via a variable in the registration advanced theme settings.
### Session Organisation UID Displayed on Session Detail
The Organisation UID (a unique identifier for customers) for sessions is now displayed at the top of the session if available. Session Organisation UIDs are imported via the Importing Sessions feature and cannot be edited. They are often used as a customer’s campaign ID, referring to them as useful.
### Visibility Expiry Date for Registration Sites
Newly created registration sites will no longer be visible after the event’s end date and time. Each registration site now has a configurable visibility expiry date and time. After the specified date, the Site can no longer be accessed. By default, this is set to the event end date/time but can be changed or removed.
### SSO User Role Provisioning
When configuring SSO, we can now set the default role for new users provisioned by customers SSO. Previously, this role was always set to 'portal.’
### SMS Countries for Custom Sender IDs
The SMS Sender IDs feature has been extended to include a “Countries Status” for each Sender ID, indicating the countries where the Sender ID can be used.
Note: This feature is informational only; it does not affect the sending of SMS messages to different countries. If a country is not listed, we will still attempt to send the SMS, but cannot guarantee delivery or that it will arrive with the configured Sender ID.
See More Here: [9.31.0 - SMS Countries for Custom Sender IDs](https://jomabluewiki.bolddesk.com/kb/article/112/9310---sms-countries-for-custom-sender-ids#overview "https://jomabluewiki.bolddesk.com/kb/article/112/9310---sms-countries-for-custom-sender-ids#overview")
## Improvement
### Test Drive Seed Data Refresh
The Test Drive Seed data has been updated for improved content, providing excellent examples of all Jomablue features.
### Updated Localisation Helper Text
The text in the localisation tab has been revised for better clarity, and it now includes a link to Event Settings for selecting the appropriate label set to use for the event.
### Registration Invoice Preview in a Modal
The registration invoice preview is now displayed in a pop-up dialogue box for improved visibility.
### Translation of Registration Field Validation
For both paid and free registration sites, field validation messages (e.g., ‘Invalid Email Address’) can now be translated into Korean, Thai, and Vietnamese.
### Improved Login Form User Experience
When using SSO with Jomablue, the login form button now disables after the user enters their email address, indicating that a process is ongoing. This improvement prevents double submissions and clears the password field after failed attempts in the username/password.
### Updated Hover Text on People Detail Header
The hover text has been revised to prioritise ‘Checked In’ over ‘Badge Printed’ since some events may not have badges.
### Portal Events List Enhancements
The Upcoming and Past Events Tabs now display a ‘Checked In’ count and percentage, enhancing consistency between the portal event list and Jomablue CX. Additionally, ‘Past Events’ now loads much faster, even for instances with hundreds of events and hundreds of thousands of registered attendees.
### Restoration of Preview Admissions Functionality
The functionality to preview an Admission, which was temporarily disabled, has been restored in this release.
### Default Sender IDs Can No Longer Expire
Default sender IDs (EventInfo for SMS, and no-reply@event-email.io) can no longer expire because they are defaults and should always be available.
### Updated “Checked In” Icon on eTickets
The “Checked In” wording has been removed from the QR code displayed on attendees’ eTickets. It has been replaced with a simple green checkmark, allowing for cross-region support without the need for localisation.
### Friendly Messaging for Events Without Vendors
When you load the Vendors page in the portal and there are no Vendors listed, users will now see a friendly message explaining what a Vendor is and their purpose.
### Relocation of Omnia Setup Page
The Omnia setup page has been moved to the organisation settings page, where users can change the event name and other settings. The original location within the portal now contains a link to the new location.
### Preventing Admin Orders Without a Payment Gateway
Admin Orders (Paid orders created from the portal) can no longer be created if a payment gateway has not been set up. This change ensures that users don’t accidentally create admin orders that cannot be paid for due to the absence of a payment gateway.
Updated Method for Copying Custom Fields From Other Events
The process for copying a Custom Field from another event has been updated. To copy a custom field from another event, follow these steps:
1. Start by creating a **new Custom Field**
2. Click on the **“Copy field from another event (optional)”** link. This will open a dialogue box that allows you to select the event you wish to copy the field from
3. Select the field that you wish to copy
**Note** that after copying the field, make any desired edits before saving the field.
### Samsung Internet Browser QR Code Fix
A specific workaround has been implemented for ‘Samsung Internet’ browser (the default browser on Samsung Devices) to prevent the QR code from darkening when the phone is in Dark Mode. This browser applies a greyscale overlay to white elements on the screen, which reduces the QR code’s contrast and makes it hard to scan. Many requests have been to Samsung for a permanent fix, but this workaround is in place for now.
### Added German, Italian, Polish, and Czech to Localisation Label Sets
German, Italian, Polish, and Czech are now available as pre-set language options for registration localisation.
### Updated Default Kiosk Template
To support the new Kiosk application release, the default Kiosk template (which is pre-filled when creating a new template) has been updated with new branding and includes a new portrait\_screen configuration option, set to false by default.
### Error message for CX Login from a user role that doesn’t support CX
Users assigned to the new event-limited role will no longer have access to CX. If they attempt to log in, they will receive a new error message stating, “Insufficient Permissions.”
## Known Defect
### URL parameters restored for the Templates Portal Page
URL parameters are now displayed correctly when navigating between the “Email,” “SMS,” and “eTicket” tabs within the ‘Templates’ section, allowing for hotlinking to these tabs.
### Unexpected Site Save When Adding Products to Site
When configuring registration and adding Products to a site, previously closing the selection modal would also save the site and close the accordion. This issue has been fixed, requiring users to manually save after selecting products.
### Fixed Timeout for Resuing Live Streams in Live Stream Block
The timeout issue when attempting to reuse existing live streams in the Live Stream Block, especially when multiple blocks are present, has been resolved.
### Inability to Disable a User From Within User Detail
The bug preventing users from disabling another user from the user detail page has been corrected.
### Added Missing Registration Customisation Label in Add-on Workflow
A previously missing customisation label in the Add-on workflow has been added, allowing for customisation via Label Sets.
### Enhanced UI for Adding a New Person
The user interface for creating a new person has been improved to prevent overlapping icons and lines when there are no timestamps in the header.
### Duplicate Event Modal Resized and Checkmark Consistency
The duplicate event modal has been restored to its original width after being narrowed by previous changes. Checkmarks that were cascading down in size for each event option are now consistent in size.
### Improved Community Login Image Uploader UI
The user interface for the community login image uploader has been improved to enhance usability while maintaining a fixed resolution for the login image.
### Aligned People Export “Categories” and “Sessions” Text in Exports For Larger Screens
The Categories and Sessions texts in exports are now properly aligned for larger screen sizes above 1800px.
### Community Name Update Display Issue
When updating the Community Name in the Organisation settings, code was briefly visible in the page title for about 60 seconds before the updated title appeared.
### Scrolling Issue When Selecting a Vendor’s ‘Sponsored Session’
There was an issue where users were unable to scroll through a long list of sessions when selecting a vendor’s sponsored session. This issue has now been resolved.
### HTML Tags Issue in Site Descriptions
In Registration > Configuration > Sites, collapsing a Site in the list would momentarily display HTML tags in the Description and Purchasing Terms Text fields. While this was purely a visual bug, it has been fixed.
### Resolved Issues with the External Links Editor
Several visual issues with the External Links editor (for Registration and Sites) have been resolved. Additionally, a problem where the modal would not fully close after saving a single External Link has been addressed.
### Consistency of External Links
The external link wrapping is now consistent between Sites and ‘Registration’ (aka clicking on “Register Now”)
### Timestamp Issue of Reverting Back to UTC When Editing Person Records
An issue where the registered timestamp on a person record reverted to UTC after editing has been resolved. The timezone is now correctly applied after saving changes.
# Survey Configuration
## Create a Survey
To create a survey:
1. Go to the **Surveys** section
2. Select **Add Survey**
You will need to populate the following fields:
- **Name** - An internal name to help you identify the survey
- **Title** - The name that attendees will see
- **Description** - Text that attendees will see
Optionally you can configure:
- **Colour** - The header colour of the survey, which must be entered as a hex value and should contrast with white
- **Close Time** - After this set time, the survey can no longer be accessed by anyone with the survey link
- **Footer Text** - Typically used to list terms and conditions for submitting the survey.
- **Success Message** - The message attendees will see after submitting the survey.
### Add general questions to the Survey
To add questions:
1. Click on the Survey you wish to edit
2. Add a general group
3. Within the group, click on **Add Question** and define possible values for each one
To preview the survey, navigate back to one page and click on **Preview**.
### Add dynamic Session questions to a Survey
When creating a Survey in Jomablue, you have the option to include questions related to Sessions attended by participants. As a person checks in to a Session using their Smart Badge, the survey questions linked to that Session will be included in their personalised survey.
#### Create session-related questions in a Survey:
1. Navigate to the **Survey** you have created
2. Click on the **Survey** **name** to edit the questions
3. At the bottom of the Survey, check the **Survey Sessions Attended** box. A dialog box will appear, allowing you to select multiple Sessions.
4. Create a new group of questions by clicking Add Session Group, and provide a name, title, and description.
5. Within this group, add questions and define their possible answers (e.g., “Rate the speaker of this session,” or “On a scale of 1-10, how relevant was the content of this session?”).
**Note**: This group of questions will appear for each selected Session
6. Click **Save**
#### Include session questions in multiple surveys
If you are creating multiple surveys for a single event and want to include session questions, please note that you can only select sessions for one survey at a time. You must close the current survey before adding session questions to another.
### Add HTML to a Survey
If you wish to customise the survey further, you might want to include links to Terms and Conditions or other resources, either before or after the submission of the survey.
You can enter HTML into the following fields:
**Footer Text**: This field supports links
Example:
For terms and conditions of entry, please see <a href="https://example.com"" target="\_blank">Terms</a>
**Success Message**: This field supports subtext and links
Example:
<h2>Thank you</h2>
We appreciate you taking the time to share your feedback. If you would like to join us again next year, please visit <a href="https://example.com" target="\_blank">our website</a>
**Note**: The Survey Success Message is displayed in a green success box. Here is an example.
****
## Survey Character Limits
#### Surveys
- **Survey Name**: 180 Characters
- **Survey Title**: 180 Characters
- **Survey Description**: No limit (note that there is no formatting, e.g., line breaks)
- An event can have unlimited surveys
#### Question Groups
- **Group Name**: 180 Characters
- **Group Description**: No limit (note that there is no formatting, e.g., line breaks)
- A survey can contain unlimited survey groups
#### Questions
- **Question Text**: No Limit (note that there is no formatting, e.g., line breaks)
- A question group can contain an unlimited number of questions, and there is no limit to how many questions a survey can contain.
## Survey Response Options
When creating Survey questions, you can use one or more of the following response formats:
**Text**: A free text field for typed responses
****
**Select**: A dropdown list from which users can choose one option
****
**Multi-Select**: Users can select multiple responses to a question.
****
**Radio**: Users select one option from always-visible choices. This format is ideal for fewer than five short response options.
****
**Radio Horizontal**: Designed for short options only (e.g., numbers).
****
**Range**: A sliding scale that allows the user to select a value from 1 to 5. The numbers are fixed and can't be altered.
****
**Rating**: Users are presented with 5 yellow stars representing values from 1 to 5.
****
## Multiple Survey Submissions
A Jomablue Survey can only be submitted once per person, per survey. The URL generated for each attendee tracks who has answered the Survey and marks them as 'Responded.’
If a user attempts to reload or follow the Survey link a second time, they will see this message:
"You have already completed this Survey"
****
Once a Survey has been submitted, the responses can’t be modified or it cannot be undone by either the User or Administrator.
## Survey Link Construction
Jomablue has built-in functionality for sending surveys that automatically handles the personalisation and the creation of short and long survey links. There may be scenarios where you need to manually create links for use in external systems.
### Survey URL structure
Survey URLs can be constructed with some understanding of how URLs work, as well as a People Export from Jomablue. The export will contain all the data required to construct the URL, but some manual filtering and construction will be required before a campaign can be sent (e.g., removing people who have not had their badges printed).
Jomablue surveys contain unique parameters in the URL that identify both the respondent and the specific survey they are responding to. It is essential that the survey URL is complete and accurate; otherwise, the survey may fail to load.
A Survey URL typically includes:
- Base URL (the URL of your Jomablue organisation)
- Survey Identifier (ID)
- qr\_uid (the unique identifier of a person)
**Example Survey URLs for a person:**
**Note**: These are non-working links.
For a survey with ID = 2 and person with qr\_uid: f3372687-56ee-424a-915b-4f09ab74192d
[https://staging-lep01.jomablue.com/community/survey/2/f3372687-56ee-424a-915b-4f09ab74192d](https://staging-lep01.jomablue.com/community/survey/2/f3372687-56ee-424a-915b-4f09ab74192d)
For a survey ID = 8 and a person with qr\_uid: 36419b25-9efc-4434-85fc-40971c9f1621
[https://staging-lep01.jomablue.com/community/survey/8/36419b25-9efc-4434-85fc-40971c9f1621](https://staging-lep01.jomablue.com/community/survey/8/36419b25-9efc-4434-85fc-40971c9f1621)
### Find the Survey ID
1. Navigate to the **Surveys** section
2. Identify the relevant survey
3. Select the **Preview** option on the right-hand side
4. The survey ID will be located in the URL after “...survey/”
For example, in [https://staging-lep01.jomablue.com/community/survey/8/demo,](https://staging-lep01.jomablue.com/community/survey/8/demo,)the survey ID is “8”.
### Testing
Links can be tested by following them in your browser. If the URL is constructed correctly and the person has attended the event, the survey will load successfully.
**Note**: No callback presents the qr\_uid as the person’s name or any other identifying remarks.
## Additional Notes
- Ensure you update the base URL with your organisation’s Jomablue domain
- The Jomablue survey is intended for attendees only. You cannot provide a survey to people who have not had their badge printed. Please ensure that you filter the export correctly before sending any campaigns to avoid errors.
- Do not add any tracking parameters, as this may lead to unexpected results
- Be cautious when dragging formulas in Excel, as incorrect references could lead to the same survey link being copied for all attendees
- We don't recommend using URL shorteners, as they may create undesired effects
- Always link using “https://” (not “http:/”/)
- Surveys can only be submitted once
# Block Types - Video
## Live Reaction Block
The Live Reaction Block is a fun, interactive addition to the wide range of content and interaction blocks. It enhances the attendee experience by adding vibrancy and encouraging interaction, allowing attendees to express their opinions. It is designed for use during live stream sessions.
****
The ‘react’ emoticons allow attendees to react in real-time to a live stream session with the emoji they can most relate to during the session. It encourages the attendees to participate more and spark a response to the content. And while it may look like a ‘react’ tab is a fun experience for the attendees, for the organisers, it provides a better analysis of attendees' reactions to the content. It helps organisers understand what content is generating the most reactions and resonating with the attendees.
#### Features of the Live Reaction Block
The Live Reaction Block is configurable and comes with its own set of features, such as:
**Adding & Removing a Reaction**
Between 2 to 5 reactions can be displayed on the tab. The default reaction tab contains the following reactions: Like, Love, Celebrate, Interesting, and Unsure.
You could also present simple thumbs-up and thumbs-down icons.
**Custom Reactions**
All icons, labels, and colours within the Reaction block can be customised. There is also an option of providing a text label beneath the reactions. The recommended image size for a reaction image is 120px x 120px transparent PNG format. Each reaction’s colour can be set using a hex code in the configuration settings.
Please note that if you wish to change the default icons, all icons must be changed with new images and labels; a mix of default and custom icons is not supported.
**Block Placement**
The live reaction block is best placed just beneath the live Stream/ Video-on-Demand Block. It is recommended that the Session block take up at least 50% of the page to provide enough space for the reactions and the equaliser.
**Data Points**
Although the exact count of reactions is not displayed in Community, the most clicked emoji will automatically form the highest curve on the equaliser compared to less popular emojis. Jomablue records data points for each reaction and timestamps when the reaction is pressed; however, this information is not currently visible to users in Jomablue.
There could be two ways data can be viewed or interpreted in post-event reporting:
- **Unique people per session per type:** For example, if two attendees clicked on multiple reactions throughout the session, the data will show the number of unique people (in this case, two) who reacted to the types of reactions in the session.
- **Overall clicks per session per type:** For example, if a single attendee clicks on the 'happy' emoji multiple times throughout the session (one reaction is recorded for every 15 seconds per person), the data will show the overall number of clicks on the ‘happy’ reaction type during the session.
**Reaction Limits**
An attendee can click on a reaction icon every second without limit. However, only one reaction is recorded per person every 15 seconds to prevent one person from overwhelming the reaction chart. The personal graph equaliser still their overall impact.
To see how to use a ‘Live Reaction’ Block on Community Plus, please proceed to the Set up a Live Reaction Block section.
#### Available interactions for this Block
When an attendee interacts with a Live Reaction Block, the ‘react’ interaction can be captured for post-event reporting. These ‘reactions’ are collected as data points, providing insights into:
- Who (people) has ‘reacted’ within a Block
- What specific reactions people have responded to within a Block
Here is an example of counting by Key and limiting by canvas:
****
In addition, block metrics are available in a People Export. When a Community contains one or more Live Reaction Blocks, a new column will be added to the report for each Reaction Key (e.g., each reaction icon) in a Live Reaction Block. Each column will have a header containing:
- The Block ID
- The name of the Block (if applicable)
- The reaction key (e.g., love, curious, etc.)
### Set up a Live Reaction Block
1. Go to the **Jomablue Portal** and log in with your email address and password
2. Click on **Canvases** under Community on the left-hand menu
3. Click on the Canvas type where you wish to add the Block (e.g., Lobby, Session, Vendor or Page)
4. Locate the specific Canvas where the Block will be added and click **Edit**
5. Click on **Layout**. This block is best positioned within the same flex as a live stream of the video player where the width of the block is at least 50% of the page.
6. Within a Flex, click **Add Block**. Here, a list of Blocks will appear. Select **Live Reaction.**
7. The Live Reaction Block is now added to the Canvas. You may now add Title, Configure, Automate or Delete the Block (**Note**: you cannot delete the Block once it has data in it).
#### Configuration options
The default Live Reaction Block includes five reactions that require no additional configuration, as shown below:
****
You can customise your own set of reactions instead of using the default reaction bar. Each reaction can be configured with the following fields:
- Reaction Name
- Image
- Reaction Label
- Custom Colour
## Live Stream Block
Live Streams created through the Live Streaming feature (found in the left menu) or the Live Stream Block are recorded and available for download via the portal. You can preview the stream recording after the session ends and generate a downloadable file in MP4 format within a few minutes.
This feature supports multiple streaming sessions within a single Live Stream. For example, if a stream is stopped and restarted (often due to technical issues), an asset will be made available for each streaming session.
If you need to download the live stream recording and upload it as VOD, refer to the How to view and download a recording section below.
#### Latency when Live Streaming
Stream latency refers to the delay between the camera capturing an event and the event being displayed on the attendee’s screen. This latency builds up at each step of the streaming workflow. Consequently, attendees will not see the event in real-time; there will always be a delay. Jomablue built-in streaming for either Streaming, Simulated live, or broadcast block is subject to the nature of HLS video delivery.
#### Jomablue Stream Latency
Jomablue latency from the camera/source to the viewer is approximately 15-30 seconds. Low-latency options can reduce this to around 10-15 seconds; however, this may come with trade-offs regarding video resolution and compatibility. Jomablue can consider reduced latency for the Broadcast or Simulated Live Block on a case-by-case basis.
#### Default Latency for Broadcast and Simulated Live
The default latency for broadcast and simulated live streaming is currently up to 30 seconds. Therefore, even with the perfect timing for the simulation play-out, viewers may see it up to 30 seconds behind real-time. For example, if a keynote started at 9 am sharp, viewers may see it start at 09:00:30.
#### Jomablue Streaming Synchronised Streaming
HTTP Live Streaming (HLS) is the widely used protocol for streaming live videos. In HLS, latency is closely linked to the duration of the media segments; thus, attendees may not be synchronised in the content they're watching. Some viewers might be 21 seconds behind, while others may be 29 seconds behind. Generally, all viewers will see the 'same' content but with a margin of approximately 10 seconds of latency.
**Note:** When conducting any time-based interactions, such as polling, ensure that there is enough buffer time to accommodate latency.
### AI Closed Captions functionality for Live Streaming
Jomablue Live Streaming now supports the addition of AI Closed Captions. This feature uses an AI speech-to-text engine to generate captions based on what is being said during the Live Stream.
If AI Closed Captions are enabled, a Closed Captions button will appear in the Live Stream player, allowing a user to enable them (if desired).
**Note:** AI Live Captions are provided on a "best effort" basis. While they are generally accurate, there may be occasional discrepancies between the captions and the actual spoken content of the live stream. This can include incorrect interpretations of specific words or phrases, such as company or product names, acronyms, or other industry-specific jargon.
In addition to the standard speech-to-text library of words and phrases, the feature also supports the creation of Vocabularies.
Vocabulary is a list of specific words and phrases that the speech-to-text engine can use to enhance transcription accuracy.
#### Configuration
To enable AI Closed Captions for an existing Live Stream:
1. Navigate to **Community > Live Streaming** in the portal left navigation
2. Select **More** on the relevant Livestream
3. Click on the **AI Closed Captions** tab
****
4. Use the radio toggle to enable AI Closed Captions
5. Press **Save** to save your changes
**Note:** If a Live Stream is currently active (e.g., it is receiving a stream to its ingest URL or has streamed in the past 5 minutes), you will not be able to modify the Live Stream configuration. An error message will appear in this case.
Once enabled, viewers will see a toggle for Closed Captions in the player when the live stream is active, allowing them to enable and view the captions.
****
****
### Vocabularies
When configuring AI Closed Captions, you also have the option to create Vocabularies and associate them with your Live Stream.
#### Add Vocabularies
To view existing Vocabularies or create a new one:
1. Navigate to **Community > Live Streaming**
2. Click on the **Vocabularies** tab
3. Click on **Create New Vocabulary** to create a new Vocabulary
****
After clicking Create New Vocabulary, you will be directed to the Vocabulary detail screen, where you can see the Vocabulary name (along with an external ID used by the Live Streaming service) and a list of linked Live Streams (this list will be empty upon creation).
****
#### Add Phrases
To add Phrases to the Vocabulary:
1. Click on the **Phrases** tab
2. Click on the **Edit Phrases** button
****
This will open a modal that allows you to add a list of Phrases (one per line) to the Vocabulary.
****
3. After saving, the list of Phrases will be visible in the Phrases tab:
****
## Live Streaming
Live Streaming provides a native solution for streaming video and is fully configured within Jomablue, requiring no external configuration.
Additionally, Streams can be created and assigned to Blocks without specifying dates and times. When the stream starts transmitting content via the ingest URL, it will automatically become available in the assigned Live Streaming Block(s).
The configuration is flexible, allowing for a single live stream to be reused for multiple sessions without the need for on-site teams to reconfigure encoders each time.
Within an event, you can view the Live Streaming Summary by navigating to **Community > Live Streaming.** The Live Streaming summary view contains a list of all Live Streams for the current event, including:
- Live Stream ID and Nickname (the nickname is editable to help identify streams that may be grouped across multiple blocks)
- Created at time
- Stream Key
- Linked Blocks (number of Live Stream Blocks using this Stream
- Actions (contains a "More" button)
**Note:** To view more information about a particular Live Stream, click **"More".**
#### Live Stream Detail view
The Live Stream detail view displays additional information about a specific Live Stream, including:
- **External ID and External Created:** the external identifier and created time for the stream. This is used for Jomablue support to reference streams within an external infrastructure.
- **Status:** The status of the stream (either idle or active; a stream is considered active when content is being ingested)
- **Linked** **Blocks:** a list of all Live Stream Blocks using this Live Stream, including columns for Block visibility and direct links to edit each block
#### Live Stream Recordings
Live Streams created via the Live Streaming feature (available in the left menu) or the Live Stream Block are recorded and can be downloaded via the portal. After the session ends, the stream recording can be previewed, and you can generate a downloadable file in mp4 format within a few minutes.
#### Configure a Live Stream Block
Live Streaming provides a native solution for streaming video, fully configured within Jomablue without the need for external configuration.
When creating streams, there’s no requirement to set specific dates and times; streams can be created and simply assigned to Blocks.
As soon as the stream is initiated 9when content is sent via the ingest URL), it will automatically be available in the designated Live Streaming Block(s).
The configuration is quite flexible, allowing a single live stream to be reused for multiple sessions without requiring onsite teams to reconfigure encoders between events.
**Configuration**
To create a Live Stream Block, select the "Live Stream" option during the setup of a new Block. (Please note that “Self Hosted Live Stream” and “Simulated Live Stream” are distinct options):
****
There are two options when using the Live Stream Block: create a new Live Stream when creating the Block or reuse an existing Live Stream.
#### Create a Live Stream Block with a new Live Stream
After creating the Live Stream Block, navigate to the Configuration tab and click the button labelled **Generate Live Stream Ingest Details** to generate a new Live Stream. Click this button:
****
Once you click this button, a new Live Stream will be generated along with its corresponding ingest and preview details. (Please note that the Live Stream Key and Live Stream Preview Link will be blurred for security.)
****
The grey fields can't be edited, but you can still copy these details to your clipboard using the buttons to the right.
The **Live Stream RTMP Ingest** and **Live Stream Key** should be provided to the AV Provider (or any source streaming the content) for their encoder. It’s important to remember that the Jomablue ingest URL remains constant; only the key changes for each stream.
The **Live Stream Preview Link** can be shared with the AV Provider for testing and with event organisers so they can monitor the stream.
**Important Note:** Some corporate networks may block outbound traffic, particularly at volume. This issue may manifest as the stream working initially but failing subsequently, due to the network detecting and blocking the traffic. It’s advisable for clients to consult their IT department to whitelist \*[.jomablue.com](http://jomablue.com/ "http://jomablue.com/") and allow outbound TCP traffic over port 5222.
#### Create a Live Stream Block with an existing Live Stream
When creating a new Live Stream Block, instead of clicking "Generate Live Stream Ingest Details", you can click on "Show Optional Fields" and then select an existing Stream to re-use:
****
Select the desired stream and then click **Save.** This action will automatically configure the Block with the corresponding Live Streaming details.
### Preview a Live Stream
For testing and monitoring purposes, a Live Stream Preview URL is generated when the Live Stream is created. To access this URL, locate the Live Stream in the Live Streaming menu and locate the Preview URL field:
****
The button to the right of this field can be used to copy the URL to your device's clipboard, and it can then be viewed in any browser.
#### **Latency**
Stream latency is, on average, between 20 and 35 seconds.
#### Usage and Charging
Live Streaming is accounted for in the following way:
- **Stream Encoding:** This refers to the hours of video sent from OBS or the Encoder to the Jomablue ingest
- **Stream Viewing:** This accounts for the hours of video watched by viewers (e.g., 1 hour x 100 viewers equals 100 hours)
These charges apply only to streamed video, which means the video being sent by OBS/Encoder to the ingest point, not simply creating a "stream" in Jomablue. The usage data is recorded in the Jomablue Subscription information for each instance.
Additionally, for every hour of live streaming encoding, there is a monthly charge for hosting the recorded stream.
e.g., 1 hour of Stream Encoding counted as 1 hour of recorded video. If this is kept for 6 months, the cost will be: 1 hour x 6 months.
#### Offline Handling
To ensure the best user experience, the goal is to make the stream available as viewers join until they leave, with no interruptions.
Failing to achieve this can detract from a seamless experience; however, Jomablue includes built-in automatic recovery features for potential live stream issues.
The player is designed to recover in most scenarios, but experiences may differ depending on browsers and devices. If no video is being streamed, viewers will see a message accompanied by an animated spinner. At this point, viewers do not need to take any action, as playback will automatically resume when the video begins again.
If playback doesn’t resume, users may need to refresh the entire page to reload the stream.
Offline status can be classified into two different states, with varying considerations and resolutions depending on the situation:
**1. No Video Streamed**
This occurs when a viewer arrives on a canvas before the video has started streaming, such as when the Pre-roll hasn't started yet. To avoid this situation, plan to reveal canvases or blocks only after the pre-roll has started. This way, the viewers will immediately see video content instead of an error message.
The same principle also applies to the end of a stream; the block should be hidden before the post-roll has finished.
**2. Dropouts**
A dropout happens when a video has been successfully streaming and is unexpectedly cut. For example, this can occur if the internet connection in the studio drops out. There are two types of dropouts: minor and major.
- **Minor dropouts** last less than 5 minutes and automatically recover from where they left off after viewers see an error message for the duration of the dropout.
- **Major dropouts** last longer than 5 minutes. On some browsers, viewers may see the last ~10 seconds of buffered video before an error message is displayed. If a viewer refreshes their browser during a major dropout, they may continue to see the buffered video for a few minutes before the player shows an indefinite error message.
Both minor and major dropouts are handled in the player, but the user experience is less satisfactory for major dropouts.
****
#### How the player looks when no stream is available
**Encoder Settings**
Live streaming supports a variety of incoming sources and types, including most modern codecs and frame rates. Only a single high-quality incoming stream is required; multiple renditions are not necessary. The following recommendations are provided, though experimenting with encoder settings is advisable to find what works best for your specific content, as this may vary based on your region or camera choices.
When selecting an encoder bitrate, consider your available upload bandwidth. There should be at least 50% bandwidth headroom above your chosen bitrate. If bandwidth is limited, it is advisable to reduce the quality of the stream (e.g., choose a setting similar to 'good quality').
The following recommendations apply to a range of content types, including talking head videos, stage productions, webinars with screen sharing, and more.
**Overall**
- Video Codec - H.264 (Main Profile)
- Audio Codec - AAC
**Great Quality**
- 1080p (1920x1080) @ 25fps or 30fps
- Bitrate - 6500 kbps
- Keyframe Interval - 2 seconds
**Good Quality**
- 720p (720x480) @ 25fps or 30fps
- Bitrate - 4000 kbps
- Keyframe Interval - 2 seconds
**Advanced Settings:**
- These are not required but provided as a reference to tweak advanced settings
- Audio sample rate: 44.1Khz
- Audio bitrate: 128Kbps Stereo
- Pixel aspect ratio: Square
- Frame types: Progressive Scan, 2 B-Frames, 1 Reference Frame
- Keyframe Interval: Recommended 2 seconds, do not exceed 4 seconds
- Bitrate Encoding: CBR
**Troubleshooting:**
When experiencing connectivity issues to the live stream servers, please ensure:
- There are no typos in the Live stream details within the device or software configuration
- There are no firewalls or antivirus programs that may prevent you from streaming
- A stable internet connection is established, preferably using a wired connection instead of WIFI
- Try using a different network, such as a mobile device hotspot, to confirm if the production network is affected by these issues.
#### How to view and download a recording
1. Navigate to **Live Streaming** in the left menu
2. Select **More** on the stream you wish to download
3. Click on the **Assets** tab
4. To preview any session of the live stream:
a. Select the **thumbnail image** to display a player
5. To download a file:
a. Select **Generate Master .mp4 file**
b. When the generation is complete, select Download Master File
#### Use a downloaded Live Stream as a VOD
After downloading a Live Stream, the file can be uploaded for use as a VOD (in a VOD Block) or made available on demand through other means. It is recommended to edit the file by removing or replacing unwanted intro/outro content to enhance the viewing experience.
**Additional Notes**
- Live Streams are always recorded by default; this feature cannot be turned off
- The process of generating a master file can take from 30 seconds to several minutes, depending on the length of the asset
- Once a file is generated for download, it will be available for 24 hours. After this period, users will need to generate a new master file for download
- If one portal user generates a file for download, it will also be available to other users
- The downloaded filename will be “master.mp4” or a variant, such as “master (1).mp4)”
- The file format is .mp4
### FAQ: Live Stream
**Q: Why is the stream key so long and hard to enter into our encoder?**
A: The stream key functions like a password. Its length and complexity ensure that unauthorised users cannot access your stream. Although it can be inconvenient to type, having a short and guessable key poses a significant security risk. Note that the ingest URL remains the same; only the stream key changes.
**Q: I need a single-line ingest URL for my encoder/My encoder doesn't support stream keys**
A: Some encoders lack separate fields for the stream ingest URL and the stream key. In such cases, you can combine both. In this example, using the following format: rtmp://ingest.jomablue.com/522/app/b5c710c8-7d7f-11ec-90d6-0242ac120003 where 'b5c710c8-7d7f-11ec-90d6-0242ac120003' is the stream key
## Self Hosted Live Stream Block
A Self Hosted Live Stream Block accepts an HLS playlist (.m3u8 URL) and allows users to consume live video content on both mobile and desktop devices. It can be used with nearly any video provider, including those not available as native Jomablue plugins. This also includes self-managed video streaming infrastructures such as Wowza.
The player supports a custom holding image, which should be hosted publicly. The URL of the image is added to the block configuration, with a recommended image size is 1920 x 1080px.
Picture-in-picture display is supported in this block, offering users greater control over the video on their devices.
If the stream becomes unavailable (either it hasn’t started or has been manually stopped), a message will appear in the middle of the player, allowing users to click a refresh button to attempt to reconnect to the stream.
#### Platforms that Support HLS Streaming
The following platforms support HLS streaming and can be used within the Self Hosted Live Stream Block, but please verify with these providers as their platforms may change over time:
- Wowza
- Kaltura
- Jwplayer
- Brightcove
- Viostream
#### Features of the Self Hosted Live Stream Block
- The Self Hosted Live Streaming feature supports the industry-standard HLS streaming protocol, which is widely compatible with almost all video streaming providers
- Automations and insights are available no matter the streaming provider used
- Custom-holding posters (images) are also supported
- The Content URL **must** start with **https://** and end with **.m3u8**. Non-https: sources cannot be played
- Captions are supported if embedded in the HLS playlist from the video provider
- Picture-in-Picture is supported, which lets users place the video anywhere on their device
#### Available interactions for this block
Available interactions for the Self Hosted Live Stream Block are:
- **playback\_started:** Triggered when the live stream begins playing in the user’s browser
- **playback\_paused:** Triggered when the user pauses playback of the live stream
- **chunk\_played:** Triggered when a chunk of the live stream has fully played
- **time\_watched:** The total amount of time the user has spent watching the stream
- **first\_playback:** A timestamp indicating when the first playback\_started interaction occurred, in the event’s timezone
Users watching Live Stream chunks create a new data point every 60 seconds, allowing us to track which parts of the Live Stream viewers engaged with to the nearest minute.
These interactions can be stored for post-event reporting and block automations. For more information, see the Available Interactions for this Block section.
### Set up a Self Hosted Live Stream Block
1. Go to the **Jomablue Portal** and log in with your email address and password
2. Click on **Canvases** under Community on the left-hand menu
3. Click on the Canvas type where you wish to add the Block (e.g., Lobby, Session, Vendor or Page)
4. Locate the specific Canvas where the Block will be added and click **Edit**
5. Click on **Layout**
6. Within a Flex, click **Add Block**. Here, a list of Blocks will appear. Select **Self Hosted Live Stream**.
7. The Self Hosted Live Stream Block is now added to the Canvas. You may now add a Title, Configure, Automate or Delete the Block.
#### Configuration options
A Self Hosted Live Stream accepts a URL via the Content URL in the Block's Configuration tab.
You can also add an image URL link and configure the following options:
- **Auto-play:** This can be turned on and off; it is recommended to keep autoplay disabled
- **Automatically poll for progress:** This can also be turned on or off. If activated, the system will automatically check if the video player is progressing and will reset the stream if it is not.
- **Progress polling interval:** If automatic polling is enabled, you can set how frequently the player checks for progress.
## Simulated Live Stream Block
The Simulated Live Stream Block allows speakers to present their pre-loaded content as a live stream. This combines the perks of live streaming with pre-recorded sessions, creating an all-encompassing experience for the audience.
#### What the Simulated Live Stream Block does
With the Simulated Live Stream Block, users can upload a video and configure the Block to play it over a stream at a certain time, without the play/pause functionality.
There is a failover system that handles unlikely stream failures, allowing another stream container to activate and continue streaming from the same point in the video playback. This preserves the illusion that the video is being streamed live rather than being a pre-recorded playback.
Note: Closed captions are currently not supported in Simulated Live Stream; attendees cannot turn subtitles on or off. However, open captions (which are always on and cannot be turned off) are supported in Simulated Live Stream.
#### Benefits of the Simulated Live Stream Block
- **Smooths over any technical glitches:** Removes stress related to technical issues during live stream sessions
- **Production control:** Allows the producer time to edit and remove mistakes from the content
- **Flexibility & convenience:** The session can be recorded anytime prior to the event, providing convenience and flexibility for speakers
- **Creates excitement:** Creates the urgency and excitement typically associated with live streaming
#### The architecture of the Simulated Live Stream Block
The Simulated Live Stream Block comprises the following components:
- **Video File:** the file that will be played back as a ‘live’ stream
- **Simulated Live Block (configuration):** Configures the ‘Container’ that will run the stream
- **Simulated Live Container:** The server that plays back the video as a ‘live’ stream
- **Streaming Service:** Takes the RTMP stream from the Container and makes it available as an .m3u8 stream URL
- **Simulated Live Block in Community:** Contains a player that plays back the content on the Canvas in the form of an .m3u8 stream.
**Note:** .m3u8 is an HTTP Live Streaming-based file format that contains a multimedia playlist
All these components work together to ensure the Simulated Live Stream Block functions properly, as shown below in the architectural diagram.
****
#### Available interactions for this Block
The available interactions for the Simulated Live Stream Block include:
- **Playback Started (playback\_started):** Triggered when the stream playback begins
- **Chunk Played (chunk\_played):** Triggered when an attendee views a chunk (1 minute) of the stream
- **Time Watched (time\_watched):** The total amount of time a person has consumed watching the stream(the sum of all obtained chunks for that person). If a person watches concurrently on two devices, their time\_watched would be twice as much as expected.
- **First Playback (first\_playback):** A timestamp in the event’s timezone indicating when the first playback\_started interaction was fired
#### Pre-roll and post-roll
Before uploading your video, it helps to understand two terms used throughout this section:
- **Pre-roll** is content that plays before your main session content starts. For example, a countdown or a "starting soon" message. Its job is to give viewers something to watch as soon as they arrive on the canvas, instead of an error message.
- **Post-roll** is the same idea in reverse - content that plays after your main Session content ends, such as a "thank you for watching" message. Its job is to keep the stream active for a short time after your content finishes, so it doesn't cut out abruptly while the Block is still visible to attendees.
Both pre-roll and post-roll are recorded as part of the same video file you upload. They're not configured or uploaded separately from your main content.
#### Video file requirements for the Simulated Live Stream Block
The video files to be played out in the Simulated Live Stream Block have the following requirements. All uploaded video files will be validated to ensure requirements are met, and consistent playback can be achieved.
For the best viewer experience, it is highly recommended to include both pre-roll and post-roll segments, ideally lasting at least 15 minutes each. Failing to include these will result in an abrupt viewer experience, where the live stream starts or stops unexpectedly, much like an error with the live stream.
**1. Video requirements**
- Resolution: 1920x1080 @ 25fps or 30fps
- Video codec: h264 avc1
- h264 profile: High
- Bitrate: 2500kb/s - 4500kb/s recommended
**2. Audio requirements**
- Audio codec: AAC (LC) Stereo
- Bitrate: 256kb/s recommended
**3. File requirements**
- Max File Size: 20GB
- Max File Length: 6 hours
- File Type: mp4 recommended
We strongly advise producing a test video before creating your final production video. The test video should match the output settings of your production content exactly. This enables you to use the built-in preview tools in Jomablue to validate and ensure good-quality playback for your audience.
#### Set up a Simulated Live Stream Block
1. Go to the **Jomablue Portal** and log in with your email address and password
2. Click on **Canvases** under Community on the left-hand menu
3. Click on the Canvas type where you wish to add the Block (e.g., Lobby, Session, Vendor or Page)
4. Locate the specific Canvas where the Block will be added and click **Edit**
5. Click on **Layout**
6. Within a Flex, click **Add Block**. Here, a list of Blocks will appear. Select **Simulated Live.**
7. The Simulated Live Block is now added to the Canvas. You may now add a Title, Configure, Automate or Delete the Block.
#### Configuration options
**Video File Settings**
- **Upload Requirement:** You must upload the desired video file in the Files section of the Jomablue portal
- **Select Video File:** Choose the Video File that you want this Simulated Live Stream to play. This file should be uploaded via the Files page in the portal.
- **Video File Duration:** The total length of your uploaded video file, including your main session content plus any pre-roll and post-roll. For example, a 30-minute session with 10 minutes of pre-roll and 10 minutes of post-roll has a Video File Duration of 50 minutes. If your file has no pre-roll or post-roll, this is simply the length of your session content.
- **Vide** **o Pre-roll Duration:** The amount of pre-roll in your video file. This determines the actual streaming start time (see the worked example below). It's a requirement to set this field; leaving it unset can result in 'stream not running' errors up until the exact session start time.
**Stream Content Settings**
- **Content Start Time:** Select the date and time for the start of the actual session stream content
- **Poster Image:** An image displayed as a placeholder when the video is not playing. Recommended size is 3840px W X 2160px H.
- **Auto-play:** This option starts playing the video automatically when the page loads and is turned off by default (it is recommended to keep it off).
- **Automatically Poll For Progress:** This option checks periodically to see if the player is progressing and resets the stream if it is not
- **Progress Polling Interval:** The frequency at which the player checks the video’s progress to ensure it is playing as expected. Defaults to 0 seconds.
- **Simulated Live Stream ID:** This is generated automatically
- **External Live Stream ID:** This field is populated automatically
**Note:** For support on uploading the Cloudinary image ID, please reach out to Jomablue.
#### **Worked example**
Say your session content runs 30 minutes, with 10 minutes each of pre-roll and post-roll.
**What you configure:**
| **Setting** | **Value** |
| --- | --- |
| Video Pre-roll Duration | 10m |
| Video File Duration | 50m (10m pre-roll + 30m content + 10m post-roll) |
| Content Start Time | 10:00 AM |
**What happens (in order):**
| **Time** | **Event** |
| --- | --- |
| 9:50 AM | Streaming starts. Pre-roll begins playing, Simulated Live Stream Block still hidden, Holding Slide shown. |
| 9:55 AM | Recommended reveal time. Hide the Holding Slide, reveal the Simulated Live Stream Block. Pre-roll has already been running for 5 minutes. |
| 10:00 AM | Content Start Time. Main session content begins. |
| 10:30 AM | Main content ends. Post-roll begins. |
| 10:35 AM | Recommended hide time. Hide the Simulated Live Stream Block, reveal the Holding Slide. |
| 10:40 AM | Streaming naturally ends. Post-roll finishes playing (already hidden from attendees since 10:35 AM). |
The same example shown visually:
This 5-minute gap at each end is deliberate, not arbitrary. Revealing the Block before pre-roll starts streaming is what triggers the "pre-roll should begin before the Block is visible" warning, so waiting until pre-roll is already running keeps you clear of it. The same buffer applies at the end: hide the Block a few minutes before the stream actually finishes, so viewers are already back on the Holding Slide first.
### Experience Rating for Simulated Live Block
An ‘Experience’ tab is available in a Simulated Live Stream Block that provides information on:
- The overall rating of the expected experience produced by the Block
- An analysis of the Block’s configuration, including any potential issues
- Hints and tips for improving the Experience, based on a set of pre-configured rules
- A timeline that displays each Transition in the Block and the durations between them
#### Experience Rating Interface
If the Block encounters at least one experience rule warning, it will appear next to the Canvas Edit button in the Canvas view, as shown below:
****
In the Canvas Detail view, the warning badge will appear next to the Layout tab:
****
In the Canvas Layout view, the warning badge will appear next to the "Edit" button for the specific Block(s) generating the warnings:
****
**Note:** As shown in the image, the inactive Simulated Live Stream Block shows a warning because all newly created Blocks will show a warning until they are configured.
On the Block Detail page, the badge will be displayed on the Experience tab:
****
The Experience Tab itself shows the overall rating, a list of detected issues, and the Transitions timeline, indicating each transition between states. A freshly created Block will likely show two high-severity issues due to a lack of configuration:
****
Once the Block is fully configured with all the correct settings, it will appear with an ‘excellent’ rating:
****
#### Experience Rules
**Rating Severity**
The Experience Tab will produce a series of messages in the portal based on potential issues, each rated at different levels of severity: "low", "medium", and "high":
- **Low:** Intended for configurations that could be valid but are not optimal based on our experience (e.g., insufficient pre-roll time)
- **Medium:** For configurations that may not adversely affect user experience but appear unprofessional (e.g., displaying a "stream not found" message before the pre-roll starts)
- **High:** For critical issues that will cause content to fail or be hidden (e.g., content starting before block reveal)
**Experience Validation Rules**
The following is the list of Experience Validation Rules along with their severity levels, and what attendees will actually experience if each one isn't resolved:
| **Rule** | **Severity** | **What viewers see if this isn't right** |
| --- | --- | --- |
| Pre-roll length must be set | High | Without this, the Block can't calculate a valid streaming start time, so content will fail to stream. |
| Pre-roll should begin before the Block is visible | Medium | If the Block becomes visible before pre-roll has started streaming, viewers will see a "Stream Not Available" message until pre-roll begins. |
| Pre-roll should be at least 10 minutes in length | Low | Viewers arriving right as the canvas opens may not have enough pre-roll to comfortably settle in before your main content starts. |
| Content start must be set | High | Without this, the Block has no reference point to calculate when streaming should begin. |
| Content start should be after block reveal | High | If content starts before the Block is revealed, part of your pre-roll (or content) will play with nobody able to see it. |
| Content start should be after the canvas reveal | High | Same issue as above, at the canvas level. Content may start streaming before viewers can access the canvas at all. |
| Content start should be before the block hide time | High | If the Block hides before your content finishes, viewers lose the stream mid-session. |
| Content start should be before the canvas hide time | High | Same issue as above, at the canvas level. |
| Simulation ends should occur after the Block disappears | Medium | If your video (including post-roll) finishes streaming while the Block is still visible, viewers will see the stream end and a "Stream Not Available" message, as though something has gone wrong. |
| Simulation ends should at least be 2 minutes before the Block disappears | Low | Cutting it too close to the Block's hide time leaves no buffer if timing drifts slightly. |
## Video On Demand (VOD) Block
The Video On Demand feature provides native on-demand video playback functionality.
#### Upload a Video On Demand asset
1. Select **On Demand** in the left navigation
2. Select **Add New Asset**
3. The **Video** button will automatically be selected under the asset type
4. Provide a unique label for the asset
5. Upload the file by dragging and dropping it into the specified area, or clicking on the area to browse and select your file
The asset will be labelled as "Processing". Once fully uploaded, it will appear in the On-Demand asset list and will be available for selection within a Block. To view more information and preview the asset, select View on the right-hand side.
#### Apply a Video Asset to a Block
1. Navigate to the **Canvas**
2. Go to the **Layout** tab
3. Add a Video On Demand Block or select an existing Video On Demand Block
4. Click on **Configure**
5. In the Configuration tab, choose your video asset from the drop-down menu (titled Select Video Asset). A preview will be provided for your convenience.
6. Customise the Thumbnail by specifying the timestamp at which the desired thumbnail displays on the video under 'Timestamp of thumbnail’
7. You can upload a Preview Image to be used as the video thumbnail; the recommended size is 1920px x 1080px
8. Optionally, you can select Autoplay if you want the video to play automatically when the page opens. Please note that this feature may only work with supported clients.
9. Make your block active in the **Details** tab and select **Save**
# Registration data file requirements
The phrase 'data in equals data out' is especially true regarding attendee experiences at events and the insights derived from attendee behaviour post-event. We believe in the importance of planning and agreeing on the data transfer schedule early on to ensure the timely delivery of attendee data. Below are our expectations for receiving data and best practice guidelines:
### **Timing**
At the outset of a project, we will establish a schedule for delivering both test and production data files. This schedule will be carefully determined based on the expected workload required to process a data file for import. We plan to receive one test file followed by the production registration data file.
### **Factor influencing the Data Schedule:**
- **e-Ticket communications schedule:** All required data must be in Jomablue to send attendee e-tickets
- **App release schedule:** If the event App is to be released 2 weeks prior to show day, attendee data must be imported into Jomablue before this date
### **Impacts o** **n timing**
We will strive to create a delivery schedule that suits you and understand that changes may occur. However, it's important to note that delays in delivering the test data file or providing data files in a different format/structure than agreed upon may affect the timing of importing event data.
### **Structure & Format**
To facilitate a speedy and hassle-free data import, we have a standard template that we encourage you to use, ensuring all event data files are consistent. Below are examples of the registration data fields we collect:
- **Basic information:** First Name, Last Name, Company, Job Title, email, mobile
- **Session entitlements:** Whether an attendee is entitled to any restricted sessions
- **Item entitlements:** Whether an attendee is entitled to collect physical items at the event
- **Categories:** Delegate, exhibitor, VIP, speaker, media
- **Other custom information:** This will be determined at the outset and refers to any information maintained within the Jomablue portal
### **Acceptable File Formats**
- Google sheets
- Microsoft Excel
- CSV files
### **Data Cleanliness**
Dirty data can significantly impact the attendee experience, and we understand that cleaning data can be time-consuming. However, it's important that we work together to ensure proper data cleaning is conducted before the file transfer. Here are some guidelines for data cleanliness:
- **First Name, Last Name Company and Job title:** Should not contain any leading or trailing spaces
- **Mobile Numbers:** Must be in international format (e.g., +61400000000) and should not contain spaces, brackets, or hyphens
- **UIDs:** Should be consistent when identifying records within your CRM
### **Delivery & Security**
Data security is a primary concern, particularly when it concerns attendees’ personal information. As such, we ask that data file deliveries adhere to the following guidelines:
- Delivered files should always be encrypted before being handed over to Jomablue
Although not recommended by Jomablue, if files are sent via email, they must be password-protected, and the password should be communicated via another means (e.g., via SMS)
- Access to files should be determined and maintained from the outset
# Communication management for Email and SMS
## Emails
Some corporate email servers have spam filters that can prevent certain emails from reaching their intended recipient. Research indicates that 1 in 5 commercial emails never reach the desired inbox [source: [https://returnpath.com/).](https://returnpath.com/)This can be frustrating and, on the surface, may appear inexplicable. While we cannot resolve every ‘email not received’ issue, Jomablue offers tools to help clarify these issues.
#### How Jomablue sends emails
- Jomablue sends an “envelope” to our email servers that contains an email for a recipient. It has instructions that say “Send this email to a specific person”
- The email servers receive the envelope and send a notification back to Jomablue to confirm receipt and the intent to send an email
- The Jomablue email server then sends the email to the recipient’s email server
- Once the recipient’s email server receives the email, it notifies the Jomablue email server that it can deliver the message to the employee’s inbox
- At that point, the recipient's email server tells Jomablue email servers, “You can consider this email as delivered.” From this point, Jomablue loses visibility of the email’s status, which could mean the recipient’s email server fails to deliver the email, places it in a quarantine queue, or marks it as spam/junk.
#### The more technical side
- Jomablue undertakes several measures to ensure smooth email operations:
- Monitors blacklists to ensure no Jomablue-owned domain appears on any email blacklist
- Tracks email sending reputation scores
- Regularly runs testing tools like Litmus and ReturnPath
### Why a recipient may show as Inactive
A recipient's email status will display as Inactive for one of the following reasons:
- **Hard bounce** - the recipient's email server permanently rejected the message (e.g. the address doesn't exist)
- **Spam complaint** - the recipient marked a previous email as spam/junk
- **Manual suppression** - the recipient was manually marked inactive in Jomablue
- **Unsubscribe** - the recipient clicked Unsubscribe on a previous email
If you're troubleshooting why a recipient appears Inactive, checking their subscription status is a good first step before assuming a delivery issue. See How to Unsubscribe and How to Resubscribe below for more on the unsubscribe-related cause.
### Resolve emails not being received
- If email messages end up in Junk, move them to your inbox to help your spam filters learn
- Ask your IT department to whitelist the domains '[jomablue.com](https://jomablue.com/ "https://jomablue.com/")' and '[event-email.io](http://event-email.io/ "http://event-email.io/")'
- For attendees, check the **Jomablue > People** section to ensure that the contact details are correct
- For Users, check the **Advanced > Users** section to ensure that the contact details are correct
- The person may have unsubscribed. See section **How to Resubscribe** below.
### Unsubscribe or Resubscribe a person from receiving Emails
Emails from Jomablue may include campaigns for e-Tickets, general correspondence, Surveys, Vendor correspondence, and requested information from Touchpoints.
#### How to Subscribe
By default, all People added to Jomablue are subscribed to email notifications, provided a valid email address is available. These emails may include various campaigns, correspondence, and requested information from Touchpoints.
#### How to Unsubscribe
All email notifications include an Unsubscribe option, which recipients can select to prevent future emails from being sent. Clicking this link will unsubscribe them.
**Notes:**
- Once a person unsubscribes, their email status will display as Inactive, which is one of four possible causes for this status. See Why a recipient may show as Inactive above for the full list.
- Unsubscribing applies instance-wide. A person who unsubscribes will stop receiving emails from all events within the same Jomablue instance, not just the current one. If this was unintentional, see How to Resubscribe below.
#### How to Resubscribe
If a person has unintentionally or deliberately unsubscribed from emails, they can easily resubscribe by following these steps:
1. Locate any email from a Jomablue event within the same instance (e.g., customer)
2. Click on the **Unsubscribe link**
3. Once redirected to the unsubscribe page, click the **Resubscribe** button
4. View the confirmation
**Notes:**
- Unsubscribing will stop emails from being sent from Jomablue for that instance. However, if a person has interacted with a Vendor, they may still receive emails directly from that Vendor (external to Jomablue), from which they can opt to remain subscribed or unsubscribe
## SMS
### Unsubscribe or Resubscribe a person from receiving SMS
To prevent a user from receiving any SMS messages, please follow these steps:
1. Navigate to People
2. Search for and select the relevant person
3. Select **Advanced Tab**
4. Under Privacy, set **Unsubscribe from SMS** to **Yes** or **No** as required
5. Press **Save**
**Note:**
- This will include marketing and transactional SMS messages, including important e-Tickets or Event surveys, which may impact the event attendance experience
- You can resubscribe them at any time by changing the value back to No
- An option to unsubscribe should also be included in SMS broadcasts. This could be as simple as instructing the user to “Send STOP” to a designated phone number.
- You can use the People Imports feature if you have a large number of records to update. Within People Imports mapping, select SMS send permission and apply the relevant rules.
**Example:** Unsubscribe from a People record:
****
# Jomablue CX
Jomablue CX is a free app available for download from the Apple App Store, designed to empower event teams to:
- Quickly and easily manage arrival for events of any style or size
- Deliver a lightning-fast arrival experience
- Choose between Badgeless check-in or select from various badge styles suitable for your event, such as Name Label or Name Badge
- Become truly mobile delivering events anywhere in the world with online and offline modes
- Reduce the number of staff needed for event check-in
For a quick start, please see these videos:
[Effortless Event Check-In with Jomablue CX](https://www.youtube.com/watch?v=DaZiIgjcIss "https://www.youtube.com/watch?v=DaZiIgjcIss")
[How to manage check-in from your iPhone or iPad with Jomablue CX](https://www.youtube.com/watch?v=AjtvNbBpNmw "https://www.youtube.com/watch?v=AjtvNbBpNmw")
### Software and Hardware Requirements
- Apple iPhone or iPad running iOS 15 or newer
- Jomablue CX app (available free in the Apple App Store)
- Printers: for additional information, please see the article: [Jomablue Event Kit](https://jomablue.bolddesk.com/kb/article/199/jomablue-event-kit).
### Badges, Labels and Badgeless options
Jomablue CX provides the following options based on your events’ requirements:
- Name Badges: customisable (branded) paper stock that can be attached to a lanyard, with an option for double-sided printing
- Name Labels: adhesive name labels that can be used independently or affixed to a backing card
- Badgeless Check-in: recording attendees’ arrival without printing labels or badges
For additional information, see the section below: **Print labels and badges.**
### Security Features
For security purposes:
- There is no option to export lists or bulk import people via the Jomablue CX appIn offline mode, data is encrypted and securely stored on the device. Users can choose to purge this data.
- All data is deleted when the app is uninstalled
- Two-factor authentication is enabled by default, so keep your phone nearby while logging into
- Jomablue CX
- Always log out of Jomablue CX if you won't be interacting with it for a while
### Reporting and Insights
Jomablue CX features a real-time counter and bar graph to display check-ins versus registrations. For more in-depth insights and reporting, please log in to the Jomablue Portal. Note that checking people into a badgeless event still counts as a "badge print," and this will be reflected in all insights and reports within Jomablue.
### Set up Jomablue CX for your event
1. If using your own iPhone or iPad, download the free Jomablue CX app from the **App Store**
2. Open the **Jomablue CX app**
3. Enter your platform URL, which will be your instance name
e.g., yourinstancename.jomablue.com
4. On the login page, enter your email and password for your instance within the Jomablue portal
5. If attendees are self-serving, please enable the “Self Check-in Mode” option prompted when logging in
**Note:** To enable/disable this mode, you must log out and back in, due to the way Jomablue CX encrypts your data for Self Check-in
6. Go to the **Upcoming EventsNote:** Jomablue CX doesn't have a fixed maximum number of Person records. Actual capacity depends on the number of Categories and Custom Fields assigned to each Person - more of either means fewer total records the event can support. As a reference point, approximately 6,000 Person records will typically download and perform reliably; contact Jomablue to confirm capacity for larger or Category/Custom-Field-heavy events before your event date.
7. Select your **event**
### Check people in
1. Select the **QR** **code** button to scan attendees’ e-Tickets using the device's camera; or
2. Use the search bar to find an attendee and check them in manually
**Note:** search for attendees by first name, last name, full name, email address, or company.
### Add people via the Jomablue CX app
1. To add a new attendee on-site, select the People icon in the top right corner
2. When adding people manually or checking people in offline, ensure you swipe down to refresh the attendee list for data synchronisation
**Note:** People added through your Portal are automatically synced to all Jomablue CX apps with your event downloaded on the device. Syncing occurs regularly.
### Print labels and badges
1. Connect printers and adjust badge layouts by selecting the **Settings cog** in the top right corner
2. Select **Badge Printing**
3. ****Connect your printer and update your badge design
4. Easily toggle Badge design settings as needed
**Note:** See Add Custom Fields to Name Badges and Name Labels below to print categories or other custom fields.
5. Test print your badge design by selecting **Print Test Badge** at the bottom of the screen
**Note:** When using Jomablue CX Name Labels and Name Badges, a recommended distance of at least 3 metres between your printer and the IOS device running Jomablue CX. This allows attendees sufficient time between getting their e-Ticket scanned and their badge printed, ensuring a smooth check-in process.
### Add Custom Fields to Name Badges and Name Labels
To include custom field data on a Name Badge or Name Label:
1. In your Jomablue Portal, define a custom field under **Settings** in your event
2. Navigate to the **CX Custom Fields** tab and select the desired Custom Field for printing on the left, centre, or right side of the Name Badge or Name Label
Note: A maximum of 3 custom fields can be printed on Jomablue CX Name labels and Name Badges
3. In Jomablue CX on each device, enable the required Left, Centre or Right Custom Field (see below)
4. Ensure this Custom Field is filled by updating People records manually or via an import
**Note:** Category Codes defined within Jomablue Categories apply only to Smart Badges. If using Jomablue CX for Name Badges or Name Labels, you must add Custom Fields to print on the badge or label.
### Enable Custom Fields to print in Jomablue CX
1. Open the **Jomablue CX** app
2. On the events selections screen, select **Settings** (the cog at the top right)
3. Select **Badge printing**
4. Choose **Edit Badge Design**
5. ****Select **Elements** (bottom right)
6. Enable the Left Custom Field, Center Custom Field or Right Custom Field as needed, place in the desired location and update the element settings
7. Press **Save** on the Badge Design screen
**Notes:**
- If using your own device, install the app in advance of your event
- Jomablue CX doesn't have a fixed maximum number of Person records. Actual capacity depends on the number of Categories and Custom Fields assigned to each Person. As a reference point, plan for up to approximately 6,000 Person records per event, and contact Jomablue to confirm capacity for larger or Category/Custom-Field-heavy events.
- We recommend downloading your event the night before the event to allow for your check-in data to be loaded
- When your event is finished, it will automatically be moved into the Past Events tab
### Go on-site with a Jomablue Event Kit
For information on setting up Jomablue CX with your Event Kit, please see the article: [Jomablue Event Kit](https://jomablue.bolddesk.com/kb/article/199/jomablue-event-kit).
## Referenced articles
[Jomablue Event Kit](https://jomablue.bolddesk.com/kb/article/199/jomablue-event-kit)
# Release 9.58.0
## Improvement
### New Merge Fields for Event Details in Email Templates
Email templates can now pull event details in automatically, so key information doesn't need to be typed in by hand each time a campaign or notification is built.
Six new merge fields are available across all email template types:
- Event Name
- Venue Name
- Venue Address
- Event Start Time
- Event Finish Time
- Event Short Description
Start and finish times display in the event's configured time zone, so recipients always see the correct local time regardless of where the email is sent from.
These fields sit alongside your existing merge fields in the template editor's merge field picker, and can be combined freely with them.
**Note:** These fields are available in Email Templates only. They are not currently supported in SMS templates.
****
### Event Selector Now Groups and Filters Events in the Page Editor
The Event list now separates Active Events from Past Events. This makes it faster to find the event you're looking for, especially on instances with a long event history.
Archived events no longer appear in the list. If a page is already linked to an event that's since been archived, that event still displays as the current selection so the page keeps its association, but it can't be selected again for a new page.
****
# Release 9.43.0
## New Feature
### Explore People - Add Static Columns at specific locations
This update introduces the ability to add static columns to the Explore People results table, giving users greater control over data presentation. Static columns can be assigned custom names, set with fixed values, and positioned either at the beginning of the table or directly after any existing column. The functionality aligns with existing column renaming behaviour, ensuring a consistent user experience. Additionally, column reordering via drag-and-drop within the data table is now tracked, supporting more flexible and auditable layout adjustments.
### Create Vendor Tags in the Vendor Portal
Users can now create custom tags directly within the Vendor Portal. These tags support improved categorisation, filtering, and management of vendor records for more efficient organisation.
The Vendor Portal has been refreshed with an updated interface and additional tabs for enhanced navigation.
###
Automatic field mapping for People Imports
The People Import process has been enhanced with automatic field mapping capabilities. Instead of requiring manual column mapping, Jomablue automatically matches import columns to appropriate fields, including standard fields and custom fields already configured for the event. Columns that cannot be matched are automatically set to “Ignore” for manual review.
### Custom Domains support for Pages
Pages have been updated to support custom domains. This implementation prepares the platform for the upcoming Single Page Registration feature.
### Export Archive of All Vendor Leads
This update adds a secure bulk export feature for vendor leads, available exclusively to trusted admins, owners, and super users. The feature is accessible via **Vendors → Actions → Export Lead Archive**. Users are then prompted to confirm the action, which generates a ZIP file containing one CSV file per vendor.
Files are named clearly, duplicates are handled separately, and the total matches the vendor count. Export progress is shown in real time, and the action is logged to the event log for visibility in Event Insights. This streamlines lead retrieval for high-volume or internal vendor setups.
## Improvement
### Campaign Recipient Preview now allows searching by full name
The Campaign Wizard name search has been enhanced to support full name searches when selecting recipients for Campaign Preview. This expands the previous capability that was limited to searching by either first or last name.
### Registration Theme Editor JSON Keys Now Alphabetically Sorted
In the Registration Theme advanced settings, JSON keys and values are now sorted alphabetically by default. This replaces the previous sorting by key length, making it much easier to find and work with specific settings.
# Release 9.36.0
Release Date: 21st March 2025
## New Feature
### French Language Set Added to Localisation
French is now available as an option for localisation sets.
****
### Minimal Display Mode for Registration
This mode offers a minimal UI experience for free registration. It includes the following changes:
- Removed Site Title
- Countdown timer is hidden until 5 minutes before expiration
- Confirmation page warning is now hidden
- Validation icons are removed
- Arrows on back and forward buttons are removed
- Additional product details, including the ‘Show More’ button, are removed
- Site descriptions are no longer required
****
Minimal Display mode for registration
### Registration and Site Images No Longer Restricted by Height
Site and Registration Images can now support taller images, as long as they are 1344 pixels wide (smaller images will scale unpredictably). While the recommendation is still to use dimensions of 1344 x 200, taller images can be uploaded, and the registration site will display them appropriately.
****
Increased height Site Header Image
### Human Verification Added to Free Registration to Prevent Spam Submissions
An invisible verification mechanism has been implemented to ensure the registrant is a human and not a bot. If this verification fails, the user will be prompted to solve a CAPTCHA when they press “Register Now” from the Store or submit their registration (the final step). Most legitimate users will not notice this process, but those using VPNs, who were previously blocked, will now have access after solving the CAPTCHA
****
Upon pressing 'Register Now' the person was prompted to solve the CAPTCHA
**Caption**
Example of the CAPTCHA displayed
## Improvement
### Preventing Whitespace in Vendor Tags
Vendor Tags created in the portal will now enforce the use of a dash between words instead of whitespace. For example, “Hot Lead” will now appear as “Hot-Lead.” Existing or currently in-use tags will be converted to use dash upon release.
****
New and Existing Tags with spaces are converted to use dash
## Known Defect
### Infinite Loading When Accessing Unpaid Admin Orders
A fix has been implemented for the infinite loading screen that appeared when accessing an unpaid order.
### Resolved Issues with Mobile Number Field in Registration
Two issues with the mobile number field during registration have been resolved:
- Registration theme customisation is now correctly applied to the field
- An issue with mobile phone number validation has been resolved, ensuring validation is correctly applied after manual editing or pasting in values
# Release 9.30.0
Release Date: Friday 11 October 2024
## New Feature
### Updated Maintenance Mode Page
The maintenance mode page has been enhanced to provide specific messaging when a subscription has expired. Instead of displaying a generic error message, it now shows “Not available. The subscription for this service may have expired”. This message appears after a customer’s subscription end date, which is manually set by the product team.
### Improved Font Consistency
Fonts have been updated to ensure consistency across different browsers. The weight of the fonts now derives directly from the font itself rather than the browser, leading to a more uniform appearance.
## Improvement
### Enhanced Front-End Validation for Registration Theme Customisation
We have tightened front-end validation to prevent users from bypassing it by using double hashes (##) in the colour fields.
## Known Defect
### Scrollbar Removal and Autosave Functionality Adjustments
Excessive scrollbars in the Registration Theming UI has been removed, and issues related to unintended autosaving have been fixed.
### Registration UX Labels Bug
A bug that caused Registration UX labels to be retrieved incorrectly has been resolved.
### Duplicate Event Modal Scrollbar
A scrollbar has been added to the duplicate event modal to ensure it displays correctly on smaller screens.
### Incorrect Text Display in Order Detail - Advanced tab
The text displayed when an order contains only add-ons has been corrected. It now properly shows “There are no products in this order” when applicable.
### Campaigns Page Button Link Issue
An issue where a button on the campaigns page linked incorrectly when no campaigns existed has been fixed. The “Create a Campaign” button now correctly links to the campaigns page instead of the template page.
# Orders
Here is an overview of the Orders pages used for Paid Registration.
****
#### Number Of Orders
****
This widget displays the total number of orders with a status of **payment\_received.**
****It does not include orders awaiting payment (payment\_pending), cancellations, or orders with failed transactions.
#### Orders Today/This Week
****
#### Orders Today
This shows the number of Orders with a status of payment\_received made from 12:01 am until 11:59 pm today. Cancelled orders or orders with failed transactions are not included.
#### Orders This Week
This indicates the number of Orders with a status of **payment\_received** made from 12:01 am Monday to 11:59 pm Sunday. Again, cancelled Orders and failed transactions are excluded.
**Note:** The ‘Week’ count includes the 'Today' counts.
### Products Ordered/Registered
The Products Ordered/Registered widget shows the number of products within orders that have a status of 'payment\_received' (products ordered) and the number of registrations within those orders. This count excludes failed transactions, cancelled orders, or pending payment orders.
The difference between the Ordered and Registered numbers indicates the extent to which purchasers have activated their registrations. Ideally, these numbers should be identical or very close, indicating that every Product sold has a Registered person. If there is a significant discrepancy, it may be appropriate to send reminders to customers 1-week post-purchase to encourage them to activate their Registrations.
#### Gross Sales
****
This section displays the total monetary value of all order totals combined. Only orders in 'payment\_received' status contribute to the gross sales total. If an order was 'cancelled' and an adjustment fee was withheld, it will still be counted in Gross Sales.
The amount includes any applicable taxes and is rounded to two decimals. Gross Sales represents the actual amount received, excluding any payment\_pending Orders but including fees withheld from cancelled orders.
#### Awaiting Payment
****
The first digit indicates the total number of Orders awaiting payment (payment\_pending). This includes all orders that were not paid for immediately through a credit card
The second figure shows the total monetary value of all orders that remain in payment\_pending status. As orders are marked as payment\_received, this value will decrease while gross sales will increase.
Orders that have this status are typically admin orders or those checked out using the Pay by Invoice option.
**Note:**
- An Order may contain one or many Products
- The displayed amount includes tax
- The displayed amount is rounded from 4 decimal places to 2 decimal places
- You can view a list of the Orders Awaiting Payment by clicking on the **Orders Awaiting Payment** tab next to **Recent Orders**
#### Search Orders
You can search for orders using the Billing Name, Billing Email, or Order ID. Clicking on a search result will open the order details.
When searching by Order ID, ensure that the entire Order ID is entered before results appear.
Keep in mind that a Person's details may not always match the billing details on the Order where their Product was purchased, making it difficult to locate a Person's Order using the search function alone.
To locate the corresponding Order record from a Person record, navigate to the Person record and click on the **link below their name** (see below):
****
#### Recent Orders
This section presents a reverse chronological list of recent orders, which includes both Product and Addon orders. This display includes orders with failed transactions, cancelled orders, and payment\_pending orders.
#### Unpaid Orders
This is a filtered list of orders with a status of "payment\_pending". These orders likely resulted from customers checking out through 'Pay by Invoice' or were created as admin orders.
#### Free of Charge (FOC) Orders
If an FOC admin order is created, it will automatically be marked as FOC with a status of 'payment\_received'. Therefore, these FOC orders are included in the relevant metrics above (e.g., Number of Orders, Orders Today/This Week, Products Ordered/Registered).
Below is an example of how an FOC order is represented in Recent Orders. Notice that the status is 'payment\_received'.
#### Order and Product Status
Orders are defined by a financial transaction and must contain at least one item of value, either a Product or an Add-on item. It's important to consider the status of Orders and Products together, as they are directly linked.
Order Status: payment\_received
****
In the screenshot above, payment has been received. This can be either a credit card or manual payment. At this stage, all Products on the Order are ready for the next step: Activate Registration.
**Available Transitions:**
- payment\_received -> cancelled
**Product Status:**
Products associated with an Order in the payment\_received status can be in one of two states:
- **registered**: The Registration has been Activated (a person has completed the Activate Registration form), and now has a Person Record at the event.
- **unregistered**: The Registration has NOT been activated, but is available for someone to activate their Registration.
#### Order Status: payment\_pending
****
In this example, the order has been created, but payment has not yet been received. Orders transition to this status when the 'Pay by Invoice' option is selected during Site checkout or when Admin Orders are created (which includes Products and Addons). While in this status, Products can't be activated, and the links for Activate Registration will not function.
**Available Transitions:**
- payment\_pending -> payment\_received
- payment\_pending -> cancelled
**Product Status:**
Products associated with an Order in the payment\_pending status can only be in one state:
- **unregistered**: Products linked to an Order with a status of payment\_pending can't be activated until payment is completed. Therefore, these Products remain unregistered and inaccessible to people for activation until the Order changes to payment\_received.
#### Order Status: cancelled
****
When an Order has been cancelled, it invalidates any Registration Activation links. If Registrations have already been activated, there is an option to preserve the Person Record during cancellation. Orders can't transition from this status.
**Available Transitions:**None
**Product Status:**Products associated with an Order in a cancelled status can only be in one state:
- **cancelled:** Once an Order is marked as cancelled, all Products within that Order are similarly marked as cancelled. In this state, Registration Activation can't be accessed.
#### Order Status: transaction\_error
****
This status results from a failed credit card transaction. The Order record remains because Orders are generated before payment is complete. Orders in this status can't be transitioned, and a new order must be created to attempt payment again.
**Available Transitions:**
None
**Product Status:**
Products associated with an Order in the transaction\_error status can only be in one status:
- **order\_incomplete:** When an Order Status is transaction\_error, all Products within that Order are marked as order\_incomplete. In this state, Registration Activation can't be accessed.
## Find an Order ID
To find an order, follow these steps:
1. Navigate to **Orders**
2. Search for an order or select one from the table view
3. The order detail screen reveals the Order ID
****
## Create FOC and Admin Orders
Admin Orders are Orders created by you, the Jomablue administrator. They offer the following benefits:
- They bypass inventory limits imposed on Site visitors
- They allow you to customise the Products and Items included in an Order without being restricted by Site configurations
- They allow you to accept payment methods other than credit cards
- They provide a way to make an Order 100% free-of-charge (FOC)
Once an Admin Order is created, you can either send the invoice to the recipient or share the Registration Activation links directly.
**Note:** Admin Orders are only available for Paid Registration.
### Create an Admin Order
1. Navigate to **Orders**
2. Click on **New Order** at the top right of the screen
****
3. Select the **Payment Method**
4. ****Enter a purchase order number (optional)
5. Populate the billing details (required, even for free-of-charge orders)
****
6. Click **Add Product** to configure your Product and Order Items
7. Configure the Product and ensure to add any required Items
8. Select **Add to Order** ****
**Note:** You can easily duplicate the Product and Item configuration after it has been added to the Order.
9. Finally, click **Generate Order** (top right). Your Admin Order will appear at the top of the Recent Orders list.
****
**For FOC Admin Orders:** The Registration links can be shared/used immediately
**For paid Admin Orders:** The Order must be marked as payment\_received before the Registration links will work.
### Register an FOC Admin Order
Once an FOC Admin Order has been created, the Registration Links within the Order can be shared or used immediately. To access the Registration links, locate the Order you created in the Recent Orders list as described above.
To share the Registration Link(s), use the **Send Reg Links** button at the top right corner of the Order view (see below).
To access individual Registration Links, click the **Copy Registration** button to copy the Registration Link to your clipboard (see below). These can be registered straight away or shared manually if desired.
****
## Cancel an Order
1. From the Orders page (located in the menu on the left), find the relevant order using the search bar and click on the order name
2. Click on the **Cancel Order** button in the top right corner of the Order Details page
3. Select **refund method** (manual refund method should be used for cash onsite; credit card is the default)
4. Provide details for the 'Reason for cancelling the order' beneath 'Adjustment Fee', specifying any cancellation fees if applicable
5. Click **Cancel Order** once you have entered all the required details
6. To send the person an invoice detailing the cancellation fee, click the **Send Invoice** button in the top right corner of the page, and enter their email address.
## Complete 'Payment Pending' Orders
There are several ways a person can pay an invoice, whether it is from an admin order or through the 'Checkout by Invoice' (if enabled on the site).
**Payment Methods**
- **Credit Card**
The self-service option. Recipients of the invoice can follow the link included at the bottom of their invoice to pay by credit card. This link directs them to the payment gateway used for the event.
- **Manual Payment (EFT, Check, Cash)**
Manual payment options include EFT transfers, cheques, or cash. Once the invoiced amount is received, the order status in Jomablue can be updated to payment\_received.
### Payment via Credit Card
The most common way to receive payment is by Credit Card. Each invoice contains a unique URL link for that order. The recipient can enter their credit card information and process the payment immediately.
****
****
Payment via Credit Card (as opposed to Manual Payment) saves you time as the process is completely automated and requires no intervention from your Event Team.
Once paid, an updated invoice and registration link are automatically sent to the recipient, allowing them to activate their Registration.
### Manual Payment
Manual Payment refers to receiving funds through alternate means to Credit Card Payment. Generally speaking, this is by EFT.
The manual payment instructions are configured on the Registration tab and are included at the bottom of the invoice and on the Invoice Payment Page.
**Note:** The Manual Payment Instructions text is limited to 191 characters
****
****
After making a Manual Payment, the Site visitor can notify the Event Team about the payment. This step is optional, and the notification link is included in the footer of the invoice. The notification will appear in the Order Log associated with that Order.
****
Once you confirm receipt of the funds (e.g., after bank account reconciliation), you can update the Order status to “Payment Received.” This action will automatically send an invoice and registration links to the user.
****
### Cancel a Payment Pending Order
**Self-cancellation**
For orders with a payment\_pending status, users can cancel their order before the funds are received. To do this, they can click cancel this order on the Payment Required page and then provide a reason for the cancellation. No email communication is sent after the cancellation is confirmed.
**Administrator Cancellation**
Alternatively, Jomablue administrators can cancel the order by pressing **Cancel Order** on the Order Details page.
**Cancel Addon Order as an administrator**
Jomablue administrators can also cancel an Addon Order stuck in payment\_pending status that is intended to be paid by credit card. This situation may occur if a user enters their billing details, submits them (creating an Order in Jomablue), and then navigates away from the credit card payment screen. This commonly happens with Stripe or Braintree payment gateways.
When cancelling an Order in payment\_pending status, a modal warning will appear, asking for a reason for the cancellation.
If a cancelled Order attempts a payment, the user will see an error message indicating that the order has been cancelled**.**
## Add Notes to Product Orders
Free text notes can easily be added to any order, including cancelled or failed orders.
They can be used to:
- Keep track of who made adjustments to the order
- Note who generated or placed the order from your team
- Document correspondence with the Billing User.
**Important considerations:**
- Notes can't be edited once created
- Created notes appear in the Logs tab
- It's advisable to include your name when creating a note to help others identify the point of contact for questions.
#### To add a note and view it:
- Click **Actions**
- Select **Add Internal Note**
- ****Enter your Note
- Press **Save**
- You can now view the notes in the Logs tab
****
Notes are kept in the log alongside any other interaction with the order (such as payments or refunds)
****
**Notes:**
- Notes can't be edited once saved, but you may add more notes.
- The name of the note creator is not automatically recorded, so it is a good practice to add your initials or name if you want others to know who wrote the note.
- Notes can only be added to Product orders (not add-on orders).
## Edit Billing information on an Order
Sometimes it is necessary to edit the billing details for an order.
To edit Billing Details:
1. Navigate to **Orders** via the left navigation menu
2. Search for the relevant Order
3. Select the **Order** you wish to edit
4. In the **Order Billing Details** panel (located at the top left), select **Edit details**
5. Update the relevant fields
6. Press **Save details**
**Notes:**
After the details have been edited, a log of all changes made (along with the user who made them) will be available in the Logs tab within the Order Details.
## Registration Support Requests
Jomablue Support Requests are designed to help you track, manage, and resolve registration-related queries and requests from your customers. Users with finance-level access and higher can access the Support Requests section.
To access Support Requests, navigate to **Registration > Support Requests** in the left-hand menu in Jomablue.
**Note:** While the Support Requests feature allows you to manage your Support Requests, communication via email must be done through your own email client, as sending and receiving emails directly through the Support Requests view is not supported
## How Attendees submit Support Requests
Attendees can submit Registration Support Requests upon registration for your Event. These requests can be accessed using a link in the confirmation Emails. See below:
****
If you are using a Custom Registration Confirmation Email, you can include the Support Request link in your Template.
For additional information, see the article: [Communication](https://jomablue.bolddesk.com/kb/article/179/communication).
## Types of Support Requests
Support Requests are categorised into three types:
- Cancellation Requests
- Transfer Requests
- Other
This categorisation helps you efficiently manage Cancellation and Transfer requests according to your event policies. Other types of requests may include:
- Changes to registration information
- Cancelling part of an Order (e.g., cancelling an Item ordered alongside a Product without cancelling the Product itself)
Below is an example list of Support Requests, each representing one of the three types:
****
### Handle Support Requests
When you first receive a Support Request, its status will be set to "Open.” Upon clicking on the Request, you will see the following view:
****
Here you can see:
- The date the request was created and the date it was last updated
- The details of the Person who made the request
- The Request type
- The initial Request message (submitted by the requester)
- Internal Support Request Notes
- Request Status
The Notes field is for internal note-taking use only, meaning the requester will not be able to see these notes. This is intended for larger support teams where requests may be handled by multiple people, providing a central place to store information about that request.
The Status field is a drop-down menu that allows you to set the Status of the Support Request.
This does not affect what the requester sees; it serves as an internal indicator. The available options are:
- Open (all requests are set to Open upon submission)
- Closed
- Waiting on External
- Transferred
Changing the status of a Request will alter its colour in the list of Requests. See below for an example:
****
## Jomablue Order data available in Stripe
During the payment process for Paid Registration, we pass the following 'Metadata' to Stripe for each transaction. This metadata is structured data attached to each order, which can be found in Stripe and exported as a file in CSV file.
The following fields are included in the metadata that is passed from Jomablue to Stripe during the payment process for Paid Registration:
- **Jomablue\_event\_id** - the numeric ID for this event, visible on the event selection page in Jomablue portal (located at the bottom left of each event, as shown below)
****
- **Jomablue\_event\_name** - The name of this event
- **Jomablue\_public\_order\_id** - The order number, which is searchable on the Orders page in Jomablue Portal and visible on the Order Details page (beneath the page header)
- **Jomablue\_private\_order\_id** - The numeric ID for this order
### Export the Stripe payments
1. Log into your Stripe account and export Payments
2. Locate and open the CSV file in your downloads
3. The last 4 columns in the file correspond to the fields detailed above
### Reference Order data in Jomablue
1. Select the **event**
2. Go to **Registration > Financial Reports** in the left navigation of Jomablue
3. Select **Generate Report** within the **Order Summary** section
4. Locate and open the CSV file in your downloads
5. Identify the Jomablue order data:
- - Column A (id) = Jomablue\_private\_order\_id in the Stripe export
- Column B (public\_order\_id) = Jomablue\_public\_order\_id in the Stripe export
## Transaction Errors in recent Orders
**Why do I see 'transaction\_error' in the Recent Orders list?**
In Jomablue, every financial transaction (regardless its status) is directly linked to an Order. In other words, a financial transaction can't take place without an order being generated first, which occurs automatically in the background.
It’s important to note that the Order ID is passed to the payment gateway. Therefore, users must generate the order before payments are sent to the payment gateway.
When a financial transaction fails, the Order ID still retains all the details associated with the Order. Although an Order is created, the Products and Items within that order were never issued or removed from inventories.
Therefore, it is safe to ignore the transaction\_error rows listed in 'Recent Orders'.
**Transaction Error Followed by a Successful Payment**
****
It is common to see an order with 'transaction\_error' followed by a successful payment (payment\_received) with the same Billing details. This situation typically arises when the user receives feedback such as 'Insufficient funds' or 'Do not Honour' while attempting to place their Order on the Site. This prompts them to try another credit card, which frequently results in a subsequent successful order.
**Note:** Feedback from the payment attempt is displayed to users and can also be seen under the **Order > Logs** tab. If their card is declined and a reason is provided by the bank (such as insufficient funds), both the user and you can view this information under the Order > Logs tab.
## Transfer a Registration
You can do the following steps when the Order is placed on a Site:
1. Find the Order
2. Navigate to the **Advanced** Tab
3. Identify the Product registered to the person cancelling their registration
4. Click on **Cancel Registration**
****
5. Provide a reason for the cancellation, including details on why and who approved/actioned the cancellation
****
6. Once confirmed, return to the **Order** tab. You can now copy the registration link and provide it to the person who will take that place.
7. The person who placed the order can manage this product from their Order Management link.
****
### Cancel and transfer a registration
1. From the Orders page (located in the left menu), find the relevant order using the search bar and click on the order name
2. From the **Order Details** page, select the **Advanced** tab
3. Locate the person registered within this order who needs to cancel
4. Next to their name, click on the small link entitled **Cancel Registration**
5. Add a note for the reason for cancellation (e.g., Replaced by Joe Bloggs)
6. Back on the Order Details page, under Ordered Products, click **Copy Registration Link** and email this to the relevant person to transfer the registration
7. This person will then be asked to fill out the registration form as normal
## Order and Registration Management FAQ
**Q: How do I send invoices?**
1. From the Orders page (located in the menu on the left), find the relevant order using the search bar and click on the order name. In the Order Details page, click on the **Send Invoice** button at the top right corner
2. A dialogue box will appear, automatically populating the email address associated with the Order. If you need to send the invoice to a different address, replace it with the desired address.
3. Click **Send** to send the invoice
**Q: How do I close registration on a Site?**
1. Navigate to **Registration > Configuration**
2. Click on the **Sites** tab
3. Select the Site you wish to close the registration for
4. Under the Active section, select **No**
5. Click **Save**
## Related articles
[Communication](https://jomablue.bolddesk.com/kb/article/179/communication)
# Block Types - Others
## Custom Ad Block
Custom Ad Blocks are a way for you to promote content, facilitate a call to action, or simply display content, including text and images. They also provide interaction data about who has loaded and who clicked on the Block.
A Custom Ad Block allows you to promote content and has two main components:
- A Title (text only)
- A Body (WYSIWYG content)
The Body can contain anything that can be displayed in a WYSIWYG Block, including formatted text and images
The Block can emulate a clickable button by adding an image of a button (one button per Block).
This is because the entire area of the Block is clickable, so if you associate a URL with the block, the user can click anywhere in the block to access that URL. An interaction is recorded when Custom Ad Blocks are loaded and clicked.
### Features of the Custom Ad Block
- The Block can be linked to an external or internal URL
- On click behaviour: Internal links open in the same window. External links open in a new tab
- Adding a link is optional (can display content only)
- The Block requires a unique ID to differentiate it from the other Ad Blocks in reporting
### Interactions available for this Block
When a Custom Ad Block is clicked on by a user, an interaction is recorded against the user's
Person record that provides information on who has clicked the Block. There are two interactions available for this Block:
- **Ad Loaded** (whenever an ad is loaded on the page)
- **Ad Clicked** (whenever an attendee clicks anywhere on the ad)
These Interactions can also be stored for post-event reporting and block automations. In addition, block metrics are available in a People Export. When a Community contains one or more Custom Ad Blocks, 2 columns will be added to the report for each Custom Ad Block.
Each Column has a header containing:
- The Block Type
- The Block ID
- The name of the Block (if provided)
- "Impressions" (ad is loaded on the canvas) or "Clicks" (the user clicks on the ad)
### Set up a Custom Ad Block
A Custom Ad Block allows you to promote content and provides you with interaction data about who has loaded and who clicked on the Block.
1. Go to the **Jomablue Portal** and log in with your email address and password
2. Click on **Canvases** under Community on the left-hand menu
3. Click on the Canvas type where you wish to add the Block (e.g., Lobby, Session, Vendor or Page)
4. Locate the specific Canvas where the Block will be added and click **Edit**
5. Click on **Layout**
6. Within a Flex, click **Add Block**. Here, a list of Blocks will appear. Select **Custom Ad.**
7. The Custom Ad Block is now added to the Canvas. You may now add a Title, Configure, Automate or Delete the Block.
### Configuration options
A Custom Ad Block can be configured via the Configuration tab in the Block Editor.
- **URL:** A link to a page is added in this tab. Internal links open in the same window, whereas external links open in a new window.
- **Is internal link:** Check this if the link leads to a page within the community app (external links open the link in a new window)
- **Track impressions:** Track the number of times the ad is loaded
- **Ad UID:** A unique ID to pass when tracking interactions with the ad is added in this tab. This makes it easy to do reporting.
- **Content:** Images & texts are added in this tab
## Image Block
A well-designed and well-placed image boosts attendance and can provide a wider reach to Community members. The Image Block specifically caters to displaying images on the Community pages.
The Image Block allows you to upload and display an image without any borders or padding. It provides a range of features, such as modal display options, as well as more advanced display options. It also supports a range of customisation features.
### Features of the Image Block
**Automatic Detection of Dimensions of an Image**
When configuring the Image Block, the configuration tab automatically detects the dimensions of the uploaded image. It adds them into the ‘Height’ and ‘Width’ fields. You can also manually modify the height and width values to display the image at different dimensions.
**Modal Configuration**
By checking the ‘Open in Modal Box’ option when configuring the Image Block, you can make the image clickable. The image then opens in a modal view, which is useful when a larger image is added but is displayed at a smaller size.
The modal is configured irrespective of the image itself through the following fields:
- **Modal Width:** Allows you to set the width of the Modal. This can be in pixels or as a percentage of the width of the entire screen.
- **Modal Max Width:** Allows you to place an upper cap on the width of the Modal
The modal max-width will always override the modal width field. For example, if a screen is 1000 pixels wide, and the modal width is set to be 800 pixels wide, but the modal max-width is set to 50%, then it will only display as 50% of the width of the page (e.g., 500 pixels).
**Responsive Fields**
Responsive fields automatically scale the image’s width and height so that they can work well on devices with widely differing screen sizes and resolutions. For example, the image will display at 250px by 250px on small devices, and 500px by 500px on large devices.
Responsive Fields support the entry of multiple values separated by commas.
### Interactions available for this Block
Available interactions for the Image Block are:
- **Image Link Clicked** (image\_link\_clicked): This is triggered when an attendee clicks on the image.
### Set up an Image Block
1. Go to the **Jomablue Portal** and log in with your email address and password
2. Click on **Canvases** under Community on the left-hand menu
3. Click on the Canvas type where you wish to add the Block (e.g., Lobby, Session, Vendor or Page)
4. Locate the specific Canvas where the Block will be added and click **Edit**
5. Click on **Layout**
6. Within a Flex, click **Add Block.** Here, a list of Blocks will appear. Select **Image**.
7. The Image Block is now added to the Canvas. You may now add a Title, Configure, Automate or Delete the Block.
### Configuration options
**Basic Configuration**
- **Upload Image:** You can add an image here. Once the image is added, it can be updated or removed. The configuration tab will automatically detect the dimensions of the uploaded image and add them to the ‘Width’ and ‘Height’ fields. These values can be modified to display the image at different dimensions
- **Open in Modal:**Option to make the image clickable by checking the box. If checked, then the image will open in a modal window. The modal can be configured via these fields:
- **Modal Width:** Allows you to set the width of the Modal (in pixels or as a percentage of the width of the entire screen)
- **Modal Max Width:** Allows you to place an upper cap on the width of the Modal
The modal max width will always override the modal width field. For example, if a screen is 1000 pixels wide, and the modal width is set to be 800 pixels wide, but the modal max width is set to 50%, then it will only display as 50% of the width of the page (e.g.m 500 pixels
- **URL to link image to:** You can provide an external or internal URL to link the image to
**Advanced Configuration**
You can access the advanced configuration by clicking on the **Show optional fields**
- **Width and Height:** These fields are responsive and determine the size at which the image is loaded from Cloudinary. They are automatically populated when an image is loaded, but can be adjusted manually.
- **M** **ax Width and Max Height:** These fields are responsive. They allow you to restrict the maximum height/width of the image independently of the size from which it is being loaded from Cloudinary, and also support percentages.
- **Cloudinary Image Parameters:** This is an advanced option. It allows you to directly apply [Cloudinary Image Parameters](https://cloudinary.com/documentation/image_transformations "https://cloudinary.com/documentation/image_transformations") to the image. For example, in the visual example above, ‘c\_fill’ is used to resize the image to fill the given dimensions.
- **Background Position**: This is an advanced option. It allows positioning and cropping of the image if it isn't an exact fit for the Block that contains it.
- **Align:** This is an advanced option. It allows you to align the image left, right, or centre within the Block if it is not as wide as the Block itself.
- **Custom CCC class:** This is an advanced option. It allows you to directly assign a CSS class to the image.
**Note:**
CSS class enables you to apply unique style properties to a group of HTML elements to achieve a desired web page appearance.
## Image Slider Block
The Image Slider Block is a way to display image content in a moving carousel. It’s an eye-catching way to showcase Exhibitors, Sponsors, Sessions, or any other area of interest in your Event. Image
Slider Blocks can be placed on any Canvas, including the Lobby, any Session or Vendor Canvas.
An example of an Image Slider block with auto-cycling enabled can be found below:
****
#### Image Slider Block Structure
An Image Slider Block has an optional heading and an image slider section. The dimensions of the Image Slider Block are configurable. For example, small, tile-shaped blocks, or large banner-shaped blocks are supported.
All images in an Image Slider Block must be the same dimensions (e.g., same height and width in pixels). Additionally, we don't recommend using more than six images in a Slider, as more than six images affect the quality of the image slider.
#### Image Slider Functionality
Images in a Slider Block can have a URL associated with them. Internal URLs (e.g., links to elsewhere in the Community) will open in the same window, while External URLs will open in a new tab/window.
#### Add Image Slider Block in Community
Here are the steps on how to add an Image Slider Block in the Community:
1. Go to the **Jomablue Portal** and log in with the provided username and password
2. Go to the Community section on the menu bar on the left. Click on the **Canvas**
3. Click on the Canvas where you want to add the ‘Image Slider’ Block
4. Click on the **Layout Editor**
5. Click on the **Add Block**, and a list of Blocks will appear. Then choose **Image Slider Block**
6. Image Slider Block is now added to the Canvas. You can now add a Title, configure, automate or delete the block.
****
### Configuration options
The Image Slider Blocks have the following configuration options:
****
- **Automatic Cycle:** This can be toggled on or off. If set to on, images slide automatically after a brief interval. If set to off, the user must click the arrows to progress through the image.
- **C** **ycling Interval:** This is set in milliseconds. The default cycling interval is 1000 milliseconds, which is equivalent to one second.
- **Hide Controls:** Hide the left and right arrows on the images
- **Hide Delimeters:** Allows you to toggle the delimiters (black bar) to enable or disable. If disabled, the images are displayed without the black bar overlaid onto them.
- **Layout:** Allows you to select between "Fixed Height" and "Scalable"
- **Width:** When using the scalable mode, Width sets the width portion of the desired aspect ratio of the image. It can be made responsive with multiple comma-separated values.
- **Height:** When using the scalable mode, set the height portion of the desired aspect ratio of the image. It can be made responsive with multiple comma-separated values.
- **Th** **e Background Size:** Allows customisation of the selected images to fit within the limitations set by the above two settings. This field supports a few different options:
- **Cover:** Scales the image as large as possible without stretching the image. If the proportions of the image differ from the element, it is cropped either vertically or horizontally so that no space is left.
- **Contain:** Scales the image as large as possible without cropping or stretching the image
- **The full width of the image:** This can be set to yes or no. If set to yes, the slider will take up the full width of the block without any padding. Image slider by default is set to no so as not to take up the full width of the Block.
Once an Image is added, you can configure the following settings for the Image within the Slider:
- **URL to link image to:** You can associate a URL with images in a Slider Block. Internal URLs (e.g., links to elsewhere in the Community) will open in the same window, while External URLs will open in a new tab/window.
- **Select Vendor to Link Image to:** Select any vendor from the list of added Vendors
- **Select Speaker to Link Image to:** Select any speaker from the list of added speakers
- **Select Session to Link Image to:** **** Select any session from the list of added sessions
- **Link name:** Enter a custom Name that will be displayed in the Click Interaction.
#### Image Slider Scalable Mode
There is an option for Image Slider to scale with any display size and allows setting different aspect ratios for different screen sizes. For example, when configuring an Image Slider Block, we can select 'scalable' in Layout and set the aspect ratio. In this case, as shown in the example below, aspect ratios (width and height) are set to 16:9 for large screens and 4:3 for small screens.
****
The result on a small screen is that the image displays at a 4:3 aspect ratio:
****
Recommended Image Dimensions in Image Slider
Below are the general image dimensions guidelines based on standard screen sizes of desktops and mobile devices:
- **Common desktop screen** (screen resolution of 1366x768):
- For a 100% width Block, use images that are 980 wide and 490 high
- For a 50% width Block, use images that are 490 wide and 250 high
- For a 25% width Block, use images that are 245 wide and 125 high
- **Larger desktop screen**(screen resolution of 1920x1080):
- For a 100% width Block, use images that are 1360 wide and 500 high
- For a 50% width Block, use images that are 680 wide and 250 high
****
- **Common mobile screen**(screen resolution of 360x640):
- For a 100% width Block, use images that are 290 wide and 400 high
- We don't recommend smaller Block sizes at this screen width, as the navigation features will become unusable
****
### Interactions available for this Block
Whenever an attendee clicks on any of the images in the image slider, interaction is recorded. This interaction can also be stored for post-event manual reporting.
## Internal Link Block
An Internal Link Block serves to redirect users from one internal page to another internal page within a community.
### Add an Internal Link Block to a Canvas
1. Go to the **Jomablue Portal** and log in with your email address and password
2. Click on **Canvases** under Community on the left-hand menu
3. Click on the Canvas type where you wish to add the Block (e.g., Lobby, Session, Vendor or Page)
4. Locate the specific Canvas where the Block will be added and click **Edit**
5. Click on Layout
6. Within a Flex, click **Add Block**. Here, a list of Blocks will appear. Select **Internal Link**
7. The Internal Link Block is now added to the Canvas. You may now add a Title, Configure, Automate, generate a Featured Block URL or Delete the Block.
### Configuration options
An Internal Link Block has the following configurations available:
- **Page Path:**The path to the page that you wish the Block to link to. This can be anything in the Community, such as the Agenda, Sessions, Vendors or Community Custom Pages. The Page path can be accepted in both forms as given below:
- **Full Community URLs:** e.g.,https://xyz.jomablue.com/community/1/agenda
- Portion after /community in the URL of the Community page you wish to link to.
For example, you can use /1/agenda
- **Link UID:** The unique identifier that will be saved in the interaction when the Internal Link Block is clicked on
- **Content:** The content that will be displayed in the Block. This can be in the form of text, images or both. Note that some content must be present here in order for the Block to be clickable.
- **Automatic Redirect:** If the toggle is set to on, the Community will automatically redirect the user to the page indicated in the Page Path field, as soon as this Block is loaded (regardless of whether the Block was loaded upon Canvas load, or if it was revealed by a timed or manual Block reveal).
## WYSIWYG Editor
What You See Is What You Get (WYSIWYG) Editor is a content management tool that lets attendees view the end result of the content in a way that is similar to when the content is being created. You can do basic editing of the text or images, such as bolding text, adding sub-heads, without getting into advanced coding in WYSIWYG Block.
### Features of the WYSIWYG Block
The WYSIWYG Editor supports the following:
- Heading/Paragraph styles
- Bold, Italics
- Set the font colour and highlight colour
- Hyperlinks
- Alignment (left, middle, right, block)
- Indentation
- Image upload and placement
- Writing code (optional)
- Preview content on reduced width device (mobile device)
### Add WYSIWYG Editor Block in a Community Canvas
Here is how to add a WYSIWYG Editor Block in Community Plus:
1. Go to the **Jomablue Portal** and log in with your email address and password
2. Click on **Canvases** under Community on the left-hand menu
3. Click on the Canvas type where you wish to add the Block (e.g., Lobby, Session, Vendor or Page)
4. Locate the specific Canvas where the Block will be added and click **Edit**.
5. Click on **Layout**.
6. Within a Flex, click **Add Block.** Here, a list of Blocks will appear. Select **WYSIWYG**.
The WYSIWYG Block is now added to the Canvas. You may now add a Title, Configure, Automate or Delete the Block.
Images can be uploaded directly to the editor and placed within your content.
**Responsive Mode**
There is a ‘responsive’ option when uploading images to the WYSIWYG Block. It allows the image to scale responsively within the Block or Flex. You can select the 'responsive' option by clicking on the Class.
**Responsive Inline Mode**
For images that are to be displayed in WYSIWYG Blocks in line with text, there is an option for **Responsive inline mode**. This mode is identical to the Responsive behaviour; only the image has line-height attached, and it will resize to smaller viewports if viewed on smaller displays. You can select the 'responsive inline' option by clicking on the Class.
### Interactions available for this Block
There are no interactions available for this Block type.
# Community Configuration
Jomablue Community is a feature-rich online event delivery platform designed to integrate seamlessly with the Jomablue platform. It offers various features for delivering virtual and hybrid virtual/in-person events.
## Community features
The features of Jomablue Community include:
**Event Lobby**
Each Event has its own lobby, which is the default page that loads when users visit for the first time. It displays your Community header image, some event details, an optional Welcome Message, and login (authentication).
**Login (Authentication)**
Users are not required to register or log in to see basic information. However, Attendees who do log in will enjoy a personalised experience and gain access to Vendor and Session Canvases, as well as the Networking feature. There are two login methods available for Community:
- Logging in with a registered mobile/cell phone number
- Logging in with a registered email address
**Agenda/Sessions**
The Community platform features an Agenda that synchronises with the Agenda in Jomablue. It presents a chronological list of all visible Sessions (each Session can be set to invisible via the Portal), including Session names, start/end times, and Locations.
**Vendors**
A list of Vendors participating in your Event is available, displayed in alphabetical order or grouped by sections such as Sponsorship levels or other relevant groupings.
**Speakers**
Community features a list of Speakers at your Event, presented in alphabetical order. Each entry includes the speaker’s Profile picture, Name, Job Title, Company and available contact links.
**Networking**
Community offers a Networking feature that intelligently recommends other attendees for Community users to connect with. This feature presents the attendee’s name, Profile Picture, Company, Job Title, Bio, and contact information. Users must opt in to become visible in the Networking feature and have full control over what information is shared in their networking profile.
**Custom Pages**
Community allows you to create custom HTML content to display within the platform. Custom Pages can be used to display important information, link to external websites, display a map of the Event, or anything else you wish to make available to your attendees.
**Canvases**
The platform includes a feature called Canvases, which allows you to create custom displays for Session content, Vendor content, Lobby content, and more.
**Note:** In Jomablue Community, everything happens in real-time. Changes made in Community may take up to 2 minutes to be reflected.
## Create digital experiences with your brand
Businesses often invest in skilled professionals to design their marketing material for a good reason - it helps tell their brand story and connect with their audience. Similarly, the experience attendees have with your events on Jomablue is a valuable opportunity to present your story.
When producing an online event, we suggest engaging a digital designer to visually communicate your event’s narrative. A designer with the right skills in digital projects can significantly enhance the user experience. Additionally, they will likely possess knowledge of CSS/HTML and be adept at working with Content Management Systems (CMS).
#### Four essential steps before starting creative design:
1. Prepare a site map and page wireframes close to final approval. Ensure that you have at least your Lobby and Session Canvas wireframes ready for sign-off.
2. Gather any corporate or event branding guidelines.
3. Write down any specific requirements or design directions you have in mind to align expectations and minimise rework.
4. Provide .psd, .ai, or .eps files of existing assets and logos, along with details of the fonts and colour palettes you wish to use.
#### What to expect from your designer
It’s a good idea to ask the designer to propose one or two design concepts. This may include an event banner, page background treatments, standard fonts, colour palettes, and an email header.
This process ensures your designer understands the event concept and brand direction, allowing you to select your preferred design concept for the event.
#### Implementing the design
The implementation of your chosen design involves a combination of design tasks and using CSS modifications to achieve the desired outcome. This process is managed within the Jomablue platform, and the time it will take will depend on the number of assets and complexity of the design. For a less experienced digital designer and a basic theme, allow between 4 and 6 hours to implement it in Jomablue. More sophisticated design implementations may take longer.
#### Working with a Jomablue Designer
Jomablue has in-house design services that can support you in creating custom themes for your events. Please contact the Jomablue team for pricing.
**1. Concept Design and Implementation Package**
**Deliverables:**
The package includes the following:
- Two custom themes designed to include an event banner, background, font, and colour palette. Design concepts will be presented in a Lobby and 1 other page. Output includes the creation of individual assets/files
- One edit to the design (if required)
- Implementation of the custom theme and assets within the event, which includes:
- Upload of individual image assets
- Configure the site to adopt the chosen design
**Requirements:**
To ensure successful implementation, you will need to provide packaged design files, high-res images, vector files for logos/icons (Ai or EPS), and custom font files.
**Scheduling:**
****Designer resources are subject to availability and should be pre-booked at least 5 days in advance.
**2. Custom Design work**
In some cases, custom design work may be necessary to support a Community build. With suitable notice, a Jomablue Designer may be available for this work, billed at an hourly rate.
## Plan for internal audience events
This section is intended for internal IT contacts with enterprise customers. The success of an internal-focused event relies on the information provided here.
For events with a large internal audience (e.g., staff), it is important to consider that IT policies (such as firewalls and content filters) on either the customer side or Jomablue’s side could exceed a threshold and disrupt services.
### Example event
Imagine your company is hosting an internal sales meeting using a Jomablue Community, expecting over 4,000 staff members to log in and engage with the content.
**Potential IT Policies to consider:**
- Internal Rate Limiting
- Corporate Firewall rules
- Bandwidth consumption for high-definition video streaming
If 4,000 employees log in from the same common corporate network or use our platform within the network, it may trigger policies on the customer network (such as firewall rules) that fail to recognise legitimate traffic from Jomablue.
For example, if 4,000 people are connected to a 6Mbps HD live stream, significant traffic will enter the corporate network (without considering any caching), potentially causing bandwidth issues and warranting a preference for employees to use a specific network configuration (e.g., not using the corporate VPN). This should be communicated beforehand.
**Note:** For some live streams, HTTP caching can be leveraged.
### Whitelist - Emails
We strongly recommend whitelisting our email domain (event-email.io) to ensure the timely delivery of passcodes required for logging into the Jomablue Community. Delays or misclassification of these emails as spam may impede staff access to the platform. It is common for us to send thousands of emails within minutes of an event starting–sometimes exceeding 50 emails per second to your domain. If no previous emails have been received from our domain, it might trigger spam protections.
It is also strongly recommended to load mobile numbers for staff. Mobile numbers are designed to provide staff with an alternate channel to receive passcodes if emails are being caught by spam filters or delayed in transit for reasons beyond our control.
If these customer-spam protections are triggered and mobile numbers are not provided, users can't access the event and rectifying this is beyond Jomablue's control.
Please note that testing with individuals or smaller audience sizes generally does not provide a realistic indication of how the customer infrastructure will respond to the load impact of a production event.
**Action Points:**
- Whitelist event-emai.io for incoming emails to your corporate network
- Whitelist jomablue.com URL to allow web browsing and media consumption
### Whitelist - Web App
We recommend whitelisting the domain name of Jomablue Community for users to access via their browser on your corporate network. The domain name will be a subdomain of jomablue.com, unique to each customer. These domains are dynamically created and could be blocked by products like Cisco Umbrella as they are considered “recently created” domains by default.
Additionally, Jomablue components utilise other domain names to load assets. You will see a large number of requests hitting these endpoints as well as jomablue.com. If required, Jomablue can provide these endpoints upon request.
**Actions:**
- Whitelist jomablue.com domains for your users to access
### Whitelist - Egress IP/VPN's
Lastly, for audiences larger than 200 staff members connecting from the same office/VPN network/corporate network, you must provide Jomablue with egress/public-facing IP addresses. This allows Jomablue to whitelist incoming traffic from your corporate networks. Failing to do so may result in service interruptions for your end users.
**Actions** **:**
- Provide Jomablue with Office/Corporate Network egress IPs for whitelisting.
## Configure your Community Settings
The Community offers a wide range of customisation options to ensure it aligns with your brand and looks great for your event. Three main areas can be customised:
- General (settings for the entire Community)
- Recommendations
- Login
Settings can be found under **Community > Settings** in the left-hand menu of your event.
The General section of Community Settings is where you activate the Community, customise some of its appearance, and enable direct messaging. To set up your Community, navigate to the Settings in Community and edit the following fields:
#### Active
Set the Community to 'Active' or 'Not Active.' It must be marked ‘Active’ to be visible to users.
#### Appearance
**Community Header Image**
Upload a Community Header Image that will be used for the Calendar of Events and may also appear on the Lobby Canvas. The recommended size is 2880px × 270 px.
**Community Menu Image**
This Image appears at the top of the navigation menu within Community. The recommended size is 600 px × 192 px.
**Community Colour**
This optional setting is recommended to enhance your branding. It will apply various elements such as buttons and hyperlinks. Please use a hex code that contrasts with white (e.g. #0000FF).
**Lobby Background Image**
Adding a Lobby Background image is optional. For more information, see the article: [Canvases](https://jomablue.bolddesk.com/kb/article/105/canvases).
**Background Colour**
If you choose not to add a Lobby Background image, you may wish to add a Community Background Colour using a hex code (e.g., #FFFFFF).
**Welcome Message**
The Welcome Message appears on the default login page for unauthenticated users. You can add a brief event description using a basic content editor.
#### Features
**Direct Messaging**
You can enable or disable direct messaging. When enabled, Community users can send direct messages to each other–provided the person has their profile set to public– through the following features:
- Clicking on a person's name in Live Chat
- Clicking on a person’s name in the Photo Booth Gallery
- Accessing the Networking Block
#### Advanced
**Organisation-wide Community Settings**
Any branding set at the organisation level should reflect your organisation or company, rather than a specific Event. Since Events within your instance can contain multiple Communities, ensure that the content set here is generic and reusable across all your Events. For additional information, see the article: [General information](https://jomablue.bolddesk.com/kb/article/142/general-information).
**Customisation (for Advanced Users only)**
The Advanced Customisation field allows for advanced customisation of the Community. Familiarity with structuring JSON data is required. For more information, please see the section: **Advanced Customisation** below.
## Default Event Setting for Community PWAs
This feature allows the setting of a PWA (Progressive Web App) default event at the instance level, allowing multi-client instances (e.g., agencies) to select a default event when viewing the Community in PWA mode (e.g., when the Community is installed as an app on your device) without revealing any other events in the same instance.
### Configure a Default Event
1. Navigate to **Community**, then select **Settings**
2. Click the **Edit Organisation Settings** button on the right of the screen
3. Choose an event from the **Show Default Event** drop-down menu
4. Click **Save**
**Note:**
- By default, no event is selected
- To deselect a default event (e.g., return the instance to normal behaviour), click the **Close** icon (the small 'x') to the right of the drop-down menu
- Only one event can be set as the default at any one time. If you have multiple events running in parallel (e.g., an agency is running 2 Community events at the same time), it is recommended to avoid this feature.
- For all non-PWA users (those accessing the Community in a browser without having installed the PWA), there will be no change in behaviour.
- For all PWA users (those who have installed the Community as an app on their device), if a default event is set, the following changes in behaviour will apply:
- If that user is directed to the Events List view of the Community from within the PWA by an Internal Link, they will automatically be redirected to the default event, without seeing the full list of events in that instance.
For example, if a Block links to https://instancename.jomablue.com/community, it will automatically redirect back to the lobby of the default event.
For example, if the default event is Event 2, and from within the PWA, they are linked to Event 3 Lobby, they will stay in Event 3. Another Internal Link would have to be provided to move the user to a different event.
- If an Internal Link directs a user to an event other than the default event, they will remain in the new event until they are directed to a different event. This will persist even if they close and reopen the PWA.
For example, if the default event is Event 2, and from within the PWA, they are linked to Event 3 Lobby, they will stay in Event 3. Another Internal Link would have to be provided to move the user to a different event.
## Using custom fonts
A Custom Font can be used in a Community using external font declarations (think of a declaration as pointers or signposts) in style sheets. These can either be customer-hosted or on public services such as 'Google Fonts'. If the font is customer-hosted, you will need two main components:
- One or more hosted font files
- A hosted CSS file referencing the hosted font files
Both the hosted font files and CSS file will need to be:
- Hosted on a publicly accessible endpoint (e.g., internet accessible, not internally hosted)
- Capable of handling high volumes of incoming requests (e.g., hosted on an S3 bucket via a CDN)
If you are using enterprise fonts, these should be web-safe fonts and hosted in an appropriate location (e.g., AWS S3 bucket or CDN - Content Delivery Network). Fonts can be in \*.ttf format, but it's recommended that additional formats such as woff/woff2 are also used to ensure the best cross-browser support.
Once the font files are in a publicly accessible and suitable location, the CSS needs to be defined and hosted. This is the CSS file that will be referenced in the Jomablue Community Advanced Customisation. The CSS file should be as small as possible, containing only the required font declarations and no other CSS (for the best user experience and to avoid any conflicts with other CSS that would reside on Jomablue)
**Example:**
Here is an example of hosted fonts (these are \*.ttf, but additional font formats such as woff/woff2 are recommended for cross-browser support). In this example, we have uploaded these fonts to an AWS S3 bucket with a CDN:
**Font file URL(s):**
https://cdn.jomablue.com/fonts/OpenSans-Bold.ttf
https://cdn.jomablue.com/fonts/OpenSans-Regular.ttf
Once we've hosted our font files, we can then build a CSS file that looks like this:
****
Note that each of the font files corresponds to a "font-family" name, which we will use to reference individual fonts in Jomablue Community Advanced Customisation.
We then host that file in a public location (that is publicly accessible and scalable). In this case, we have it hosted in the same place the fonts are (this isn't a requirement, but it may be more convenient to do so).
**CSS file URL:** https://cdn.jomablue.com/fonts/myCustomFonts.css
Finally, the CSS file URL can be referenced in Jomablue Community Advanced Customisation (see "href" at the top of the image below), and the individual fonts can be assigned to variables in Advanced Customisation using the "font-family" names defined in the CSS file (see "body-font-family" and "heading-font-family" in the image below):
****
For additional information on how to add external fonts, please see the section: **Add External Font API URL** below.
## Community Agenda
The Agenda view within Community is a valuable tool for displaying all Sessions occurring during an event in chronological order. It offers several features that personalise each user’s Agenda view and keep it up-to-date.
Each Session in the Agenda includes the Session name, start and end times, and location. A sample Agenda view can be seen below:
****
### Features of Community Agenda
**My Agenda**
The Agenda allows users to create a personalised Agenda, accessible via the My Agenda toggle in the top bar. Users can add Sessions to their personalised Agenda by tapping the calendar icon next to each Session name. See below for an example of the Agenda and My Agenda views:
****
**Note:** Sessions saved in My Agenda can only be viewed in the browser where they were saved. There is no synchronisation across devices, which means sessions saved in My Agenda won't be visible if accessed from a different device or browser.
**Jump-to-now**
While an event is live, opening the Agenda will automatically scroll to the Session(s) that are currently running, showing the current date/time. Ongoing Sessions will be highlighted with the “on now” text pulsing in green.
****
**Quick Dates**
Users can easily jump to different days of the event using date buttons located at the top of the screen. This allows users to jump directly to the Sessions scheduled for that day.
The date tab is visible only for event days that have Sessions. The displayed date format is designed to be region-agnostic and is not configurable.
**Agenda Filtering**
Users can filter the Agenda based on a set of configurable Session Traits, which are properties that can be applied to Sessions for better organisation. They can be grouped by type and enable the Sessions they are interested in. To filter the Agenda, click the Filtering icon in the top right of the Agenda:
** **
Then use the checkboxes to select the desired Session types:
****
Filtering is also available based on a Session's Location (for example, different Streams or the Keynote Stream):
****
On desktop or laptop devices, the Filter button for the Agenda is located in the top right-hand corner, as shown in the example below:
****
The colour of the Filter button corresponds to the Primary colour of the Community. You can change the word 'Filter' by modifying the Advanced Customisation section in Community Settings. For example, as shown below, adding the following JSON Snippet will replace ‘Filter’ with ‘Stream’:
****
**Agenda Display**
Agenda dates are highlighted when a desktop user hovers over a day or Session in the Agenda. The date corresponding to the day the Session is in will become highlighted at the top of the Agenda, as shown below:
****
**Note:** The clock icon and promo text (shown to the left of the session time) both derive from the dark "rgb" variable in custom theming. These are set to 30% and 50% opacity. This cannot be configured in the Community and can only be configured through custom theming.
****
**Session Entitlements**
When a user is logged in, they can see whether they are entitled to attend each Session.
- If a Person is not entitled to attend a Restricted Session, a red padlock will appear next to the Session name in the Agenda
- If they are entitled, a small green unlocked padlock will appear instead
- Entitlements are managed by an organiser, either at an individual level or entitling anyone within a category to attend a session.
Not Entitled to attend:
****
Entitled to attend:
****
**Automatic updating**
If changes are made to the Agenda in Jomablue, they will automatically be updated within the Community Agenda.
This eliminates the need for downloadable PDF agendas, which can quickly become outdated, are harder to manage, and are less convenient to view compared to a responsive web page like the Community Agenda.
**Notes:**
- Sessions can be hidden from the Community. This setting can be configured under the Session details in Jomablue.
### Community Schedule
The Community Schedule provides an alternative view of the Agenda. For additional information, see the article: [Session Canvases](https://jomablue.bolddesk.com/kb/article/145/session-canvases).
## Preview Mode
It’s recommended to check your Canvases in Preview Mode before launching them to attendees. Preview Mode allows you to ensure the configuration is correct and that the content appears as intended without revealing it to the entire Community audience.
#### Preview a Canvas in Preview Mode
To view a Canvas in Preview Mode, follow the steps below:
1. Before previewing the Canvas, ensure its visibility is set to active by visiting the Canvas Details page
2. Go to the People tab to ensure you have a person’s record in the event
3. Log in at xyz.jomablue.com/community/organiser (“xyz” should be replaced with your relevant instance name) using your Jomablue user email and password
4. Select the event you wish to check by clicking **View in Preview Mode.**
You will now see the Community in Preview mode and can access the Canvas you wish to review.
### View Canvases and Blocks scheduled to reveal in the future
If you are using Block reveal times to display Blocks at a time in the future, you can preview how this will look like when the Block reveals using Preview Mode.
In Preview Mode, a box at the top of the screen will display:
****
The bottom banner displays that you are in Preview Mode and have the option to ‘disable’ the mode.
The top banner displays the time at which you are viewing the Canvas. Controls in this panel enable you to view the Canvas at a specified future time, letting you preview blogs that are not yet revealed. This is especially useful for complex Block reveal/hide timing considerations. For example, if you have a Vimeo VOD Block set to reveal after a Live Stream, you can preview the scheduled ‘visible from’ time set on the Vimeo Block to check that the correct video will appear on the Canvas.
You can step forward or backward in time in 1hr and 1 min increments, and refresh the page contents while preserving the current viewing time. Please note that refreshing the page will reset the viewing time back to real-time.
**You can click on the ‘Settings’ icon to:**
- Quickly toggle between viewing the Canvas "Now" and "at the specified time"
- Configure the specified time and date
- View the timezone that the Event is in
- View inactive blocks by toggling the "Show inactive Blocks" option
****
To apply any of these changes, you will need to click **Apply Settings**
**Notes** **:**
- No Block interactions are saved in Preview Mode
- Session entitlements are ignored, and Canvases are displayed regardless of visibility settings
- Once authenticated into ‘Organiser,’ the idle timeout is 72 hours. If there is no activity within this period, the organiser is automatically logged out and must log in again.
- If you have multiple timed Blocks in the same location, these cannot be viewed in Preview Mode
- Preview mode does not cache Community, so changes made in the Portal will be immediately visible in Preview Mode
## URL for Community
The Community can be accessed in a web browser, allowing you to include a link to the Community in pre-event communications, emails or other activities.
The URL is the same across all platforms (e.g., no different stores for Android vs Apple), including desktop browsers.
You can find your Community URL by navigating to Community Settings and clicking **Go to Community.**
The new window/tab that is launched will contain the URL you can share with Attendees. Example url: [https://acme.jomablue.com/community.](https://acme.jomablue.com/community.)Use this structure of URL if you are going to publicly advertise a URL (e.g., printing on a paper guide).
**Note:** Custom domains are not currently supported for Jomablue Community. The Community URL will always be a subdomain of jomablue.com (e.g., [https://yourinstance.jomablue.com/community).](https://yourinstance.jomablue.com/community%29.)
## Direct Linking
Directly linking to specific pages within the Community is supported. For example, you may want to link directly to a particular event or a specific page within the Community, such as the Login page, Agenda or Vendors.
This feature is especially useful for sending an SMS upon check-in to a Session, linking users directly to the Session details within the Community.
Let's say you have multiple Events in the Community and you want to link people directly to the Event they are attending, not the full Calendar of Events. Simply navigate to the page you would like people to land on, and directly copy and publicise the URL.
**Examples:**
**Note:**
- Ensure you copy the URL from your Event App so the link works correctly.
- In these examples, “xyz” should be replaced with your relevant instance name.
- Don't link to pages that require authentication, such as Networking or the Feed. This will result in an error message for the user. To verify that your URL doesn't require authentication, test the link in Incognito mode. If you see the page, you're good to go.
Link directly to an Event:
https://xyz.jomablue.com/community/1
Link Directly to the Agenda:
https://xyz.jomablue.com/community/1/agenda
Link Directly to a Vendor Profile:
https://xyz.jomablue.com/community/1/vendors/3
## Manage the appearance of the Community Page Title
Jomablue allows you to control the visibility of the Community Page Title. You can set the Page Title to be visible or hidden, allowing for flexibility in branding throughout the Community.
By default, the Community Page Title is visible, as shown in the example below:
****
#### Disable the Community Page Title
**Note:** This disables the Page Title for the entire Community.
To disable the Community Page Title, please follow these steps:
1. Navigate to **Portal > Community > Settings > Customisation**
2. Add the following code to the Advanced Customisation section of Community Settings: pageTitleEnabled":false
3. Click **Save**. The Community Page Title will now be hidden, as shown in the example below:
****
## HTML Support
The Community supports the use of a content editor, meaning no coding is required. The code examples below are no longer maintained. For additional information, see the article: [Block Types - Others](https://jomablue.bolddesk.com/kb/article/180/block-types---others) under the section **WYSIWYG Editor.**
**Session Descriptions**
The following is supported within a Session description:
<br />
<img src=" ">
<a href= " " target="\_blank"></a>
<b></b>
<center></center>
<h2></h2>
<h3></h3>
<p></p>
<p color="red">This is some red text!</p>
**Vendor Descriptions**
The following is supported within a Vendor Description:
<br />
<img src=" ">
<a href= " " target="\_blank"></a>
<b></b>
<center></center>
<h2></h2>
<h3></h3>
<p></p>
<p color="red">This is some red text!</p>
**Speaker Descriptions**
The following is supported within a Speaker bio:
<br />
<img src=" ">
<a href= " " target="\_blank"></a>
<b></b>
<center></center>
<h2></h2>
<h3></h3>
<p></p>
<p color="red">This is some red text!</p>
## Restrict Access to a Custom Page using Category Entitlements
Custom Pages are pages in Community that can be used to present content outside of other pages, such as the Lobby, Session and Vendor Canvases. They are fully customisable static HTML pages that can serve various purposes.
If you want to restrict access to certain Custom Pages for specific attendee types (e.g., enabling only VIPs to access a VIP Custom Page), you can apply Category Entitlements to the Custom Page of your choice.
### Apply Category Entitlements to a Custom Page
To apply Category Entitlements to a Custom Page, follow the steps below:
1. Go to the **Portal > Community > Community Pages**
2. Click on the respective Community Page where you want to change the Entitlement, as shown below:
****
3. To apply the Category Entitlement, select ‘yes’ on ‘**Requires Authorisation**’
****
**Note:** if set to ‘No,’ viewing the page does not require authentication.
4. Select the Category you wish to allow access to:
****
Category entitlements are now applied to the Custom Page in Community. Only authenticated Community users belonging to the selected categories will be able to view the Custom Page.
## Hide events from the Community Calendar
Sometimes you may need to hide an Event from the Calendar in your Community. You may want to keep the Event hidden from the Calendar until the Event is fully set up, or you may want to hide it once the Event's life cycle has concluded. To do this, follow these steps:
1. In Jomablue, select the Event you wish to hide from the Community
2. Navigate to **App Specific > Settings**
3. At the top left of the screen, you will find a radio switch labelled **Active**. Switch this from "Yes" to "No" (as shown below)
****
4. Click **Save** at the top right of the page to save your settings
## Conduct a content audit of a Community site
**Introduction**
Just as in-person events require careful organisation, producing digital experiences with live or simulated components also requires checks and balances for success. This includes executing a testing or audit plan in the final days before going live.
The purpose of an audit is to verify that every piece of content and every configuration (such as session titles, speakers, videos, and reveal timings) is correct. It's important to catch discrepancies that may arise during the upload and Community build process. Additionally, things can change at the last minute, and without proper change-management processes in place, these changes may not be captured.
At the start of your project, determine when you need to have all your content complete and uploaded. Set realistic deadlines and make sure to allocate time for your audit, allowing for any issues that may arise during the process. Avoid scheduling the audit for the night before you plan to go live with your Community.
**Plan for a successful audit**
- Build time into your project plan to complete a content audit
- Ensure the Community site is 100% complete before the audit
- Use a show flow document as a reference to verify the site’s content (e.g., what times will Canvases and Blocks be revealed?).
- Allocate 2 people to conduct the audit, preferably those who did not complete the content upload
- An audit is best done in the morning, and if possible, not on the last business day of the week
You need a consolidated document to cross-check the site against and we suggest using a detailed show flow. As you make decisions during planning and collecting content, your show flow should be populated so it becomes a single source of truth before building your site or adding content.
**Checklist before you start the audit**
- The show flow is complete
- Every video has been watched before upload (and the audit)
- All copies have been proofread before uploading
- All content has been uploaded to the site
- Block and Canvas reveal times have been set
**What to Audit and How**
Below is a list of items typically included in an audit. Recognise that every Community and every project is different, so some items may not be necessary for all projects. Your audit team of 2 should work together using the show flow displayed on a separate screen from the site. This works if they are in-person and doing it virtually.
Your show flow is ideally created within a tool such as Google Sheets for easy filtering of content by date, time, or location (what page) it happens on. For example, we suggest you audit one content page at a time rather than looking across all things that occur at 9 am.
**What to Audit**
- The time each session reveals and is then locked
- The time each block reveals
- The configuration of each Block, including the Name
- Any expected automation per Block is correct
- Flex and Layout configurations
- Overall layouts appear as expected
- If multiple blocks are in the same position, test them in each state
- Video Table and Live Chat settings are correct
- Tracking Pixel is on each Canvas
## Blacklist Users from a Community Event
During your event, you may be required to blacklist or cancel Community users from your Community event. Once a Community user is cancelled from the event, they will be automatically logged out of the event they are in. There may be a short delay of up to 60 seconds before the person is logged out.
To cancel a Person from the event, follow these steps:
1. Go to **People** in the left-hand navigation
2. Search for the person you want to cancel from the event by their first name, last name, or company in the **Search for People** field
3. Click on the **Person name** you want to cancel
4. Click on the Actions button at the top right
5. Select **Cancel Event Registration**
6. The person is now cancelled from the event, and they cannot access the event anymore
**Note:** You can reverse the cancellation by selecting the Actions button and clicking the **Reverse Cancellation of Event Registration** button, so the person will be able to access Community and receive communications again.
#### User Experience when a Person is Blacklisted
Once the person is cancelled, they will be automatically logged out. If the Community user attempts to log in again, they will see the following message on the login card in Community:
****
## Community header image safe space
To provide a responsive experience for all users on Desktop and Mobile devices, it is essential to consider whether the Community Header Image looks good on Desktop and Mobile devices. We recommend following the design safe space.
Any important logos or design elements should be placed within the designated safe space to ensure they will properly display across all devices. Design elements located outside of this safe space may not be displayed on mobile devices (and are dependent on the width of the device).
****
**Safe Space:** Approximately 1/3 from the left
**Asset Total Size:** 2880px x 270px
## Advanced customisation
The Advanced Customisation field allows for advanced customisation of the Community. By using JSON, you can customise labels (e.g., Agenda can become Schedule) and modify the presentation of the menu items. There are default settings for all customisable elements in Advanced Customisation, so if you don't make any customisations, the app will operate as expected.
You need to be familiar with structuring JSON data. It’s advisable to use a JSON linter to validate your customisation before placing it in the field. Be aware that it will only validate that the structure is correct and won't check if you have the correct values for the customisation of the Community. Moreover, while you can copy CSS (advanced customisation) from one event to another, copying CSS between different Canvases is not possible.
Customising Community Menu items is achieved by creating a JSON object, which can be found in the Jomablue Portal under the Community section on the Settings page, in the Customisation text box. This JSON object must contain two keys: language and nav. The language key should refer to an Object, while the nav key should refer to a List of Objects. A JSON object for this purpose will look like this:
{
"language": {
"page\_name\_1":"new\_page\_name\_1",
"page\_name\_2":"new\_page\_name\_2",
...
"page\_name\_n":"new\_page\_name\_n"
},
"nav": [
{
"name":"page\_name\_1",
"order":1,
"enabled":true
},
{
"name":"page\_name\_2",
"order":2,
"enabled":true
},
...
{
"name":"page\_name\_n",
"order":n,
"enabled":true
}
]
}
### Hide menu
You can toggle the visibility of the left-hand Menu on the desktop view by setting the property to true (visible) or false (hidden). By default, the visibility is off, which means the menu is hidden. You can expand the menu by clicking on the menu icon, commonly referred to as the 'hamburger icon,' in the upper left corner of the page. On mobile view, the menu is also hidden by default.
{
"permanentMenu":true,
}
### Menu language
You can change the labels of the following words.
- Vendor / Vendors
- Agenda
For example, you might wish to change Vendors to Exhibitors and Agenda to Program. To do so, inside the language object, add the page name as the key and the desired new wording as the value. Here is the JSON example of that customisation, renaming "Vendor" to "Exhibitor", "Vendors" to "Exhibitors", and "Agenda" to "Program":
{
"language": {
"vendor": "exhibitor",
"vendors": "exhibitors",
"agenda": "program"
}
}
You can choose to include or omit any value within the JSON, e.g., only include 'Vendors' if you're not waiting to change the 'Agenda' language.
If you don't see the change applied, it may indicate incorrect JSON formatting. Changes take effect immediately, so refreshing the Community page should display the change.
### Menu order
With this customisation, you can change the order of menu items and disable certain items. If you disable a menu item that usually appears in the 'quick links' on the homepage, it will also be hidden.
#### Ordering menu items
Place a single menu item in the first position in the menu:
{
"nav": [{
"name": "agenda",
"order": 1
}]
}
**Important:** Custom pages are considered a single menu element. Therefore, you can order all custom pages as a "block" inside the menu, but you can't order them individually alongside other menu items.
Here is the ordering Agenda in position 2, speakers in position 3, and then all the custom pages in position 4:
{
"nav": [{
"name": "agenda",
"order": 2
},
{
"name": "speakers",
"order": 3
},
{
"name": "custom\_pages",
"order": 4
}
]
}
### Disabling/hiding Menu items
In the Jomablue Community, you may want to hide certain pages based on the style of your event. This can be done using JSON in Community Settings > Customisation field.
**Default Pages**
The default pages and their names in Community Menu are:
- Login ("path": "/:eventid/login")
- Networking ("path": "/:eventid/networking")
- Speakers ("path": "/:eventid/speakers")
- Agenda ("path": "/:eventid/agenda")
- Vendors ("path": "/:eventid/vendors")
- Logout ("path": "/:eventid/logout")
Here is an example of disabling the Networking, Event Feed, and Vendors functionality:
{
"nav": [{
"path": "/:eventid/vendors",
"enabled": false
},
{
"path": "/:eventid/feed",
"enabled": false
},
{
"path": "/:eventid/networking",
"enabled": false
}
]
}
**Hiding Switch event**
It is recommended that the Home and Switch Event menu items not be hidden, if required, you can remove the Switch Event by applying the following JSON code:
{
"nav": [
{
"path":"/events",
"enabled":false
}
]
}
**Hiding Static Elements**
Common static elements in the Lobby, such as the welcome message, event description, and profile section, can be hidden by adding the following JSON code snippet in the Customisation field within Community Settings:
{
"hideStaticElements":true
}
**Example of the Lobby Canvas with the Static elements:**
**Example of the Lobby Canvas with the Static elements hidden:**
### Combine language and menu customisation
The JSON structure allows you to include multiple customisations within the same customisation field. Here is an example of changing the language while also disabling some pages.
{
"language": {
"vendor": "exhibitor",
"vendors": "exhibitors",
"agenda": "program"
},
"nav": [{
"name": "speakers",
"order": 2
},
{
"path": "/:eventid/vendors",
"enabled": false
}
]
}
**Important notes:**
- The name or path inside the nav must be the original name. It can't be the updated language name. For example, above you see we renamed Agenda to 'Schedule', but within the nav object for changing the order, it's still named 'Agenda'
- Some menu items are only displayed based on the user’s status. For example, if a user is logged in, the ‘Login’ option will not appear. However, the order of items will still be visible, even if the user cannot see them.
### Menu icons
The community uses Material Design Icons. You can see all available icon options in the library [here](https://fonts.google.com/icons "https://fonts.google.com/icons"). Here is an example of changing two of the icons.
Note: If you have created Custom Pages for your event, icon settings are configured within Custom Page settings and can't be customised via Advanced Customisation.
{
"language": {
"vendor": "exhibitor",
"vendors": "exhibitors",
"agenda": "program"
},
"nav": [{
"name": "speakers",
"order": 2,
"icon": "assignment\_ind"
},
{
"name": "networking",
"icon": "whatshot"
}
]
}
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
All page names and available attributes
**Page Names:**
"name": "login",
"name": "feed",
"name": "networking",
"name": "speakers",
"name": "agenda",
"name": "vendors",
"name": "switch event",
"name": "custom\_pages",
"name": "logout",
**Attributes:**
"order": (1,2,3,4 etc)
"enabled": (true, false)
"icon": ("icon\_name" from material design library)
### Renaming Lobby
To rename the Lobby Page to Homepage or any other title, navigate to the **Portal > Community Settings** and add the following code in the advanced customisation box:
"language": {
"Lobby": "Homepage"
},
Below is a visual example:
****
The new name of the Lobby will appear on both the navigation bar and the top title. You can review the changes you made by clicking **Go to Community.**
### Add external font API URL
Any self-hosted fonts and CSS must be externally accessible and have the appropriate CORS configuration for the Jomablue application to access the resources. If you use a service like Google Fonts API, this is all taken care of, and the Google Fonts API URL is simply inserted into the Jomablue Community Advanced Customisation.
1. Go to the **Google Font library**
2. Search for the font ‘DM Sans’
3. Select the font and choose your desired style
4. Click **Select this style** on the right
5. Copy HREF and the font family from the codes as shown below:
- - "https://fonts.googleapis.com/css2?family=DM+Sans&family=Ms+Madi&display=swap"
****
6. Navigate to your **Portal>Community>Settings>Advanced Customisation**
7. Add the copied URL into the Advanced Customisation tab under ‘theme,’ as shown below:
- - "href":
["https://fonts.googleapis.com/css2family=DM+Sans&family=Ms+Madi&display=swap"",](https://fonts.googleapis.com/css2?family=DM+Sans&family=Ms+Madi&display=swap "https://fonts.googleapis.com/css2?family=DM+Sans&family=Ms+Madi&display=swap")
8. Update the JSON code variable to choose the correct font:
- - "heading-font-family": "DM Sans, sans-serif",
****
- "body-font-family": "DM Sans, sans-serif",
9. The Google font API is now added to the Jomablue Community
**Note:** We advise against hotlinking to other websites' CSS unless you have permission and are knowledgeable about the scale capabilities. Improper usage may result in unexpected traffic spikes on the destination website or block requests from Jomablue, which can cause additional issues for delegates attempting to access other resources. Furthermore, it may inadvertently alter the appearance of the Jomablue Community.
## Troubleshooting
### Blurry images in Community
Example of a blurry Vendor logo:
****
Example of a blurry Speaker image:
****
Images are recommended to be 500px x 500px. If your Speaker profile photos or Vendor logos appear blurry or pixelated, the source image uploaded to Jomablue might not be of sufficient quality (resolution).
**Speaker Photos**
Keep in mind that Speaker photos in Community are automatically centred on the Speaker's face. So, a full-body shot of the Speaker taken at 500px x 500px may still end up blurry once it is cropped to focus on the face. To address this, use a cropped image of the Speaker's head and shoulders at a size of 500px x 500px or ensure that a full-body shot is at least 2000px x 3000px.
### New content not displaying
Jomablue Community uses worldwide caching to provide users with fast in-app experiences worldwide. This means no matter where you are in the world, Community content loads quickly for the best experience possible.
As part of caching the content, updates to Community content can take up to 2 minutes to roll out and be visible in the Community.
This is only noticeable if you are the one making changes in Jomablue and are refreshing your browser to double-check your work. To the attendees, this 2-minute delay is not noticeable at all.
**How to see your updates immediately**
If you are updating content and want to see the change instantly, you can add this URL parameter. By doing this, you will always see your updates immediately.
Be careful, this URL should only be used for you to check the content and should never be distributed as the link for attendees to access the event app.
Simply add the following parameter to any Community URL: ?cache=0
For example:
https://xyz.jomablue.com/eventapp?cache=0
https://xyz.jomablue.com/eventapp/1/agenda?cache=0
## Referenced articles
[Canvases](https://jomablue.bolddesk.com/kb/article/105/canvases)
[General information](https://jomablue.bolddesk.com/kb/article/142/general-information)
[Session Canvases](https://jomablue.bolddesk.com/kb/article/145/session-canvases)
[Block Types - Others](https://jomablue.bolddesk.com/kb/article/180/block-types---others)
# Specifications for Information Counter
If an information counter is required, we will work with you to place Jomablue Smart Badge printers on it. To accommodate these printers, the information desk must have the following:
- A minimum of 4 power outlets. A 4-outlet powerboard is sufficient in this case.
- A modesty panel that extends at least 200mm above the surface of the information desk OR a shelf with 300mm clearance between the shelf and the counter (suitable for high counters only)
##
# Jomablue Dashboards
## Organiser Dashboards - Event Insights
The Organiser Dashboards provide an immediate snapshot of your in-person (Event Insights) or online (Community Insights) event, accessible from both your computer and mobile device.
You may also be interested in the article: [Jomablue Insights](https://jomablue.bolddesk.com/kb/article/366/jomablue-insights "https://jomablue.bolddesk.com/kb/article/366/jomablue-insights")
The following widgets are included for in-person events:
#### Check-in Overview
These widgets provide an overview of the number of registered attendees and the number of people who have checked in to the event so far
****
#### Check-in by Category
This breakdown shows the attendees who have checked in to the event, subdivided into Categories
****
#### Onsite Registration Summary
This widget indicates the number of people who registered onsite and shows what percentage of total attendees checked via onsite registration
****
#### Event Registration Sites
This widget displays the registration sites configured for the event along with their visibility status. Selecting a site opens the live page in a new tab, making it easy to review or share active registration links.
#### Event Check-in over time
A graphical representation of the rate at which attendees have been checking in throughout the event
****
#### Apple Wallet Setup
Apple Wallet Setup
A Readiness counter displaying the number of attendees who selected Add to Wallet from their digital ticket email. This metric provides visibility into how many attendees are using Apple Wallet for entry, supporting planning for onsite scanning and throughput.
#### **Event Check Ins Per Day by Category**
This widget displays the daily check-ins by category, giving a clearer view of how many attendees in each category had their badge printed each day.
#### Session Check-in
A paginated list of Sessions along with the number of attendees who have checked in to each. You can sort this list by Time, Location, Session Name, or Checked-In count
****
#### Vendor Lead Overview
A pair of widgets displaying the total number of leads captured and emails sent by all Vendors at the event. It also breaks down the number of leads captured in the past 60, 15, 5, and 1-minute intervals
****
#### Vendor Lead Performance
A paginated list of Vendors and the number of Leads they have captured, sortable by Vendor name or Leads count
****
#### Touchpoint Interactions
This widget presents a paginated list of Touchpoints, detailing the number of interactions each touchpoint has had throughout the event. It can be sorted by Touchpoint Name or Interaction count
****
#### Items Collected
A paginated list of Items with summaries indicating how many have been collected and how many are allocated but not yet collected. You can sort this list by Item name, Collected count, or Not Collected count.
****
#### Has Interacted Today
This widget allows you to track attendee interactions by individual event day. Previously, Dashboards only displayed overall totals for the event, making it difficult to measure daily engagement. With this feature enabled, you can view per-day counts for activities such as:
- Badge Printed
- Badge Reprinted
- Checked into a Session
- Checked out of a Session
- Captured using Session Related Content
- Captured as a Vendor Lead
- Used a Touchpoint
- Used Item Collection
This makes it easier to compare performance across event days, understand engagement trends, and generate more accurate daily reports.
**How to enable:**
To enable this feature, go to **Event Settings → Event Day Interactions**. Daily counts are based on the Event Day Settings you’ve configured. A custom field is added to each person for every day they interact. While you can edit field keys and values, it’s generally not recommended.
**Further information:**
- The feature can be configured to include interactions before Day 1 as if they were Day 1 interactions (e.g. for Vendors printing badges the day before).
- If you want a separate count for a Bump-in Day, update your Event Settings to include Bump-in Day and turn off “Include Interactions Before First Day in Day 1.”
**Where to locate this data:**
Daily interaction counts from this feature can be found in:
- Explore People
- Insights & Dashboard
- Post Event Data
#### Badges Printed by Day by Category
A table showing the number of badges printed each day, broken down by Category. This allows organisers to track badge printing patterns across event days and understand when specific attendee groups are arriving on-site.
#### Event Check-ins per Day by Category
A daily breakdown of check-ins by Category. This table helps identify attendance patterns, peak arrival periods, and differences in behaviour between attendee groups across the event.
#### Apple Wallet Engagement on Person Records
Individual attendee records include Apple Wallet interaction data under the Advanced tab. This shows whether the attendee received their ticket email, opened it, and added their e-Ticket to Apple Wallet. These details provide a complete view of the attendee’s digital ticket journey.
## Accessing Dashboards
Jomablue provides real-time data for your events with two types of dashboards available:
- **Event Insights** for in-person events
- **Community Insights** for virtual events
Dashboards can be viewed on desktop and mobile devices.
#### Steps to access the dashboards
1. Enter [your\_instance].jomablue.com/community/organiser into the browser address bar
2. Log in with your credentials
3. Locate your event and select the **Dashboards** button
4. Select the **Open Dashboard** button underneath either **Event Insights** (for in-person events) or **Community Insights** (for online events).
5. Real-time data for your event will be displayed, including the number of registrations, logins, a summary of people registered by category, and live stream viewers.
## Public Sharing Links for Dashboards
Jomablue Dashboards support the creation of secret public links. Public links do not require a username or password to access but remain confidential and are not searchable on the internet. Access to a link can be revoked at any time.
### To enable a Dashboard Share Link
1. Log into Organiser mode
e.g., [https://\[instance](https://[instance)name].jomablue.com/community/organiser
2. Select your Event
3. Choose either the Event Insights or Community Insights dashboard
4. Click the link icon at the top right corner
5. Toggle on **Enable Dashboard Share Link**
6. Copy the URL using the **Copy** icon and share this dashboard with the relevant people
7. The link will be set to expire 1 month from when it was generated, but this can be revised as required
### To revoke/re-enable all access to a Dashboard Share Link
**Note**: Anyone accessing the dashboard via that link will be automatically logged out
- To revoke access: Toggle off **Enable Dashboard Share Link**
- To re-enable access: Toggle the switch to reactivate the existing link to everyone
### To reset a Dashboard Share Link
**Note**: This action will affect all users, so proceed with caution if the link has already been shared
1. Click the Refresh icon to disable the current Dashboard Share Link
2. Re-enable the Dashboard Share Link to generate a new link
3. Select the Copy icon to share this dashboard with the relevant people
## Referenced Articles
[Jomablue Insights](https://jomablue.bolddesk.com/kb/article/366/jomablue-insights "https://jomablue.bolddesk.com/kb/article/366/jomablue-insights")
# Release 9.50.0
## New Feature
### Trigger event experiences with Touchpoint Webhook actions
Badge taps now do more. A new HTTP Endpoint Touchpoint Action lets you send a real-time payload to any webhook when an attendee interacts with a Touchpoint onsite. The result is a more connected, more dynamic onsite environment, where a single tap can update a live display, trigger gamification logic, or activate a third-party system instantly.
- Send structured payloads to a configured webhook endpoint upon a tap of a badge
- Include attendee profile data and event context in each payload
- Supports use cases including live leaderboards, digital activations, and third-party integrations
- Adds to existing Touchpoint Actions (send email, send SMS)
### Configure Ingest Endpoints without writing JSON
Building and editing Ingest Endpoints is now faster and more accessible. A new guided UI builder walks you through field mapping and validation configuration for standard scenarios, no raw JSON required. For teams managing complex and custom setups, Advanced mode remains fully available.
- Create and edit Ingest Endpoints through a clean, guided interface,
- Configure field mapping and validation rules without entering raw JSON
- Advanced mode available for non-standard configurations
- Accessible to users with the Product Team or Trusted-Support-Integrator role
Where to find it: *Portal Sidebar > Advanced > Integrations > Add Ingest Endpoint*
## Improvement
### Reuse your best layouts with Organisational Page Templates
Preferred page designs can now be preserved and shared across your organisation. Any page can be converted into an Organisational Template, making it available to all members when starting a new page. Templates are displayed prominently at the top of the Template Selection view, and any edits to a Custom Template remain independent of pages already using it.
- Convert any Page to a Template from the Page List or the Page Edit view
- Organisational Templates appear first in the Template Selector when creating a new page
- Edit Templates independently without affecting live or draft pages based on them
- Preview screenshots are generated and updated automatically for easy identification
- Available to users with the Owner, Support, or above role
### Correct name formatting for East Asian Badge naming
Badge name ordering now supports the conventions used in Korean, Japanese, and other East Asian markets. The Last+First and First+Last name order options in the Badge Layout Editor each have a new no-space variant, allowing names to appear without a separator, as is standard in those regions. Existing name order setting remains unchanged.
- New no-space variants for both Last+First and First+Last name ordering
- Names output without a separator when the no-space variant is selected
- Existing behaviour for original name order options is unaffected
New name order options available in the editor, with and without space:
****
Based on direct feedback from teams running events across East Asian markets, this update ensures that every attendee badge reflects local naming standards, so attendee names are represented correctly across all markets.
### Custom Field Aliases now carry over when duplicating events
When duplicating an event, Custom Field Aliases are now duplicated alongside their associated Custom Fields. Previously, aliases were excluded from the duplication process, requiring manual recreation. This update removes that friction and keeps your event data structure consistent from the moment a new event is created.
# Release 9.45.0
## New Feature
### Added ‘Full Name’ element to Smart Badge Designer
This update introduces a single “Full Name” element that automatically combines first and last names into one field. Users can apply font size, alignment, and other styling options to the full name as a whole, simplifying layout design and ensuring consistent formatting. This enhancement streamlines badge creation and improves visual consistency for name presentation.
### Added AI Suggested Tags to the Vendor Portal
AI-based tag suggestions have been added to the Vendor Portal. These appear in the new Tags tab in the Vendor Portal. Users can click on suggested tags to automatically add them to their list of tags.
### Added per-day interactions for individuals on Person pages
When Event Day Interactions are enabled, Person pages now display a table below Custom Fields showing whether the person attended each event day and any associated key/value data. This mirrors export content, supports accessibility, and adapts to multi-day layouts, giving users a clearer and more detailed view of individual engagement.
## Improvement
### Improved Survey Report page loading
The Survey Report page now loads significantly faster, improving the overall performance and user experience when generating or reviewing reports.
# Products
People select Products when registering to attend your event. They can either be Free or Paid. In both cases, the following applies:
- Each Person must select at least one Product
- A Product must include Admission to an Event
- A Product can optionally include Items for collections (e.g., merch bags, T-shirts or dinner tickets)
## Create a Free Product
**To create a Free Product**
1. Navigate to **Registration > Configuration**
2. Select the **Products** tab
3. Select **New Product** ****
Fill out the following fields to create your Free Product:
- **Name**: The name of the Product, which will be displayed on the Sites where this Product is included
- **Description**: A brief description of the Product, which will also appear on the Sites
- **Admission**: The Admission associated with the Product, which categorises the Attendee registering
- **Items** **:** Specify any Item Entitlements that will accompany this Product
- **Inventory**: Indicated how many of these Products will be available
- **Type**: Can be paid or free. For this purpose, this should be set to **Free**
**Example of a completed Free Product:**
## Create a Paid Product
1. Enter a **Name** and **Description**
2. Select an **Admission type** from the dropdown menu
3. Enter the **Base Price** (up to 4 decimal places, excluding tax)
4. Specify the **Inventory** (amount available for sale)
5. Add **Items**
6. Click **Save**
These Products can now be added to Sites via the **Sites** Tab
****
## Product Description
We recommend that Product descriptions be limited to 300 characters. The image below highlights where descriptions are displayed on the Site.
****
The description should provide an explanation of the Product. For example, if the Product Name is 'Early Bird Delegate,’ a suitable description might be:
“Get in quickly, as there are limited places at Early Bird rates. Early Birds gain access to the 3-day conference from Monday, November 2, to Wednesday, the 4th. Early Birds also have the opportunity to purchase limited edition merch. Don’t miss out!”
## Delete a Product
A Product can be deleted only if it’s not associated with any other items in the Portal and has not been used to create an Order. Relationships that prevent deletion include:
- Products tied to an Order (through either Paid Registration or an Admin Order)
- Products associated with any Items
- Products linked to a Coupon
- Products listed in one or more Stores
**Steps to delete a Product:**
1. Go to **Registration > Configuration** in the left navigation menu
2. Select the **Products** tab
3. Click on the relevant **Product**
4. ****Click the **Delete** button
If an attempt is made to delete a Product that has existing relationships, an error message will appear. If no relationships exist, a confirmation pop-up will be displayed. Confirming the action will permanently delete the Product.
## Access to Products
For the general public, Products are displayed on Sites for purchase, typically via credit card. Not all Products need to be displayed; for example, you may want to reserve a discounted Product for Admin Orders only. Event administrators can add Products to an Order and generate Manual Payment (EFT, Cash, etc.) or Free-of-charge (FOC) Orders.
## Configure the display order of Products on a Site
In Online Stores and Free Registration Sites, you may want to change the order in which your Products are displayed. This can be done using a drag-and-drop interface in the Site configuration.
To change the order of Products on a Site, follow these steps:
1. Navigate to **Registration > Configuration**
2. Click on the **Sites** tab
3. Select the Site you want to edit
4. Use the Drag-and-Drop Interface to re-order the Products
5. Click **Save**
## Items
Items refer to extras available for purchase, such as Gala Dinner Tickets, T-shirts, Swag, or other merchandise. Items can be added to a Product as free of charge or set up to allow the Person to select quantities.
For example, if you want to offer a free event T-shirt with an Early Bird Product, you would set up the Item as follows:
****
This limits one free T-shirt per purchase. The quantity field won’t be editable.
****
In another example, if you want to allow Early Bird purchasers the option to buy Gala Dinner tickets, follow this:
- Attendees are not required to attend the Gala Dinner
- Each attendee can purchase up to 2 tickets
You would configure the Items like so:
****
The default quantity for Gala Dinner tickets will be set to 0, but purchasers can increase it to 2, being charged $281.8271 (excluding tax) for each. See photo below:
****
## Inventory
Using the example below, let's break down the counts:
****
- **3 of 100 Sold**
- **100** = The total number of Inventory for that Product
- **3** = The number of Products sold that have a status of:
- "payment\_received"
- “payment\_pending”
- "eft\_pending"
- "Cancelled"
- **97 Remaining** = The Inventory amount minus the number of Products sold
### Set Global Stock Level when Selling Items
When selling Items on a Site, you can set a Global Stock level applicable across all Sites in an event. Items with a Global Stock level can be included in multiple Products across various Sites.
This feature is particularly useful if you have limited quantities of Items for sale, such as restricted entries for a gala dinner or limited swag bags.
How to set a Global Stock Level for an Item:
1. Create the Item (refer to Creating Items)
2. Go to the **Registration** section of Jomablue
3. Open the **Configuration** page
4. Choose the **Items** tab
5. Here, you can apply Taxes to the Item and set a Global Stock Level for it.
**To view the current stock level of an Item:**
1. Navigate to **Registration > Configuration > Items,** and the number of Items sold will appear on the right as shown in the example below.
****
Within a Site, an Item will be marked as Sold Out if its Global Stock Level has been exhausted. Note that the Product itself may still be available for purchase.
If an Item that is automatically included in a Product becomes sold out, the entire Product will also be marked as sold out, even if there is remaining stock for the Product itself.
**How does this affect Add-ons?**
If your Global Stock levels for an Item are sold out, users will be unable to complete their orders if there are outstanding add-ons that have not been redeemed. They will see a 'Sold Out' message.
To avoid this situation, make sure there is sufficient Global Stock available if you have pending add-on offers.
****
### Sold Out
The “Sold Out” message will display on the Sites when the number of Products sold exceeds the available Inventory. Once this happens, 'Sold Out' will replace the 'Register Now' message on the Registration Site, preventing people from registering or accessing the registration form.
For example:
**Inventory**: 100
**Sold**: 99
**Remaining**: 1 (before “Sold Out” is displayed)
If you wish to release more Products for purchase, simply increase the Inventory by the needed amount.
**Admin Orders and Sold Out**
When a Product becomes sold out, a SOLD OUT message will be shown to all Site visitors. However, you can still create Admin Orders for that Product.
Admin Orders aren't restricted by the Inventory count, allowing you to place orders even when the Product is sold out. In short, Inventory counts only affect Sites.
The images below depict how “Sold Out” appears on the Site and inside Jomablue.
** **
****
**Do Cancelled Orders count towards Sold?**
Yes. If an order is cancelled, it is still counted as a "Sold" product. This prevents the automatic release of a Product into Sites (e.g., it will remain in SOLD OUT status).
If you want to make cancelled Products available for purchase by other users, we recommend increasing the inventory by the number of cancelled Products you have.
### Manually set an Item to Sold Out
To manually set an Item to appear as Sold Out in Sites and Add-ons, follow these steps:
1. Navigate to **Registration > Configuration**
2. Click on the **Items** tab
3. Select the **Item** you wish to mark as Sold Out
4. Adjust the Global Inventory limit to be equal to or less than the number of Items already sold
### Calculate Amounts Excluding Tax
Jomablue automatically calculates tax on Products and Items where applicable. Therefore, the prices you enter into Jomablue must be exclusive of tax.
These amounts should be rounded to 4 decimal places.
**Why 4 Decimal Places?**
Although rounding to 4 decimal places is less common, it allows Jomablue to more accurately calculate Tax totals. Rounding errors (in fractions of cents) can occur in financial systems, and Jomablue is no exception. Using 4 decimal places reduces the likelihood of significant rounding errors when adding multiple items to a cart and applying various discounts to each item.
**Calculate the excluding Tax pricing using Excel or Google Sheets**
If you want to remove 10% Tax (as with Australian GST), represent that as a decimal of 1.1 (which is 110% of the base number). For 20% tax, you would use 1.2, and so on.
To calculate the price excluding tax, divide the total amount by 1.1. For example, if the tax-inclusive value is $425.00 in cell A3, use the formula: =A3/1.1
****
This calculation results in $386.36 excluding tax. However, we need to round it to 4 decimal places. This can easily be done with the ‘Increase Decimal’ and ‘Decrease Decimal’ buttons in Excel and Google Sheets.
****
After rounding, you will arrive at $386.3636, which is the amount excluding tax.
****
## Product per Order Limit
Setting a Product Limit per Order helps restrict the number of Products that can be added to a single Order.
For example, you might want to limit each order to a maximum of 20 products to ensure fairness for everyone purchasing tickets, preventing a single order from buying up all the available tickets.
Please note that this limit does not stop someone from checking out multiple times using the same order details or credit card. Therefore, it's important to consider this limit carefully. If you’re unsure, it’s advisable to set a higher limit (e.g., 50 or 100).
Setting the limit too low (for example, to '1') will force customers to check out multiple times if they wish to purchase on behalf of colleagues. This can cause duplicate order data, making administration more challenging. Additionally, it may frustrate users and increase the likelihood of order abandonment.
##
# Block Types - Audience engagement
## File Download Block
Files can be made available for Community Members to download using the File Download Block on any Canvas.
An attendee can download various types of files, including:
- Slides for a Presentation (on a Session Canvas)
- Whitepapers or other supporting documentation for a Session or Vendor
- Zip archive containing multiple files to be made available to attendees
#### Features
The File Download Block includes the following features:
- **Title:** The title displayed at the top of the File Download Block (optional)
- **List of files:** A list of the Files that have been included in this File Download Block
Example with Title, File Titles and Subtext:
****
Each listed File has the following structure:
- **File type icon:** An icon indicating the file type is displayed on the left (always displays)
- **File title:** The name given to the File. If not specified, the uploaded filename is used
- **File subtext:** Text displayed below the File Title (optional)
- **File size:** Displays the size of the file below the download icon
- **File Type:**The file can be in formats such as jpg, png, gif, zip, or docx
#### Available interactions
The following interactions are available for the File Download Block:
- **Download Started** (download\_started)
This interaction can be stored for post-event reporting and block automation.
Block metrics are also available in a People Export. Each File Download Block in a Community will have a corresponding column added to the report for each file.
Each column will have a header containing:
- The Block ID
- A "File Download" label
- The filename of the file
Files can be made available for Community Members to download using the File Download Block on any Canvas.
### Upload a File into the Portal
1. Click on **Files** under Community on the left-hand menu
2. Select **Upload** in the top right corner.
3. Select the Files you wish to download. Please note to name the file correctly, as you cannot edit the file name once it has been uploaded.
4. Now you can proceed to add this file to a File Download Block, see instructions below.
### Add File Download Block in a Community Canvas
1. Go to the **Jomablue Portal** and log in with your email address and password
2. Click on **Canvases** under Community on the left-hand menu
3. Select the type of Canvas where you wish to add the Block (e.g., Lobby, Session, Vendor or Page)
4. Locate the specific Canvas you want to edit and click **Edit**
5. Click on **Layout**
6. Within a Flex, click **Add Block.** A list of Blocks will appear. Select **File Download Block**
7. The File Download Block is now added to the Canvas. You can now add a Title, Configure, Automate or Delete the Block.
### Configure the File Download Block
You can add files to download through the Configuration tab. First, ensure that the file is uploaded. The following fields are optional to fill:
- **Title:** Set a title for the file; if left blank, the filename will appear by default
- **Subtitle:** A short subtitle that appears under the title
- **Download filename:** A filename without an extension can be set here.
**Note:** A file can be a document, sound, video, or image.
#### Configure the number of files in the File Download Block
There is no enforced limit on the number of files that can be added to a single File Download Block.
By default, the Block displays all files, which can make the File Download Block large. You can configure the number of files to add to the File Download Block and set the number of files that can be displayed on the Block.
Example showing the display when the "maximum\_displayed\_files" is set to 5:
****
The Block height can be customised by setting how many files to show. If there are more included files than the set amount, a vertical scrollbar is shown.
This is done by following these steps:
1. Click on the **Advanced** tab of the File Download Block
2. Paste the following JSON in the Data field:
{"files": [ ], "maximum\_displayed\_files": 5}
****
3. Click **Save**
**Note:** There is no limit to the number of files that can be uploaded or their sizes, and this won't affect the performance of the File Download Block. However, to improve user experience, we recommend keeping files as small as possible and PDF files over ZIP files wherever possible.
## Live Chat Block
Live chat in virtual events allows attendees to interact and network with each other. A Live Chat Block allows attendees who have access to the Canvas to chat with one another.
Attendees can view other participants' profiles and chat directly with them on the Canvas using text, emojis, and comments as little or as often as they like.
It’s recommended to use Live Chat Block with the Live Stream, ensuring all participants are present on the Canvas at the same time, regardless of their time zones.
**Note:** Images cannot be loaded in the Live Chat; only texts and emojis can be used.
#### Features
**User Profile**
- An attendee's full name is displayed in chat messages
- Profile pictures are shown in chat messages; if a profile picture is unavailable, the attendee’s initials will be displayed instead
- When an attendee changes their profile image or updates their name after sending messages in the Live Chat Block, previous messages will not be updated with the new photo or name. Only future messages will reflect the updated name or profile image
**Moderating Live Chat**
- Undesired chat messages cannot be deleted from a Live Chat Block. However, if an attendee behaves unfavourably, they can be removed from the event, which will log them out of the Community. Their comments will remain visible, and they will be logged off in approximately 30 seconds, losing the ability to participate in the chat
**Profanity Filter**
- A basic profanity filter is implemented in the Live Chat Block. Words matching the profanity list are automatically filtered out; however, misspelled or slightly altered versions of bad words may bypass the filter and can only be deleted by the original poster of the message.
- If desired, words can be added to or removed from the profanity filter at an additional cost.
**Message Retention**
- When an attendee loads the Chat Block/Canvas, existing messages will be displayed in the Live Chat Block, allowing them to catch up on the ongoing conversation. They can scroll up to read previous messages.
- The default message retention period is seven days, but it can be increased to 15, 30, or unlimited days for an additional fee.
- The history of messages in the Chat Box is not currently downloadable.
**Word Limit**
- There is a limit of 500 words per message.
**Message Actions**
- Attendees can delete their messages by hovering over the message and clicking on the bin icon.
- Attendees can like messages from other participants in the Live Chat Block by hovering over the message and clicking the thumbs-up icon.
**1:1 Chat from a Live Chat (direct messaging)**
- Users can initiate 1:1 chats from a live chat block by clicking on another user's name. The 1:1 Messaging Icon (located in the bottom-right corner of Community when direct messaging is enabled) is hidden until a user has at least one 1:1 chat started. The 1:1 chat will then open in a separate live chat window.
- Enabling or disabling direct messaging does not affect Live Chat Block. If direct messaging is disabled and the person's profile is public, others can still see their profile, but won't see a 'send message' option.
**Note:** There is no message alert notification when receiving a direct message. The only indicator of a new message is a small bubble above the message icon.
**Person Details Modal**
Clicking on another user’s name in the chat history will open a modal displaying basic details about that user and relevant actions (such as sending a message or connecting).
#### Available interactions
Available interactions for the Live Chat Block are:
**Participated**
In addition, block metrics are available in a People Export. When a Community contains one or more Live Chat Blocks, a column will be added to the report for each Live Chat Block, containing:
- The Block Type
- The Block ID
- The name of the Block (if provided)
- "Participated," indicating the column is about whether a user participated in a live chat
Each column will contain a 'Y' if the Person participated in the corresponding Live Chat.
#### Available interactions
Available interactions for the Live Chat Block are:
**Participated**
In addition, block metrics are available in a People Export. When a Community contains one or more Live Chat Blocks, a column will be added to the report for each Live Chat Block, containing:
- The Block Type
- The Block ID
- The name of the Block (if provided)
- "Participated," indicating the column is about whether a user participated in a live chat
Each column will contain a 'Y' if the Person participated in the corresponding Live Chat.
### Set up a Live Chat Block
A Live Chat Block enables attendees to chat with each other in real time. To set it up, follow the steps below:
1. Go to the **Jomablue Portal**
2. Click on **Canvases** under Community on the left-hand menu
3. Click on the Canvas type where you wish to add the Block (e.g., Lobby, Session, Vendor or Page)
4. Locate the specific Canvas where the Block will be added and click **Edit**
5. Click on **Layout**
6. Within a Flex, click **Add Block**. Here, a list of Blocks will appear. Select **Live Chat.**
7. The Live Chat Block is now added to the Canvas. You may now add a Block Title, Configure, Automate or Delete the Block.
### Configuration options
There are no configuration options available for this Block type.
## Networking Block
Networking is a strong motivator for attendees to participate in events, as it creates opportunities to connect with potential allies. While face-to-face interactions or handshakes may be missing in virtual events, effective networking opportunities still exist. A Networking Block provides a space for attendees to find people with similar interests based on their registered information and actively engage in knowledge sharing or building connections.
A Networking Block allows Community Networking features to be available to attendees. Through this Block, attendees can review potential matches, initiate connections, manage connection requests, and view a list of all users who have opted in to allow Networking. The Networking Block looks like this:
****
#### Features
There are four tabs in the Networking block:
- **Find:** This tab displays recommended people to connect with based on mutual interest
- **List:** Attendees can browse the list of other registered attendees, searching by first name, last name, or company name. Here, they can initiate one-on-one chats by clicking the message icon or start a private conversation by selecting a name and clicking the ‘Send Message’ button
- **Requests:** Attendees can send connection requests and check the status of their connection (approved or pending)
- **Connections:** This shows a list of approved connections
#### Available interactions
Currently, no interactions are available for the Networking Block.
#### Different uses
**Intelligent Networking**
Intelligent Networking provides personalised recommendations for each user by analysing their profiles and interactions at the event and comparing them to those of other attendees.
These recommendations are presented to the user in the order of recommendation score, from highest to lowest. Users can see their recommendation score, which ranges from 0 to 100, indicating how highly they are recommended.
**Recommendation Frequency**
Recommendations are made for users over time. When a user first logs into Community, they won't have any recommendations. It is advisable for users to come back later to see the recommendations tailored for them. If no recommendations have been generated based on their score, users will see a random selection of up to 50 users who have made themselves discoverable in Networking.
**Privacy**
All users must opt into Networking through their profile settings. By default, Networking is disabled. Users have control over what information is visible in their Networking profile, including their job title and preferred contact methods.
Users can adjust their privacy settings by clicking the person Icon in the top-right corner and selecting Privacy. They have the option to enable or disable the "Discoverable in Networking" feature. When this feature is enabled, users can choose to make the following information visible:
- Email address visible to approved Connections
- Job Title visible in Networking
- Mobile phone number visible to approved Connections
**Communicating**
Each user's profile will contain their preferred contact methods, which may include their email address, mobile phone number, or social media accounts like LinkedIn, Twitter, Facebook, and Instagram. Selecting a contact method will open the relevant application (e.g., an email address will open the default email client, social media accounts will open the relevant app, and phone numbers will open the dialler). On desktop or laptop devices, these will typically open in a browser.
### Set up a Networking Block
Community Plus includes a Networking Block that intelligently recommends attendees for potential connections. This block displays the user’s name, profile picture, company, job title, bio, and contact information. Attendees must opt-in to become visible in the Networking feature and have full control over the visibility of their networking profile.
**Add Networking Block in a Community Canvas**
1. Go to the **Jomablue Portal** and log in with your email address and password
2. Click on **Canvases** under Community on the left-hand menu.
3. Click on the Canvas type where you wish to add the Block (e.g., Lobby, Session, Vendor or Page)
4. Locate the specific Canvas where the Block will be added and click **Edit**
5. Click on **Layout**
6. Within a Flex, click **Add Block**. Here, a list of Blocks will appear. Select **Networking**.
7. The Networking Block is now added to the Canvas. You may now add a Title, Configure, Automate or Delete the Block.
#### Configuration options
No configuration is available for the Networking Block.
## Photo Booth Block
The Photo Booth Block offers Community audiences a fun and engaging experience during virtual or hybrid events. This block enables attendees to take photos and apply different backgrounds, frames, and stickers. Photos can be captured with any device that has a camera and internet access, without the need to install an app.
A Photo Booth Block is designed to be used together with the Photo Booth Gallery Block.
#### Features
**Background Removal:** When a user applies a background image, the original photo’s background will be automatically removed using an AI (Artificial Intelligence) background remover. If the user doesn't choose one of the offered background images, the original background of the photo will be retained.
Images containing multiple people can make it more complex for the AI to identify the primary face and effectively remove the background. The background removal process may take a few seconds, or even longer, depending on the following factors:
- Complicated backgrounds
- Things going on in front of the people in the photo can hinder the AI’s ability to recognise the main subject
**Customisation Options:** As an organiser, you can add custom frames, stickers, and background images when configuring the Block. These will be available for attendees to use when capturing their photos.
**Note:** Although there is no limit to the number of backgrounds, stickers, and frames an organiser can upload, it is best to limit to 10 of each per Photo Booth for a seamless user experience.
**Download Photos:** Attendees can download their photos to share or post on different social media platforms such as Facebook and Instagram
**Desktop Users Options:** When a desktop user opens the Photo Booth and chooses to take a photo with their webcam, a dropdown menu will appear to allow them to select from multiple available cameras. This option will not appear for mobile users or for desktop users with only one camera.
**Customisable ‘Disclaimer’ Text:** When an attendee clicks the ‘Photo Booth Launch’ button, a modal pop-up will display the Terms Title and text, along with a checkbox that allows them to opt-in to have their image displayed in the Photo Booth Gallery.
**Moderation Options:** As an organiser, you have the option to moderate attendees' pictures before they are posted in the Photo Gallery Block. This can be enabled by turning on ‘moderation’ when configuring the Photo Booth Block. A submitted photo will appear in one of three states:
- **Private Submission:** These photos are submitted where the user did not consent to have their photo added to the gallery. They can only be viewed by the portal user and won’t appear in the Photo Booth Gallery.
- **Visible in Gallery:** These photos are submitted with consent to be displayed in the gallery and are visible in any gallery on the same canvas as the booth that created them. As the organiser, you can hide the photo using the toggle switch.
- **Hidden in Gallery:** These photos are submitted with consent to be displayed in the gallery but are hidden from the gallery and will not be visible in Community. The organiser can reveal the photo using the toggle switch.
If the moderation is turned on, all new photo submissions (excluding private submissions) will be automatically set to "Hidden in Gallery" and require manual approval from a moderator to appear in the gallery. If moderation is turned off, all new non-private submissions will automatically be visible in the Photo Booth Gallery.
#### Available interactions
Available interactions for the Photo Booth Block are:
- **p** **hoto\_created:**This interaction is triggered when a user completes the Photo Booth workflow by clicking 'Finish' and reaches the stage where they can download their photo or restart the Booth flow. The interaction includes data about the Block ID, the Canvas containing it, the Cloudinary ID, and whether the photo was a public submission.
### Set up a Photo Booth Block
The Photo Booth Block allows attendees to take selfies. They can customise their photos by adding backgrounds (a required step), as well as frames or stickers, without needing to download or install any app.
1. Go to the **Jomablue Portal**
2. Click on **Canvases** under Community on the left-hand menu
3. Click on the Canvas type where you wish to add the Block (e.g., Lobby, Session, Vendor or Page)
4. Locate the specific Canvas where the Block will be added and click **Edit**
5. Click on **Layout**
6. Within a Flex, click **Add Block.** Here, a list of Blocks will appear. **Select Photo Booth.**
7. The Photo Booth Block is now added to the Canvas. You may now add a Title, Configure, Automate or Delete the Block.
8. Populate each field of the block:
**a. Settings**
**i. Call to Action (CTA) Text:** You can customise the CTA text here. This is the button that is used to launch the Photo Booth.
**i. Requires Moderation:** If ticked yes, new photo-booth submissions require moderator approval before they are visible in the Photo Gallery
**iii. Terms of Service:** The Title and Text of the terms of service that are displayed when the user clicks on the Photo Booth Block.
**b. Images**
**i. Background Images:** You can upload backgrounds here. Image size must be 1000px x 1000px, in PNG format with no transparency.
**ii. Sticker Images:** You can upload stickers here. Image size is recommended to be 300px x 300px, in PNG format with a transparent background.
**iii. Frame Images:** You can upload frames here. Image size must be 1000px x 1000px, in PNG format with transparent background.
[https://cdn.jomablue.com/example/example_photo_booth_assets.zip](https://cdn.jomablue.com/example/example_photo_booth_assets.zip)
### User Experience when using the Photo Booth block
To use a Photo Booth Block, the attendee must follow the steps below:
1. Go to a **Canvas Page** of the event where the Photo Booth is located.
2. Click on the **Photo Booth button.** The naming of the block is customisable when configuring it, for example: Launch Photo Booth.
3. Upon clicking on ‘Launch Photo Booth’, the Photo Booth opens in a modal pop-up. The attendee will see the Terms Title and Text, and a checkbox that provides the option to opt-in to have their image displayed in the Photo Booth Gallery or not.
4. Clicking **Continue** expands the modal and displays camera settings. If they choose a webcam, their browser will ask permission to use their webcam (if it hasn't already asked). Otherwise, they can upload a photo via a standard file picker.
5. If the attendee chooses to use the webcam, they will be able to proceed with taking a photo.
6. Once they have taken the photo, they can choose to use the photo or cancel and go back.
7. Once the user has clicked **Use Photo**, artificial intelligence will detect and remove the background from the person in the photo.
8. The attendee can then select the background, stickers, and frames.
9. They can add multiple stickers to a photo, and each sticker can be resized, rotated, and removed if desired.
10. Once the attendee clicks **Complete**, their image will be saved and added to the Photo Booth Gallery, if they have opted in.
11. An attendee can also download their image, start the process, or simply click **Finish** to exit the Photo Booth Block.
**Note:** If the attendee has opted to have their image added to the Photo Booth Gallery, it will be visible there (to them) immediately. However, for all other users, the photo will follow standard caching rules and may take up to 2 minutes to appear.
### FAQs: Photo Booth & Photo Booth Gallery Blocks
Below are some common questions organisers may encounter, along with their answers:
#### **Q. Can the Photo Booth Block and Photo Booth Gallery Block be used in separate Canvases?**
A. The Photo Booth Block and Photo Gallery Block are designed to work together and cannot be used separately.
#### **Q. What does an attendee need to use Photo Booth?**
A. Attendees must meet the following prerequisites:
- Be a registered attendee
- Have a suitable internet connection (see below)
- Have a functioning webcam
- Use a modern browser (see below)
#### **Q. How can an attendee take a photo with the Photo Booth Block?**
A. To take a photo, users need to launch the ‘Photo Booth Block.’ For additional information, please see the section: **User Experience when Using the Photo Booth** **Block** above.
#### **Q. Can attendees download their photos from the Photo Booth?**
A. Yes, attendees can download their photo prior to publishing it, and they can use it as a profile photo or share it on other social media platforms.
#### **Q. Is it possible to moderate the Photo Booth Gallery?**
A. Yes, the Photo Booth Gallery can be moderated. This option can be enabled by turning on ‘moderation’ when configuring a Photo Booth Block. For additional information, see the section:**Set up a Photo Booth** **Block** section above.
#### **Q. What happens if someone doesn’t have a webcam?**
A. If an attendee does not have a webcam, they cannot take their photo. They can, however, upload their photo to the Photo Booth Block. For more information, check out the User Experience when Using a Photo Booth section above.
#### **Q. How long does it take for a photo to appear in the Photo Gallery Block?**
A. The latest photos in the Photo Booth Gallery will display once the Community page is refreshed and the cache time has expired (60 seconds). If moderation is not required, attendees will see their submitted photos immediately.
#### **Q. Is there a limit to the number of attendees who can join the Photo Booth?**
A. No, there is no limit to the number of attendees who can participate in the Photo Booth.
#### **Q. What browser is required for attendees to use the Photo Booth?**
A. Any modern and updated browser, such as Chrome, Edge, Safari, or Firefox, is suitable for participation.
#### **Q. What happens if an attendee has low bandwidth?**
A. A small pop-up message will appear in the Photo Booth Block to indicate a 'Poor Connection'.
#### **Q. Can attendees access the Canvas while using the Photo Booth?**
A. No, attendees cannot access Canvas while using the Photo Booth. When an attendee joins a Photo Booth, it pops up as a modal, and everything is greyed out in the Canvas.
#### **Q. Does the Photo Booth Gallery Block Auto-Refresh**
A. The Photo Booth Gallery Block does not auto-refresh when a user is on the page, and other photos are being submitted. The Gallery will only auto-refresh when the user has uploaded a new photo and no moderation is enabled. This is to ensure the user receives a visual confirmation that their image has been uploaded.
A "Show More" button will appear on the gallery when enough photos have been submitted. You may want to place the Photo Booth Gallery Block in a different location of Community so that it refreshes the content as they navigate to it.
## Question and Answer Block
The Question and Answer Block allows audiences to ask questions during an event. It is generally placed beside the Live Stream Block to engage the audience with the content and allow for a communication flow between the audience and the hosts.
Please note that the host is different from the presenter/speaker of the event.
- A **host** is a person who monitors the host view and coordinates incoming questions, with the ability to view, edit, approve, remove and organise questions
- The **speaker/presenter** is the person presenting content via a Live Stream or similar medium. The presenter may also serve as the host, or a different person may assume that role.
#### Features
The Question and Answer Block provides a native question and answer functionality within Jomablue without any third-party plug-in. Below is a list of features available in this Block:
- Provides a separate Host interface
- Moderation of submitted questions (with an auto-accept setting)
- The ability for the host to edit questions before displaying them
- Attendee voting on submitted questions
- Ability to answer questions in text format via the Questions and Answer Block itself
### Available interactions
Available interactions for the Question and Answer Block are:
- **voted\_for\_question:** Recorded when a user votes for a question in the Suggested tab. Interaction data includes the Question and Answer question ID.
- **submitted\_question:**Recorded when a user submits a question. Interaction data includes the Question and Answer question ID.
### Workflow of a Question and Answer Block
Questions within the Question and Answer Block can have one of the following states:
- **Pending:** A newly submitted question awaiting approval by the host; it is not visible to attendees
- **Suggested:** A submitted question that has been approved by the host and is available for voting by other users. This status can be automatically enabled by selecting the "Automatically Approve" setting during setup. For more information, check out the Set up a Question and Answer Block section.
- **Accepted:** A question that has been accepted and will be answered by the host or presenter of the session. This can be skipped by enabling the "Automatically Accept" setting when configuring the Q&A Block.
- **Answered:** A question that has been answered by the host or presenter, either during the session stream itself or through the Block in text form.
- **Rejected:** A question that was rejected by the host. It is invisible to normal users.
### Host a Question & Answer
A host is responsible for reviewing, editing, managing, and collecting questions for the speaker. A host can be either a speaker or a different person as well.
As a host, you can access the Tools page to manage questions and answers, as shown below:
****
There are two ways to access the Tools page. You can either:
1. Log in to the Community using your credentials
2. Expand the left-hand menu
3. Click on your name provided at the top of the menu bar
4. Select **Tools**
Or you can directly link hosts to their Tools page in an email or campaign. The structure of the URL of the Tools page is as follows:
https://{instance}.jomablue.com/community/{event\_id}/tools
e.g., https://acme.jomablue.com/community/22/tool
On the Tools page, hosts can view the list of Question and Answer Blocks. By selecting a Block, hosts can see the questions and take actions to manage them, as shown in the image below.
****
**Submit & edit questions in** **host mode**
As a host, you can edit questions and change their statuses. The status can be:
- Pending
- Suggested
- Accepted
- Answered
- Rejected
For more status information, please check out the Question and Answer Block section.
If no suggested questions are being received by the audience, the host can submit the questions themselves. The host can also disable suggested questions for the Block or handpick certain questions from the chat block or from an in-person/hybrid event.
In case the ‘anonymous questions’ is enabled, the host has the option to hide the questioner’s name. If the ‘anonymous questions’ are not enabled, the first and last name is shown below.
****
**Moderate pending questions**
The host is responsible for managing pending questions by either accepting, editing, or marking them as ‘accepted’ or ‘suggested.’
****
**Note:** When new questions are suggested and added to the Pending questions view, a badge will appear on the Refresh button to indicate to the host that there are new Pending questions. This facilitates the host to avoid constantly monitoring the view.
**Monitor suggested questions**
Suggested Questions are available for Community users to vote on, and the Host can transition them to Accepted based on their scores, as shown below.
****
**Manage accepted questions**
Once questions are accepted, they will be available for the presenter to answer. The Host should monitor these questions and mark them as answered once the Presenter has answered them, or move them back to pending status if required.
****
**Manage answered questions**
After marking a question as answered, the host has the option to edit the question to add a text summary of the answer.
****
### **Use cases of managing Question and Answer**
#### **Moderate Question and Answer by a Dedicated Host**
When the host of the Question and Answer Block is not the same person as the speaker/presenter in the accompanying live stream session, the host moderates and selects questions to provide to the presenters for answering.
**General Configuration**
The general configuration in this case is:
- Automatically approve submitted questions: disabled
- Automatically accept newly suggested questions: disabled
- Initial View - Suggested Questions
- Show Suggested Questions View: enabled
- Suggest a Question: enabled
- Show Accepted Questions View: enabled
- Show Answered Questions View: enabled
You can configure these settings when setting Question and Answer Block. For more information, check out the Set up a Question and Answer Block section.
**Workflow**
The workflow in this case is:
- Users suggest questions via the Suggest a Question box
- The host moderates the suggested questions:
- Can use "Mark as Suggested" to add Pending questions to the Suggested Questions view, where other users can vote on them
- Can use "Mark as Accepted" to mark the most voted-for Suggested Questions as Accepted, indicating they are ready to be answered by the presenter(s)
- Can also directly mark Pending questions as Accepted to fast-track them
- Questions in the Accepted view can be viewed directly by the presenters or communicated via other means by the host to the presenters
- Questions that have been answered by the presenters can be marked as Answered
- Optionally, the host can add a text summary of the answer to the Question itself via the Edit button
**Submit a Question and Answer via other Channels**
Questions for this session can be submitted through methods other than the “Suggest a Question” feature, such as a Live Chat Block or a custom registration field.
**General Configuration**
The general configuration in this case is:
- Automatically approve submitted questions: disabled
- Automatically accept newly suggested questions: disabled
- Initial View: Accepted Questions
- Show Suggested Questions View: disabled
- Suggest a Question: disabled
- Show Accepted Questions View: enabled
- Show Answered Questions View: enabled
**Workflow**
The workflow in this case includes the following steps:
1. Users submit questions via the alternate channel
2. The host adds chosen questions directly to the Accepted view using the "Add a Question" box in the host view
3. Questions in the Accepted view can be viewed and answered by the host
4. Once a question has been answered by the presenters, it can be marked as Answered
5. Optionally, the host can add a text summary of the answer to the Question using the Edit button
### Set up a Question and Answer Block
A Question and Answer Block allows attendees to ask questions during a virtual or hybrid event, allowing a host (or hosts) to answer the attendees’ questions.
#### Steps to Add Question and Answer Block in a Community Canvas
1. Go to the **Jomablue Portal** and log in with your email address and password
2. Click on **Canvases** under Community on the left-hand menu
3. Click on the Canvas type where you wish to add the Block (e.g., Lobby, Session, Vendor or Page
4. Locate the specific Canvas where the Block will be added and click **Edit**
5. Click on **Layout**
6. ****Within a Flex, click **Add Block.** A list of Blocks will appear. **Select Question and Answer.**
7. The Question and Answer Block is now added to the Canvas. You may now add a Title, Configure, Automate or Delete the Block.
### Configure the Question and Answer Block
The block configuration contains useful field labels that explain the functionality of each toggle. Configuring these toggles can change the experience for Community Members or Hosts. For example, specific configurations may allow a session to run without a host (in scenarios where a single speaker is presenting and handling everything). Alternatively, if there is a host curating questions for on-stage speakers, a specific configuration is available to support that. For additional information, please see the section: **Host a Question & Answer and use cases** above.
#### **1. Submission and Approval Settings**
**Hosts**
Hosts are considered the 'coordinators' of incoming questions. They can view, edit, approve, remove, and order questions. While there is typically one host, multiple hosts can manage a single Question and Answer Block. To host a Question and Answer Block, a host or hosts must:
- Be a person attending the event
- Be logged into the Community
- Access their hosted Question and Answer Block by navigating to their profile.
**Note:** For additional information, please see the section: **Host a Question & Answer and use cases**above.
**Automatically approve submitted questions**
When enabled, submitted questions are automatically approved. This setting is toggled off by default.
**Automatically accept newly suggested questions**
This setting allows suggested questions to be immediately accepted. Approved questions will bypass the suggested questions list and go directly to the accepted question list. This is toggled off by default.
#### **2. View Settings**
**Select Initial View**
This is the view attendees see when the block first loads on a canvas. By default, the "Suggested Questions View" is selected. However, there may be situations where you prefer attendees to view Accepted or Answered Questions first.
For example, after a live event has concluded, setting the default view to 'Answered' along with a recording of the live stream could enhance the audience experience.
**Show Suggested Questions View**
The view allows users to suggest questions, view a list of suggested questions, and vote on them. This is toggled on by default.
**Suggest a question**
The host can choose to accept or decline suggested questions submitted by attendees. Suggestions can also be collected from other sources, such as the Live Chat Block, or prepared in advance.
This feature is enabled by default. If disabled, attendees can only view accepted questions on the canvas and will not have the option to suggest questions.
**Suggest a question text**
This text is optional and appears directly above the input field on the Block. For example,
“We welcome all your feedback; please submit a question or feedback about today’s session.”
**Anonymous questions**
Allow attendees the option to submit questions without their names being displayed publicly.
**Highlight the first question**
By default, this feature is enabled. The first question in the accepted question list is highlighted to indicate the "current question".
**Note:** The background colour used here is based on the 'Primary Colour' set in the event theme, which must contrast with the 'Primary text' colour.
#### **3. Advanced Settings**
**Height**
You can adjust the height of the Question and Answer Block here. Multiple values can be added, separated by commas, for responsive design. If no specific height is set, the Block will default to 500 px in height.
**Maximum questions displayed**
This setting is applicable only for events with over 10,000 people. The default is already set to accommodate most events, ensuring an efficient and optimal user experience. If there’s a possibility that an event will exceed 10,000 people, Jomablue will provide guidance on the best value for this setting.
### FAQs: Question and Answer Block
Below are some common questions organisers may come across and how to resolve them.
#### **Q. Can a single person host multiple Questions and Answers Blocks?**
A. Yes, a single person can host multiple blocks. To do this, they should navigate to "Tools" within the Community, where they will see all the blocks they are hosting. For additional information, please see the section: **Host a Question & Answer and use cases**above.
#### **Q. How long does it take for a question to display for all the attendees?**
A. The Jomablue Q&A block uses caching to support large-scale interactions. Due to caching mechanisms, it’s common for users to receive content updates at different times. When a question changes statuses, it may take up to 60 seconds for it to be displayed to everyone. Therefore, different community members viewing the Question and Answer Block may see questions appear at different times within that timeframe.
#### **Q. How can a host access the Tools page?**
A. There are two ways to access the Tools page, you can either:
1. Log in to the Community using your provided credentials
2. Expand the left-hand menu
3. Click on your name provided at the top of the menu bar
4. Select **Tools**
Alternatively, you can directly provide hosts with a link to their Tools page in an email or campaign.
#### **Q. Can a presenter also be the host of the Question and Answer Block?**
A. Yes, the presenter can serve as the host of the Question and Answer Block.
#### **Q. Can you highlight specific questions?**
A. You can only highlight the first question in the accepted questions list to indicate the "current question". For additional information, please see the section: **Set up a Question and Answer** **Block**above.
## Quick Survey Block
A Quick Survey Block allows you to place one or multiple quick survey-style questions on a Canvas. This Block is designed to measure overall event or session satisfaction, providing users with an easy-to-answer survey experience. The Quick Survey Block supports a simple 5-star rating system that users can click to submit. The more stars selected, the more positively the users responded to the survey.
#### Features
Multiple questions can be added to a single Quick Survey Block
Upon submitting an answer to any question in a Quick Survey Block, a custom success message can be displayed
**Use-case example of Quick Survey Block:**
- Secondary question text can be included as optional helper text beneath the main question
- Once a user submits a response in a Quick Survey Block, they will be unable to resubmit their response. Their browser will store the individual response and display it again if they return to the Canvas containing that Block.
**Note:** If the user clears their local storage or views the Block on another device, they will be able to submit another response
#### Benefits of using a Quick Survey Block
The Quick Survey Block has the following benefits:
- **Ease of use:** The survey is quick and easy to use, as users only need to click on the stars to provide their feedback
- **Visual medium:** The star system provides a tactile visualisation for collecting feedback
- **E** **asy to analyse:** Each star corresponds to a weighted scale that can be converted into numerical data, making it convenient for generating reports
- **Interactive:** Users can express their satisfaction or dissatisfaction with the session
#### Available interactions
Available interactions for the Quick Survey Block are:
- **Response Submitted** (response\_submitted)
All responses are recorded as Block Interactions. The interaction data includes the question UUID, text, and the response given. This interaction can also be stored for post-event reporting and block automation.
Additionally, block metrics are available in a People Export. When a Community contains one or more Quick Survey Blocks, a column will be added to the report for each question in all Quick Survey Blocks. For example, if a Community has 8 Quick Survey Blocks with 2 questions each, a total of 16 columns will be added.
Each Column has a header containing:
- The Block Type
- The Block ID
- The name of the Block (if provided)
- The Question Text
### Set up a Quick Survey Block
A Quick Survey Block allows you to place one or more quick survey-style questions on a Canvas in a Block.
1. Go to the Jomablue Portal
2. Click on **Canvases** under Community on the left-hand menu
3. Click on the Canvas type where you wish to add the Block (e.g., Lobby, Session, Vendor or Page)
4. Locate the specific Canvas where the Block will be added and click Edit
5. Click on **Layout**
6. Within a Flex, click Add Block. Here, a list of Blocks will appear. Select Quick Survey.
7. The Quick Survey Block is now added to the Canvas. You may now add a Title, Configure, Automate or Delete the Block.
8. Populate each field of the Block:
**a.** **Description** - An optional message, such as ‘Post Session Survey’, can be added here. It will appear above the list of questions.
**b.** **Success Message** - A success message appears after the submission has been made. A success message can be customised, for example, ‘Thanks, have a great day’. If left blank, it defaults to ‘Thanks for providing your feedback!’.
**c.** **Questions** - you can add one or more questions to the survey here. For each question, these are the following fields:
**i.** **Question Text** - The text of the question itself
**ii.** **Question Type** - Currently, only 5-star ratings are available
**iii.** **Secondary Question Text** (optional) - It’s a helper text that can be displayed below the
main question text.
**iv.** **Question UUID** - This is automatically generated upon saving, and it’s not editable
## Vendor Lead Capture
Vendor Lead capture is the contact information of a prospective customer that is gathered when they click on an online advertisement. The Vendor Lead Capture Block is a configurable Block that can be placed on any Canvas, meaning it is not limited to just a Vendor Canvas; it can also be placed on Session or Lobby Canvases.
#### Features
Vendor Lead Capture Blocks always feature a Button that captures the Person using the Block as a Lead.
Additionally, these Blocks can be configured to allow a Person to include a message when submitting their lead, and the option to include "Tags" to indicate their level of interest in a product or specify which product they are interested in.
**Notes:**
- The Vendor must be visible in the Community for leads to be captured
- If multiple Vendor lead capture blocks are assigned to the same Vendor, you need to identify where they came from. In the Block Configuration, add a note to the "default note" field describing the source. For example, if Vendor has both a "Contact me" and a "Subscribe to our newsletter" Vendor Lead Capture Block, you add a note associated with these use cases.
#### Available Interactions
Sometimes, a person may submit a Vendor Lead Capture multiple times during an event - either to add more notes or select different Tags. The following interactions will be recorded when a Lead already exists for a Person:
- The time when they first captured themselves as a Lead (the lead creation time) will be retained
- The time when they first captured themselves as a Lead (the last modification time) is also recorded
- Any new Tags selected by the Person will be saved and added to the existing tags. If a previously selected Tag is not chosen again, it will remain in place.
- Any new Notes added by the Person will be added to the end of the existing Notes
### Set up a Vendor Lead Capture Block
1. Go to the **Jomablue Portal** and log in with your username and password
2. Go to the **Community** section on the left-hand menu bar. Click on the **Canvas**
3. Click on the Canvas where you want to add ‘Vendor Lead Capture’ Block
4. Click on the **Layout Editor**
5. Click on **Add Block.** A list of Blocks will appear; choose **Vendor Lead Capture Block.**
6. The Vendor Lead Capture Block is now added to the Canvas. You can now add a Title, configure, automate or delete the block.
****
### Configuration Options
In addition to the customisable fields listed above, the Vendor Lead Capture Block features the following configuration options:
****
A Vendor Lead Capture Block has a number of optional, configurable fields, including:
- **Select Vendor:** Choose the vendor here
- **Description:** Plain text displayed below the Heading (optional)
- **Tags heading:** If Tags are enabled, this heading appears above the Tag checkboxes (optional)
- **Allow Adding Tags:** If you enable the "Allow Tags" option, you can configure one or more Tags for selection by the Lead when they submit their Vendor Lead Capture. These Tags will be indicated in your Vendor Lead Capture Export. An example of how Tags look in the Vendor Lead Capture Block can be seen below:
- **Allow Adding Message:** A toggle option that allows the Person to include a free-text message when submitting their Vendor Lead Capture
- **Button label:** The label on the button to submit the Vendor lead capture (required)
- **Button Full Width/Wrap Text:** Determines if the Block is to display in a way that wraps the button label over multiple lines
- **Privacy warning text:** A text that warns the Person that their details will be shared with the Vendor (optional)
- **Success message text:** The text displayed to the person after successfully completing the Vendor lead capture form (required)
- **Default Note:** If configured to allow a Person to leave a message, then a "Default Note" will be attached to the start of the message the Person leaves. It helps indicate which Block the lead was captured from in the Vendor Lead Export.
****
- **Button Full Width/Wrap Text:** This option enables the Block to display in a way that wraps the button label over multiple lines:
****
- Without this option enabled, a longer button label will display in a single line, like this in Community:
****
[NextPage](https://support.jomablue.com/llms-full.txt/1)