Skip to main content

​
Overview

Confirmed Delivery tracks when a device actually receives a push notification sent through OneSignal. When the OneSignal SDK on the device receives a push, it sends a confirmation event back to OneSignal containing the notification ID and the device’s Subscription ID. This lets you see exactly which subscriptions received which notifications. In your OneSignal Dashboard, Confirmed Delivery appears in the Message Report as Confirmed (or Received). For all delivery and engagement metrics, see the Metrics Glossary.
Confirmed Deliveries Flow
Confirmed Delivery is different from “Delivered.” Platform push services (APNs, FCM, ADM, HMS) report whether a notification was accepted by the service — not whether the device actually received it. Confirmed Delivery is the device-side confirmation.

​
Requirements

  • Available only on paid plans. Compare plans.
  • Complete the Web SDK Setup and/or Mobile SDK Setup.
    • Confirmed Delivery only works if the device has the OneSignal SDK installed.
    • Not supported for subscriptions created via API only.

​
Platform-specific limitations

iOS
  • Requires both the Notification Service Extension and App Group setup.
  • APNs keeps only one message per app when offline. If multiple pushes are sent while offline, only the latest is delivered.
Huawei
  • Supported only for the data Huawei message type.
  • For the message type, Huawei provides receipt data only in their own dashboard.
Web
  • Safari does not support Confirmed Delivery.

​
Troubleshooting Confirmed Delivery

If you are not receiving push notifications at all, see Notifications not showing first.

​
iOS

Confirmed Delivery on iOS requires two things working together:
  1. A Notification Service Extension (NSE) that runs OneSignal code when a push arrives
  2. An App Group shared between your main app target and the NSE target so they can exchange data
If either is missing or misconfigured, the device receives the push but never reports it back to OneSignal. Verify your iOS setup
1

Confirm the NSE target exists and has the correct code

In Xcode, check that you have a OneSignalNotificationServiceExtension target listed under your project targets. If it does not exist, follow Step 2 of the iOS SDK Setup.Open the NSE’s NotificationService.swift (or .m) file. It must call OneSignalExtension.didReceiveNotificationExtensionRequest inside didReceive(_:withContentHandler:). If the file still contains Apple’s default template code, replace it with the OneSignal NSE code.
2

Confirm the NSE has the OneSignalExtension package

Select your NSE target > General > Frameworks and Libraries (or Build Phases > Link Binary With Libraries). Verify that OneSignalExtension is listed. The main app target uses OneSignalFramework, but the NSE target must use OneSignalExtension — these are different packages.
3

Verify the App Group is configured correctly on both targets

The OneSignal SDK uses an App Group to share data between your main app and the NSE. There are two ways to configure this — pick the one that matches your setup.
  1. Select your main app target > Signing & Capabilities > App Groups.
  2. Confirm the App Group.
If your App Group is group.YOUR_MAIN_APP_BUNDLE_ID.onesignal — where YOUR_MAIN_APP_BUNDLE_ID is your main app target’s Bundle Identifier (found under General > Identity), then follow the Default App Group tab. Otherwise, follow the Custom App Group tab.
  1. Select your NSE target > Signing & Capabilities > App Groups.
  2. Confirm the exact same App Group is listed. If missing, add it via + Capability > App Groups and select the same group.
A common mistake is using the NSE’s bundle identifier instead of the main app’s:
  • Correct: group.YOUR_MAIN_APP_BUNDLE_ID.onesignal
  • Wrong: group.YOUR_MAIN_APP_BUNDLE_ID.OneSignalNotificationServiceExtension.onesignal
Your main app target and NSE target should have the same App Group identifier.
If you use .xcconfig files for build settings, verify the App Group is not being overridden or omitted in those files.
4

Confirm minimum deployment targets match

Select your NSE target > General > Minimum Deployments. This value must match your main app target’s minimum deployment. A mismatch can prevent the NSE from running on certain OS versions.
5

Uncheck "Copy only when installing"

Select your main app target > Build Phases > Embed App Extensions. Make sure “Copy only when installing” is unchecked. If checked, the NSE is not embedded during development builds, so it never runs when testing.
6

Verify NSExtension Info.plist values

Select your NSE target > Info tab and expand the NSExtension key. Confirm it contains:
<key>NSExtensionPointIdentifier</key>
<string>com.apple.usernotifications.service</string>
<key>NSExtensionPrincipalClass</key>
<string>$(PRODUCT_MODULE_NAME).NotificationService</string>
If your NSE is written in Objective-C, use NotificationService instead of $(PRODUCT_MODULE_NAME).NotificationService.
7

Verify mutable-content is set

OneSignal automatically sets mutable-content: 1 in the push payload, which tells iOS to invoke the NSE. If you send pushes via the REST API, verify you are not explicitly setting mutable_content: false. Without mutable-content, iOS does not run the NSE and Confirmed Delivery cannot fire.
8

Test that the NSE is running

Add this line temporarily inside didReceive before the OneSignal call:
bestAttemptContent.body = "[Modified] " + bestAttemptContent.body
Send yourself a test push. If the notification body starts with [Modified], the NSE is running correctly. If it does not, revisit the steps above — the NSE is not being invoked. Remove this line after testing.For advanced NSE debugging with Xcode Console logs, see Debugging the iOS Notification Service Extension.

​
Android

​
Web

  • Safari is not supported.
  • For other browsers, ensure migration to v16 SDK is complete:
    • Correct SDK init: 
      <script src="https://cdn.onesignal.com/sdks/web/v16/OneSignalSDK.page.js" defer></script>
    • Correct Service Worker reference: 
      importScripts("https://cdn.onesignal.com/sdks/web/v16/OneSignalSDK.sw.js");

​
FAQ

​
Why are my Confirmed Delivery numbers low or missing?

The most common causes are setup issues (especially on iOS), inactive devices, and platform limitations.
  1. iOS misconfiguration: The Notification Service Extension or App Group is missing or incorrect. See Troubleshooting Confirmed Delivery on iOS above.
  2. Inactive or abandoned devices: Devices that are offline or no longer in use do not receive pushes or send Confirmed Delivery events. See How do I handle inactive devices? below.
  3. Platform limitations: Huawei message type and Safari do not support Confirmed Delivery.
  4. Android force quit: Some device manufacturers treat swiping the app away as a force quit, which stops SDK events. See Mobile push not shown guide.

​
How do I handle inactive devices?

Devices that are offline or abandoned do not receive push notifications or send Confirmed Delivery events. This is common when users replace or abandon devices. To re-engage inactive users:
  • Use Audience Activity to resend to users who did not confirm delivery.
  • Create Segments based on Last Session (e.g., inactive for 90+ days).
    • Combine with a Re-engagement Journey to win them back.
    • Periodically target inactive users to prune unreachable devices.
See When do push Subscription statuses update? for more details on how OneSignal updates subscription status.

​
Why does it show Confirmed but not appear on my device?

A Confirmed Delivery event means the device received the push payload. In rare cases, the notification may not display. Possible causes:
Need help?Chat with our Support team or email support@onesignal.comPlease 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
We’re happy to help!