The exhibitor lead export fields that decide whether follow up ever happens

A sales manager at an exhibiting company opens the file you sent. Four columns: first name, last name, company, email. Two hundred and forty rows.

She has six salespeople and no way to divide the list. She does not know which of her staff met which person, when, or what was said. She does not know whether row 118 was a serious buyer at 10:40 on the Tuesday or a student who wandered past on the Thursday afternoon. So she does what everyone does, which is to send one generic email to all 240 and mark the show as low quality when eleven people reply.

Nothing about that outcome is her fault. The exhibitor lead export fields decided it, months before anyone stood on a stand.

The column contract

Ten columns cover the working case. Write them down, put them in the exhibitor manual before the show, and hold the vendor to them. They are a different contract from the scan table you keep on your own side, which carries operational fields no exhibitor needs.

badge_id. The stable identifier for the registration record. It is what lets an exhibitor deduplicate their own file and what lets you answer questions about the same file later.

name and company. Split into first and last, and keep company exactly as registered.

job_function. The registration question, not free text job title. Free text titles are unusable at volume and the function taxonomy is the thing your categories were built on.

country. Two letter code. It routes the lead to the right sales region and it is the first thing an international exhibitor filters on.

consent_flag. Whether the visitor agreed to their details being passed to exhibitors for follow up, with the timestamp of that agreement.

captured_at. Timestamp with timezone, at the moment of capture.

captured_by. The named person on the stand who captured it.

grade. Whatever grading scheme the show published, applied consistently.

notes. Free text the stand staffer typed at the point of capture.

qualifier answers. One column per question the exhibitor configured, with the question text in the header rather than q1, q2, q3.

Four of those ten do most of the work, and they are the four most often missing.

Why do captured_at and captured_by change the behaviour?

Give a sales manager capture time and scanner identity and she can do something she cannot otherwise do, which is assign the file.

With captured_by she splits 240 rows into six lists and hands each salesperson the people they personally met. The email that follows can honestly say "we spoke on Tuesday morning", and the person receiving it remembers. Without it she has one undifferentiated list and no route to a personal message.

With captured_at she can sequence. The people captured in the first two hours of day one are different from the people captured in the last hour of day three, and she knows that from experience even if she cannot articulate why.

The arithmetic is worth doing. Suppose 240 leads, six staff, and a follow up call that takes eight minutes including notes. That is 32 hours of calling, which nobody does. Given captured_by and a grade, she calls the 44 graded A that she or her colleagues personally met, which is under six hours and gets done in the first week. The rest go to a sequenced email programme. The difference between those two worlds is two columns.

The consent column is not optional

Article 7 of the GDPR requires that where processing rests on consent, the controller can demonstrate that the person consented, and gives that person the right to withdraw at any time, as easily as it was given.

For a show, the consent decision is usually made at registration, when the visitor is asked whether their details may be shared with exhibitors. The exhibitor at the stand cannot see the answer. They scan a badge and receive a record, and whether that record can lawfully be emailed next week was decided months earlier by somebody else.

So the flag has to travel with the row, and it has to be a real value rather than a blanket yes applied to the whole file. An exhibitor who receives 240 rows of which 31 carry no consent needs to know which 31, because a suppression they can apply is worth considerably more to them than a warning paragraph in the covering email that nobody reads.

Withdrawal is the part organisers handle worst. Consent given at registration can be withdrawn after the show, and by then the row is sitting in the exhibitor's CRM and outside your control entirely. The practical answer is contractual rather than technical, and it belongs in the exhibitor agreement: a stated obligation to honour withdrawal notifications you pass on, and a channel to pass them on through.

Why does nobody fill in the qualifier fields?

The single most useful column on the export is the one that is usually blank.

Writing for CEIR's Industry Insights series in 2019, Jefferson Davis reported that according to the major lead retrieval vendors Experient and CompuSystems, fewer than 10 per cent of exhibitors use custom qualifiers, and noted that the incremental cost of adding them is typically nominal.

Look at how the tooling is arranged and the number stops being surprising. Cvent's LeadCapture exhibitor guide has qualification questions configured by the exhibitor admin in the portal, under a separate tab, before the show. On the device, qualifying is a second action after the scan: the staffer taps Qualify Lead, answers, and saves. The default path through the app is scan and move on.

So the 90 per cent is a design outcome. An exhibitor who never opened the portal tab has no questions to answer, and a staffer with a queue of three people at the stand will not invent them.

There are two organiser side fixes and I would do both. Set a default question set at show level, three or four questions built from your own registration taxonomy, so that every exhibitor who configures nothing still gets something. And put the qualifier completion rate on the exhibitor's live dashboard during the show, because a stand that can see 11 per cent of its captures carry an answer at the end of day one will usually fix it by lunchtime on day two.

Deliver it twice, in two formats

The file you send at close and the file the exhibitor uses in March are not the same file.

At close, or ideally hourly during the show, send a CSV to a per exhibitor endpoint with every column above. This is the operational file. It gets loaded into a CRM, split among staff, and worked in the first ten days when the leads are warm, and it is the point where exhibitor analytics either earns its keep or becomes a slide nobody acts on.

Later, send the same data in a form a human can read without a spreadsheet, sorted by grade and then by capture time, with the qualifier answers rendered inline. This is the file that gets forwarded to a sales director who will never open a CSV, and it is the one that decides whether anybody at the exhibiting company believes the show worked.

One warning on the mechanics. Cvent's guide notes that leads which have not synced cannot be exported by the exhibitor admin, and that a device must connect to sync after the event. Any file you generate before the last device reconnects is incomplete, and an exhibitor who compares your file against their app count and finds a gap will trust neither. Send the count of unsynced devices alongside the file, or wait.

Two smaller mechanics decide whether the file is usable on arrival. Put the header row in plain language, because a column called qual_3 will be renamed by hand by every one of your exhibitors and renamed differently each time. And write dates in ISO order with a four digit year, since a file crossing between a European exhibitor and a US organiser will otherwise turn 09/07 into two different days depending on who opens it. Neither of these is interesting. Both of them cost somebody an hour per show.

The permission model needs a decision too. In Cvent's arrangement only the exhibitor admin can export leads, and booth staff cannot see the leads their colleagues collected in the app. That is a sensible privacy default and it means the export lands with one named person at the exhibiting company, who may be the stand coordinator rather than anyone in sales. Ask for a second recipient in the exhibitor manual, name the role you want, and send the file to both.

Where this stops

A good export cannot make anybody follow up.

The columns above remove the excuses that make follow up hard. They do not create sales capacity, they do not create a process at the exhibiting company, and they do not help at all when the leads are routed to independent dealers or distributors who have no obligation to report back. Davis was direct about this in the same 2019 report: where the relationship is a partner one, limited to routing leads to independent representatives, dealers or distributors, the exhibitor does not have as much control, though they can still exert influence.

There is also a limit on what you can honestly put in the grade column, because the grade is only as good as the scheme behind it and most schemes are invented by each stand independently. Fixing that means the organiser publishing the grading scale rather than collecting whatever each exhibitor happened to use.

And there is a cost to the ten column contract. Every field you demand from a vendor is a field you have to validate, and a consent flag populated with a default of Y because the integration was never finished is worse than no column at all. Check the distribution before you ship. If 100 per cent of rows carry consent, somebody hardcoded it.

Open the last lead file your show sent to an exhibitor and count the columns. If captured_by is missing, ask your lead retrieval vendor this week whether the field exists in their export and simply was not selected, which is the usual answer.