From 76c97ad803f4c0e1126ac597177970c2f8f257cf Mon Sep 17 00:00:00 2001 From: Ji Zhang Date: Mon, 30 Sep 2024 17:02:26 -0700 Subject: [PATCH 1/2] CH-5690: Update docs to vend new field --- _docs/_api/objects_filters/messaging/android_object.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_docs/_api/objects_filters/messaging/android_object.md b/_docs/_api/objects_filters/messaging/android_object.md index 4f4cfbcc1b8..c30b03809f5 100644 --- a/_docs/_api/objects_filters/messaging/android_object.md +++ b/_docs/_api/objects_filters/messaging/android_object.md @@ -24,6 +24,7 @@ You must include an Android push object in `messages` if you want users you have "message_variation_id": (optional, string) used when providing a campaign_id to specify which message variation this message should be tracked under (must be an Android Push Message), "notification_channel_id": (optional, string) the channel ID the notification will be sent with, "priority": (optional, integer) the notification priority value, + "android_priority": (optional, string) the FCM sender priority, "send_to_sync": (optional, if set to true we will throw an error if "alert" or "title" is set), "collapse_key": (optional, string) the collapse key for this message, // Specifying "default" in the sound field will play the standard notification sound @@ -47,6 +48,7 @@ You can send "Big Picture" notifications by specifying the key `appboy_image_url | Parameter | Details | | --------- | ------- | | `priority` | This parameter will accept values from `-2` to `2`, where `-2` represents "MIN" priority and `2` represents "MAX". `0` is the "DEFAULT" value.

Any values sent outside of that range will default to 0. For more information on which priority level to use, see [Android notification priority]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/customization/advanced_settings#notification-priority). | +| `android_priority` | This parameter will accept values either "normal" or "high" to specify the FCM sender priority. By default, notification messages are sent with high priority, and data messages are sent with normal priority.

For more information on how different value will impact the delivery, see [Android message priority](https://firebase.google.com/docs/cloud-messaging/android/message-priority). | | `collapse_key` | FCM can simultaneously store only up to four collapse keys per device. If you use more than four collapse keys, FCM does not make any guarantees as to which ones will be kept. Braze uses one of these by default for campaigns, so make sure to specify only up to three additional collapse keys for Android messages. | | `push_icon_image_url` | The value for the large icon parameter should be a URL that links to where your image is hosted.

Images need to be cropped to a 1:1 aspect ratio and should be at least 40x40. | | `notification_channel` | If this is not specified, Braze will attempt to send the notification payload with the [dashboard fallback][45] channel ID. For more, see [Notification channels][44] and refer to the steps for [defining notification channels][43] during integration. | From d1aefb201bfcb7d894cbd9666b9fc07bff5e4b0b Mon Sep 17 00:00:00 2001 From: Lydia Xie <87040416+lydia-xie@users.noreply.github.com> Date: Tue, 1 Oct 2024 09:51:15 -0700 Subject: [PATCH 2/2] Update _docs/_api/objects_filters/messaging/android_object.md Co-authored-by: Ian Leue --- _docs/_api/objects_filters/messaging/android_object.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_docs/_api/objects_filters/messaging/android_object.md b/_docs/_api/objects_filters/messaging/android_object.md index c30b03809f5..2f86749543f 100644 --- a/_docs/_api/objects_filters/messaging/android_object.md +++ b/_docs/_api/objects_filters/messaging/android_object.md @@ -48,7 +48,7 @@ You can send "Big Picture" notifications by specifying the key `appboy_image_url | Parameter | Details | | --------- | ------- | | `priority` | This parameter will accept values from `-2` to `2`, where `-2` represents "MIN" priority and `2` represents "MAX". `0` is the "DEFAULT" value.

Any values sent outside of that range will default to 0. For more information on which priority level to use, see [Android notification priority]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/customization/advanced_settings#notification-priority). | -| `android_priority` | This parameter will accept values either "normal" or "high" to specify the FCM sender priority. By default, notification messages are sent with high priority, and data messages are sent with normal priority.

For more information on how different value will impact the delivery, see [Android message priority](https://firebase.google.com/docs/cloud-messaging/android/message-priority). | +| `android_priority` | This parameter will accept values either "normal" or "high" to specify the FCM sender priority. By default, notification messages are sent with high priority, and data messages are sent with normal priority.

For more information on how different values impact delivery, see [Android message priority](https://firebase.google.com/docs/cloud-messaging/android/message-priority). | | `collapse_key` | FCM can simultaneously store only up to four collapse keys per device. If you use more than four collapse keys, FCM does not make any guarantees as to which ones will be kept. Braze uses one of these by default for campaigns, so make sure to specify only up to three additional collapse keys for Android messages. | | `push_icon_image_url` | The value for the large icon parameter should be a URL that links to where your image is hosted.

Images need to be cropped to a 1:1 aspect ratio and should be at least 40x40. | | `notification_channel` | If this is not specified, Braze will attempt to send the notification payload with the [dashboard fallback][45] channel ID. For more, see [Notification channels][44] and refer to the steps for [defining notification channels][43] during integration. |