Skip to content
NewNeenOpal Earns ISO 42001 Certification for AI GovernanceKnow More

Zoom Events to BigQuery: Capturing the Attendee Data Standard Zoom APIs Miss

Talk to Our Data Engineers

Talk to our team

Tell us what you’re working on. A senior consultant will follow up with next steps.

Overview

A leading dental-industry media company hosts hundreds of webinars a year on Zoom Events. Its reporting showed how many people attended each one, but not who they were. Without attendee-level data, the team couldn't follow up with the right people or connect webinar engagement to the rest of its marketing and CRM data. NeenOpal traced the problem to how Zoom Events is built and found an API route that returns the attendee records the client's own registrants generate. A Google Cloud Run pipeline now loads those records into Google BigQuery and refreshes them every month. The initial load covered more than 200 webinars and identified over 13,000 unique attendees.

200+
webinars processed in the initial load
60K
attendee records loaded into BigQuery
13K
unique attendees identified across all webinars
12
of attendee history kept current by a monthly automated refresh

Customer Challenges

Zoom offers more than one webinar product, and the data for each lives in different places, so the usual integration approach missed most of the data.

  • Access Restricted to One App Type

    The participant report permission the pipeline needed is available only on Zoom's Server-to-Server OAuth apps, not on general apps. The wrong app type means the data is simply unreachable, with no obvious error to explain why.

  • A 12-Month Retention Window

    Zoom keeps participant report data for the last 12 months only. Requests for older events waste API calls and return nothing.

  • Registrant APIs That Returned Almost Nothing

    The client ran its webinars on Zoom Events, not standard Zoom Webinars. Attendees registered through the Events hub, so the standard registrants API returned close to zero records for events that had drawn hundreds of people.

  • Head Counts Without Names

    The existing pipeline captured only aggregate webinar metrics. With no individual attendee names or emails stored, subscriber-level engagement analysis was impossible.

  • Pagination Totals That Couldn't Be Trusted

    The Zoom Events API reported unreliable record totals, returning the page size as the total on every request. A pipeline that trusted those totals would stop early and silently miss attendees.

Solutions

NeenOpal worked within Zoom's platform constraints rather than against them, starting with how Zoom Events relates to the rest of Zoom.

  1. Map Each Event to Its Underlying Webinar

    Zoom Events runs on top of standard Zoom Webinars, so every event has an underlying webinar ID. The pipeline reads those IDs from the client's existing BigQuery staging data, so it knows exactly which webinars to query.

  2. Query Participant Reports With Server-to-Server OAuth

    For each webinar, a Cloud Run function calls Zoom's participant report endpoint using a Server-to-Server OAuth token. That combination returns the attendee-level records the standard registrants API could not.

  3. Page Through Every Result, Ignoring Unreliable Totals

    The pipeline pages through every result set without relying on Zoom's record totals, so no attendee is dropped when those totals are wrong. Records are then inserted into BigQuery.

  4. Skip Events Outside the Retention Window

    A 12-month date filter skips events outside Zoom's retention window before any call is made. API usage goes only to webinars that can return data.

  5. Join Attendees to Event Titles and Refresh Monthly

    A staging view joins attendee records with event titles, giving analysts a reporting-ready table of who attended what. Google Cloud Scheduler runs the refresh every month with no manual effort.

Services

  • Google BigQuery
  • Google Cloud Run
  • Google Cloud Scheduler
  • Events API
  • Participant Report API

Benefits

  • 13K+ Named Attendees Instead of Head Counts

    Attendee names and emails are now captured for every webinar in the last 12 months, turning aggregate attendance figures into a list of real people the team can act on.

  • Attendance Tied Directly to CRM and Campaigns

    Attendee records sit in the same BigQuery warehouse as the client's CRM and campaign data, so webinar attendance can be tied to leads, contacts and campaigns.

  • Repeat Attendees and Popular Topics, Finally Visible

    The team can now see which individuals attend repeatedly and which topics draw new audiences, analysis that was impossible with head counts alone.

  • Every API Call Returns Usable Data

    Retention-aware filtering means every request goes to a webinar that can return data, keeping each run fast and within Zoom's limits.

  • No More Manual Attendee Exports

    The monthly refresh runs on its own. No one has to download attendee reports by hand after each event.

Conclusion

By working out how Zoom Events and Zoom Webinars fit together, NeenOpal found the one API route that returns accurate attendee data and built a pipeline around it. The client now has subscriber-level webinar engagement data in the same warehouse as the rest of its marketing intelligence. This pipeline is part of the wider platform described in Unified Cross-Platform Intelligence Across 20+ Data Sources.

FAQ

Common questions about capturing attendee data from Zoom Events

Why do standard Zoom APIs return almost no registrants for Zoom Events webinars?

Because Zoom Events and Zoom Webinars are different products. When attendees register through the Events hub rather than a standard webinar registration page, the standard registrants API returns close to zero records even for events that drew hundreds of people. The data exists, but not where the usual integration looks for it.

How do you get attendee-level data out of Zoom Events?

Zoom Events runs on top of standard Zoom Webinars, so every event has an underlying webinar ID. The pipeline reads those IDs, then calls Zoom’s participant report endpoint for each webinar to retrieve attendee-level records. It pages through every result set without relying on Zoom’s reported record totals, which return the page size as the total on every request and would otherwise cause a pipeline to stop early and silently drop attendees.

Why does this require a Server-to-Server OAuth app?

The participant report permission is available only on Zoom’s Server-to-Server OAuth apps, not on general apps. With the wrong app type the data is simply unreachable, and there is no obvious error message explaining why, which makes this a common dead end for teams attempting the integration themselves.

How far back can Zoom attendee data be retrieved?

Zoom retains participant report data for the last 12 months only. The pipeline applies a 12-month date filter before any call is made, so requests are never spent on events that cannot return data. A monthly automated refresh then keeps that rolling 12-month window current.

Authors

  • Madhumita GiribabuSenior Associate Consultantin

Case studies

Related case studies