300 badge scans. 80 survey responses. Nobody matched them.
This is the post-show reality for most exhibitors who think they have a lead capture system. They have two separate data collections happening at the same booth, simultaneously, with no connection between them.
The badge scanner is provided by the event organiser. The rep points it at the visitor's badge. The system records a name, an email address, a job title, and sometimes a phone number. That is all it records. There is no field for qualifying questions. No space for a hot/warm/cold rating. No note about what the person said they needed. Just the data they typed when they registered for the event.
The Google Form is the marketer's attempt to get around this. Build a survey. Put it on a tablet. Ask the visitor to fill it after the scan. Some do. Most do not.
The rep does not know which form response belongs to which badge scan. The marketer does not know either. The badge scan has contact details but no qualification. The form response has qualification answers but no reliable contact match - the email the visitor typed into the form may or may not be the same one they registered the event with.
Two data points. Same person. No way to connect them. This is not a technology problem. It is a stack design problem.
The problem is structural. It was built in from the start when two tools with no integration were placed next to each other and called a system. The badge scanner cannot ask a qualifying question. The form cannot access the badge data. The rep in the middle is supposed to be the bridge. They are busy.
At the end of the show, you have a badge export with 300 contacts and a form export with 80 responses. Someone on your team will spend a day trying to manually match them by email address. Some will match. Many will not. The 220 people who only got scanned but never filled the form - you have their contact details and nothing else.
Whether any of them are leads depends on questions nobody asked while they were standing in front of you.