Bricks Builder Popup Triggers Not Working on Mobile? Here Is the Fix

Bricks Builder includes a powerful popup system for displaying forms, offers, and announcements.

Setting up a popup with a button trigger takes only a few minutes using the Bricks Builder interface.

But sometimes the popup works correctly on desktop computers but does nothing on mobile phones.

The visitor taps the trigger button, but the popup never opens or opens with a long delay.

This problem frustrates mobile users who make up the majority of website traffic nowadays.

Why Bricks Builder popup triggers fail on mobile devices

Bricks Builder uses click events to detect when a trigger button gets pressed by the user.

Mobile browsers handle click events differently than desktop browsers, causing potential problems.

A 300-millisecond delay exists on some mobile browsers between tap and click event firing.

If another element overlays the trigger button on mobile, the tap never reaches the button at all.

The popup trigger may be set to show on specific devices, and mobile may be excluded accidentally.

JavaScript optimization plugins can also delay the popup script on mobile devices specifically.

How to check if mobile popup triggers are configured correctly

Edit the popup in Bricks Builder and navigate to the popup settings panel for the element.

Look for the display conditions section that controls where and when the popup appears.

Check that “Mobile” and “Tablet” devices are enabled in the display conditions settings.

If these device types are disabled, the popup will never open on phones or tablets.

Re-enable any disabled device types and save the popup settings to apply the changes.

Step by step guide to fixing Bricks Builder mobile popup triggers

Follow these steps to ensure popup triggers work correctly on all mobile devices.

• Edit the popup in Bricks Builder and check the display conditions for device types
• Ensure that Mobile and Tablet devices are both enabled in the popup display settings
• Set the popup trigger to use “Click” instead of “Hover” because hover does not work on touch screens
• Increase the click delay setting to 300 milliseconds for better mobile browser compatibility
• Check that no other element has a higher z-index and overlaps the trigger button
• Disable JavaScript defer or delay features for Bricks Builder popup scripts in caching plugins
• Test the popup on real mobile devices instead of relying on browser simulation tools
• Use browser developer tools to inspect the trigger button for overlapping elements
• Add custom CSS to increase the touch target size for better mobile usability
• Consider using a dedicated mobile popup plugin if Bricks Builder popups continue to fail

Custom CSS to improve mobile popup touch targets

Add this CSS to Bricks Builder global settings or theme customizer for better mobile touch targets.

.brx-popup-trigger {
cursor: pointer;
display: inline-block;
min-height: 44px;
min-width: 44px;
}
@media (max-width: 768px) {
.brx-popup-trigger {
padding: 12px;
}
}

This CSS ensures touch targets meet accessibility standards for mobile devices.

The minimum size of 44×44 pixels is recommended by Apple for touch-friendly interface elements.

Bricks Builder mobile popup troubleshooting reference table

Here is a reference table for diagnosing popup trigger problems on mobile devices.

For more information about Bricks Builder popups, visit the Bricks Builder page on wpwizzy.com.

Preventing Bricks Builder mobile popup problems in the future

Always test popups on real mobile devices during the design process before publishing them live.

Use click triggers instead of hover triggers for any popup that should work on mobile phones.

Set popup dimensions using percentages or viewport units instead of fixed pixel values.

Keep popup content minimal on mobile devices to improve loading speed and usability.

Test popup triggers with various JavaScript optimization settings enabled and disabled.

Regularly review mobile analytics to catch popup problems before visitors report them.