🔗 EP-45958 | Integration team | API - Check-in data
What
Expose a reliable API endpoint providing event check-in data (e.g., attendee ID, timestamp, location/device, status) with pagination, filtering, and secure access for partners and internal systems.
Why
Operational partners and downstream systems (CRM, marketing automation, BI tools) require real-time or near-real-time attendance signals to trigger journeys, measure engagement, reconcile capacity, and validate SLAs.
How it’s helpful
-
Operations: Automates attendance reconciliation and reduces manual exports.
-
Sales/Marketing: Enables timely follow-ups based on actual attendance.
-
Analytics: Improves accuracy of session and event ROI reporting.
-
Integration: Standardizes data exchange, lowering maintenance costs.
💼 EP-47499 | Exhibitor team | Add ‘is_new’ column to exhibitor export
What
Extend exhibitor export reports with a boolean or categorical ‘is_new’ column indicating first-time exhibitors for the event/series, with clear data definition and format.
Why
Organizers and sales teams segment communications and measure acquisition by differentiating new vs. returning exhibitors. Analysts need the flag for trend and cohort reporting.
How it’s helpful
-
Sales/CS: Tailored outreach and upsell playbooks.
-
Marketing: Accurate new-logo reporting and campaign targeting.
-
Analytics: Cleaner cohort analyses without custom post-processing.
-
Exhibitors: Receive communications relevant to their lifecycle stage.
📅 EP-48874 | Organizer team | Client Manager: persistent banner during event cloning
What
Add a persistent, non-dismissable banner in the Admin Panel during event cloning that warns and blocks conflicting edits until cloning completes.
Why
Concurrent edits during cloning cause data inconsistencies, partial copies, and rework. Persistent UX guidance prevents accidental changes.
How it’s helpful
-
Organizers: Avoids corrupt or partial event setups.
-
Support: Fewer incidents from mid-clone edits.
-
Reliability: Improves integrity of cloned configurations.
-
Speed: Reduces rollback and retry cycles, saving staff time.
👤 EP-49202 | Visitor team | Admin panel: Profile completion in Participants list
What
Display a profile completion indicator (score/state) in the Participants list, with clear criteria and visual status for quick scanning and filtering.
Why
Organizers need to identify incomplete profiles at a glance to improve data quality, discoverability, and networking outcomes.
How it’s helpful
-
Operations: Targets reminders to users needing profile completion.
-
Attendees: Better matches and visibility from richer profiles.
-
Analytics: Improves data completeness KPIs.
-
Scalability: Reduces manual checks across large cohorts.
📊 EP-49221 | Visitor team | Participant Profile Completion Calculation Update
What
Revise the algorithm and weights for profile completion to reflect current fields, relevance, and quality thresholds (e.g., photo, job title, interests, company, consent).
Why
Legacy scoring may misrepresent completeness and value. An updated, transparent model aligns incentives and improves matching quality.
How it’s helpful
-
Users: Clearer guidance on what to fill and why.
-
Matching: Higher-precision recommendations and search results.
-
Product: More reliable KPI for growth and activation funnels.
-
Compliance: Incorporates current consent and visibility requirements.
📄 EP-49223 | Visitor team | Profile Completion Column in Export Reports (Participants)
What
Add the profile completion score/state as a dedicated column in participant export reports, aligned with updated calculation logic and defined data types.
Why
Offline analysis and targeted outreach rely on exportable data. Including completion data reduces manual enrichment and spreadsheet work.
How it’s helpful
-
Marketing/CRM: Segment audiences by completeness for campaigns.
-
Analytics: Track improvements over time across events.
-
Operations: Prioritize nudges where they’ll have the most impact.
-
Consistency: Matches in-app list views and external reporting.
📱 EP-49879 | Mobile team | Change meeting rating trigger in app
What
Revise the in-app trigger for rating meetings (e.g., timing, context, or signal) to prompt users at a more effective moment while minimizing disruption.
Why
Current triggers may prompt too early or late or in the wrong context, reducing response rates and skewing feedback.
How it’s helpful
-
Product insights: Higher-quality, more representative ratings.
-
UX: Less intrusive prompts, improved session flow.
-
Organizers: Better NPS and meeting outcome analytics.
-
Attendees: Feedback feels timely and meaningful.