Send web push notifications to your visitors' browsers and devices using Firebase Cloud Messaging (FCM HTTP v1). Visitors opt in from the frontend with a single toggle button; from there you can notify them manually, automatically in response to any WordPress or plugin event, or through scheduled and recurring campaigns with click and conversion analytics. There are no subscriber or send limits \u2014 nothing here is metered by volume.<\/p>\n\n
Notifications are sent with your own Firebase project<\/strong>: you connect your Google OAuth2 client and your Firebase credentials, and your site talks to FCM directly. No third-party sending service sits in between.<\/p>\n\n Scheduled and recurring campaigns run through WP-Cron<\/strong>, a server crontab<\/strong>, or an external service such as cron-job.org<\/strong> calling the plugin's cron endpoint.<\/p>\n\n No coding required for the core experience \u2014 shortcodes, visual template editors and point-and-click settings get you running. For teams who want to go further:<\/p>\n\n Subscriptions are created in the browser using the Firebase JavaScript SDK and a Web Push VAPID key; the resulting FCM device token is stored in your site database, together with whichever optional fields you chose to collect. To deliver a notification, the site authenticates to Google with your own OAuth2 client and calls the FCM HTTP v1 API.<\/p>\n\n Get NotifReach Pro<\/a><\/p>\n\n Web push cannot work without a push service: the browser vendors require one, and this plugin uses Google Firebase Cloud Messaging (FCM)<\/strong>, with the Firebase project you<\/strong> own and configure. Two further services (OpenStreetMap) are used only by the optional Subscribers Map.<\/p>\n\n This plugin connects to the following third-party services.<\/p>\n\n 1. Firebase Cloud Messaging \u2014 HTTP v1 API (Google)<\/strong>\nHosts: 2. Google OAuth 2.0 \/ Google APIs (Google)<\/strong>\nHosts: 3. Firebase JavaScript SDK (Google)<\/strong>\nHosts: 4. Nominatim \u2014 reverse geocoding (OpenStreetMap Foundation)<\/strong>\nHost: 5. OpenStreetMap map tiles (OpenStreetMap Foundation)<\/strong>\nHost: Please make sure your site's privacy policy reflects the use of Firebase\/Google (and OpenStreetMap, if you enable the Subscribers Map).<\/p>\n\nCollecting subscribers<\/h4>\n\n
\n
subscribed<\/code> \/ unsubscribed<\/code> CSS classes.<\/li>\nicfp:external-subscribe<\/code> JavaScript event.<\/li>\nSending notifications<\/h4>\n\n
\n
.json<\/code> file<\/strong> (file picker or drag & drop) from the Push Templates screen; duplicate and near-duplicate templates are detected on import.<\/li>\nCampaigns<\/h4>\n\n
\n
Measuring and managing<\/h4>\n\n
\n
Reliable scheduling<\/h4>\n\n
GDPR-ready<\/h4>\n\n
\n
Developer-friendly<\/h4>\n\n
\n
ICodePlugins\\FirebasePush\\API<\/code>) for sending, managing subscribers and reading metrics.<\/li>\nicfp\/v1<\/code> (usable with WordPress Application Passwords) to send notifications, run campaigns, read metrics and manage subscribers.<\/li>\nicfp_subscriber_recorded<\/code>, icfp_save_subscriber<\/code>, icfp_delete_subscriber<\/code>, icfp_rest_capability<\/code>, icfp_webpush_urgency<\/code>, and more.<\/li>\n.pot<\/code> is included in \/languages<\/code>; translations are provided via translate.wordpress.org).<\/li>\n<\/ul>\n\nShortcodes<\/h4>\n\n
\n
[icodeplugins_firebase_subscribe_btn]<\/code> \u2014 the subscribe\/unsubscribe toggle button. Optional attributes: label<\/code>, class<\/code>, parent<\/code> (CSS selector to move the button into), modal<\/code> (target a specific modal template by ID or slug).<\/li>\n[icodeplugins_firebase_subscribe_feedback]<\/code> \u2014 the feedback region. Optional attributes: class<\/code>, parent<\/code>, display<\/code> = inline<\/code> (default), toast<\/code>, or both<\/code>.<\/li>\n[icodeplugins_firebase_subscribe_assets]<\/code> \u2014 loads the subscription assets on a page that renders its own custom subscribe UI.<\/li>\n[icodeplugins_notification_preferences]<\/code> \u2014 the subscriber preference center.<\/li>\n<\/ul>\n\nHow it works<\/h4>\n\n
External services<\/h3>\n\n
https:\/\/fcm.googleapis.com<\/code>\nWhat it is \/ why: the push service that actually delivers notifications to your subscribers' browsers. It is required for the plugin to send anything at all.\nData sent, and when: every time a notification is sent<\/strong> (manually, by a campaign, or by a hook-triggered template), the plugin sends the message content (title, body, icon\/badge\/image URLs, click URL, action buttons) together with the recipient's FCM device token. No other subscriber data (email, phone, name, coordinates) is ever sent.\nTerms of service: https:\/\/firebase.google.com\/terms\/ \u2014 Privacy policy: https:\/\/policies.google.com\/privacy<\/p>\n\nhttps:\/\/accounts.google.com<\/code>, https:\/\/oauth2.googleapis.com<\/code>, https:\/\/www.googleapis.com<\/code>\nWhat it is \/ why: authenticates your site to your own Firebase project, so it can call the FCM API above.\nData sent, and when: when the administrator clicks \"Connect Google Account\" (browser redirect to Google), then whenever an access token must be issued or refreshed before a send, and once more if the administrator clicks \"Disconnect\" (token revocation). Only your own OAuth client ID\/secret and the authorization\/refresh tokens are exchanged. No subscriber data is involved.\nTerms of service: https:\/\/policies.google.com\/terms \u2014 Privacy policy: https:\/\/policies.google.com\/privacy<\/p>\n\nhttps:\/\/firebaseinstallations.googleapis.com<\/code>, https:\/\/fcmregistrations.googleapis.com<\/code> (contacted by the SDK; the SDK files themselves are bundled with the plugin and served from your own domain).\nWhat it is \/ why: runs in the visitor's browser and in the service worker to register the browser with FCM and obtain the device token that identifies it.\nData sent, and when: only when a visitor chooses to subscribe<\/strong> (and afterwards, if the browser rotates the token). The browser sends your Firebase project identifiers, your Web Push VAPID public key and the browser's push subscription details to Google. Nothing is sent for visitors who never subscribe.\nTerms of service: https:\/\/firebase.google.com\/terms\/ \u2014 Privacy policy: https:\/\/policies.google.com\/privacy<\/p>\n\nhttps:\/\/nominatim.openstreetmap.org<\/code>\nWhat it is \/ why: turns the coordinates a subscriber agreed to share into a readable address (country, region, postcode) for the optional Subscribers Map.\nData sent, and when: only if a visitor explicitly grants the browser's location permission when subscribing.<\/strong> The plugin then sends those coordinates (latitude\/longitude) and an identifying User-Agent, once per subscriber. If permission is denied \u2014 or the browser prompt is dismissed \u2014 nothing is collected and nothing is sent. No personal detail (email, phone, name, device token) is sent.\nTerms of service: https:\/\/osmfoundation.org\/wiki\/Terms_of_Use \u2014 Nominatim usage policy: https:\/\/operations.osmfoundation.org\/policies\/nominatim\/ \u2014 Privacy policy: https:\/\/osmfoundation.org\/wiki\/Privacy_Policy<\/p>\n\nhttps:\/\/tile.openstreetmap.org<\/code>\nWhat it is \/ why: supplies the background map images of the Subscribers Map screen. (The map library, Leaflet, is bundled with the plugin \u2014 it is not loaded from a CDN.)\nData sent, and when: only when an administrator opens the Subscribers Map<\/strong> admin screen, and only what any image request carries \u2014 the administrator's IP address and browser user-agent. No visitor or subscriber data is sent. No tile is requested on the front end.\nTile usage policy: https:\/\/operations.osmfoundation.org\/policies\/tiles\/ \u2014 Privacy policy: https:\/\/osmfoundation.org\/wiki\/Privacy_Policy<\/p>\n\nPrivacy and consent<\/h4>\n\n
\n