Breadcrumbs

June 2026 Product Updates

API V3 Migration — Floorplan Halls Endpoint ( EP-51338 )

  • What: Migrated /api/v2/floorplan/getHalls to API V3.

  • Why: V2 endpoints are deprecated; V3 provides a consistent, modern API.

  • How it's helpful: Integrators can retrieve floorplan hall data via the standardized V3 API with clearer structure and documentation.

API V3 Migration — Floorplan Stands Endpoint ( EP-51337 )

  • What: Migrated /api/v2/floorplan/getStands to API V3.

  • Why: V2 endpoints are being sunset; stands data needed the new API standard.

  • How it's helpful: Third-party systems can access stand and booth information through V3 with consistent response formats.

Sorting & Multi-Select for Internal Floorplan ( EP-51701 )

  • What: Added sorting and multi-select to the internal floorplan management interface.

  • Why: Managing many stands individually slowed organizers working on complex layouts.

  • How it's helpful: Organizers can sort stands by criteria and perform bulk actions on multiple stands.

Universal Pagination Memory — Required Lists ( EP-52457 ) ⚡ Urgent

  • What: Implemented pagination memory in Admin Panel for all "Required" lists, preserving page and sort state across navigation.

  • Why: Users lost their place when navigating away from long lists, disrupting workflows.

  • How it's helpful: Administrators no longer lose pagination state when switching sections — the panel remembers where they left off.

Standardising Pagination in Admin Panel ( EP-52989 ) ⚡ Urgent

  • What: Standardized pagination across all Admin Panel sections for consistent UX.

  • Why: Pagination behaved inconsistently across the panel, causing confusion.

  • How it's helpful: Administrators now see predictable, uniform pagination regardless of section.

Restoring GA4 Integration and Validation ( EP-53455 ) 🔺 High

  • What: Restored Google Analytics with full GA4 integration and measurement ID validation.

  • Why: GA4 support had degraded, leaving organizers without tracking.

  • How it's helpful: Organizers can track visitor behavior with GA4 and avoid misconfiguration via validation.

Admin Panel Rearrangement — Move Sponsorship ( EP-53413 ) 🔺 High

  • What: Moved the Sponsorship section to a more logical position in the navigation.

  • Why: Sponsorship was in a non-intuitive location, making it hard to find.

  • How it's helpful: Organizers can find and manage sponsorship settings more naturally within the panel.

API V3 Migration — Location Regions ( EP-51343 )

  • What: Migrated /api/v2/location/regions to API V3.

  • Why: V2 deprecation required regions to adopt V3.

  • How it's helpful: Integrators can retrieve location regions via the modern V3 API.

API V3 Migration — Location Countries ( EP-51344 )

  • What: Migrated /api/v2/location/countries to API V3.

  • Why: Countries reference data required V3 standardization amid V2 deprecation.

  • How it's helpful: Integrators can retrieve country lists via the V3 API.

API V3 Migration — Sessions Languages ( EP-51354 )

  • What: Migrated /api/v2/sessions/getLanguages to API V3.

  • Why: Session metadata endpoints needed V3 consistency.

  • How it's helpful: Integrators can access session language data via the unified V3 interface.

API V3 Migration — Sessions Tags ( EP-51355 )

  • What: Migrated /api/v2/sessions/getTags to API V3.

  • Why: Tags are essential for session filtering; the V2 endpoint was being sunset.

  • How it's helpful: Third-party systems can retrieve session tags through V3 for richer content filtering.

API V3 Migration — Sessions Types ( EP-51359 )

  • What: Migrated /api/v2/sessions/getTypes to API V3.

  • Why: Session type classification required V3 migration during deprecation.

  • How it's helpful: Integrators can filter and categorize sessions by type via standardized V3 endpoints.

API V3 Migration — Sessions Tracks ( EP-51360 )

  • What: Migrated /api/v2/sessions/getTracks to API V3.

  • Why: Track data is critical for agenda views and needed V3 standardization.

  • How it's helpful: External systems can access session track information via V3 for custom agendas.

Always Display Sponsor Name on Session Cards and Pages ( EP-53036 ) 🔺 High

  • What: Ensured sponsor names always appear on session cards and detail pages.

  • Why: Sponsor branding displayed inconsistently and sometimes hid due to layout.

  • How it's helpful: Sponsors get consistent visibility, and attendees always see who sponsors a session.

Removal of Lead Capture Pro Global Settings & QR Codes Export Adjustments ( EP-54261 ) 🔺 High

  • What: Removed deprecated Lead Capture Pro settings and adjusted QR code export in Admin Panel.

  • Why: Legacy settings confused users, and QR export needed alignment with current features.

  • How it's helpful: The Admin Panel is cleaner, and QR export now matches current lead capture.

D2i — Native Integration Build ( EP-52290 )

  • What: Built the D2i native integration using the Abstract Integration Schema.

  • Why: D2i required a custom integration; a native option simplifies setup and maintenance.

  • How it's helpful: Clients using D2i can connect via a supported native integration with minimal configuration.

Google Analytics Field Front-End Validation ( EP-53548 )

  • What: Added front-end validation for Google Analytics measurement ID fields in Admin Panel.

  • Why: Users could enter invalid GA IDs without feedback, causing tracking to fail silently.

  • How it's helpful: Organizers get immediate feedback on invalid GA4 IDs, preventing broken analytics.

Universal Pagination Memory — Good To Have Lists ( EP-53117 )

  • What: Extended pagination memory to "Good To Have" lists, completing the rollout.

  • Why: After Required lists received pagination memory, remaining lists still lost position.

  • How it's helpful: Full pagination memory across the Admin Panel — no list loses your place.

Session: External Registration URL for "Register" Button ( EP-52375 )

  • What: Added support for external registration URLs on the session "Register" button to redirect attendees to third-party systems.

  • Why: Some sessions require registration through external platforms (e.g., limited-seat workshops).

  • How it's helpful: Attendees can register for externally managed sessions without leaving the event experience.

Enhancing Meetings & Custom Meeting Wizard Reports ( EP-53966 )

  • What: Added "Business Transaction Likelihood" and "Meeting Did Not Take Place" columns to Meetings and Custom Meeting Wizard reports.

  • Why: Organizers and exhibitors lacked visibility into meeting quality and no-shows.

  • How it's helpful: Reports show commercial potential and whether meetings occurred — key for ROI measurement.

Team Member Creation Rules & Login Uniqueness Validation ( EP-53945 ) ⚡ Urgent

  • What: Updated team member creation rules with stricter login uniqueness validation.

  • Why: Duplicate logins caused identity conflicts and access issues.

  • How it's helpful: Prevents duplicate accounts and ensures each team member has a unique login across events.

Additional Logic for LC, Custom Questions and Product QR ( EP-54359 ) 🔺 High

  • What: Added enhanced logic for Lead Capture, custom questions, and Product QR interactions.

  • Why: Existing logic missed edge cases in custom question flows and product QR scenarios.

  • How it's helpful: More robust lead capture workflows that handle complex custom question paths and QR-based product interactions correctly.