Event Settings
Create an event
To create a new Event in your Instance, follow these steps:
- Log into Jomablue
- Navigate to the Event List in your Instance
- Click on the Add Event button at the top-right of the page
This will bring up a form with several fields that need to be filled out to create the Event. Below are explanations for each field:
Event Name:
This is the public-facing event name. It will be used in emails and other public contexts.
Event Start Date/Time
This indicates when the event starts and is used for representing sessions in the grid view and other time-based calculations.
Event Finish Date/Time
When the event ends. It is crucial for calculating the validating period for lead capture exports and other important functions.
Timezone
Specify the event’s timezone to ensure that all times displayed in Jomablue are shown in local time. This is also important for scheduling campaigns correctly. To find your timezone, look for the continent and then the specific location (e.g., Asia > Singapore).See the section below: Timezones for more information.
Target
This is an estimate of the total number of attendees you expect, including speakers, staff, crew, delegates, and others. You can safely exceed this number without impacting performance.
Event Preset (Optional)
Event Presets allow you to automatically configure parts of this new event saving you setup time and driving consistency across your experiences. They are exported from an existing event on settings that support Event Presets.
Notes:
- All of these fields can be updated later through Settings after the event is created.
- You can only add a new event using a desktop. If you attempt to create an event on a mobile or tablet device, a notification will pop up stating, “Launch Jomablue on your desktop to add an event.”.
Event Settings
The Event Settings page is central to configuring your Event in Jomablue. Here, you can manage the date, time, timezone, and other information about your Event. To modify Event Settings, navigate to Event Configuration > Settings.
Email and SMS
SMS From Name
Note: SMS sending capabilities are disabled by default in new instances. Please complete a request to enable SMS-sending capabilities.
By default, the SMS sender ID is set to EventInfo for each new event. You can select a different SMS Sender ID from the dropdown menu.
Email From Address
By default, the Email sender ID is set to no-reply@event-email.com for each new event. You can choose a different Email Sender ID from the dropdown menu.
For additional information see the article: SMS and Email Sender IDs
Extended Detail
Session Restricted Message
This message is displayed on the Session Check-In device when a person is not entitled to attend a particular session. You can include information to guide the person to the right location for further assistance (e.g., "You're not entitled to attend; please see the information counter").
Short Description
A short description of your Event.
Long Description
This will be used on the welcome page of the Event App to inform attendees about the event. It typically mirrors the welcome text from the event website.
Venue Name
If the event is virtual, you can enter “online”. This can be free text, allowing for multiple venues to be listed. This information will be displayed on the Community welcome screen and events listing.Venue Address
The physical address of the Venue if it’s an in-person event, or specify ‘online’ for a virtual event.
Creative Assets
Default Event Header
This image must be sized 600x100px and is used as the header for all registration emails. It will serve as the default header whenever you create a new Email Template.
Default e-Ticket Header
This image must be sized 1200x300px and is displayed at the top of the event e-Ticket. There is only one e-Ticket header per event.
Label Settings
Apply Custom Registration Labels to this event, for example different languages.
Privacy Settings
Allow vendor lead exports to include mobile numbers
This setting determines whether mobile numbers will be included in Vendor Lead Exports.
Session Settings
Inferred Sessions
Users can enable or disable inferred sessions. If enabled, Jomablue will automatically infer which sessions a person has attended based on check-in and session check-out interactions. For additional information see the article: Inferred Sessions.
Timezones
In Jomablue, many features such as Sessions, Email, and SMS Campaigns rely on accurate time settings. Therefore, it’s essential to set the correct timezone for your event.
Regardless of the event type (in-person, hybrid or community), all dates and times displayed in Jomablue are displayed in the time zone for the event. This timezone reflects when the event will take place, which may differ from the organiser’s timezone or the timezone of individual attendees, depending on their locations.
For example, if you are in San Francisco but organising an event in Singapore, you will set the event’s timezone to Singapore. Thus, all related timings will be displayed according to Singapore time.
When scheduling a campaign for an event in Singapore, if you set it to send at 9:00 am in Jomablue, it will be sent at 9:00 am Singapore time.
How does Jomablue handle Daylight Savings?
Jomablue automatically handles timezone conversions and adjustments for daylight savings times.
What if the city is not displayed in the list?
If you find that the event location is not listed, choose an alternate city that shares the same timezone. For example, if your event is in San Francisco, you might select Los Angeles since both cities fall under the same time zone.
Change an Event Timezone
Times assigned to Sessions or for “hide and reveal” features within Community depend on the Event Timezone. Should you change the timezone, any times set prior will be adjusted to the equivalent time in the new timezone. It’s important to update any existing records accordingly.
Scheduling Campaigns and changing the Event Timezone
When scheduling a Campaign, the original timezone is recorded within the Campaign. If you change the timezone after scheduling, the Campaign won't automatically reflect this change. In such cases, you should cancel the existing Campaign and create a new Campaign after altering the timezone.
Use Test Events in Jomablue
Jomablue supports running multiple events for an organisation, allowing for common settings and attributes across different events. This feature helps a person's record be persistent across multiple events and offers deeper insight into engagement.
However, it’s crucial to note that Test Events can clutter production data. For example, if you create a Test Event with various test categories and person records, this will remain visible across your event reporting in your Jomablue instance indefinitely.
In addition, the level of effort to get a Test Event running to test some functionality, it's generally not worth it.
What we suggest
Each Jomablue instance comes with a default test event named "Christmas Party,” which serves as a playground for you to add people's records and content to familiarise yourself with the platform.
If you wish to test an email, we recommend adding yourself as a person record in the production event, categorising yourself correctly as “Staff” or “Crew.” You can then use the Test Campaign feature to send yourself emails from the event, allowing you to test the experience without creating unnecessary workloads or disrupting event data.
If you have any questions or need assistance, feel free to reach out. We can help you conduct test cases without affecting production insights.
