OneSignal – Web Push Notifications


OneSignal is an easy way to increase user engagement. Use OneSignal to send visitors targeted push notifications so they keep coming back. It takes just a few minutes to install.

After setup, your visitors opt-in to receive push notifications when you publish a new post. Visitors receive these notifications even after they’ve left your website, thus driving re-engagement.

You can configure notification delivery at preset intervals, create user segments, and customize the opt-in process for visitors.

OneSignal is free for up to 30,000 subscribers; there are no limits on the number of push notifications you can send. Contact if you have any questions. We’d love to hear from you.


OneSignal is trusted by over 650,000 developers and marketing strategists. We power push notifications for everyone from early stage startups to Fortune 500 Companies, sending 4 billion notifications per day. It is the most popular push notification plugin on WordPress with 90,000+ installations.


  • Supports Chrome (Desktop & Android), Safari (Mac OS X), Microsoft Edge (Desktop & Android), Opera (Desktop & Android) and Firefox (Desktop & Android) on both HTTP and HTTPS sites.

  • Notificaciones automáticas– Envía notificaciones a los seguidores cada vez que publiques una nueva publicación . O configure un recordatorio que se envíe automáticamente si no lo han visitado durante unos días.

  • Segmentación de objetivos– Envía notificaciones a visitantes específicos en función del idioma , la cantidad de veces que han visitado tu blog o incluso configura tus propios atributos de usuario a los que puedes orientar tus anuncios.

  • Personalización Opt-In– Elija cuándo y cómo solicitar a sus visitantes que acepten las notificaciones del navegador . Personaliza el aviso que ven primero.

  • Análisis en tiempo real – Ve sus notificaciones entregadas en tiempo real, y míralas convertirse en visitantes.

  • Prueba A / B– ¡Prueba diferentes mensajes a un pequeño conjunto de tus visitantes para averiguar qué mensajes son más efectivos y luego enviar el mensaje más eficaz para el resto de los visitantes!

  • Notificaciones programadas – Programar notificaciones para entregar en el futuro, según la zona horaria de un usuario, o incluso en función de la misma hora del día en que visitó por última vez su sitio web.


  • Notificaciones en Chrome, Safari y Firefox.
  • Our detailed setup instructions to get you started.
  • Our configuration main configuration setup page.
  • Our OneSignal dashboard users page, where you can see your subscribed users.
  • Our OneSignal dashboard sent notifications page, where you can see the status of your sent notifications.
  • Our OneSignal dashboard notification creation page, with show some of the browser settings available.
  • Our OneSignal WordPress welcome notification options.
  • Our OneSignal WordPress setting for prompting options.


  1. Instala OneSignal desde el directorio de plugins de o subiendo la carpeta del plugin WP-OneSignal a tu directorio wp-content/plugins
  2. Activa plugin OneSignal desde tu escritorio de WordPress .
  3. Sigue las instrucciones en la página de Configuración .

Preguntas frecuentes

HTTP Site Setup Video
HTTPS Site Setup Video

HTTPS Setup Video:


5 stars

Great service which comes with a great support = 5 stars.

Great product and customer support

I love this plug in! I can see subscribed users and they very easily obtain push notifications when I update my posts. Better than filling up their inbox with email. The technical support is also amazing. Very friendly and fast.

Great product

Support is very helpful and the plugin is fantastic as it is easy to use and retain visitors
Leer todas las 109 reseñas

Colaboradores y desarrolladores

“OneSignal – Web Push Notifications” es un software de código abierto. Las siguientes personas han colaborado con este plugin.


Traduce “OneSignal – Web Push Notifications” a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN , o suscríbete al log de desarrollo por RSS .

Registro de cambios

