Exhibitor can use third-party Lead Capture (via Exhibitor API)
Exhibitor can now plug their in-house or third-party lead capture (e.g., CRM-connected tools like Captello) directly into Swapcard. Scan a badge with your system, send the exhibitor ID + event ID + badge code within the Exhibitor API, and Swapcard creates the connection just like a scan in the Swapcard app, then returns the attendee’s contact details for instant routing.
Why exhibitors care
- One scanner, every event: Standardize across organizers and apps without changing your booth workflow.
- Speed to lead: Push contacts straight to your CRM, scoring, email sequences, or meeting tools.
- Consistent reporting: Every scan still creates a Swapcard-native connection for event analytics.
- Less training, fewer errors: Keep the tools your team already knows while preserving data quality.
What it does
- Mirrors Swapcard scans: The API behaves the same way as scanning a badge in the Swapcard Lead Capture app.
- Permission-aware: Only works when Lead Capture is enabled for your exhibitor in that event.
- Immediate contact data: Returns the attendee details you’d normally access via Swapcard.
How it fits your flow
- Exhibitor member scans a badge with their existing lead tool.
- Swapcard checks the Lead Capture permission for that event.
- A connection is created in Swapcard for reporting and follow-up.
- You receive the attendee’s contact details to route into your CRM or booking system.
Governance & privacy
- Respects the event’s Lead Capture settings and data policies.
- Follows the same rules, duplicate handling, and consent logic as the Swapcard app.
- Exhibitor remain responsible for managing PII within your connected systems.
Who benefits
- Multi-event brands standardizing a single capture process.
- Teams with deep CRM workflows that require instant, automated lead routing.
Getting started
- Ensure Lead Capture and Leads API are enabled for the exhibitor in the target event.
- Ask your technical team to connect your lead tool using the Exhibitor API (implementation details are in the developer portal).
- Test on a staging event, align CRM field mapping, and brief booth staff on the updated flow.