No. Virtual Events works without the Zoom integration; the virtual flag and platform meta are independent. When Zoom is enabled, the platform pie surfaces Zoom as one of the platform values. Sites that use a generic virtual URL still get all four cards with the platform pie reading the generic type.

Virtual Events writes a platform type meta on each virtual event, such as zoom, generic, or a custom integration label. The pie groups on that meta and renders one slice per distinct value, so the team sees the exact platform mix across the upcoming programme.

Yes. The top-hosts bar joins on _EventOrganizerID to tribe_organizer and labels by organizer name. A site that uses organizer to mean host gets the host load chart directly, while sites that distinguish those roles can use a custom meta field instead.

Yes. The dataset filters on the virtual flag, so the virtual dashboard reads only online events. In-person events from the same Tribe install do not skew the platform pie or the weekly density curve and remain available through their own dataset for other dashboards.

Yes. A separate pie or bar card on the full tribe_events dataset grouped on the virtual flag returns the virtual versus in-person split. That can sit alongside the virtual-only programme dashboard or live in its own season overview screen.

Zoom meeting IDs are stored in _tribe_events_zoom_meeting_id on virtual events. The dashboard does not need to display them, but they are queryable in the dataset for sites that want to confirm every upcoming session has a Zoom meeting attached before going live.

Yes. Every card has a filter scope that can target organizer or platform meta. A weekly density card filtered to one host returns only that contributor's upcoming load, and a top-hosts bar filtered to Zoom returns only the Zoom-platform hosts.

Analytics tools track page views or join clicks, not the programme itself. SleekView Charts reads the virtual events records directly and aggregates the production data, so the dashboard answers programming questions about the virtual schedule rather than questions about traffic to virtual event pages.