Hopin

Overview

Hopin grew rapidly during the pandemic as a virtual events platform and has since expanded to include hybrid event capabilities and webinar hosting. The platform supports multi-track events with stages, networking areas, breakout sessions, and expo booths. When embedded on a website, Hopin's widgets typically handle event registration and livestream viewing, allowing attendees to participate without navigating to a separate platform.

What This Script Does

Hopin's client-side scripts embed event-related functionality on websites. Scripts are loaded from Hopin's domains to render registration widgets and video players.

Registration Widgets

Embedded registration forms collect attendee information:

• Name and email address (required)
• Organization and job title (optional, configurable by event organizer)
• Custom registration fields defined by the event organizer
• Ticket selection for paid or multi-tier events

Livestream Player

For live and recorded events, Hopin may embed a video player that handles:

• Live video streaming from event stages
• Chat and Q&A interfaces alongside the video
• Session switching for multi-track events

Cookies and Session Management

• hopin_session — session cookie maintaining the attendee's authenticated session during the event
• hopin_visitor — identifies returning visitors who have previously registered

Engagement Tracking

The scripts track basic engagement metrics for event organizers:

• Registration completion events
• Session attendance duration
• Chat participation and Q&A submissions

Data is transmitted to Hopin's servers. The tracking is limited to event engagement and does not extend to general website browsing behavior. Hopin does not set advertising or cross-site tracking cookies.

Consent & Compliance

Hopin is classified as functional. Its scripts provide event registration and attendance functionality that users explicitly request when they choose to register for or attend an event. The engagement tracking (attendance duration, participation metrics) serves the event organizer's operational needs.

Under GDPR, the session cookie for maintaining event attendance state is functionally necessary when a user is actively participating in an event. Registration data processing is justified under the steps necessary to enter into a contract (event registration agreement). The visitor identification cookie for returning registrants serves a functional convenience purpose.

Under the ePrivacy Directive, cookies necessary for the event service the user has requested are exempt. The engagement metrics tracking is tied to the event service rather than general browsing monitoring.

Under CCPA/CPRA, Hopin processes attendee data as a service provider for the event organizer. Registration and engagement data serves the business purpose of event management and is not sold or shared for advertising.

Should You Block This Without Consent?

No. Hopin scripts serve a functional purpose — enabling event registration and attendance. Blocking them would prevent visitors from registering for or participating in embedded events. The engagement tracking is inherent to the event service rather than a separate marketing function.