Release 9.32.0

Release Date: 4 Feb 2025

New Feature

Jomablue Push API now supports Vendor Lead and Session Participation data

The Jomablue Push API, which utilises AWS SNS to broadcast data from Jomablue to allow third parties/customer apps to consume event data, now supports Vendor Lead data and Session Participation (Session Attendance) data.

This addition complements the existing event and people data. With these enhancements, customers can consume real-time data from Jomablue as it happens, including information related to the event and its settings, attendees and their checked-in statuses, interactions with Vendors, and engagement during sessions. The sessions data includes inferred sessions when it’s enabled.

Customers are now able to feed this additional Jomablue event data back into their CRMs or power third-party event apps.

Documentation for these APIs can be found here: https://apidocs.jomablue.com/docs Integration Test API

Integration Test API

As part of the Jomablue Push API integration process, our customers’ technical teams often request testing of their integration. We have introduced a specific API that allows them to trigger a test data stream from Jomablue, simulating real production data without the need to print someone's badge, check them into a session, or collect a lead using Omnia.

Granular controls on enabling Push API

Previously, the Push API was an all-or-nothing feature for all events in an instance. We have now implemented granular controls allowing customisation on a per-event and per-resource type basis. This means we can enable “only people” data for one event while allowing “vendor lead and session participation” data for another event within the same instance. This represents a significant step towards automatically disabling integrations when events are archived.