ON24 offers an option to embed your events into your own site if needed. While we recommend using the full-page Webcast Elite console for the best experience, this article can help you understand your options and reach out if this is the right fit for your ON24 events.
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.
Considerations
The ON24 Webcast Elite console is purpose-built to deliver a seamless, engaging, and branded experience across all devices and audiences. Using the Webcast Elite Console, or Embedding our Engagement Hub solution is the suggested for all ON24 customers. These solutions are fully tested, and supported by the ON24 team. ON24 recommends to all customers using the Full-Page Browser Experience designed specifically for events.
If third party is embedding is required, 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 operation
However, for those who need an embedding solution outside of the ON24 ecosystem or the Engagement Hub, event embedding options are available.
- For 3rd party embedding without the Engagement Hub, the suggested method is to embed the full ON24 console via iFrame, maintaining all event capabilities, integrity, and allowing for the most robust support.
- 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.)
Note: The embedding option is a new and evolving feature. Currently there are known issues to consider before implementing any solution.
- 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.
- The SSO use case has not been tested and is not currently supported.
Embed Setup
If embedding is decided upon, reach out to ON24 Support to enable the availability in your account. Once embedding is enabled in your account, you'll need to set up the predetermined domains in the account, and then create the event before you are able to embed the event on your domain.
From your account settings add the domain(s) where this event can be embedded. Separate multiple domains by commas (without spaces) and use asterisks as a wildcard, to allow all subdomains. Once supported domains are set up the 'Link and Embed' button will become available.
Note: Manage User permissions is required to set or add domains.
Two embed codes will be available via the 'Link and Embed' button on your events 'Overview' or 'Registration' page.
Copy the code that works best for your specific use case and implement on your site.
Embed URL Options
Within the embed code section you will find two options, "Webinar in Website" and "Webinar in WordPress Site". Select the best option based on your use case.
Webinar in Website
This option allows you to embed your full Registration page and Event Console.
Depending on your sites style and setup you may wish to adjust or add styling for height and width of the iframe.
Webinar in WordPress Site
This option allows you to embed your full Registration page and Event Console in your WordPress site via Supported Shortcode
Install and activate the ON24 Webcast Embed Plugin to use this option.
Use the supplied short code in a short code block.
Adjust the width and height as needed to match your WordPress content.
Additional Options
If using Seamless Registration for your embedded event, additional parameters must be added.
- 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 fail.
- You can also use Unified Seamless Registration - https://seamlessreg.on24.com or https://seamlessreg.eu.on24.com
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
- Under report signals that drive campaign ROI
Comments
0 comments
Please sign in to leave a comment.