This article covers how to embed a Webcast Elite event into a third-party webpage.

Note:  Embedding an ON24 event into a third-party website is available for those who need it for alignment with existing ecosystems, though the full-page experience remains ON24's recommended approach for optimal performance and audience engagement.   
A ticket to Support is needed to discuss/enable this feature.

Things to Know

The ON24 Webcast Elite console is purpose-built to deliver a seamless, engaging, and branded experience across all devices and audiences.  Any approach that minimizes, fragments, or alters the full console environment compromises the value and integrity of the platform, while introducing operational risks that ON24 does not support.

If you choose to embed an event, we recommend using the ON24 Engagement Hub or embedding the full console.

• The preferred embedding method is to use the the ON24 Engagement Hub—which aggregates and curates webinar content—is a scalable, low-maintenance solution:
  • All updates are centralized
  • Content changes propagate automatically
  • You preserve the ON24 experience and simplify your internal operations

OR

• The officially supported method is to embed the full ON24 console via iFrame, maintaining all capabilities, integrity, and supportability.
• You can embed a single event, or every event in your workspace.  (The Support team will ask you to detail your use-case on this point to help you determine which is right for you.)
• Details on how to do this are listed below under Set Up.

Find more information on why you want to use the full event console here. 

Known Issues

• Size of the embed area can have negative effects on consoles with responsive behavior on. Tools might be too small or hidden when embed area is too small.
• Returning registrants are not remembered in Mac or iOS devices. The Registration page will be presented every time when someone visits the page.
• For iOS attendees, End of Event survey responses do not save.

Set up 

Once embedding is enabled in your account, you'll need to set up the event before you embed the event in your domain.

You will add a list of trusted sites to your ON24 Registration page to ensure content is only shared on trusted sites and reduce setup time.

From the event's Registration tab, click on Security, then toggle Embedding ON.

Add the domain(s) where this event can be embedded.  Separate multiple domains by commas and use asterisks as a wildcard, to allow all subdomains.

Embed on trusted Domains

To embed the ON24 webinar into a 3rd party webpage, you'll need to create an iFrame with your specific event details, either pointing to the Audience Link/URL or an ON24 seamless API.  

Grab the event's key from the Audience Link/URL.  Click the copy button, then paste the link into a text editor.  The key will be the long string of characters after the event ID.

For example: 

https://event.on24.com/wcc/r/48585XX/1D58070C469E9D24E3E32783AB12XXXX

Note: Do not use the URL shown in the Event/Audience Link browser bar to avoid any potential custom parameters.

The creation of the iFrame is standard in most ways.

The iFrame dimensions should be big enough to match the console setup in Console Builder. We recommend enabling responsive behavior for console so the Console will adjust based on viewing area.

The source of your iFrame will match your Event/Audience Link.

Audience URL

• When an Audience URL is embedded, the workflow for viewers will be standard ON24 workflow.
  • Viewers will start from the ON24 registration page and end on either the ON24 Lobby page or the Audience Console, depending on if the event has been started or not.

Example of an Embed Code for Live Event WITHOUT Forums/Breakouts

<iframe src="https://event.on24.com/wcc/r/########&key=#######################" 
width="1280" height="720" allow="fullscreen"></iframe> 

Example of Embed Code for Event WITH Forums/Breakouts

<iframe src="https://event.on24.com/wcc/r/########&key=#######################" 
width="1280" height="720" allow="microphone; camera; fullscreen; display-capture"></iframe> 

Seamless API

• When data is passed seamlessly, viewers will skip the ON24 registration page but the rest of the workflow will be the same.
• The event id, key & email are required parameters.
  • If an email is not available, a unique identifier can be passed in place of that.
• You must use HTTP POST method: https://event.on24.com/utilApp/r for the Seamless URL.
  • HTTP GET https://event.on24.com/interface/registration/autoreg/index.html WILL NOT WORK

Example of an Embed Code for Live Event WITHOUT Forums/Breakouts

<iframe src="https://event.on24.com/utilApp/r?
eventid=########&key=#######################&email=
<email>&firstname=<firstname>&lastname=<lastname>" 
width="1280" height="720" allow="fullscreen"></iframe> 

Example of Embed Code for Event WITH Forums/Breakouts

<iframe src="https://event.on24.com/utilApp/r?
eventid=########&key=#######################&email=
<email>&firstname=<firstname>&lastname=<lastname>" 
width="1280" height="720" allow="microphone; camera; fullscreen; display-capture"></iframe> 

Why ON24 Recommends Full-Page Browser Experience

ON24 is Designed as a Full-Browser, Immersive Application

• The ON24 console operates as a robust single-page application optimized for modern browsers and screens.
• This architecture ensures a consistent, stable user experience with fully synchronized media, layouts, and engagement tools.
• Altering this setup—such as rendering it in limited containers—undermines layout control and responsiveness.

Limited Display Area = Reduced Business Impact

• Smaller render areas reduce how many engagement tools can be displayed, directly impacting:
  • User interaction levels
  • Behavioral signals captured
  • Engagement scoring and lead qualification
  • Fewer visible tools = less participation = slower conversion.
• Example: When looking at Webcast vs Engagement Hub launch data for leading fortune 100 companies, the average Engagement Score for full browser direct launch is 3.5/4.0 and embedded was 2.3/4.0 (over the last 30 days).

Degraded Cross-Device and Cross-Browser Experience

• When the console is embedded in constrained environments, layout anomalies like scrollbars, overlapping content, or broken responsiveness often emerge—especially on mobile.
• These inconsistencies can reflect poorly on both ON24 and the customer's brand, even if ON24 is not the root cause.

Brand Risk: Loss of Plausible Deniability

• When the experience is embedded directly into a customer-managed environment, any issue—whether ON24’s fault or not—can be perceived as the customer's fault.
  • Example: If ON24 experiences latency, it’s the host brand that may take the reputational hit.
• Using the full ON24 console preserves a clear line of ownership and trust.

Operational Complexity: Managing Dynamic Event Changes

• When webinars are independently published into a third-party experience:
  • Any update to metadata (title, time, speaker, etc.) must be propagated downstream.
  • APIs exist to support this, but managing them requires additional effort and infrastructure on the customer’s side.
• As the recipient site, the burden of ensuring real-time accuracy becomes yours.

Diminished Personalization and AI Automation

• ON24’s Smart Tips, Smart Questions, Engagement Scoring, and post-event nurture automation rely on context from the complete user experience.
• Restricting the engagement surface reduces data availability, making personalization and AI less effective.

Analytics and Attribution Gaps

• ON24’s analytics model assumes complete visibility into user behavior across all tools.
• If the experience is constrained, analytics:
  • May become fragmented or unreliable
  • Miss key engagement milestones
  • Underreport signals that drive campaign ROI