
Audience Acquisition
Part of Event audience acquisition
Defining who should attend before promoting an event
Write a useful attendee definition with inclusion criteria, clear boundaries and a check against the event's actual promise.
Define the intended attendee as someone who faces the problem the event addresses and can use its promised outcome. Write that definition before building an invitation list or buying promotion. It helps the team identify whom the session serves and whom it may disappoint.
Describe the need
A sector or seniority band may help locate people, but neither explains why they would attend. Complete this sentence: This event is for people who are currently trying to… Then name the decision or task the session will help with. For a hypothetical supplier-approval programme, “people responsible for reducing approval delays” is more useful than “senior operations professionals”.
Check the description against the actual programme. State any prior knowledge needed. If the session is introductory, do not promise advanced discussion. If two groups need different answers, make their respective parts clear or consider separate sessions.
Set usable boundaries
A short audience brief can answer four questions:
Question / What to record
- What task connects attendees?
- The specific work or decision.
- What should they already know?
- Any context needed to follow the session.
- What can they use afterwards?
- A realistic takeaway.
- Who is outside this session's promise?
- A different need the programme will not meet.
An exclusion describes fit with this session, not a permanent judgement about a person. Avoid criteria chosen only because they are easy to target. The same job title can cover different responsibilities.
Check the definition against what people ask
Ask colleagues who handle relevant enquiries which questions recur. Review the language of those enquiries where the organisation may appropriately use it.
Compare the questions with the planned programme: will the session answer them or only touch on the general subject? Ask a colleague not involved in planning to apply the audience description. If their interpretation differs, clarify the brief.
In the hypothetical supplier-approval session, a process owner, an employee submitting requests and a consultant advising clients could all have reason to attend. They may need different examples. If the programme only demonstrates how to complete a request, it should not promise a strategic comparison to the other groups.
Use the brief in promotion
Give invitation writers and channel planners a one-paragraph brief covering the attendee's task, required context, promised outcome and boundaries. If it does not help them make consistent choices, sharpen it before promotion starts.
If registration information will be used to check audience fit, ask only for details with a clear purpose. For organisers covered by the Australian Privacy Principles, the applicable collection necessity and notification requirements must also be considered.
Australian Privacy Principles (APP) considerations for data collection
- Collection necessity under APP 3
- Only collect personal information necessary for the event
- Notification requirement under APP 5
- Inform attendees why their data is being collected
- Data use limitations
- Do not use registration data for unrelated marketing without consent



