localhost에서 테스트하려면 프로덕션 앱과 별도의 OneSignal 앱을 사용하고 init 옵션에 allowLocalhostAsSecureOrigin: true를 추가합니다.자체 서명된 인증서로 HTTPS에서 localhost를 테스트하는 경우 --allow-insecure-localhost를 사용하여 Chrome에 잘못된 인증서를 무시하도록 지시해야 할 수 있습니다. Firefox와 Safari는 보안 인증서에 예외를 추가하는 기본 제공 메커니즘을 제공합니다.
웹 푸시 구성의 다음 페이지에서 OneSignalSDKWorker.js 서비스 워커 파일이 제공됩니다.Web SDK는 기본적으로 사이트 루트에서 이 파일을 찾습니다(예: https://yourdomain.com/OneSignalSDKWorker.js). 코드에서 파일 위치, 이름 및 범위를 변경할 수 있습니다.
Apple은 iOS 16.4+를 실행하는 iPhone 및 iPad에서 웹 푸시 알림 지원을 시작했습니다. 지원되는 브라우저에서 방문하면 웹 푸시가 그냥 “작동하는” Android 기기와 달리, Apple은 manifest.json 파일 및 사용자가 사이트를 홈 화면에 추가하는 작업 등 몇 가지 추가 요구 사항을 추가했습니다.
iOS 웹 푸시 설정
필요한 manifest.json 파일을 추가하고 사용자가 사이트를 홈 화면에 추가하도록 안내합니다.
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.
Web push native permission prompt
2
Check your OneSignal dashboard
Go to Audience > Subscriptions.
You should see a new entry with the status Subscribed.
Dashboard showing subscription with 'Subscribed' status
You have successfully created a web push subscription.
Web push subscriptions are created when users first subscribe to push notifications on your site.
If all setup steps were completed successfully, the test users should receive a notification.
Only Chrome supports images. Images will appear small in the collapsed notification view. Expand the notification to see the full image.
Expanded push notification with image on Chrome macOS
5
Check for confirmed receipt.
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.
Safari does not support confirmed receipt.
푸시 알림 메시지 보고서
푸시 알림의 전달, 클릭 및 전환 통계를 확인하세요.
You have successfully sent a notification via the API to a segment.
If notifications are not arriving, contact support@onesignal.com with the following:
The API request and response (copy-paste into a .txt file)
The previous section covered creating web push Subscriptions. This section expands to identifying Users across all their subscriptions (including push, email, and SMS) using the OneSignal SDK. It covers External IDs, tags, multi-channel subscriptions, privacy, and event tracking to help you unify and engage users across platforms.
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 the SDK’s login method each time a user is 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 the SDK is highly recommended to identify users across all their subscriptions, regardless of how they are created.
Tags are key-value pairs of string data you can use to store user properties (like username, 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 the SDK’s 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.
A user profile in OneSignal with a tag called "current_level" set to "6"
We can create a segment of users that have a level of between 5 and 10, and use that to send targeted and personalized messages:
Segment editor showing a segment targeting users with a current_level value of greater than 4 and less than 10
Screenshot showing a push notification targeting the Level 5-10 segment with a personalized message
The OneSignal SDK creates web push subscriptions automatically when users opt in. You can also reach users through email and SMS channels by creating the corresponding subscriptions.
If the email address and/or phone number already exist in the OneSignal app, the SDK will add it to the existing user, it will not create duplicates.You can view unified users via Audience > Users in the dashboard or with the View user API.
A user profile with push, email, and SMS subscriptions unified by External ID
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.
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.
