From 8a39394e370151e878cea84a8f09e59ea6809113 Mon Sep 17 00:00:00 2001 From: Lydia Xie Date: Fri, 30 Aug 2024 10:05:26 -0700 Subject: [PATCH 1/2] BD-3407 --- .../message_building_by_channel/push/best_practices.md | 4 ++++ .../push/ios/rich_notifications.md | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/_docs/_user_guide/message_building_by_channel/push/best_practices.md b/_docs/_user_guide/message_building_by_channel/push/best_practices.md index a24c453d534..2b1c11c6c65 100644 --- a/_docs/_user_guide/message_building_by_channel/push/best_practices.md +++ b/_docs/_user_guide/message_building_by_channel/push/best_practices.md @@ -14,6 +14,10 @@ Push notifications are powerful tools for engaging with your app's users, but th Your push messages must fall within the guidelines of the Apple App Store and Google's Play Store policies, specifically regarding using push messages as advertisements, spam, promotions, and more. Learn more about [Mobile push regulations]({{site.baseurl}}/user_guide/message_building_by_channel/push/about/#mobile-push-regulations-for-apps). {% endalert %} +## Compose your push message + +As a general rule of thumb, Braze recommends keeping each line of text for both the optional title and message body to approximately 30-40 characters in a mobile push notification. Note that the character counter in the composer doesn't account for Liquid characters. This means the final character count of a message depends on how Liquid renders for each user. When in doubt, keep it short and sweet. + ## Optimize targeting ### Collect relevant user data diff --git a/_docs/_user_guide/message_building_by_channel/push/ios/rich_notifications.md b/_docs/_user_guide/message_building_by_channel/push/ios/rich_notifications.md index f287158a586..1e797f7cb96 100644 --- a/_docs/_user_guide/message_building_by_channel/push/ios/rich_notifications.md +++ b/_docs/_user_guide/message_building_by_channel/push/ios/rich_notifications.md @@ -34,7 +34,7 @@ As of January 2020, iOS rich push notifications can handle images 1038x1038 that While we can't provide a hard and fast rule for the precise number of characters to include in a push, we [provide some guidelines]({{site.baseurl}}/user_guide/message_building_by_channel/push/best_practices/message_format/) to consider while designing iOS messages. There may be some variance depending on the presence of an image, the notification state and display setting of the user's device, and the size of the device. When in doubt, keep it short and sweet. -> As a general rule of thumb, Braze recommends keeping each line of text for both the optional title and message body to approximately 30-40 characters in a mobile push notification. +As a general rule of thumb, Braze recommends keeping each line of text for both the optional title and message body to approximately 30-40 characters in a mobile push notification. #### Notification states From f07689f5e5cef0819d67912bcf8043d35ef95096 Mon Sep 17 00:00:00 2001 From: Lydia Xie Date: Fri, 30 Aug 2024 10:14:16 -0700 Subject: [PATCH 2/2] remove general rule of thumb --- .../message_building_by_channel/push/best_practices.md | 2 +- .../message_building_by_channel/push/ios/rich_notifications.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/_docs/_user_guide/message_building_by_channel/push/best_practices.md b/_docs/_user_guide/message_building_by_channel/push/best_practices.md index 2b1c11c6c65..703c43cf836 100644 --- a/_docs/_user_guide/message_building_by_channel/push/best_practices.md +++ b/_docs/_user_guide/message_building_by_channel/push/best_practices.md @@ -16,7 +16,7 @@ Your push messages must fall within the guidelines of the Apple App Store and Go ## Compose your push message -As a general rule of thumb, Braze recommends keeping each line of text for both the optional title and message body to approximately 30-40 characters in a mobile push notification. Note that the character counter in the composer doesn't account for Liquid characters. This means the final character count of a message depends on how Liquid renders for each user. When in doubt, keep it short and sweet. +As a best practice, Braze recommends keeping each line of text for both the optional title and message body to approximately 30-40 characters in a mobile push notification. Note that the character counter in the composer doesn't account for Liquid characters. This means the final character count of a message depends on how Liquid renders for each user. When in doubt, keep it short and sweet. ## Optimize targeting diff --git a/_docs/_user_guide/message_building_by_channel/push/ios/rich_notifications.md b/_docs/_user_guide/message_building_by_channel/push/ios/rich_notifications.md index 1e797f7cb96..9a2325b848d 100644 --- a/_docs/_user_guide/message_building_by_channel/push/ios/rich_notifications.md +++ b/_docs/_user_guide/message_building_by_channel/push/ios/rich_notifications.md @@ -34,7 +34,7 @@ As of January 2020, iOS rich push notifications can handle images 1038x1038 that While we can't provide a hard and fast rule for the precise number of characters to include in a push, we [provide some guidelines]({{site.baseurl}}/user_guide/message_building_by_channel/push/best_practices/message_format/) to consider while designing iOS messages. There may be some variance depending on the presence of an image, the notification state and display setting of the user's device, and the size of the device. When in doubt, keep it short and sweet. -As a general rule of thumb, Braze recommends keeping each line of text for both the optional title and message body to approximately 30-40 characters in a mobile push notification. +As a best practice, Braze recommends keeping each line of text for both the optional title and message body to approximately 30-40 characters in a mobile push notification. #### Notification states