Bloom plugin review and common issues

Bloom uses cookies to track whether a visitor has seen or dismissed a popup. In Bloom’s settings for each opt-in form, configure the “Display Frequency” option — set how many days must pass before the popup shows again to the same visitor. If visitors are seeing the popup on every visit despite this setting, a caching plugin or CDN may be preventing the Bloom cookie from being set correctly. Ensure your caching plugin does not cache pages for logged-in users and that it respects cookies for popup suppression logic.

Email platform connections in Bloom use API keys. Go to Bloom → Email Accounts and verify your API key is current — many platforms periodically expire or revoke API keys. Generate a new API key from your email platform’s account settings and update it in Bloom. For Mailchimp specifically, ensure the API key has list management permissions. After updating the API key, save and test the connection by submitting a test form entry.

Content locking in Bloom uses JavaScript to hide content below the lock. If content is visible without subscribing: (1) a browser extension (reader mode, privacy tools) may be stripping JavaScript; (2) the Bloom script is not loading — check browser DevTools Console for errors; (3) caching is serving a cached version of the page where the content lock JavaScript was not rendered — clear all caches. Content locking is not security-grade protection (determined visitors can inspect page source) — it is friction-based, appropriate for low-stakes gated content.

In the Divi page editor, add a Code Module or use the Bloom Optin module if available in your Divi version. For the shortcode method: in Bloom → Optins, click the “Embed Code” button on your inline form to copy its shortcode. Paste the shortcode into a Divi Text Module or Code Module where you want the form to appear. Inline forms inherit Bloom’s styling and display directly within the page content without popup behavior.

Bloom’s targeting capabilities are more limited than OptinMonster or Convert Pro — it does not include referral source targeting as a native display rule. Bloom targeting is based on page/post-level rules (show on specific posts, categories, or everywhere). For referral-source-based targeting, use a more advanced popup plugin like OptinMonster or Convert Pro alongside Bloom, or implement UTM parameter detection via custom JavaScript to conditionally trigger Bloom forms.

If your email list building strategy relies primarily on well-timed forms without exit intent or A/B testing, Bloom covers the use case at no additional cost. If you need exit intent recovery (capturing visitors before they leave) or systematic A/B testing of different offers, you will need OptinMonster or Convert Pro regardless of your Elegant Themes membership. Many Divi sites use Bloom for standard embedded forms and add OptinMonster specifically for exit intent campaigns.

Yes — Bloom functions on any WordPress site regardless of page builder. The content design options are theme-agnostic and the opt-in forms display correctly with Elementor, Bricks, Beaver Builder, and native WordPress themes. However, Bloom’s design aesthetics are most harmonious with Divi-built sites, and tight integration within Divi’s builder is its primary strength.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.