Allow Messaging Web Widget launcher position to be set dynamically via JavaScript / API | Community
Skip to main content
Idea Submitted

Allow Messaging Web Widget launcher position to be set dynamically via JavaScript / API

Related products:Chat and messaging (Chat)
  • March 2, 2026
  • 1 reply
  • 0 views

We would like to request support for dynamically setting the Messaging Web Widget launcher position (bottom-left vs bottom-right) via JavaScript and/or API, rather than only through a global Admin Center setting.

Current limitation

  • Launcher position can only be configured globally in Admin Center.
  • There is no supported way to change left/right positioning per page via code.
  • Workarounds (multiple widget instances, custom launcher, embedded mode) add operational and maintenance overhead.

Use case

  • On certain pages, the default bottom-right launcher interferes with existing UI elements (e.g., floating CTAs, forms, or consent components).
  • On other pages, bottom-right is the preferred placement.
  • We want a single widget configuration that can adapt based on page context.

Requested capability
One of the following (any would be sufficient):

  • A JavaScript API option, e.g.
    zE('messenger:set', 'launcher.position', 'bottom-left')
  • A page-level override parameter in the widget configuration
  • Support for dynamically updating the launcher position at runtime

Why this matters

  • Reduces the need for duplicate widget configurations
  • Avoids custom launcher implementations for a simple layout concern
  • Aligns with modern SPA / component-based websites where layout varies by route
  • Improves developer experience without impacting non-technical customers

Current workarounds (not ideal)

  • Maintaining multiple Messaging Web Widgets with identical configs
  • Building and maintaining a custom launcher
  • Switching to embedded mode solely for positioning control

This would be a small but high-impact improvement for teams with complex or responsive layouts.

1 reply

Marcin15
  • March 3, 2026
Thank you for taking the time to provide us with your feedback. This has been logged for our PM team to review. For others who may be interested in this feature request, please add your support by upvoting this post and/or adding your use case to the comments below. Thank you again!