> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.onesignal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Confirmed receipt

> Confirmed receipt tracks when a device receives a push sent through OneSignal. Covers paid-plan requirements, platform limitations, and troubleshooting for iOS, Android, Huawei, Web, and Live Activities.

Confirmed receipt (also known as Confirmed Delivery) tracks when the OneSignal SDK on a device **receives** a push. The SDK sends a confirmation containing the notification ID and the device's [Subscription ID](./subscriptions). You can inspect those receipts in [push message reports](./push-notification-message-reports), Audience Activity, and the `message.push.received` [Event Stream](./event-streams-data) event.

Confirmed receipt is not available on every plan or platform. See [Requirements](#requirements) and [Platform limitations](#platform-limitations). For metric definitions, see the [Metrics glossary](./analytics-metrics-glossary).

<Frame caption="Confirmed receipt flow">
  <img src="https://mintcdn.com/onesignal/_KaXe4GQkxsEfa17/images/docs/35ba167-analytics-ensure-confirmed-message-delivery_1.png?fit=max&auto=format&n=_KaXe4GQkxsEfa17&q=85&s=17ce8f50b8e92e0d368abe42865709c3" alt="Diagram of a push reaching the device and the OneSignal SDK sending a confirmation receipt back to OneSignal" width="800" height="667" data-path="images/docs/35ba167-analytics-ensure-confirmed-message-delivery_1.png" />
</Frame>

<Note>
  Confirmed receipt is different from Delivered. Platform push services (APNs, FCM, ADM, HMS) report whether they **accepted** the notification, not whether the device received it. Confirmed receipt is the device-side confirmation.
</Note>

***

## Requirements

* Available only on **paid plans**. [Compare plans](https://onesignal.com/pricing). There is no separate dashboard toggle. If the app is on a paid plan and the device has the OneSignal SDK, confirmed receipt is recorded for supported platforms.
* Complete the [Web SDK Setup](./web-sdk-setup) and/or [Mobile SDK Setup](./mobile-sdk-setup). Confirmed receipt only works if the device has the OneSignal SDK installed.
* **Not supported** for subscriptions created via API only, with no OneSignal SDK on the device.

***

## Platform limitations

Confirmed receipt does not fire in these cases, even when Delivered is greater than zero:

* **Safari** web push.
* **Huawei `message` type.** HMS displays the notification. OneSignal does not get a device receipt.
* **Silent iOS notifications.** iOS never launches the Notification Service Extension for content-available silent pushes. See [Do confirmed deliveries work with silent notifications?](./data-notifications#do-confirmed-deliveries-work-with-silent-notifications).
* **VoIP** pushes. The Notification Service Extension does not run for VoIP. See [VoIP notifications](./voip-notifications).
* **Subscriptions created via API only**, with no OneSignal SDK on the device.
* **Live Activities** on iOS SDK versions earlier than 5.2.15. See [Live Activities analytics](./live-activities-analytics).

### iOS limitations

* Requires both the **Notification Service Extension** and **App Group** to be set up correctly. See [Troubleshoot iOS](#troubleshoot-ios).
* Push notifications must include the `mutable-content` key set to `1`. OneSignal sets this automatically. Do not set `mutable_content: false`.
* APNs keeps only **one message per app** when offline. If multiple pushes are sent while the device is offline, only the latest is delivered.
* Live Activities confirmed receipt also requires iOS SDK **5.2.15 or higher**, plus the same NSE and App Group setup.

### Android limitations

* Some device manufacturers treat swiping the app away as a force quit, which stops the SDK from running and sending a receipt. See [Mobile push troubleshooting](./notifications-show-successful-but-are-not-being-shown).
* A custom Android notification service extension can suppress display or block the receipt. See [Troubleshoot Android](#troubleshoot-android).

### Huawei limitations

* Supported only for the `data` [Huawei message type](/reference/push-notification#body-huawei-msg-type).
* For the `message` type, Huawei provides receipt data only in their own dashboard.

### Web limitations

* Safari does **not** support confirmed receipt.
* Other browsers require the **v16** Web SDK. See [Troubleshoot Web](#troubleshoot-web).

***

## Troubleshooting confirmed receipt

If you are not receiving push notifications at all, see [Notifications not showing](./notifications-show-successful-but-are-not-being-shown) first.

### Troubleshoot iOS

Confirmed receipt 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

<Steps>
  <Step title="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](./ios-sdk-setup#step-2-add-a-notification-service-extension-nse).

    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](./ios-sdk-setup#step-2-add-a-notification-service-extension-nse).
  </Step>

  <Step title="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.
  </Step>

  <Step title="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 under **General > Identity**), follow the Default App Group tab. Otherwise, follow the Custom App Group tab.

    <Tabs>
      <Tab title="Default App Group - group.YOUR_MAIN_APP_BUNDLE_ID.onesignal">
        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.
      </Tab>

      <Tab title="Custom App Group">
        Use this option if your App Group identifier does not follow the `group.YOUR_MAIN_APP_BUNDLE_ID.onesignal` format.

        1. Select your **main app target > Signing & Capabilities > App Groups**.
        2. Confirm your custom App Group is listed.
        3. Select the `Info.plist` of your main app target and add the following key:

        ```xml theme={null}
        <key>OneSignal_app_groups_key</key>
        <string>group.your-custom-group-name</string>
        ```

        Replace `group.your-custom-group-name` with your actual App Group name.

        4. Select your **NSE target > Signing & Capabilities > App Groups**.
        5. Confirm the **exact same** custom App Group is listed. If missing, add it via **+ Capability > App Groups** and select the same group.
        6. Select the `Info.plist` of your NSE target and add the following key:

        ```xml theme={null}
        <key>OneSignal_app_groups_key</key>
        <string>group.your-custom-group-name</string>
        ```

        Replace `group.your-custom-group-name` with your actual App Group name.

        Your main app target and NSE target should have the same App Group identifier.
      </Tab>
    </Tabs>

    <Warning>
      If you use `.xcconfig` files for build settings, verify the App Group is not being overridden or omitted in those files.
    </Warning>
  </Step>

  <Step title="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.
  </Step>

  <Step title="Uncheck &#x22;Copy only when installing&#x22;">
    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.
  </Step>

  <Step title="Verify NSExtension Info.plist values">
    Select your **NSE target > Info** tab and expand the `NSExtension` key. Confirm it contains:

    ```xml theme={null}
    <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`.
  </Step>

  <Step title="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](/reference/push-notification), verify you are not explicitly setting `mutable_content: false`. Without `mutable-content`, iOS does not run the NSE and confirmed receipt cannot fire.
  </Step>

  <Step title="Test that the NSE is running">
    Add this line temporarily inside `didReceive` before the OneSignal call:

    ```swift theme={null}
    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](./service-extensions#debugging-the-ios-notification-service-extension).
  </Step>
</Steps>

### Troubleshoot Android

* If notifications are not displaying, see [Mobile push troubleshooting](./notifications-show-successful-but-are-not-being-shown).
* If notifications show but confirmed receipt is missing, a custom Android notification service extension may be blocking it. See [Android notification service extension](./service-extensions#android-notification-service-extension).

### Troubleshoot Web

* Safari is not supported.
* For other browsers, use the **v16** Web SDK:
  * SDK init:
    ```html theme={null}
    <script src="https://cdn.onesignal.com/sdks/web/v16/OneSignalSDK.page.js" defer></script>
    ```
  * Service Worker reference:
    ```html theme={null}
    importScripts("https://cdn.onesignal.com/sdks/web/v16/OneSignalSDK.sw.js");
    ```

***

## FAQ

### Why are my confirmed receipt 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 [Troubleshoot iOS](#troubleshoot-ios).
2. **Inactive or abandoned devices:** Devices that are offline or no longer in use do not receive pushes or send confirmed receipt events. See [How do I handle inactive devices?](#how-do-i-handle-inactive-devices).
3. **Platform limitations:** Safari, Huawei `message` type, silent iOS notifications, VoIP, API-only subscriptions, and Live Activities on iOS SDK versions earlier than 5.2.15 do not confirm. See [Platform limitations](#platform-limitations).
4. **Android force quit:** Some device manufacturers treat swiping the app away as a force quit, which stops SDK events. See [Mobile push troubleshooting](./notifications-show-successful-but-are-not-being-shown).

### How do I handle inactive devices?

Devices that are offline or abandoned do not receive push notifications or send confirmed receipt events. This is common when users replace or abandon devices.

To follow up with Subscriptions that did not confirm:

* From the message report, use [Retargeting](./retargeting) on the **Did Not Confirm Receipt** Audience Activity category. Retargeting is available for 30 days after the send.
* Create [Segments](./segmentation) based on **Last Session** (for example, inactive for 90+ days).
  * Combine with a [re-engagement Journey](./journeys-examples#re-engagement-campaign) to win them back.
  * Periodically target inactive users to prune unreachable devices.

See [When do push Subscription statuses update?](./subscriptions#when-do-push-subscription-statuses-update) for more details on how OneSignal updates subscription status.

### Why does confirmed receipt show but the notification doesn't appear?

A confirmed receipt event means the device received the push payload. In rare cases, the notification may not display.

Possible causes:

* **Missed notification:** Send yourself a test push via [Find and set Test Users](./test-users) to rule this out.
* **iOS Focus Mode:** Do Not Disturb, Sleep, or other [Focus modes](./ios-focus-modes-and-interruption-levels) delay or group notifications. You may have dismissed a grouped notification without seeing it.
* **App code suppressing display:**
  * `event.preventDefault()` in the [foreground lifecycle listener](./mobile-sdk-reference#addforegroundlifecyclelistener-push) or the [Android notification service extension](./service-extensions#android-notification-service-extension) stops the notification from displaying. The iOS Notification Service Extension does not use `preventDefault()`.
  * Calls to [`removeDeliveredNotifications(withIdentifiers:)`](https://developer.apple.com/documentation/usernotifications/unusernotificationcenter/removedeliverednotifications\(withidentifiers:\)) or [`removeAllDeliveredNotifications()`](https://developer.apple.com/documentation/usernotifications/unusernotificationcenter/removealldeliverednotifications\(\)) remove notifications after they arrive.
* **Push payload settings:**
  * Ensure `priority` is set to high. See [Push priority](./push#priority).
  * [`collapse_id`](./push#collapse-id-mobile-push) replaces older pushes with newer ones using the same ID.

***

## Related pages

<Columns cols={2}>
  <Card title="Push notification message reports" icon="chart-bar" href="./push-notification-message-reports">
    Review delivery, engagement, and confirmed receipt metrics for each push.
  </Card>

  <Card title="Analytics metrics glossary" icon="book-open" href="./analytics-metrics-glossary">
    Definitions for every delivery and engagement metric in OneSignal.
  </Card>

  <Card title="iOS SDK setup" icon="apple" href="./ios-sdk-setup">
    Add the Notification Service Extension and App Group required for iOS.
  </Card>

  <Card title="Service extensions" icon="code" href="./service-extensions">
    Customize notification behavior on iOS and Android with service extensions.
  </Card>
</Columns>

<Info>
  Need help?

  Chat with our Support team or email `support@onesignal.com`

  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](/docs/en/capturing-a-debug-log)

  We're happy to help!
</Info>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.