Frequently Asked Questions
Is there a native Uncanny Automator integration for Popup Maker?
No. Popup Maker and Uncanny Automator don’t have built-in integration code. This is a workflow-based integration using Popup Maker’s JavaScript API and targeting conditions with Automator’s general automation actions.Can I trigger popups without Automator Pro?
Yes. Use the cookie-based targeting method with Automator’s free user meta/tagging actions. This works entirely with free versions of both plugins. The JavaScript `PUM.open()` method requires Automator Pro’s “Run Code” action.Will popups trigger instantly during automation?
Not with the JavaScript method—the code executes server-side during automation, but the popup displays on the user’s next page load. For immediate display, you’d need custom real-time webhook handling. Cookie-based targeting works on subsequent page views.What's the popup ID and where do I find it?
The popup ID is the unique number WordPress assigns to your popup. Find it in Popup Maker → All Popups—it’s shown in the ID column or in the browser URL when editing a popup (post=POPUP_ID).Can I use Automator tokens in popup triggers?
Directly, no—Popup Maker’s JavaScript API expects a static popup ID number. But you can use Automator tokens to determine WHICH automation runs, effectively routing different events to different popup IDs via conditional recipes.Does this work with Automator's free version?
Partially. Cookie-based targeting works with free Automator (using user meta/tag actions). JavaScript triggering requires Automator Pro for the “Run Code” action. Webhooks also require Pro.How do I trigger different popups for different events?
Create multiple Automator recipes, each with its own trigger and a different popup ID in the “Run Code” action. Example: Recipe 1 (course complete → popup 123), Recipe 2 (purchase → popup 456).Can anonymous (logged-out) visitors see automated popups?
With the JavaScript method, yes—if they’re on a page after the automation runs (requires session context). Cookie-based targeting typically requires logged-in users unless you implement custom cookie-setting for anonymous visitors.
