jeans, pocket, business card, trousers, note, stitched, blue, rivet, notepad, close up, paper, white, rectangle, jeans, pocket, pocket, pocket, pocket, pocket, business card, business card, business card
Photo by Uki_71 on Pixabay

Event Strategy

Lead capture at business events

Plan event lead capture around a clear purpose, expressed interest, useful handoffs and separate contact permissions.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Event Strategy Desk.

Responsible lead capture at Australian business events starts with purpose: tell attendees why you are collecting their details, how they may be used and who may contact them. This overview covers capture methods, qualification, sales use and partner permissions.

Registration, a badge scan or an exchanged business card shows how you obtained a detail; it does not by itself explain a business need, purchase intent or intended use. Record the person's stated interest and any marketing permission separately.

Decide what the record is for

Before the event, distinguish attendance administration, delivery of a requested resource, responses to enquiries, sales conversations and future marketing. Design each collection point for its purpose.

A check-in desk may need to confirm attendance; a product specialist may need an address to send a specification someone requested. Neither task makes the entire attendee list a sales queue.

For organisations covered by the Australian Privacy Principles, collection obligations include assessing what personal information is reasonably necessary for their activities and taking reasonable steps to make people aware of relevant collection matters. Check the position of each organiser and partner rather than assuming they have the same obligations.

Under APP 3, an APP entity that actively requests details or takes steps to collect them is soliciting personal information. It may collect only what is reasonably necessary for its functions or activities, using lawful and fair means.

A narrow request tied to an event task is more appropriate than gathering details simply because they are available. A request or capture method does not, by itself, establish a marketing purpose.

Sensitive information has an additional collection test: it may be collected only when the general conditions are met and the person consents, unless an exception applies. Avoid asking event attendees for sensitive details unless the collection is necessary for the stated activity and the applicable requirements are met.

Capture the interest actually expressed

Give staff a way to record a particular request without enrolling the person in every follow-up activity. At a stand, a brief explanation can lead to a form or fuller notice identifying the collector and purpose.

At a roundtable, participants could be invited to request private follow-up instead of having the room's details placed in a sales list. At a badge scan or business-card exchange, explain the purpose and record any marketing choice separately from the contact detail.

Use a distinct consent field at capture to record whether the attendee agreed to marketing and which organisation they agreed to hear from. Do not treat attendance, a scan or an exchanged card as that recorded choice.

Event signalWhat it establishesSuitable next action
Registration or attendanceThe person joined or planned to joinProvide the event service and promised information
A requested documentInterest in that documentDeliver it through the agreed route
A question about a business problemA topic worth clarifyingAsk whether a further discussion would help
An agreed meetingA defined next stepAssign an owner and record the agreed timing

These are working distinctions, not automatic legal permissions or a scoring system. A crowded session, downloaded slide deck or scanned badge should not silently become evidence of purchase intent.

Explain collection at the point of capture

For organisations covered by the Australian Privacy Principles, APP 5 is the collection-notice principle: take reasonable steps to notify people of relevant collection matters or ensure they are aware of them. The Office of the Australian Information Commissioner (OAIC) sets out this guidance.

Do this before or when collecting their information; if that is not practicable, do so as soon as practicable afterwards. The notice should identify the collecting organisation and its contact details, and explain the purposes of collection.

A collection notice should also cover whether collection is required or authorised by law, the consequences of not providing information, usual disclosures of that kind of information and where to find the organisation's privacy policy. If the organisation is likely to disclose information to overseas recipients, include that fact and, where practicable, the countries involved.

If a sponsor or partner may receive contact details, make its role, the intended use and the relevant disclosure clear at capture. A badge scan or staff member collecting details on an organisation's behalf does not remove these notification steps.

The OAIC says the notification requirement applies to information collected directly from a person or from a third party, including solicited information.

Privacy Compliance Essentials for Event Organisers

APP 5 Requirement
Notify individuals of collection matters before or at capture
Spam Act 2003
Marketing messages must include consent and unsubscribe option
Sensitive Information
Only collect if necessary and with explicit consent
Small Business Guidance
Applicable privacy obligations apply even to small event organisers

Keep qualification separate from permission

A useful lead record says what the person is trying to do, whether your organisation may be able to help and what they asked to happen next. Record a relevant role, problem or timeframe when stated; mark unknowns as unknown.

Do not present staff guesses about budget or authority as facts. Interest and permission are separate considerations.

For commercial electronic marketing, Australia's Spam Act 2003 requires consent and an unsubscribe option. Record a separate marketing choice at capture, and include a usable unsubscribe option in marketing messages.

An attendee's choice to hear from the organiser and a sponsor's intended use are distinct. As a safe operational rule, obtain and record a separate opt-in before passing details to a partner for its own marketing.

Make clear which organisation will send a partner message and what the attendee agreed to receive. Do not assume that permission to hear from the organiser covers a partner's messages.

Make the handoff usable

A sales colleague needs the attendee's question and the promised next step, not a label such as 'hot'. A sales handoff should match the person's stated request and the contact permissions recorded.

A compact handoff can include the event and conversation date, who spoke with the person, their stated need, material promised, chosen contact route and response owner. Keep free-text notes relevant to the business request; avoid speculative or unnecessary personal details.

After the event, review records for duplicates, errors, unclear permission and fulfilled requests. Limit access to staff who need the information and follow the organisation's retention process.

Where there is no clear purpose or appropriate next step, keep the record out of a sales sequence. When an event partner collects information for another organisation, make the partner's role and the intended use clear at the collection point.

In this guide

  1. Explaining why contact details are being collectedExplain event contact collection at each touchpoint, with clear purposes and separate choices for optional marketing.
  2. Qualifying event interest without treating every attendee as a leadUse what attendees say and request to choose a suitable next step, without turning attendance into a sales lead.
  3. Handling contact-sharing permissions with partnersSet clear purposes, attendee choices and export controls before sharing business event contacts with a partner.

More in Event Strategy