Trade Show Database: What a Usable Record Needs

Trade Show Database: What a Usable Record Needs

A trade show database is usable when each row says which edition, which company, which role, from which source, checked when and changed since. Judge a database by that row, not by its total, and test it on a sample before you build outreach on top of it.

A database can look complete in a preview and still fail on the first sales call. Someone asks why a company is listed, and nobody can say whether the entry came from this year's directory or a copy of last year's. The question that matters is what one row lets you defend.

What must one row of a trade show database say?

Six things, kept as separate fields rather than folded into a note.

FieldThe question it answers
Event and editionWhich occurrence of the show does this concern?
Company identityWhich business is this, by domain and legal or trading name?
RoleDid the company exhibit, sponsor or speak?
SourceWhere was this published, and can a reader open it?
Date checkedWhen did someone last confirm it?
Change sinceWas the entry added, corrected, moved or withdrawn?

An event is the recurring identity and an edition is one occurrence of it. A row that carries only the event name will blur this year with last year. A row that carries only "participant" hides whether a company took a stand or a speaking slot, and those support different conclusions.

Why does the source matter more than the volume?

An exhibitor entry on an organiser's directory is a published statement from the organiser about an edition. A company name copied into a spreadsheet is a different thing: it has lost its edition and its source. Ask what each row carries with it. Where a trade show exhibitor list comes from sets out how to check an individual source.

This post is about the row. The questions to put to a supplier about licensing, refresh and permitted use sit in the dataset buying checklist, and are not repeated here.

What four tests can you run on a sample?

Ask for a sample you can interrogate, and choose the rows yourself.

  1. A show you know. Pick an event whose last two editions you can check by hand. Compare the sample's companies and roles with the organiser's own pages. A mismatch tells you more than a match.
  2. A company that withdrew. Pick a company you know stopped exhibiting. Does the database show an earlier role and a later gap, with the gap labelled as a gap?
  3. A rebrand or merger. Pick a company that changed its name. Can you tell whether the old and new names are one identity, and how the match was made?
  4. A date move. Pick an edition that moved or was cancelled. Does the row keep the old dates, show the new ones and record when the change was learned?

A database that passes the first test and fails the other three has recorded a snapshot, not a history. That may be enough for a single lookup, and it is not enough for monitoring.

What does an empty result mean?

Keep "no record in the database" apart from "did not take part". A company can appear at an event without being on any published exhibitor list, speaker agenda or sponsor page. The database cannot see that, so an absence is a gap in the record. The same holds for attendee names: where an organiser publishes an attendee list, WHR provides it, with no claim to lists for every event.

If you are weighing a one-off download against a record that someone keeps current, read should you buy exhibitor data or keep a participation record. WHR's prospecting page is the relevant starting point for participation records, kept current, and its partner page for platforms that need the data in bulk.

What else do buyers ask?

What should an exhibitor database contain?

The same row: edition, company identity, role, source, date checked and changes. An exhibitor database narrows the role to exhibiting. Ask whether sponsoring and speaking roles are kept as separate roles or dropped.

Is a trade fair database the same as a trade show database?

The words differ by region and the requirement is the same. Check that each company is tied to an edition of a named event, with its role and source, whatever the product is called.

How do I know a trade show database is current?

Ask for the date each row was last checked and how corrections are recorded. A single "last updated" date on the whole file cannot tell you whether the row you care about was revisited.

See where companies show up at whr.ai.