What to ask at registration to personalise an event
Six registration questions with options and practical uses for recommending content, creating audiences and preparing communication with EVA.
To personalise an event, ask what each attendee wants to learn, what they are trying to solve and which people they would like to meet. Only collect answers you will use. These six questions form an adaptable bank for your form, rather than an obligation to add six fields to registration.
The options are designed for a professional event about event technology. Change them to reflect your programme and the recommendations you can offer through EVA. Your registration platform provides the form; EVA then receives the data through the relevant integration or import.
Six questions with options and a planned use
1. Which topic would you like to explore at this event?
Options: attendee communication; team knowledge; audience analysis; participant experiences; I have not decided yet.
Let people select relevant topics to guide content recommendations. If you allow multiple options, make it clear whether you need a priority or an unordered selection. An unordered list should not be interpreted as though its first answer were the favourite.
Use with EVA: recommend sessions from the available programme and create audiences for topic-specific communication.
2. What would you like to take away from the event?
Options: ideas for future projects; examples of implementation; meeting suppliers; sharing experiences with colleagues; understanding a new technology.
This question adds purpose. Two people interested in communication may need either a practical demonstration or a conversation with a supplier.
Use with EVA: adapt the type of recommendation and clarify what the person expects when asking about an activity.
3. Which part of your work would you like to improve?
Options: preparing proposals; team coordination; attendee enquiries; event communication; post-event analysis; other.
This connects content with a work situation. If you include “other”, you can offer a short optional comment so people are not forced to place their needs in an unsuitable category.
Use with EVA: add context to the answer. When recommending a session about AI agents, it can explain the connection with attendee enquiries if that is the need the person selected.
4. Which kind of experience helps you learn best?
Options: demonstration; practical workshop; discussion with other professionals; case study presentation; no preference.
Use this if your event offers different formats. At an event consisting entirely of talks, collecting a preference for workshops will not change any available recommendation.
Use with EVA: prioritise activities by format when the programme and access conditions allow it.
5. Which people would you like to meet?
Options: corporate event managers; agency professionals; technology suppliers; production suppliers; people with similar interests; I am not looking for contacts on this occasion.
The selection identifies the people someone wants to meet, rather than their own job role. Keep that distinction so you do not recommend someone simply because they have the same job.
Use with EVA: refine a search for people when the integration and the event’s public profiles are set up. The answer does not guarantee that someone with that profile is attending or that a meeting will happen.
6. What kind of project would you like to apply your learning to?
Options: conference; exhibition; corporate event; incentive trip; several event types; I am still exploring.
This adds context without asking for a budget or turning the form into a sales classification exercise. Someone working on conferences may be interested in a topic for another format.
Use with EVA: adapt the examples in an answer and help the organiser prepare relevant content for registered attendees.
Preserve the meaning when sending data to EVA
The integration needs to distinguish the question from the answer. “Technology suppliers” as the people someone wants to meet means something different from the same option as their professional activity. Give fields clear names and check a test registration before using it for recommendations.
It is also worth keeping values consistent. If you change an option while registration is open, check how it relates to earlier answers. An audience mixing labels with different meanings stops being a useful group to communicate with.
Ticket types and bookings remain separate from interests. Before recommending or sending a workshop reminder, check the relevant access. Selecting “demonstrations” does not amount to booking a place.
Test one journey before adding more questions
Imagine Lucía selects attendee enquiries, implementation examples and demonstrations. Add those answers to a test registration and ask EVA: “What would you recommend so I can learn something useful for my work?” Check whether it uses that context and the event’s actual programme.
Then prepare an audience linked to that interest in EVA Insights and review what communication you would send. If there is no relevant recommendation or message, reconsider the question or the content before making the form longer.
In how to understand audience interests and personalise their experience with EVA, we explain the complete journey. To start, an answer only needs to change something useful: a recommendation, a reminder or a content decision.
EVA and EVA Insights use the information you provide to work with that context. Collect preferences related to the experience and explain their use; do not turn this question bank into a request for personal data without a purpose.
Frequently asked questions
Should I include every question?
No. Choose those with a planned action at your event, and use “no preference” or an optional answer where appropriate. Registration should remain easy to complete.
Can these interests identify buyers?
They describe what the person says they are interested in or wants to achieve. They do not demonstrate a budget or purchase intent, and do not, on their own, justify a sponsor campaign.
Do I need to ask for the ticket type again?
If it already exists in the registration platform, retain that information for the integration instead of asking again. You will need to relate it to the interest when checking access or preparing communication.
