MailOptin plugin review and common issues

New post notifications depend on WordPress post publishing hooks and your email platform’s API. Check: (1) the notification is configured and active in MailOptin → Email Campaigns → New Post Notification — verify the target list and template are selected; (2) the post status at publish time is “Publish” (not scheduled, draft, or private) — only standard public post publication triggers the notification; (3) your email platform API key has list management permissions. Test by publishing a test post and checking your email platform’s activity log for the campaign send.

Exit intent mouse tracking does not work meaningfully on mobile. In MailOptin campaign Display Rules, add a Device targeting condition and exclude Mobile. Alternatively, configure a different trigger for mobile (scroll depth or time delay) while keeping exit intent only for desktop visitors. Set up two versions of the campaign — one desktop version with exit intent and one mobile version with scroll trigger — both targeting the same opt-in form design.

MailOptin A/B testing uses cookie-based variant assignment. Visit the page multiple times in different browsers or incognito windows to verify different variants appear. If the same variant always shows, check the A/B test configuration in the campaign settings — ensure both variants are active and the split percentage is configured (50/50 by default). Clear caching plugins and CDN cache, as cached pages may always serve the same cached variant.

Go to MailOptin → Email Campaigns → New Post Notification. Create a new notification, select the email list from your connected platform, and choose a template. Configure which post categories trigger notifications — you can send notifications only for specific categories (e.g., newsletter subscribers only get posts tagged as newsletters). The notification sends automatically when a qualifying post is published, creating an effortless “auto-newsletter” for content sites without manual campaign creation.

Yes — each MailOptin opt-in campaign connects to a specific list (or tag/segment) in your email platform. Configure each form to send subscribers to a different list or tag based on the form they convert on. For example, a sidebar form sends to a general newsletter list, while a content upgrade popup sends to a segmented list for that specific lead magnet. Subscriber segmentation is managed at the email platform level using MailOptin’s list/tag targeting per campaign.

MailOptin partially overlaps with MailPoet for newsletter functionality, but the two have different strengths. MailOptin connects to external email platforms and adds popup lead generation. MailPoet is a full self-hosted email marketing system with more sophisticated campaign automation, subscriber management, and email design tools. MailOptin is better for sites that want popup forms plus basic newsletter automation through an existing email platform. MailPoet is better for teams that want to manage email marketing entirely inside WordPress without an external ESP.

MailOptin Pro includes WooCommerce integration — targeted campaigns based on cart value, purchase history, and product categories. For stores needing popup-based cart abandonment campaigns and new purchase follow-up sequences, MailOptin Pro covers the basics. For more sophisticated WooCommerce email automation (post-purchase sequences, abandoned cart flows, product recommendation emails), a dedicated WooCommerce CRM plugin like FluentCRM or a full ESP like Klaviyo provides more depth.

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.