Breadcrumbs

September 2026 Product Updates

Multi-Day Session Calendar View Enhancements & Dedicated Day Endpoints ( EP-57107 , EP-57014 )

  • What: Extended POST /api/v1/search/sessionsCalendarView to accept an inclusive date range (dayFrom, dayTo up to 31 days) and introduced a dedicated POST /api/v1/search/sessionsDates endpoint returning all event days holding sessions alongside per-day session counts.

  • Why: The session calendar previously rendered only a single day or fixed week at a time, and the day picker had to be built from heavy, unpaginated search queries.

  • How it's helpful: Significantly accelerates calendar initialization and enables seamless agenda navigation across flexible, multi-day event schedules.

Session Calendar: Dynamic Display Filter Sync for Side Drawer ( EP-57237 )

  • What: Updated the Session Calendar Side Drawer so the "By Track" tab label dynamically inherits the organizer-configured Display Filter name from Admin Panel (e.g., "By Streams", "By Topics"), including multi-language translations.

  • Why: The Side Drawer hardcoded "By Track", creating a label discrepancy when organizers customized their display terminology.

  • How it's helpful: Ensures terminology remains consistent across the entire attendee event experience and localized interfaces.

Session Filters API V2 Integration (Read & Write) ( EP-57347 , EP-57348 )

  • What: Added support for event session filter slots (filter_1 to filter_5) across Open API V2 write (POST /api/v2/sessions/set) and read endpoints (GET /api/v2/sessions/get, GET /api/v2/sessions/getSession) with case-sensitive validation, multi-language matching, and timestamp-based delta support.

  • Why: Custom session filters configured in the Admin Panel were previously inaccessible via Open API V2, blocking external catalog syncs.

  • How it's helpful: Enables external systems to programmatically read and assign session filter tags without requiring manual admin entry.

Private Favouriting for Opted-Out Users on Mobile ( EP-57577 , EP-53978 )

  • What: Enabled the favourite affordance on mobile apps (iOS & Android) for networking opted-out users across exhibitor, visitor, and product profiles, privately recording their favourites without exposing their identity or creating public leads.

  • Why: Opted-out users previously had the favourite action hidden entirely in mobile apps, preventing them from bookmarking items of interest.

  • How it's helpful: Provides feature parity with web and allows privacy-conscious attendees to maintain personal shortlists across devices.

Restrict Meetings and Messages for Exhibitors Without Team Members on Mobile ( EP-54176 , EP-54268 )

  • What: Enforced the organizer setting "Restrict meetings and messages for exhibitors with no team members" on mobile apps, greying out Meet and Message buttons with informative toast feedback when an exhibitor has no active team members.

  • Why: Attendees on mobile could previously send meeting requests and messages to unstaffed exhibitors, causing unanswered inquiries and user frustration.

  • How it's helpful: Eliminates dead-end attendee interactions and aligns mobile meeting rules with the web platform.

Lead Capture Pro: Granular Profile-Level Configuration & Custom Questions ( EP-50535 , EP-48813 )

  • What: Introduced account-level configuration flags for Lead Capture and AI Note Taker on mobile, along with unrestricted access to Standard and Additional Lead Capture custom questions when purchased by exhibitors.

  • Why: Feature access was previously tied to global App Builder toggles or organizer-wide question caps rather than individual exhibitor packages.

  • How it's helpful: Allows organizers to monetize advanced Lead Capture Pro features per booth/user and empowers exhibitors to fully customize their lead qualification workflows.

Dedicated SAML 2.0 Integration Page in Integrations Hub ( EP-57684 )

  • What: Migrated SAML 2.0 configuration to a dedicated settings page (/admin/integrations/saml) built on the modern hub integration template.

  • Why: SAML authentication settings were previously placed inside shared legacy settings, making them hard to locate and configure.

  • How it's helpful: Unifies SSO and enterprise IdP configuration within the centralized Integrations Hub.

Native Swoogo Integration via Integration Hub ( EP-54645 )

  • What: Launched a native inbound integration for Swoogo supporting automatic attendee/visitor onboarding, exhibitor record generation, team member linking, OAuth2 token auto-refresh, and incremental sync watermarks.

  • Why: Organizers using Swoogo needed automated attendee and exhibitor sync without maintaining manual scripts.

  • How it's helpful: Keeps attendee lists and exhibitor booth staff synchronized in real time with zero manual intervention.

Admin Panel Untitled UI Modernization ( EP-54462 , EP-54463 , EP-54464 , EP-54465 , EP-54466 , EP-54547 )

  • What: Restyled key Admin Panel modules to the modern Untitled UI design system across Event Setup, Categories Setup (Networking & Matchmaking), Exhibitor List, Participants List, Sessions List, and Event List.

  • Why: Legacy admin interfaces suffered from visual inconsistency and outdated table layouts.

  • How it's helpful: Delivers a cleaner, more responsive, and visually cohesive management interface for event organizers.

WebP Image Delivery & Frontend Asset Optimization ( EP-57489 )

  • What: Migrated image requests across portal-ui (Site Builder, cards, banners, headers) to dynamically sized WebP variants (xf-webp), eliminating raw unresized PNG uploads.

  • Why: Unresized PNG assets represented over 76% of daily image bandwidth, slowing down page loads and impacting Core Web Vitals.

  • How it's helpful: Significantly improves Largest Contentful Paint (LCP) and page load speed for attendees while decreasing data transfer.

Integration Hub: "Email First" Compound Identity Matching ( EP-54452 )

  • What: Added an "Email First" matching strategy that falls back to External ID when emails do not match, and renamed the existing "Both" strategy to "External ID First".

  • Why: Attendees who updated their email addresses in third-party registration systems (e.g. VISIT/GES) were previously getting duplicate accounts created.

  • How it's helpful: Preserves attendee profiles, engagement history, and connections across sync updates.