One connected journey
What the integration does
HockeyStick AI connects one designated, licensed Zoom Webinar host to one authenticated HockeyStick engagement. It keeps the customer in control while HockeyStick performs three launch workflows: it supports Webinar provisioning, hosted Webinar enrolment and post-event attendance only.
Provision
Create a Webinar from an approved brief, then read it back before HockeyStick treats the binding as verified. This release creates Webinars only; it never updates or deletes one.
Enrol
Send a consented registration from the HockeyStick-hosted Webinar page to Zoom and reconcile the registrant before any retry.
Reconcile
After the Webinar, match occurrence-scoped participation to the enrolment and calculate attendance evidence.
Before you connect
Prerequisites
- An active HockeyStick AI engagement with Activate enabled, and a designated integration contact who can sign in.
- A Zoom Workplace account and a paid Webinar licence assigned to the authorizing host.
- The authorizing host must be the engagement's designated integration contact.
- Where Zoom app controls are enabled, an administrator may need to pre-approve HockeyStick AI first.
- For Production, use a Zoom account not already connected to another HockeyStick engagement.
Install from HockeyStick
Connect from your engagement
Sign in, open the correct engagement, then go to Activate → Strategy & setup → Integrations and select Connect with Zoom. In the horizontal Activate bar, select the gear icon under Measure & improve (accessible name Strategy & setup); scroll the bar if needed. It opens Partnership strategy first. Select Integrations inside it.
Webinar lifecycle
Create, bind and reconcile
When an authorized user confirms Create Zoom webinar, HockeyStick sends the approved timing and configuration once, records the returned Webinar identity, then performs an exact authenticated read-back. A Webinar is not treated as verified until the returned identity and expected configuration reconcile; an ambiguous result stays visible for review and HockeyStick does not blindly create another Webinar. Editing the plan in HockeyStick afterwards does not push a change to Zoom: this release has no Webinar update path.
A participant registers on the HockeyStick-hosted page with first name, last name, email and consent; HockeyStick checks Zoom's registrant list, adds the person when needed and reconciles the enrolment. The private join link is returned to the participant and is not stored. After the event, HockeyStick reads the completed occurrence's participant timing, matches to enrolments by Zoom registrant identifier, calculates watch time and flags ambiguous matches for review. That reconciliation runs on the scheduled integration pull — every 15 minutes, with a full pull daily at 01:00 UTC — and only after the Webinar's scheduled end time has passed.
Removal
Disconnect, remove or reconnect
Disconnect from HockeyStick: Activate → Strategy & setup → Integrations → Revoke Zoom. HockeyStick removes local authorization material immediately and asks Zoom to revoke the access token when no other active engagement shares the account.
Remove from Zoom: Zoom has already removed the app before it
sends the signed app_deauthorized event, so HockeyStick
does not call Zoom's revocation endpoint again. It removes local
grants, pending state, direct Zoom identifiers and legacy recording
links, and marks every affected engagement as requiring
authorization. Zoom-derived person data is deleted or anonymized
within 24 hours of that event. See the
privacy policy for the full lifecycle.
Exact initial declaration
Requested permissions and why
Support
Get help
Use the Hockey Stick Advisory contact form for Zoom integration support. Support is staffed 24 hours a day, 7 days a week, including public holidays, and the target is an initial human response within 24 elapsed hours of receipt. That is a target for a first reply from a person, not a resolution time, and an automated acknowledgement does not satisfy it.
Provide your name, organisation and a safe reply address, the engagement and Webinar identifier, the issue type, the approximate time and any visible error. For a security incident, begin the message with SECURITY; for a privacy request (access, correction, deletion, consent), begin with PRIVACY.