OCM Pulse

OCM Pulse lets editorial teams send web push notifications directly from the WordPress post editor, without leaving the dashboard or opening the OCM Pulse interface.

Works with both the Gutenberg block editor (sidebar panel) and the Classic Editor (metabox). The Send button is fully decoupled from post save — publish when you’re ready, notify when you choose.

Features

• Send push notifications from the post editor with one click

• Gutenberg sidebar panel and Classic Editor metabox

• Pre-fills notification title, body, and URL from the current post

• Auto-populates the featured image as the notification image

• Category and segment targeting

• Schedule notifications for a future date and time

• AI-powered copy generation (requires OCM Pulse AI feature on your server)

• RSS feed trigger warning — alerts you when sending might cause duplicate notifications

• API token stored server-side and never exposed to the browser

Requirements

• An active OCM Pulse account

• WordPress 6.7 or later, PHP 7.4 or later

External services

This plugin connects to the OCM Pulse push notification service. An active OCM Pulse account and a connected app are required for the plugin to function.

com/terms-and-conditions

com/privacy-policy

OCM Pulse API

This is used to send and schedule push notifications, and to populate the editor UI.

• What is sent, and when:

• Connecting: when you click “Connect to OCM Pulse” in Settings → OCM Pulse, your browser is redirected to your configured OCM Pulse server to authorise the connection (OAuth 2.0). No post content is sent at this step.

• Sending: when you click “Send Push Notification” or “Schedule” in the post editor, the notification’s title, body, URL, optional image URL, category, segment, and schedule time are sent to your OCM Pulse server to create the delivery.

• AI copy generation: when you click “Generate with AI”, the post’s title and content (HTML stripped) are sent to your OCM Pulse server to generate suggested notification copy. This only happens when you explicitly click the button.

• Editor setup: the plugin fetches your app’s categories, segments, and RSS-trigger status from your OCM Pulse server each time the editor loads, to populate dropdowns and warnings.

• Service URL: the server address you enter under Settings → OCM Pulse (“OCM Pulse API URL”). This is configured per installation, not a fixed OCM Pulse endpoint.

OCM Pulse SDK (enabled once you connect an app)

This is a client-side script, served from the SDK URL returned by your configured OCM Pulse server, that registers a browser service worker and prompts site visitors to subscribe to push notifications. Production installations load it directly from the OCM Pulse CDN.

• It is controlled by “Inject SDK script and service worker into this site” under Settings → OCM Pulse, which is on by default. Nothing is loaded until you connect the plugin to an OCM Pulse app; from then on it loads on every frontend page, for every visitor, until you turn the option off.

• Enabling it also writes an ocm-push-worker.js file to your site root — a one-line stub that loads the service worker from your OCM Pulse server. It is removed again when you turn the option off, disconnect, or deactivate the plugin.

• The SDK performs its own visitor consent check before prompting for a subscription, unless you separately enable “Skip consent check” (also disabled by default). Enabling that option is your decision as the site operator, and you are responsible for complying with applicable privacy laws (e.g. GDPR/ePrivacy) if you do.