The problem
An established exhibitions and conference client wanted registrants to browse exhibitor booths, companies, and contact details through Jublia, a third-party exhibitor-engagement platform, without it feeling like a separate product bolted onto their Swoogo event microsite. Syncing registration data to Jublia in the background on a schedule wasn’t going to cut it. Attendees needed to move from looking at their Swoogo event page to standing inside the exhibitor Engagement Hub in one step, already identified as themselves, no extra login required.
The approach / solution
- Built a custom JS snippet at the Swoogo theme layer that reads the current registrant’s ID and passes it into Jublia’s Engagement Hub URL for exhibitors, surfacing booth, company, and contact data in context, directly from the Swoogo microsite.
- This is the front-end half of a two-layer integration for the same client. A separate NestJS backend service, documented in a companion case study on the backend integration platform, pushes registrant data to Jublia via webhook whenever Swoogo registration data changes, keeping Jublia’s own attendee record current on its own.
- Kept the theme-layer piece deliberately small and single-purpose: a registrant-ID hand-off. The ongoing sync work stays entirely on the backend layer, so that logic isn’t duplicated inside the page-builder constraint.
Outcome / result
This client’s Jublia integration is independently built and verified at two separate layers of the stack: a backend webhook service keeping attendee data in sync, and this Swoogo theme/JS snippet handling the in-context front-end hand-off into Jublia’s exhibitor Engagement Hub. That’s full-stack depth on a single account. Most of the platform’s integration breadth is spread across many different clients; this is depth on one.
Why it matters for enterprise event-tech
A Swoogo specialist who can point to the same client’s integration working correctly at both the backend-sync layer and the theme/front-end layer makes a stronger, more concrete claim than “integrated with N third-party platforms.” It shows the whole pipeline was actually owned end to end, for at least one account. No single layer was someone else’s problem.
