The problem
A Swoogo microsite page loads once and shows whatever was there at that moment. This client needed one part of their event microsite to update on its own, without an attendee having to refresh the page to see it.
The approach / solution
- Swoogo’s page builder only accepts Twig templates, so the connection code was written directly into this account’s own microsite template.
- Used Socket.io as the client library to open and hold a live connection to a backend service.
Outcome / result
This connection runs in production on the client’s microsite today. It’s a small build, one connection doing one job, sitting alongside the same client’s larger wallet-pass, messaging, and flight-sync work on the platform.
Why it matters for enterprise event-tech
Most Swoogo microsites are static once they load. Getting a live backend connection working inside that same page-builder constraint is a narrow capability, but a real one most theme-only builds never need to reach for.
