Co-located scanning

Feature Purpose:

When enabled this feature allows cross-event badge scanning for badges from other events that are within the same ExpoPlatform back-end.

Admin Panel Settings

In the Admin Panel, under Event Setup → Networking & Matchmaking → Contact Sharing Tab, there is a setting called “Allow users to scan badges from colocated events”.

• When enabled, this setting allows users to scan badges from other events within the same database environment. This configuration is pushed to the mobile app through an API, activating the cross-event scanning capability.

• If this setting is disabled, users can only scan badges from the current event, and badges from other events will display a “not found” message (or possibly information from the scanned QR code if the Allow Any Code Scanfeature is enabled.

Data Export Enhancements

In the Data → Import/Export section, both the Exhibitors Scanned Report and Visitors Scanned Report include an additional column called “Event Name”. This column provides:

• The name of the current event for regular badge scans.

• The originating event name for badges scanned from other events in the environment.

This enhancement allows event organizers to easily differentiate and manage badge scans based on the event, making it simple to track participation across multiple colocated events.

Frontend

1. User Profile - Lead File Download
   When the “Allow users to scan badges from colocated events” setting is enabled, users can view all badge scans in their lead files, including those from other events within the same database. This data can be downloaded from User Profile → Download Leads File. The file includes an “Event Name” column:

   • For scans from the current event, the current event name will be displayed.

   • For scans from other events, the event name of the scanned badge will be shown, making it easy to identify the attendee’s origin event.

Mobile App Scanning Flow

1. Updated Scanning Logic
   When this feature is enabled, the mobile app’s scanning logic is enhanced to recognize accounts across all colocated events in the environment:

   • The app first checks the scanned code in the local database. If it’s not found, it queries the server.

   • If the account is found but associated with a different event, the server returns basic information such as the attendee’s name, job title, company, photo, and location (country/city).

   • This scan appears in the app’s scan list with a “Other Event” ribbon, indicating that it was scanned from a different event.

2. Profile and Lead Capture

   • For lead capture-enabled scans, users can fill out additional fields as usual.

   • For visitor scans without lead capture, a simplified public profile page opens, displaying the returned basic data from the server.

3. Lead File Email Export
   For users with lead capture enabled, the lead file emailed to them also reflects cross-event scans. Similar to the downloadable file on the frontend, the “Event Name” column shows either the current event or the originating event for each scan.