Use the same structured design approach your team follows for the rest of the site instead of treating every popup as an isolated one-off.

Apply the established classes, tokens, and responsive rules that make Bricks content easier to maintain across a growing site.

Review the design at the constrained widths where it will appear, then correct layout pressure before it becomes a visitor-facing problem.

Let Bricks own the content while Popup Maker owns the trigger, audience, frequency, and surrounding popup presentation.

Build Bricks popups with containers, elements, global classes, and responsive controls—without copying a separate template into Popup Maker.

Use Cases:

• Reusable design systems: Apply Bricks global classes to popup elements for consistent styling
• Responsive campaigns: Refine content at Bricks breakpoints before launch
• Complex layouts: Build popup structures with Bricks containers and nestable elements

Configuration: Save a Popup Maker popup draft, choose Edit with Bricks, build the element tree, and save from Bricks.

See the selected Popup Maker theme, size, position, title, and close control around the editable Bricks content for a more realistic design review.

Use Cases:

• Theme checks: Review the popup container and overlay styling around the Bricks layout
• Dimension checks: Confirm content fits the configured popup size and position
• Close-control spacing: See how the Popup Maker close control relates to the Bricks content

Configuration: Choose the Popup Maker theme and display settings before opening or refreshing the Bricks editor canvas.

Display the layout, styling, and compatible interactive elements you created in Bricks inside Popup Maker’s campaign frame.

Use Cases:

• Bricks-built landing pages: Show a Bricks-authored popup without replacing the landing page layout
• Dynamic elements: Use compatible Bricks elements that need the popup’s own content context
• Mixed content: Show a Bricks popup on a Bricks-built page while keeping both designs intact

Configuration: Save the popup in Bricks, preview it on a real frontend page, and test every interactive element used in the campaign.

Keep the approved Bricks styling intact whether the popup opens from a click, after a delay, or later in the visitor’s journey.

Use Cases:

• Click-triggered campaigns: Preserve the approved design when a visitor opens the popup from a link or button
• Multiple campaigns: Keep more than one Bricks-designed popup consistent on the same page
• Frontend consistency: Deliver the campaign without maintaining a duplicate landing page

Configuration: No separate asset setting is required. Test custom code and third-party Bricks add-ons used in the popup.

Keep Bricks-designed campaigns connected to Bricks while other popups on the same site can continue using their existing editor.

Use Cases:

• Multi-builder sites: Use Bricks for selected campaigns without changing every existing popup
• Team clarity: Open a campaign in the editor where its design is actually maintained
• Gradual adoption: Try Bricks on a new popup before deciding whether to rebuild older designs

Configuration: Save the campaign in Bricks. Keep established popups in their current editor unless you intentionally rebuild them.

Pair Bricks popups with Popup Maker’s themes, opening triggers, targeting conditions, cookies, positioning, and available analytics.

Use Cases:

• Targeted offers: Combine Bricks layouts with Popup Maker targeting rules
• Click and timed campaigns: Choose Popup Maker triggers independently of the Bricks content
• Frequency control: Apply Popup Maker cookies around the Bricks-authored popup

Configuration: Return to Popup Maker after saving in Bricks and configure the campaign settings your use case requires.