Leftover deploy - February 6, 2025

_docs/_api/endpoints/messaging/send_messages/post_send_transactional_message.md

@@ -126,116 +126,6 @@ Most endpoints at Braze have a rate limit implementation that will return a 429
 
 ## Transactional HTTP event postback
 
-All transactional emails are complemented with event status postbacks sent as an HTTP request back to your specified URL. This will allow you to evaluate the message status in real-time and take action to reach the user on another channel if the message goes undelivered, or fallback to an internal system if Braze is experiencing latency.
-
-In order to associate the incoming events to a particular instance of send, you can choose to either capture and store the Braze `dispatch_id` returned in the [API response](#example-response), or pass your own identifier to the `external_send_id` field. An example of a value you may choose to pass to that field may be an order ID, where after completing order 1234, an order confirmation message is triggered to the user through Braze, and `external_send_id : 1234` is included in the request. All following event postbacks such as `Sent` and `Delivered` will include `external_send_id : 1234` in the payload allowing you to confirm that user successfully received their order confirmation email.
-
-To get started using the Transactional HTTP Event Postback, navigate to **Settings** > **Email Preferences** in your Braze dashboard and locate the section **Transactional Event Status Postback**. Input your desired URL to receive postbacks.
-
-{% alert note %}
-If you are using the [older navigation]({{site.baseurl}}/navigation), this page is located at **Manage Settings** > **Email Settings**.
-{% endalert %}
-
-![]({% image_buster /assets/img/transactional_webhook_url.png %})
-
-### Postback body
-
-```json
-{
-  "dispatch_id": (string, a randomly-generated unique ID of the instance of this send),
-  "status": (string, Current status of message from the following message status table,
-  "metadata" : (object, additional information relating to the execution of an event)
-   {
-     "external_send_id" : (string, If provided at the time of the request, Braze will pass your internal identifier for this send for all postbacks),
-     "campaign_api_id" : (string, API identifier of this transactional campaign),
-     "received_at": (ISO 8601 DateTime string, Timestamp of when the request was received by Braze, only included for events with "sent" status),
-     "enqueued_at": (ISO 8601 DateTime string, Timestamp of when the request was enqueued by Braze, only included for events with "sent" status),
-     "executed_at": (ISO 8601 DateTime string, Timestamp of when the request was processed by Braze, only included for events with "sent" status),
-     "sent_at": (ISO 8601 DateTime string, Timestamp of when the request was sent to the ESP by Braze, only included for events with "sent" status),
-     "processed_at" : (ISO 8601 DateTime string, Timestamp the event was processed by the ESP, only included for events with "processed" status),
-     "delivered_at" : (ISO 8601 DateTime string, Timestamp the event was delivered to the user's inbox provider, only included for events with "processed" status),
-     "bounced_at" : (ISO 8601 DateTime string, Timestamp the event was bounced by the user's inbox provider, only included for events with "bounced" status),
-     "aborted_at" : (ISO 8601 DateTime string, Timestamp the event was Aborted by Braze, only included for events with "aborted" status),
-     "reason" : (string, The reason Braze or the Inbox provider was unable to process this message to the user, only included for events with "aborted" or "bounced" status),
-   }
-}
-```
-
-#### Message status
-
-|  Status | Description |
-| ------------ | ----------- |
-| `sent` | Message successfully dispatched to a Braze email sending partner |
-| `processed` | Email sending partner has successfully received and prepared the message for sending to the user's inbox provider |
-| `aborted` | Braze was unable to successfully dispatch the message due to the user not having an emailable address, or Liquid abort logic was called in the message body. All aborted events include a `reason` field within the metadata object indicating why the message was aborted |
-|`delivered`| Message was accepted by the user's email inbox provider |
-|`bounced`| Message was rejected by the user's email inbox provider. All bounced events include a `reason` field within the metadata object reflecting the bounce error code provided by the inbox provider |
-{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
-
-### Example postback
-```json
-
-// Sent Event
-{
-    "dispatch_id": "acf471119f7449d579e8089032003ded",
-    "status": "sent",
-    "metadata": {
-      "received_at": "2020-08-31T18:58:41.000+00:00",
-      "enqueued_at": "2020-08-31T18:58:41.000+00:00",
-      "executed_at": "2020-08-31T18:58:41.000+00:00",
-      "sent_at": "2020-08-31T18:58:42.000+00:00",
-      "campaign_api_id": "417220e4-5a2a-b634-7f7d-9ec891532368",
-      "external_send_id" : "34a2ceb3cf6184132f3d816e9984269a"
-    }
-}
-
-// Processed Event
-{
-    "dispatch_id": "acf471119f7449d579e8089032003ded",
-    "status": "processed",
-    "metadata": {
-      "processed_at": "2020-08-31T18:58:42.000+00:00",
-      "campaign_api_id": "417220e4-5a2a-b634-7f7d-9ec891532368",
-      "external_send_id" : "34a2ceb3cf6184132f3d816e9984269a"
-    }
-}
-
-// Aborted
-{
-    "dispatch_id": "acf471119f7449d579e8089032003ded",
-    "status": "aborted",
-    "metadata": {
-      "reason": "User not emailable",
-      "aborted_at": "2020-08-31T19:04:51.000+00:00",
-      "campaign_api_id": "417220e4-5a2a-b634-7f7d-9ec891532368",
-      "external_send_id" : "34a2ceb3cf6184132f3d816e9984269a"
-    }
-}
-
-// Delivered Event
-{
-    "dispatch_id": "acf471119f7449d579e8089032003ded",
-    "status": "delivered",
-    "metadata": {
-      "delivered_at": "2020-08-31T18:27:32.000+00:00",
-      "campaign_api_id": "417220e4-5a2a-b634-7f7d-9ec891532368",
-      "external_send_id" : "34a2ceb3cf6184132f3d816e9984269a"
-    }
-}
-
-// Bounced Event
-{
-    "dispatch_id": "acf471119f7449d579e8089032003ded",
-    "status": "bounced",
-    "metadata": {
-      "bounced_at": "2020-08-31T18:58:43.000+00:00",
-      "reason": "550 5.1.1 The email account that you tried to reach does not exist",
-      "campaign_api_id": "417220e4-5a2a-b634-7f7d-9ec891532368",
-      "external_send_id" : "34a2ceb3cf6184132f3d816e9984269a"
-    }
-}
-
-```
-
+{% multi_lang_include http_event_postback.md %}
 
 {% endapi %}

_docs/_api/endpoints/messaging/send_messages/post_send_triggered_campaigns.md

@@ -77,7 +77,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 |`trigger_properties`| Optional | Object | See [trigger properties]({{site.baseurl}}/api/objects_filters/trigger_properties_object/). Personalization key-value pairs that will apply to all users in this request. |
 |`broadcast`| Optional | Boolean | You must set `broadcast` to true when sending a message to an entire segment that a campaign or Canvas targets. This parameter defaults to false (as of August 31, 2017). <br><br> If `broadcast` is set to true, a `recipients` list cannot be included. However, use caution when setting `broadcast: true`, as unintentionally setting this flag may cause you to send your message to a larger than expected audience. |
 |`audience`| Optional | Connected audience object| See [connected audience]({{site.baseurl}}/api/objects_filters/connected_audience/). |
-|`recipients`| Optional | Array | See [recipients object]({{site.baseurl}}/api/objects_filters/recipient_object/).<br><br>If `send_to_existing_only` is `false`, an attribute object must be included.<br><br>If `recipients` is not provided and `broadcast` is set to true, the message will be sent to the entire segment targeted by the campaign. |
+|`recipients`| Optional | Array | See [recipients object]({{site.baseurl}}/api/objects_filters/recipient_object/).<br><br>If `send_to_existing_only` is `false`, an attribute object must be included.<br><br>If `recipients` is not provided and `broadcast` is set to true, the message will be sent to the entire segment targeted by the campaign. <br><br> If `email` is the identifier, you must include [`prioritization`]({{site.baseurl}}/api/endpoints/user_data/post_user_identify#identifying-users-by-email) in the recipients object. |
 |`attachments`| Optional | Array | If `broadcast` is set to true, then the `attachments` list cannot be included. |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 

_docs/_api/endpoints/messaging/send_messages/post_send_triggered_canvases.md

@@ -67,7 +67,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 |`canvas_entry_properties`| Optional | Object | See [Canvas entry properties]({{site.baseurl}}/api/objects_filters/canvas_entry_properties_object/). Personalization key-value pairs will apply to all users in this request. The Canvas entry properties object has a maximum size limit of 50 KB. |
 |`broadcast`| Optional | Boolean | You must set `broadcast` to true when sending a message to an entire segment that a campaign or Canvas targets. This parameter defaults to false (as of August 31, 2017). <br><br> If `broadcast` is set to true, a `recipients` list cannot be included. However, use caution when setting `broadcast: true`, as unintentionally setting this flag may cause you to send your message to a larger-than-expected audience. |
 |`audience`| Optional| Connected audience object | See [Connected audience]({{site.baseurl}}/api/objects_filters/connected_audience/). |
-|`recipients`| Optional | Array | See [Recipients object]({{site.baseurl}}/api/objects_filters/recipient_object/). If not provided and `broadcast` is set to true, the message will be sent to the entire segment targeted by the Canvas.<br><br> The `recipients` array may contain up to 50 objects, with each object containing a single `external_user_id` string and a `canvas_entry_properties` object. Either `external_user_id` or `user_alias` is required for this call. Requests must specify only one. <br><br> When `send_to_existing_only` is `true`, Braze will only send the message to existing users—however, this flag can't be used with user aliases. When `send_to_existing_only` is `false` and a user with the given `id` does not exist, Braze will create a user with that ID and attributes before sending the message.|
+|`recipients`| Optional | Array | See [Recipients object]({{site.baseurl}}/api/objects_filters/recipient_object/). If not provided and `broadcast` is set to true, the message will be sent to the entire segment targeted by the Canvas.<br><br> The `recipients` array may contain up to 50 objects, with each object containing a single `external_user_id` string and a `canvas_entry_properties` object. This call requires an `external_user_id`, `user_alias`, or `email`. Requests must specify only one. <br><br> When `send_to_existing_only` is `true`, Braze will only send the message to existing users—however, this flag can't be used with user aliases. When `send_to_existing_only` is `false` and a user with the given `id` does not exist, Braze will create a user with that ID and attributes before sending the message. <br><br> If `email` is the identifier, you must include [`prioritization`]({{site.baseurl}}/api/endpoints/user_data/post_user_identify#identifying-users-by-email) in the recipients object. |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 Customers using the API for server-to-server calls may need to allowlist the appropriate API URL if they're behind a firewall.

_docs/_developer_guide/banner_cards/integration.md

@@ -429,6 +429,14 @@ This feature is not currently supported on Roku.
 
 {% enddetails %}
 
+## Handling test sends
+
+Use test sends to verify Banner Card integrations before launching a campaign. Test Banner Cards are stored in a separate in-memory cache and do not persist across app restarts. While no extra setup is needed, the device must be able to receive foreground push notifications to display test Banner Cards.
+
+{% alert important %}
+A test banner is treated like any other banner except it's removed at the next app session. You must have its placement set up in your app for the test banner to display.
+{% endalert %}
+
 ## Dimensions and sizing
 
 Here's some things to know about Banner Card dimensions and sizing: