Skip to main content
All CollectionsContentExhibitorsExhibitors' Leads Generation features
Testing your lead scanner for a seamless experience
Testing your lead scanner for a seamless experience
Updated this week

Introduction

Testing the lead scanner functionality is crucial to ensuring exhibitors and attendees have a seamless lead capture experience during your event. Proper testing helps identify potential issues before the event, saving time and preventing dissatisfaction on-site.

Benefits:

  • Guarantee exhibitors can capture leads effectively without technical interruptions.

  • Enhance the attendee experience by ensuring smooth interaction during lead scanning.

  • Avoid last-minute troubleshooting by addressing settings-related issues in advance.

Strategic Value:

Lead scanning is a key metric for exhibitors to measure ROI. Ensuring its functionality strengthens exhibitor satisfaction, encourages repeat participation, and enhances the event’s reputation.


Key steps for testing Lead Scanning

1. Understand groups and permissions settings

Event organizers often overlook how group settings and permissions can impact lead scanning. Incorrect configurations can disable scanner functionality for specific user groups.

Step-by-Step Instructions:

  1. Review Group Settings:

    • Navigate to the Groups and Permissions section in your event platform.

    • Confirm that the groups assigned to exhibitors and attendees have Lead Scanning Enabled.

  2. Check Lead Scanning Access:

    • Ensure lead scanning is not inadvertently restricted by custom group settings.

    • Verify permissions for scanning, exporting, and accessing captured leads.

Additional Implementation Details:

  • Use the shared settings document (Sample Spreadsheet) to track and confirm all group configurations.


2. Test the Lead Scanner functionality

Testing the lead scanner in a real-world scenario helps identify any technical or settings-related issues before the event.

Step-by-Step Instructions:

  1. Assign roles for testing:

    • Create a test exhibitor group with the same settings as live exhibitors.

    • Assign test attendees to simulate scanning interactions.

  2. Perform scanner tests:

    • Use a mobile device or scanner to capture test attendee badges.

    • Check if the scanned data is recorded correctly in the system.

  3. Verify data capture and export:

    • Ensure lead details (e.g., names, emails, and notes) are logged.

    • Test the export functionality to confirm exhibitors can access their leads post-event.

Additional Implementation Details:

  • Test across multiple devices (iOS and Android) to ensure compatibility.

  • Check network connectivity, as some scanners require internet access to sync data.


3. Address common issues during testing

The testing phase often uncovers common misconfigurations that, if unresolved, could disrupt the lead scanning process during the event.

Step-by-Step Instructions:

  1. Resolve permission errors:

    • Adjust permissions for any groups that cannot access the lead scanner.

    • Ensure exhibitors have full lead capture and export rights.

  2. Check badge QR Code formatting:

    • Confirm QR codes on badges are properly formatted and scannable.

  3. Ensure app and device compatibility:

    • Update the scanning app to the latest version.

    • Test the scanner on all supported devices.

Additional Implementation Details:

  • Maintain a checklist of resolved issues to prevent reoccurrence in future events.


Best Practices for a Seamless Lead Scanning Experience

  • Communicate with Exhibitors: Share clear instructions on using the lead scanner and testing it independently.

  • Use the settings tracking document: Regularly update a shared document, such as this example, to document and verify settings.

  • Conduct a Final Pre-Event Test: Schedule a full-system test one week before the event to confirm all configurations.


By proactively testing the lead scanner and monitoring group settings, you can ensure a smooth and successful lead capture experience for all event participants.

Did this answer your question?