Check Your PushEngage Setup with AI
Get a plain-English check of your push notification setup: connection, subscribers, auto-push, segments, and anything in the debug log.
Prerequisites
A connected site running PushEngage 4.2.10 or newer on WordPress 6.9 or newer. The check is read-only.
I use PushEngage on my WordPress site. Give me a health check of my push notification setup. Use the PushEngage abilities, and only the read-only ones: do not send anything and do not create or change anything. Check the connection status first. If the site is not connected to a PushEngage account, tell me that is the whole problem, tell me where to connect it, and stop. Otherwise read the plugin info, the subscriber numbers, the auto-push settings, the segments, the category to segment mappings, and the list of debug log files. Give me a checklist with a clear pass, warning, or fail for each of these: the connection and the PushEngage site ID, active subscribers this week and in total, whether auto-push is on, which content types trigger a push and whether any look like internal content such as templates or quizzes, how many segments exist and whether any have zero subscribers, whether my main categories are mapped to segments, and whether the debug log has recent entries. If there are log files, read only the most recent one and summarize what it says in two or three sentences without pasting its contents. If a number is zero, say it is zero and do not guess at the reason. For every warning or fail, give me one line on why it matters and where I fix it.
Skip pasting the full prompt. Drop this into your AI on a site that already has WPVibe:
Run the “Check Your PushEngage Setup with AI” recipe from the WPVibe cookbook on my connected site.
Push notifications fail quietly. The plugin got disconnected during a migration. Auto-push was switched off for a test and never switched back. The subscriber count has been flat for a month because the opt-in stopped showing. Nothing errors and nothing alerts you. You find out when someone asks why they stopped hearing from you, or when you notice the traffic from notifications went to zero some time ago.
The AI runs PushEngage’s read-only abilities and turns them into one checklist: is the site connected and to which PushEngage site ID, how many active subscribers there are this week and in total, whether auto-push is on and what triggers it, how many segments exist and whether any are empty, how your categories map to segments, and whether the debug log has anything in it. It changes nothing. Every item that needs attention comes with the screen where you fix it.
Paste the prompt as it is, after any migration, host move, or plugin cleanup, and once a month otherwise. Two limits worth knowing. The check reads what PushEngage reports, so it can tell you subscribers are flat and cannot tell you why the opt-in prompt is not showing on your pages. And the debug log can contain URLs and request details, which is why PushEngage only lets an administrator read it. The prompt asks for a summary of the log and not a copy of it.
Outcome
A short list of what is working, what is not, and where to fix each item.