A visit registration (visitor record) has a related contact record. The contact record contains personally identifiable information such as name, company, email and address details. These properties are system-defined, and as such available to all registrations. The visitor record holds additional information which associate the contact with the event. This is where you will find the responses to questions which have been captured as part of the registration process, also system properties such as the registration time and, naturally, the event which they have registered for. The set of data captured for a visitor record will depend how the event has been configured in Visit. All registrations are associated with a registration form (even if imported or added over the API); registration forms are configured with page(s) of questions to meet the needs of the event organizer.
A visitor record associates a contact record with an event instance.
Contacts are considered to be unique within the context of an Organization (Visit client). Thus the same contact may participate in multiple event registrations; as such they have a common set of contact details in a shared contact record, but their individual visitor records contain information unique to each registration. In the following diagram, contact A represents a person who is participating in both events A and B. Their visitor records (Visitor 1 and Visitor 2) contain the registration information applicable to the two events. Contact B has a registration for event B only.
Partners also follow the same pattern; all partners have an associated contact which contain the details of the company (company name) and the lead person. The partner contact is linked to the event through a partner record; this is where event-specific information is to be found, including the exhibition booth number and size if applicable.