Attendance Reporting for Zoom® Meetings
Attendance reporting for Zoom® meetings is an automated process to capture attendee data from Zoom and store it in Vault CRM, enabling admins to analyze and report on metrics for meetings hosted outside of Vault CRM.
Who can use this feature?
- Business Admin Users - Browser, iPad
- Attendance Reporting for Zoom® Meetings
- Users require an Engage license
Configuring Attendance Reporting for Zoom® Meetings for
To configure this feature:
- Ensure Scheduling and Starting Zoom® Meetings is complete.
- Ensure either the zoom_call_meeting_attendee__v layout or a custom layout is assigned to the zoom_call_meeting__v object type on the remote_meeting__v and remote_meeting_attendee__v objects.
- Navigate to Admin > Configuration > Remote Meeting.
- Select Manage in the Zoom tile to view the Zoom Administration page.
- Enable the Attendance Reporting toggle.
- Select the appropriate option fields to include in attendance reporting.
- Select Save.
System Users are created in Vault CRM instances and managed by Veeva for integration purposes. By default, these users are assigned the appropriate permission set. Customers cannot update the permission set.
To grant the Engage System User permissions for custom objects, fields, or object types, create a custom permission set and assign it to the Engage System User via an Application Role. See System Owned Users in Vault CRM for more information.
Using Attendance Reporting for Zoom® Meetings as
When the Engage Reporting Process runs, attendance data for a given meeting is retrieved from Zoom using the Zoom admin account matching the meeting host's Zoom user account and loaded into Vault CRM. The Engage Reporting Process can be scheduled to run at certain intervals or performed immediately by selecting the Run button on the Engage Meeting Process Administration page.
If a different remote meeting type was previously scheduled for the call, attendance data is only pulled for remote_meeting__v record zoom_call_meeting__v object type. For more on switching meeting types, see Switching Remote Meeting Types.
The following data is captured on a remote_meeting__v record for each Zoom meeting started from Vault CRM:
- engagement_minutes__v - Captures the total number of minutes where the host and at least one attendee were in the meeting together
- meeting_outcome_status__v - Indicates the meeting outcome using the following values:
- meeting_not_started__v - Displays if the meeting never started
- meeting_not_started_and_attendees_joined__v - Displays if attendees join the meeting but the host never starts the meeting. Whether attendees can join a meeting before the host depends on the organization’s Zoom configuration.
If waiting rooms are enabled for Zoom and an attendee joins the waiting room, but does not join the meeting, they are not counted as an attendee.
- meeting_started_without_attendees__v - Displays if the meeting started but attendees did not join
- meeting_started_with_attendees__v - Displays if the meeting started and at least one attendee joined
- attendance_report_process_status__v - Indicates the status of the reporting process:
- success__v - Displays when the record is successfully processed for the last time. If more than one call references the same Remote remote_meeting__v record, this value is the last time the last call is processed.
- retry__v - Displays if the admin manually sets the field value to retry__v. During the next attendance processing job, remote meeting and remote meeting attendee data is updated accordingly.
- Empty (no value) - The field is empty if the process was retried once, but the record is still in the two-week processing window or the record is set to a date in the future.
Only one remote_meeting__v record is created for each Zoom Meeting, regardless of how many times the individual meeting was started and stopped.
The following data is captured on a remote_meeting_attendee__v record for each device joining the meeting:
- Data from Zoom:
- attendee_type__v - The type of attendee. Available values are:
- host__v - Attendee has the host role
- user_attendee__v - Attendee is not a host and has a Participant User ID
- external_attendee__v - All other attendees
- device__v - The device used to join the meeting. This data may or may not be provided by Zoom.
- ip_address__v - The IP address of the attendee. This data may or may not be provided by Zoom.
- join_time__v - Datetime when the attendee joined the meeting
- leave_time__v - Datetime when the attendee left the meeting
- meeting_duration__v - Number of minutes the attendee was in the meeting
- meeting_end_time__v - Datetime when the meeting ended
- meeting_start_time__v - Datetime when the meeting started
- name__v - The name the attendee joined the meeting with
- network_type__v - The network type of the attendee. This data may or may not be provided by Zoom.
- remote_meeting__v - Lookup to the remote_meeting__v record for the meeting joined
- vexternal_id__v - Unique record ID for the attendee
- Data from attendee reconciliation (see Reconciling Zoom® Meeting Attendees with Accounts and Users for more information):
- account__v
- attendee_email__v
- external_user_id__v
- system_reconciliation_processed_datetime__v
- system_reconciled_account_id__v
- system_reconciled_rule__v
- system_reconciled_user_id__v
- user__v
If an attendee rejoins a meeting after leaving or being disconnected for any reason, a new remote_meeting_attendee__v record is created each time they join or rejoin the meeting.
Reviewing Attendance Reporting Process History
To monitor success and failure rates, admin users can view the process history and download logs for the last 10 Zoom attendance job runs in the Zoom Attendance Report Process History table.

