Let designers and clients work in the Beaver Builder interface they already understand, with the campaign content kept on the popup where they expect to find it.

Review the campaign at realistic popup widths before launch so crowded columns, oversized headings, and weak mobile actions can be corrected before visitors see them.

Adapt trusted calls to action and saved layouts for focused campaigns instead of starting each promotion from an empty canvas.

Adjust when the campaign opens, who sees it, and how often it returns in Popup Maker while leaving the approved Beaver Builder design intact.

Build the popup content with Beaver Builder’s rows, columns, and modules while Popup Maker supplies the popup frame and campaign behavior.

Use Cases:

• Lead capture layouts: Combine a headline, supporting copy, form, and call to action in one focused design
• Promotional campaigns: Build product announcements, discount offers, and event registrations with familiar modules
• Rich media popups: Add images or videos without leaving the Beaver Builder editing workflow

Configuration: Create and save a Popup Maker popup, open the Beaver Builder tab, design the layout, and save your changes.

Use Beaver Builder’s responsive previews and device-specific controls to improve spacing, typography, visibility, and column behavior inside the popup.

Use Cases:

• Mobile opt-ins: Reduce multi-column layouts to a clear, comfortable mobile experience
• Readable announcements: Tune heading sizes and spacing for the popup’s actual width
• Focused mobile CTAs: Hide nonessential elements on smaller screens when the campaign needs a simpler path

Configuration: Open Beaver Builder’s responsive editor, review each relevant breakpoint, then test the saved popup on a real frontend page.

Insert saved templates, rows, columns, or modules with Beaver Builder’s shortcode when a campaign should reuse an established layout.

Use Cases:

• Shared calls to action: Reuse one approved CTA across pages and popups
• Repeatable client campaigns: Start from saved promotional sections instead of rebuilding every launch
• Central updates: Edit linked reusable content once and carry the change into each shortcode placement

Configuration: Save the Beaver Builder item, copy its shortcode, and place that shortcode in the popup content. Confirm every placement before deleting or replacing a shared item.

Apply the Beaver Builder typography, colors, spacing, and global styles your team already uses so the popup feels connected to the page behind it.

Use Cases:

• Brand consistency: Carry established colors and type choices into campaign content
• Agency handoff: Give client teams the same visual controls they already use for page updates
• Faster reviews: Compare the popup and page in one familiar design system

Configuration: Apply the appropriate Beaver Builder global and module-level styles, then preview the complete popup with its Popup Maker theme and close control.

Choose a Popup Maker campaign from the Beaver Builder Button module’s Open Popup action or from a supported module’s popup-aware link selector.

Use Cases:

• Lead magnet buttons: Open an opt-in popup from a call to action on a landing page
• Product details: Reveal sizing, specifications, or supporting content without sending visitors to another page
• Video lightboxes: Connect a designed page button to a focused video popup

Configuration: In a supported Beaver Builder module, choose the popup action or selector, select the intended popup, save the layout, and verify the click on the frontend.

Pair the Beaver Builder design with Popup Maker’s themes, opening triggers, targeting conditions, cookies, positioning, and available analytics.

Use Cases:

• Timed announcements: Open a Beaver Builder-designed offer after a useful delay
• Page-specific campaigns: Show the popup only where its message is relevant
• Frequency control: Use cookies to avoid repeating a campaign more often than intended

Configuration: Return to Popup Maker after saving the Beaver Builder layout and configure the campaign settings required by your use case.