內容簡介
OCM Pulse 讓編輯團隊能夠直接從 WordPress 文章編輯器發送網頁推播通知，無需離開控制台或打開 OCM Pulse 介面，提升了工作效率。
【主要功能】
• 一鍵從文章編輯器發送推播通知
• 支援 Gutenberg 側邊欄與 Classic Editor 元件
• 自動填充通知標題、內容與 URL
• 自動選取特色圖片作為通知圖片
• 目標分類與區段設定
• 可預約未來的通知發送
外掛標籤
開發者團隊
原文外掛簡介
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.6 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.
Terms of Use: https://pulse.orangeclickmedia.com/terms-and-conditions
Privacy Policy: https://pulse.orangeclickmedia.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 (optional, disabled by default)
This is a client-side script, served from your configured OCM Pulse server, that registers a browser service worker and prompts site visitors to subscribe to push notifications.
It only loads when you enable “Inject SDK script and service worker into this site” under Settings → OCM Pulse. When enabled, it loads on every frontend page, for every visitor.
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.
