Merge pull request #7523 from braze-inc/BD-2968_actual

BD-2968: Help article for tracking push unsubscribes

_docs/_help/help_articles/push.md

@@ -26,5 +26,8 @@ guide_menu_list:
   - name: Resetting Push Permissions
     link: /docs/help/help_articles/push/resetting_push_permissions/
     image: /assets/img/braze_icons/check-circle.svg
+  - name: Tracking Push Unsubscribes
+    link: /docs/help/help_articles/push/push_unsubscribes/
+    image: /assets/img/braze_icons/users-01.svg
 
 ---

_docs/_help/help_articles/push/push_unsubscribes.md

@@ -0,0 +1,30 @@
+---
+nav_title: Tracking Push Unsubscribes
+article_title: Tracking Push Unsubscribes
+page_type: solution
+description: "This help article provides some tips to track push unsubscribes."
+channel: push
+---
+
+# Tracking push unsubscribes
+
+Push unsubscribes depend on updates to a user’s push status from providers like Apple or Google. These updates can be infrequent and unpredictable. As a result, push unsubscribes are not included as a metric in push campaign analytics. 
+
+However, manually tracking push unsubscribes can still provide valuable insights into user responses to your notification frequency and content relevance. Here's are two options for tracking push unsubscribes.
+
+## Option 1: Use segment filters
+
+As a workaround, you can create a segment to identify users who aren't push enabled, meaning they're not subscribed or opted-in and don't have a [foreground push token]({{site.baseurl}}/user_guide/message_building_by_channel/push/push_registration/#push-tokens). For example, to see the number of unsubscribes in your Android app, you would use the combination of the following segments: 
+
+- `Background or Foreground Push Enabled for App "TEST (Android)" is false`
+- `Has Uninstalled`
+
+![The Segment Builder section with the filter "Background or Foreground Push Enabled for App" for the TEST (Android) app is false, and the filter "Has Uninstalled" are selected to show 2,393 reachable users.]({% image_buster /assets/img/push_unsub_segment_example.png %})
+
+Note the segmentation filters will be approximate and cannot be specifically tied to a date and campaign.
+
+## Option 2: Use a custom event
+
+For a different workaround, we also recommend creating a custom event for push unsubscribes based on whether a user's push enabled status is `true` or `false` in order to track this metric.
+
+_Last updated on June 13, 2024_

_includes/campaign_analytics.md

@@ -255,6 +255,8 @@ Here is a breakdown of some key metrics you may see while reviewing your message
 | Opens | Instances including both _Direct Opens_ and _Influenced Opens_ in which the Braze SDK has determined, using a proprietary algorithm, that a push notification has caused a user to open the app. |
 {: .reset-td-br-1 .reset-td-br-2}
 
+Push unsubscribes are not included as a metric in campaign analytics. Refer to [Tracking push unsubscribes]({{site.baseurl}}/help/help_articles/push/push_unsubscribes) for steps on how to manually track this metric.
+
 {% alert tip %}
 Even though _Direct Opens_ and _Influenced Opens_ include the word "opens", they're actually different metrics. _Direct Opens_ refers to the direct opening of a push notification, as stated in the table above. _Influenced Opens_ refers to the opening of an app, without opening a push notification within a specific time frame after receiving it. So, _Influenced Opens_ refers to the app opens, not push notification opens.
 {% endalert %}