= 1.17.5 [

  • Updated notice message to reflect changes to time limiter, removed extra newline from description


  • Changed time limiter to 2 minutes from 1 hour to ease restrictions on sending update notifications


  • Added debug to logging to responses with non 200-level status codes
  • Made notices unique
  • Bug fixes


  • Lengthened timeout, debugging tool, status-code bug fixes


  • Support for more detailed error messages


  • Bug fixes, edge-case handling, refactoring


  • Code to catch error where core/editor is not defined for old versions of the editor


  • WP5 notice support and error handling for errors arising from v 1.16.14


  • Replaced cURL calls with HTTP API


  • Added timestamp to allow re-pushing notifications upon editing an existing post after 1 hr


  • Reverted unchecking send notifcation on post publish


  • On WordPress 5.0 «Send notification on post publish» now unchecks after posting.
  • Added extra checks to ensure double notifications are not sent for the same post.


Updated plugin description and added FAQ section.


Reverting the UI changes for HTTP switch.


This release makes HTTP switch match the dashboard (renamed to «My site is not fully HTTPS») and removes deprecation warnings for php 7.2.


This release updates the service worker to use a 50% smaller service worker-only file.


This release the issue where even after saving the form, the error about not completing the required fields would appear because the settings for the new page view were loaded before the previous page’s settings were saved. Also a broken doc link was fixed.


Esta versión cambia el límite de velocidad de envío de notificaciones de como máximo uno cada 10 segundos a como máximo uno cada 1 segundo.


This release removes begining and ending whitespaces from textboxes when saving. This can fix common errors like pasting the App ID, REST API Key, or subdomain (also called label) with an ending whitespace which normally causes errors.


Esta versión simplifica en gran medida la guía de configuración para seguir nuestra documentación en lugar de una guía en línea .

  • Actualizados los archivos de ayuda de AMP para que se centralicen en lugar de JavaScript en línea codificados


Esta versión actualiza los archivos amp-helper-frame.html y amp-permission-dialog.html utilizados para amp-web-push debido a cambios de permisos en Chrome 62.

  • Update readme to show tested up to 4.9 Release Candidate 2


This release adds an option to disable the «Successfully sent a notification to X recipients» message, and also includes files for AMP web push (to be used with another AMP plugin) in case you decide to add AMP web push for your site.

  • Añadida la opción «Mostrar mensaje de estado después de enviar notificaciones»
  • Incluye amp-helper-frame.html y amp-permission-dialog.html para su uso con AMP web push


Esta versión incluye un mensaje de ayuda con la cuenta de recepciones de notificaciones actualizada tras cada una. Tras publicar un post, por ejemplo, la caja de información puede mostrar «Correctamente enviado a 100 receptores.».

  • Lowered priority of wp_head hook from 5 to 10.


Esta versión corrige un error con la versión 1.15.0 que verifica el campo «Descartar notificaciones automáticamente después de ~ 20 segundos». El campo incorrecto estaba siendo revisado y provocó que apareciera una advertencia .


Esta versión añade un ajuste para ocultar notificaciones en plataformas Mac OS X.

  • «Dismiss notifications automatically after ~20 seconds» has been replaced with «Hide notifications after a few seconds» with a couple of
    choices «Yes», «No», «Yes on Mac OS X. No on other platforms». Previously, notifications would be persisted on all platforms except Mac OS X.


This release restores 4 missing image files in the Setup guide included in our WordPress plugin (Chrome & Firefox Push step 7, OneSignal Keys step 2).

No se hicieron cambios de código en este parche.


  • Uso de iconos de mayor tamaño para la imagen destacada

    Notification small icons and large images previously used the uploaded image closest to size 80×80. For a large uploaded image with no
    resized variants, there would be no issues. But for uploaded images resized to different sizes by WordPress, this caused the smallest image
    size to be selected and look blurry. Notification small icons now use the closest available image to 192×192 for a sharper image, whereas
    large images use the closest available image to 640×480.


  • Update Setup tab’s images and text

    Clarify some steps that are typically confusing to new users setting up the plugin, like how to get the value in the Subdomain textbox.


  • Remove .htaccess file

    Apache httpd.conf configurations that don’t allow custom .htaccess options will error out with a 500 if we place this file there.


  • Update semantic versioning; update minor version for new backwards-compatible functionality
  • Hide Google Project Number from configuration (using one is unnecessary since we provide a default Project Number)
  • Add option «Use the post’s featured image for Chrome’s large notification image» (see:
  • Lower notification rate limit from 55 seconds to 10 seconds. Countdown shows time remaining (e.g. «Please try again in 6 seconds»)


  • Check in missing image to SVN: admin Configuration page HTTP Permission Request modal
  • Remove obsolete admin option «Show the OneSignal logo on the prompt»
  • Remove unused Bootstrap CSS/JS assets
  • Fix Prompt options custom language text not outputted for HTTPS sites (


  • Config page changes


  • Add rate limiting to prevent notifications from being sent too quickly; one notification can be sent every 55 seconds
  • Remove Preview Popup button; users can still follow the screenshot in the section header to match their customized
    values with the window their users will see
  • Add Configuration page UI option to show the slidedown permission message on HTTPS sites before the browser’s native
    permission request
  • Implement the HTTP permission request as the default for new sites (only for those who turn on Automatic prompting)
  • Clarify «Use my own SDK initialization script» –> renamed as «Disable OneSignal initialization»
  • Add a hidden page comment if users disable OneSignal initialization for easier debugging
  • Our plugin is in but not Hopefully resubmitting the
    plugin fixes it


  • Update style that was being overridden on some sites


  • Fix undefined index gcm_sender_id error
  • Do not resend notifications for posts restored from trash


  • Assign the script initialization variable OneSignal globally so initialization still works if plugins modify our
    inline script to be run from an external script file


  • A user reported the ‘prompt_auto_accept_title’ variable being undefined and causing issues with her site. This issue
    is now fixed.


  • Add proper WordPress action/filter hook for OneSignal init


  • The web SDK initialization of our plugin can now be fully customized
  • Removed the Intercom live chat support plugin from our plugin. Users can still email
  • Click Allow, Site Title, and the auto accept HTTP prompt title can now be customized
  • Spaces are removed when users save their Subdomain textbox value
  • The meta box checkbox «Send post on notification publish» now correctly does not send a notification if unchecked.
    Previously, there was a logic bug where users could check the box, initially save the post without publishing, and
    have a notification sent out when later publishing.
  • The default plugin tab is now «Setup» if the user is setting up for the first time, and if their App ID or REST API
    Key is blank (both values are required)
  • Correctly call has_post_thumbnail for WordPress versions below 4.4
  • Check for admin capabilities is done correctly so as to be compatible for users in stateless mode (DISALLOW_FILE_MODS)
  • Apostrophes and other HTML encoded entities are correctly decoded when using the HTTP prompt
  • Minor: Remove phantom tooltip linking to GCM page
  • Minor: site.css now has a source map


  • Fix broken documentation link


  • Add option to show GCM Project Number field


  • Bug fix for manifest.json GCM Sender ID


  • Remove Google project from the setup flow


  • Allow HTTP users to select «Automatically prompt…» to use the HTTP prompt
  • Improve setup documentation screens, add extra troubleshooting notices


  • Add admin UI to change notification title
  • Add admin UI to send to Android and iOS platforms (if available)


  • Add admin UI and filter for custom post types
  • Add filters for overriding post processing behavior
  • Add filter for overriding meta box send notification checkbox behavior
  • Add admin UI for adding UTM tracking code parameters (notification URL parameters)
  • Add admin UI for hiding notify button after subscription
  • Fix Preview Popup not displaying correctly if an ‘’ Subdomain textbox value is used
  • Display visible error message if notification fails to send
  • Updated Google Project Setup guide
  • Fix poorly named global function that is conflicting with another template’s global function


  • Push notifications should now be sent out for posts created in the default WordPress editor if scheduled, being edited, or awaiting publication


  • Change setup URL –>
  • Modify onesignal_send_notification filter hook to also allow notifications to not be sent


  • Enable PHP error logging by file


  • Fix on_save_post function not being declared statically
  • Fix other PHP warning about property not existing


  • Forgot to add onesignal-utils.php


  • Automatic sending functionality has been rewritten


  • Fix scheduled notifications to be more reliable by associating data with the post’s metadata and rewriting the send notification logic
  • Modified the WDS Log plugin to log OneSignal-related things; WDS Log plugin must be installed to view
  • Add a filter hook for to modify the data we post to create notifications API to allow customizing of notifications
  • Fixed Configuration page saving so that a user can choose to only use the Safari platform and skip the Chrome subdomain


  • Make WordPress plugin compatible with PHP v5.2.4
    • Using workaround for constant ENT_HTML401 not defined in < PHP 5.4 used in decode_html_entity


  • Relax subdomain validation now that the web SDK auto-corrects almost-valid values


  • Add Henkler’s contributions to WordPress plugin:
    • Allow notification dismissal by Chrome’s persistNotification flag
    • Allow featured image to be used as notification icon


  • Restore ‘Automatically send notifications using 3rd party post editors’


  • Clarified subdomain instructions to not include «»
  • Improved support for HTML encoded entities


  • Add bell color customization
  • Add bell offset position customization
  • Add initial support for custom post types


  • Including missing CSS file


  • Fix settings for initial user showing an error for WordPress function get_option()


  • Organized and clarified plugin settings
  • Add screenshots to plugin description


  • Fixed error reporting being enabled in version 1.6.0
  • Rebranded bell widget to notify button
  • Minor fixes to functions that would error but are silent because error reporting is usually disabled
  • Update default settings


  • Added interactive bell widget for site visitors to manage push notification subscription
  • Improved toggle button text readability


  • Added option to send a welcome notification to new site visitors
  • Removed {modalPrompt: true} as the default prompt method for HTTPS sites; the native browser prompt is once again the default
  • Added option to use the modal prompt instead of the native prompt method
  • Popup settings now display for both HTTPS modal users and HTTP prompt users


  • Added option to disable automatically prompting new visitors to register for push notifications


  • Fixed settings save when subdomain goes from set to empty. Admin JS now uses jQuery instead of $.


  • Fixed HTTP popup prompt dialog to not display empty values if configuration options are unset


  • Added popup settings to localize prompt text. Updated fonts to render better on Firefox and Safari.


  • Graphical redesign of the plugin. Much better instructions.


  • OneSignal library initialization now occurs regardless of whether the window.onload event has yet to be fired or has already fired.


  • Added Safari Mac OSX support.


  • UTF-8 characters in post’s titles now display correctly in notifications.
  • Se corrigió el error donde manifest.json no se creaba para sitios HTTPS debido a permisos.
  • Ahora se adapta para usar HTTPS para los ficheros de los service workers si la configuración de WordPress no es correcta.


  • Corregido error en algunos plugins que crean mensajes no fueron enviando una notificación automáticamente cuando OneSignal ‘Todos los mensajes creados a partir de otros plugins’ se habilitan .
  • Fixed errors that display when ‘WP_DEBUG’ is set to true


  • Added Automatic Push Notifications option for ‘All Posts created from other plugins’ on the «Notification Settings» tab.
    • Note, this is on by default for new installs but off of existing ones so behavior does not automatically change when you update.
  • Fixed errors with missing images.


  • Send notification on post is now available to any WordPress user with permissions to create or edit posts.


  • Notifications sent with the Automatic Push Notifications on Post feature directly link to the post instead of the homepage when opening the notification.
  • Updated GCM instructions and added HTTP subscribe link/widget instructions on the Getting Started tab.


  • Fixed compatibility issue with PHP versions older than 5.3.0
  • For HTTPS sites a modal dialog is shown before the native Chrome Notification permission prompt.


  • Fixed bug with OneSignal not getting initialized in some cases.
  • Now omits extra unneeded manifest link from the head tag when using HTTP.
  • Clicks handler added to elements with the class OneSignal-prompt are now setup in a more compatible way.


  • Modified description


  • Initial release of the plugin