If HTML Forms is installed, Popup Maker detects it automatically. No API keys, no account connections, no setup wizards. Install both plugins and start building form popup experiences immediately—your custom HTML markup works in overlays without modification.

HTML Forms submits via AJAX by default through WordPress admin-ajax.php—no page reloads, no interruptions, no external dependencies. Popup Maker hooks directly into HTML Forms’ submission events, so close behaviors fire instantly, follow-up overlays trigger seamlessly, and conversion tracking registers the moment server-side validation completes. Your hand-coded forms maintain full AJAX functionality inside popups without configuration.

Whatever you build with raw HTML—contact forms, newsletter signups, API documentation feedback, bug report templates, beta registration workflows, developer surveys—works seamlessly inside popups. Write your HTML structure once with data attributes, reuse it in inline context or popup overlay without changing markup. The integration respects your code structure completely.

Popup Maker integrates at the form submission event level, so all HTML Forms add-ons function normally inside popups: Mailchimp (via MC4WP), reCAPTCHA validation, hCaptcha, custom action hooks, redirect attributes, and custom submission handlers. Your existing configuration transfers to popup context without modification.

Automatically close the popup when visitors successfully submit your HTML Forms form. No extra clicks, no confusion—just a clean transition.

Use Cases:

• Developer Contact Forms: Close HTML Forms popup immediately after AJAX submission—no redundant overlays or lingering dialogs
• Support Ticket Collection: Auto-dismiss form popup overlays after submission completes server-side validation
• API Documentation Feedback: Close popup instantly when users submit bug reports or enhancement requests
• Responsive Newsletter Signups: Dismiss lightweight popups on desktop while keeping mobile overlays visible (via targeting conditions)
• Technical Form Workflows: Auto-close popup without forcing developers to locate close button

Configuration: Enable in Popup Settings → Close → Form Submission. Add optional delay for confirmation feedback before closing.

Open a different popup when any HTML Forms form is submitted. Works with forms inside popups or anywhere on your site.

Use Cases:

• Beta Program Enrollment: Show custom HTML Forms thank you popup with credential download after developers submit signup—no redirect page required
• Feature Request Workflows: Display API documentation popup after users submit enhancement requests via inline form
• Multi-Step Developer Onboarding: Chain form popups: initial contact → qualification overlay → environment setup popup
• Integration Testing Confirmation: Trigger webhook delivery popup after developers submit test results
• Progressive Disclosure Workflows: Build popup sequences where each submission unlocks next interaction layer
• Environment Configuration: Show deployment options popup after users submit initial preference via inline form

Configuration: Target specific form IDs or trigger on any form submission. Chain multiple popups in sequence.

Prevent form popups from reappearing after visitors have already submitted. Respect their time and avoid repeated prompts.

Use Cases:

• API Credential Management: Stop showing access request popups after developers submit and receive authentication tokens
• Documentation Feedback Control: Prevent form popup from reappearing—users only submit feedback once per session
• Beta Program Enrollment Tracking: Suppress signup popups for registered developers; show upgrade path popup instead
• Issue Tracking Deduplication: Hide bug report template popups after users file GitHub issues; prevent duplicate submissions
• Contributor Workflow Respect: Once developers submit feature request via form popup, suppress for 30 days
• Segmented Campaigns: Exclude form submitters from general signup popup campaign; show “existing users” offer instead

Configuration: Set cookie duration from session-only to persistent. Each form can have independent cookie settings.

Target visitors who are actively filling out a form. Show contextual popups to users engaged with specific forms.

Use Cases:

• Code Example Assistance: Show syntax reference popup when developers begin filling out the bug report form—providing context-sensitive help
• Draft Preservation Workflows: Trigger “Save as draft” popup when users engage with complex multi-field forms
• API Specification Help: Display format reference popup when developers interact with technical forms
• Contextual Support Chat: Show “Need help?” popup when users engage with technical questionnaire forms
• Documentation Surfacing: Display related docs popup as developers interact with forms—context-sensitive help based on engagement

Configuration: Select target form(s). The condition triggers when visitors begin interacting with the form.

When someone submits your form, Popup Maker counts it as a conversion and can automatically stop showing that popup to them.

Use Cases:

• Self-Hosted Analytics: Track form popup submissions as conversions without external SaaS dependencies
• Enrollment Deduplication: Automatically hide beta signup popups from developers who already registered
• Progressive Engagement Workflows: Show survey popup only to users who haven’t submitted initial intake form
• API Access Tracking: Count credential requests as conversions; suppress “request access” popups for approved developers
• Performance-First Measurement: Measure popup conversion without external tracking scripts that bloat page weight

Track every form popup with detailed metrics in the analytics dashboard.

Use Cases:

• Trigger Strategy Testing: Compare “exit intent” vs “scroll 50%” triggers for same popup—identify optimal timing
• Developer Engagement Measurement: Track which documentation feedback popups convert best across dev portal
• Traffic Source Attribution: Monitor API access request popups by referrer—prioritize marketing channels driving qualified developers
• Form Friction Analysis: Compare popup submission time across field configurations—identify which inputs create friction (time-to-conversion metric)
• Fatigue Detection: Measure popup close rates over time—if increasing, users declining repeated form offers