Descripción general
Esta guía explica cómo integrar notificaciones push de OneSignal en una aplicación ReactJS o NextJS. Cubre todo desde instalación hasta configuración y gestión de service workers.Requisitos
- App y plataforma de OneSignal configuradas. Consulta Configuración de Web Push para comenzar.
Instalación
Elige tu gestor de paquetes preferido:Inicialización
Importa el servicio OneSignal e inicialízalo en tu componente raíz. ReemplazaYOUR_APP_ID con tu ID de app de OneSignal que se encuentra en Claves e IDs.
Personalizar opciones init
Puedes personalizar tu inicialización con parámetrosinit adicionales.
Configuración del Service Worker
Si aún no lo has hecho, necesitarás descargar el archivo Service Worker de OneSignal para agregarlo a tu sitio. El archivoOneSignalSDKWorker.js debe ser públicamente accesible. Puedes colocarlo en tu directorio public, raíz de nivel superior o un subdirectorio. Sin embargo, si estás colocando el archivo en un subdirectorio y/o tienes otro service worker para tu sitio, entonces asegúrate de especificar la ruta. Consulta Service Worker de OneSignal para más detalles.
| Opción | Descripción |
|---|---|
serviceWorkerParam | Alcance controlado por el worker de OneSignal. Recomendación: Usa una sub-ruta personalizada (ej., "/onesignal/"). |
serviceWorkerPath | Ruta a tu archivo de service worker de OneSignal alojado (ej., "onesignal/OneSignalSDKWorker.js"). Debe ser públicamente accesible. |
Ve un ejemplo completo funcional aquí: Ejemplo React + OneSignal
Alojar el worker
- Raíz pública (predeterminado):
/OneSignalSDKWorker.js - Carpeta personalizada (recomendado): ej.,
/onesignal/OneSignalSDKWorker.jscomo se estableció en el paso anterior.
Verificar alojamiento del service worker
Visita la ruta en tu navegador para confirmar que es accesible. Si usaste raíz:Notas importantes
- Evita inicialización duplicada en desarrollo
- Al probar en un entorno de desarrollo, podrías ver el SDK de OneSignal inicializar dos veces, lo que puede causar errores de consola.
- Esto sucede debido a que
<React.StrictMode>causa que los efectos se ejecuten dos veces en desarrollo. Para resolverlo, elimina<React.StrictMode>de tu componente raíz durante el desarrollo.
Testing the OneSignal SDK integration
This guide helps you verify that your OneSignal SDK integration is working correctly by testing push notifications and subscription registration.Check web push subscriptions
Launch your site on a test device.
- Use Chrome, Firefox, Edge, or Safari while testing.
- Do not use Incognito or private browsing mode. Users cannot subscribe to push notifications in these modes.
- The prompts should appear based on your permission prompts configuration.
- Click Allow on the native prompt to subscribe to push notifications.

Check your OneSignal dashboard
Check the OneSignal dashboard:
- Go to Audience > Subscriptions.
- You should see a new entry with the status Subscribed.

You have successfully created a web push subscription.
Web push subscriptions are created when users first subscribe to push notifications on your site.
Set up test subscriptions
Test subscriptions are helpful for testing a push notification before sending a message.Add to Test Subscriptions.
In the dashboard, next to the subscription, click the Options (three dots) button and select Add to Test Subscriptions.

Name your subscription.
Name the subscription so you can easily identify your device later in the Test Subscriptions tab.
Name the segment.
Name the segment
Test Users (the name is important because it will be used later).Send test push via API
Get your App API Key and App ID.
In your OneSignal dashboard, go to Settings > Keys & IDs.
Update the provided code.
Replace
YOUR_APP_API_KEY and YOUR_APP_ID in the code below with your actual keys. This code uses the Test Users segment we created earlier.Check images and confirmed delivery.
If all setup steps were completed successfully, the test subscriptions should receive a notification.

Check for confirmed delivery.
In your dashboard, go to Delivery > Sent Messages, then click the message to view stats.You should see the confirmed stat, meaning the device received the push.
If you’re on a Professional plan or higher, scroll to Audience Activity to see subscription-level confirmation:


You have successfully sent a notification via our API to a segment.
User identification
Previously, we demonstrated how to create web push Subscriptions. Now we’ll expand to identifying Users across all their subscriptions (including push, email, and SMS) using the OneSignal SDK. We’ll cover External IDs, tags, multi-channel subscriptions, privacy, and event tracking to help you unify and engage users across platforms.Assign External ID
Use an External ID to identify users consistently across devices, email addresses, and phone numbers using your backend’s user identifier. This ensures your messaging stays unified across channels and 3rd party systems (especially important for Integrations). Set the External ID with our SDK’slogin method each time they are identified by your app.
OneSignal generates unique read-only IDs for subscriptions (Subscription ID) and users (OneSignal ID).As users download your app on different devices, subscribe to your website, and/or provide you email addresses and phone numbers outside of your app, new subscriptions will be created.Setting the External ID via our SDK is highly recommended to identify users across all their subscriptions, regardless of how they are created.
Add data tags
Tags are key-value pairs of string data you can use to store user properties (likeusername, role, or preferences) and events (like purchase_date, game_level, or user interactions). Tags power advanced Message Personalization and Segmentation allowing for more advanced use cases.
Set tags with our SDK addTag and addTags methods as events occur in your app.
In this example, the user reached level 6 identifiable by the tag called current_level set to a value of 6.



Add email and/or SMS subscriptions
Earlier we saw how our SDK creates web push subscriptions to send push. You can also reach users through emails and SMS channels by creating the corresponding subscriptions.- Use the
addEmailmethod to create email subscriptions. - Use the
addSmsmethod to create SMS subscriptions.

Best practices for multi-channel communication
- Obtain explicit consent before adding email or SMS subscriptions.
- Explain the benefits of each communication channel to users.
- Provide channel preferences so users can select which channels they prefer.
Privacy & user consent
To control when OneSignal collects user data, use the SDK’s consent gating methods:setConsentRequired(true): Prevents data collection until consent is given.setConsentGiven(true): Enables data collection once consent is granted.
Listen to push, user, and in-app events
Use SDK listeners to react to user actions and state changes. The SDK provides several event listeners for you to hook into. See our SDK reference guide for more details.Push notification events
- Click event listener: Detect when a notification is tapped.
- Foreground lifecycle listener: Control how notifications behave in foreground.
User state changes
- User state change event listener: Detect when the External ID is set.
- Permission observer: Track the user’s specific interaction with the native push permission prompt.
- Push subscription change observer: Track when the push subscription status changes.
Advanced setup & capabilities
Explore more capabilities to enhance your integration:- 🔁 Migrating to OneSignal from another service
- 🔌 Integrations
- 🛎️ Action buttons
- 🌐 Multi-language messaging
- 🛡️ Identity Verification
- 📊 Custom Outcomes
Web SDK setup & reference
Make sure you’ve enabled all key features by reviewing the Web push setup guide. For full details on available methods and configuration options, visit the Web SDK reference.Congratulations! You’ve successfully completed the Web SDK setup guide.
Need help?Chat with our Support team or email
[email protected]Please include:- Details of the issue you’re experiencing and steps to reproduce if available
- Your OneSignal App ID
- The External ID or Subscription ID if applicable
- The URL to the message you tested in the OneSignal Dashboard if applicable
- Any relevant logs or error messages
