01Who this is for
- Digital marketing agencies benefit because they can offer branded price banners or countdown timers that integrate directly into client funnels.
- Ecommerce owners gain flexibility to embed custom upsell components without altering the core funnel builder code.
- SaaS product teams can showcase subscription status widgets that update in real time within their sales funnels.
02Web widgets, explained
The custom widget feature lets developers extend the HighLevel funnel builder with interactive UI elements built in any JavaScript framework or plain HTML/CSS/JS. The widget runs inside an iframe, and on each configuration change it emits HTML, CSS, and optional JavaScript back to the parent builder via a Postmate event. The builder then injects that code so the widget appears on the funnel page.
Developers register an app on the HighLevel App Marketplace, create the widget application, and package the output files into a zip archive. After marketplace approval, the widget appears under a “Custom Widgets” section where users can install it, drag it onto a funnel, adjust limited visual settings, and let the widget’s own pop up handle advanced configuration.
03How businesses use web widgets
- Digital marketing agency. The agency builds a price banner widget that emits HTML and CSS based on client chosen colors and text. After uploading the zip to the marketplace, the agency’s clients install the widget, drag it onto their sales funnels, and adjust margin and padding in the builder. The banner updates in real time as the client changes settings in the iframe pop up.
- Ecommerce store. The store creates an upsell widget using React that returns HTML, CSS, and JavaScript through the createHtml(), createJs(), and createCss() functions. The zipped build is submitted to the marketplace. Once approved, the store adds the widget to checkout funnels, configures basic spacing in the builder, and relies on the widget’s internal pop up for product selection.
- SaaS company. The SaaS team develops a subscription status widget that listens for user interaction and dispatches a customWidgetOpenPopup event to show a renewal dialog. After publishing the widget, product managers install it in onboarding funnels, place it via drag and drop, and let the widget’s iframe manage settings while the builder renders the supplied code.
04The numbers and rules that matter
- Settings object may include widgetHeight, widgetWidth, image.
05Before you start
- Basic knowledge of HTML, CSS, and JavaScript or experience with a frontend framework such as Angular, React, or Vue.
- Familiarity with iFrames and event driven programming concepts.
06How to set up and use web widgets in HighLevel
Set up custom widget
- Develop an independent web app that generates the widget’s HTML, CSS, and optional JavaScript.
- Implement functions named createHtml(), createJS(), and createCss() that return the respective code strings.
- Use Postmate to establish iFrame communication and emit a ‘code’ event containing html, js, and elementStore to the parent.
- On initial handshake, listen for an elementStore payload and emit the initial widget state back to the parent.
Upload widget to marketplace
- Build the widget project and ensure all asset paths are relative.
- Compress the HTML, CSS, and JavaScript files or the framework’s dist folder into a .zip archive.
- Upload the .zip file to the App Marketplace during the widget setup process, following platform guidelines.
Integrate with Funnel Builder
- Install the approved widget from the marketplace into a funnel.
- Drag the widget onto the funnel canvas to place it.
- Adjust limited settings such as margin, padding, visibility, and custom classes directly in the builder.
- Verify that the funnel builder correctly renders the widget by interpreting the supplied HTML, CSS, and JavaScript.
Handle events and communication
- Host the widget’s settings interface inside an iframe within the funnel builder.
- Generate and send updated HTML, CSS, and JavaScript code whenever a setting changes.
- Dispatch custom events like customWidgetOpenPopup or customWidgetGoToNextStep to interact with the funnel preview.
07Settings that matter
- createHtml(). Returns the HTML markup that the widget needs to render inside the funnel.
- createJS(). Returns optional JavaScript code required for the widget’s interactive behavior.
- createCss(). Returns the CSS styles that apply to the widget’s HTML.
- elementStore. An object that holds the widget’s configurable variables and is sent to the parent builder during initialization.
08Things to know before you rely on it
- Only .zip archive files are accepted for upload; .rar and other formats are not supported.
- Asset paths must be relative; absolute paths are prohibited to avoid loading errors.
- The widget must not introduce external scripts that could conflict with the builder’s core functionality.
- Widgets should not disrupt white labeling, overlap existing elements, or cause state inconsistencies across revisits.
09How it connects to the rest of HighLevel
- Marketplace app distribution settings explained App distribution
- How to configure pricing for a HighLevel Marketplace app App pricing
- Managing developer users and permissions in HighLevel Developer permissions
Michael's take

In my experience, packaging the code as a zip and letting users drag and drop it makes distribution straightforward, while the platform handles the marketplace side.