Integration Approaches

are you designing activations for your event? if you're building an activation, you have two approaches to integrate with the jomablue platform approach one diy build your own activation you provide hardware nfc reader + software integration that calls jomablue apis jomablue provides apis to retrieve attendee data this approach requires hardware that can read an nfc badge, an attendee’s nfc badge, and some functionality that will take that badge id and post it to a jomablue http endpoint, and receives attendee details (name, segment, attributes) to personalise the experience example workflow attendee taps their badge on your nfc reader your system sends the badge id to a jomablue endpoint jomablue returns attendee details (name, segment like "marketing", "it", "sales", etc ) your activation displays personalised content based on that data optionally, attendee makes selections or provides preferences during the experience \[summary tap → api call → get name & segment → show personalised content] data storage recommendation it's recommended that any data generated from the activation experience, such as attendee selections, opt ins, or preferences, is stored within the activation itself while you can send this data back to jomablue via ingest apis, we recommend keeping it simple store the attendee's unique identifier along with their preferences in your activation system, then ingest this data into your crm or other systems once processed approach two jomablue touchpoints available march 2026 onwards you provide web service/application to receive data and run the activation jomablue provides touchpoint hardware (nfc enabled handheld devices) touchpoints are jomablue devices that can be configured to send http post requests (ie, a webhook) to your activation endpoint when an attendee taps their badge the request contains attendee details (first name, last name, and other configurable fields) that you use to personalise the experience hardware details device specs battery powered, wireless, 5g enabled handheld device deployment options held by staff for human initiated, personalised interactions mounted in custom enclosures (oversized phone cases shaped as discs, shields, cloud icons, or other thematic elements) configuration flexibility configure each touchpoint to send requests to different endpoints use multiple touchpoints for multi station activations (e g , four touchpoints at four stations, each triggering different screens or experiences) customise which attendee data fields are included in the webhook payload—you only receive what you need what you build with touchpoints, you focus entirely on the activation software create a web service or web application implement an endpoint to receive http post webhooks from jomablue parse the incoming data and trigger the personalised experience no need to develop or maintain nfc hardware infrastructure further considerations jomablue does not provide the onsite screens, led walls, or display hardware that your activation runs on at a minimum, you will need a screen and computer running a web browser to display your activation jomablue provides the badge reading infrastructure and apis that facilitate the connection between the smart badge tap and your activation, triggering the personalised experience on your displays choosing your approach use approach one (diy) if you have existing nfc hardware infrastructure such as usb readers you need complete control over hardware implementation you're integrating badge reading into custom physical installations you want to handle all aspects of the hardware and software stack use approach two (touchpoints) if you want to focus solely on software development you value staff initiated, human led interactions you need wireless, battery powered, mobile badge reading you want faster time to market without hardware development overhead you prefer jomablue to handle the nfc hardware infrastructure technical foundation all jomablue smart badges use rfid/nfc technology with unique identifiers jomablue provides apis that look up attendees via these ids and return their data for personalisation whether you choose diy or touchpoints, the core principle is the same badge tap → data retrieval → personalised experience