How to Set Up Cvent Lead Retrieval on Your Phone
Your event organiser has given you a Cvent LeadCapture API key and a quick-start PDF. Here’s how to connect it to your business card scanner app in under five minutes.
What you need before you start
Your Cvent API key, from your event organiser or from the Cvent portal for the specific event. Your business card scanner app installed on the phones your exhibition team will use. That’s it.
Your admin doesn’t need to do anything in advance. Every rep can configure their own device in a couple of minutes.
Step 1: paste the API key
Your scanner has an Events section in settings. Your rep taps “add event”, selects Cvent from the platform list, and pastes the API key.
Your scanner verifies the key against Cvent’s API in a second or two and shows the event name back. Wrong key? Clear error message.
Step 2: confirm field mapping
Your Cvent attendee profile has standard fields (name, email, company) plus any custom fields the event organiser collected at registration. Your scanner shows the mapping preview.
Your rep confirms or adjusts where each Cvent field lands in your CRM. Defaults are sensible, most reps don’t need to change anything.
Standard attendee fields
Name, title, company, email, phone map automatically to your CRM’s Contact standard fields.
Custom registration fields
Industry, region, product interest, session tracks picked, map these to custom fields on your CRM Contact or Lead object.
Step 3: set the Campaign attribution
Your scanner asks which Salesforce Campaign (or HubSpot List, Pipedrive source tag, etc.) should attach to every scan for this event. Your rep picks once.
Every scan from that point on attaches to the right Campaign automatically.
Step 4: test with a sample badge
Your rep grabs a test badge, any attendee’s, or a fellow exhibitor’s, and scans the QR. The attendee profile pulls from Cvent, the CRM record gets created, the Campaign attaches.
Your setup is done. Your reps can start capturing leads for real.
If you have multiple exhibition events on the same trip
Your team might be at three different conferences in a week. Your scanner holds multiple API keys, one per event.
Your rep picks the active event before they start scanning each day. Each scan attributes to the correct Campaign automatically.