Deploy - June 18, 2024

_docs/_api/api_campaigns.md

@@ -21,7 +21,7 @@ You'll then send that information to your development team to use in the API req
 After the campaign begins, you can view the results in the dashboard. API campaigns use the Braze [messaging APIs]({{site.baseurl}}/api/endpoints/messaging/), which have the same detailed reporting and retargeting options as campaigns created completely through the dashboard.
 
 {% alert warning %}
-Because API campaigns are typically transactional, all users are eligible for API campaigns, even those in your Global Control Group.
+Because API campaigns are typically transactional, all users are eligible for API campaigns, even those in your Global Control Group. A [one-click list-unsubscribe]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#list-unsubscribe) header is not added to these sends. If you'd like to add a one-click list-unsubscribe header to all API campaigns, contact your customer success manager.
 {% endalert %}
 
 ## Create a new campaign

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

@@ -55,7 +55,14 @@ Authorization: Bearer YOUR-REST-API-KEY
       "send_to_existing_only": (optional, boolean) defaults to true, can't be used with user aliases; if set to `false`, an attributes object must also be included,
       "attributes": (optional, object) fields in the attributes object will create or update an attribute of that name with the given value on the specified user profile before the message is sent and existing values will be overwritten
     }
-  ]
+  ],
+  "attachments": (optional, array) array of JSON objects that define the files you need attached, defined by "file_name" and "url",
+    [
+      {  
+       "file_name": (required, string) the name of the file you want to attach to your email, excluding the extension (for example, ".pdf"). Attach files up to 2 MB. This is required if you use "attachments",
+       "url": (required, string) the corresponding URL of the file you want to attach to your email. The file name's extension will be detected automatically from the URL defined, which should return the appropriate "Content-Type" as a response header. This is required if you use "attachments",
+      }
+    ]
 }
 ```
 
@@ -69,6 +76,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 |`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 send to the entire segment targeted by the campaign. |
+|`attachments`| Optional | Array | If `broadcast` is set to true, then `attachments` list cannot be included. |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 - The recipients array may contain up to 50 objects, with each object containing a single `external_user_id` string and `trigger_properties` object.
@@ -147,7 +155,13 @@ curl --location --request POST 'https://rest.iad-01.braze.com/campaigns/trigger/
         "first_name" : "Alex"
       }
     }
-  ]
+  ],
+  "attachments": [
+    {
+      "file_name" : "YourFileName",
+      "url" : "https://exampleurl.com/YourFileName.pdf"
+    }
+  ] 
 }'
 ```
 

_docs/_api/use_cases.md

@@ -6,7 +6,7 @@ page_type: reference
 page_order: 4.8
 ---
 
-# Use cases
+# API use cases
 
 > The [Braze REST API]({{site.baseurl}}/api/basics/) provides a wide range of endpoints designed to help manage and optimize your customer engagement strategy. In this article, we’ll explore several use cases for each endpoint collection: catalogs, email lists and addresses, export, messages, preference center, SMS, subscription groups, templates, and user data.<br><br>Each section introduces a scenario with a step-by-step guide, code sample, and expected outcome. By the end of this article, you’ll better understand how to use the Braze REST API to enhance your customer engagement efforts.
 

_docs/_contributing/content_management/images.md

@@ -48,7 +48,7 @@ braze-docs
 
 When linking to your new image, you can either use in-line or reference-style syntax. In-line syntax prioritizes clarity, while reference-style syntax prioritizes readability.
 
-{% tabs local %}
+{% tabs %}
 {% tab in-line %}
 In your Markdown file, link to your new image using the in-line syntax.
 
@@ -126,6 +126,36 @@ Your links should be similar to the following:
 {% endtab %}
 {% endtabs %}
 
+### Step 3: Set the image's max width (optional)
+
+You can set the image's max width by appending the following liquid code to your image link:
+
+{% raw %}
+```markdown
+{: style="max-width:NUMBER%;"}
+```
+{% endraw %}
+
+Replace `NUMBER` with the maximum width you'd like to set as a percentage. Your image link should be similar to the following:
+
+{% tabs %}
+{% tab in-line %}
+{% raw %}
+```markdown
+![The form for creating a new pull request on GitHub.]({% image_buster /assets/img/contributing/getting_started/github_pull_request.png %}){: style="max-width:65%;"}
+```
+{% endraw %}
+{% endtab %}
+
+{% tab reference-style %}
+{% raw %}
+```markdown
+![The form for creating a new pull request on GitHub.][10]{: style="max-width:65%;"}
+```
+{% endraw %}
+{% endtab %}
+{% endtabs %}
+
 ## Updating an image
 
 ### Step 1: Find the original reference

_docs/_developer_guide/platform_integration_guides/sdk_primer.md

@@ -5,9 +5,9 @@ description: "This onboarding reference article provides a technical overview fo
 page_order: 0
 ---
 
-# SDK overview for developers
+# [![Braze Learning course]({% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/path/developer/sdk-integration-basics){: style="float:right;width:120px;border:0;" class="noimgborder"}SDK overview for developers
 
-> Before you begin to integrate the Braze SDKs, you may find yourself wondering what exactly you're building and integrating. You may be curious about how you can customize the SDK to further to meet your needs. This article can help you answer all of your SDK questions. You can also check out our [Technical Integration Checklists and Toolkits](https://learning.braze.com/technical-integration-checklists-and-toolkits) course on Braze Learning.
+> Before you begin to integrate the Braze SDKs, you may find yourself wondering what exactly you're building and integrating. You may be curious about how you can customize the SDK to further to meet your needs. This article can help you answer all of your SDK questions. 
 
 Are you a marketer looking for a basic rundown of the SDK? Check out our [marketer overview][1], instead.
 

_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_

_docs/_hidden/other/documentation_request.md

@@ -194,7 +194,7 @@ hide_toc: true
     textarea {
       border-radius: 0 !important;
     }
-    #doc_pm_label, #doc_verify_label {
+    #doc_verify_label {
       font-size: 12pt !important;
       font-family: Sailec W00 Regular,Arial,sans-serif;
     }
@@ -431,12 +431,17 @@ hide_toc: true
                 <label for="doc_name" id="doc_name_label">Name</label>
                 <input type="text" name="Name" id="doc_name" maxlength="80" required="required" value="" placeholder="Enter your name" class="form-control" />
               </div>
-              <div class="form-group" id="doc_pm_div">
+              <div class="form-group" id="doc_urgent_div">
               <div class="form-check">
-                <input class="form-check-input" type="checkbox" value="Y" id="doc_is_pm" name="Request_Is_PM">
-                <label class="form-check-label" for="doc_is_pm" id="doc_pm_label">
-                <span></span> I'm a product manager
-              </label>
+                <label class="form-check-label" for="doc_urgent" style="display: block;">
+                Request Type
+                </label>
+              <select id="doc_urgent" name="Request_Type" class="drop-down-sel">
+              <option value="urgent">Urgent — This request raises smoke on the Doc Site or requires a high-priority change.</option>
+              <option value="feature_release">Feature Release: Feature Update - This request is for new or existing product features that need to be communicated to the Tech Writing and Braze Learning teams.</option>
+              <option value="standard" selected="selected">Standard: I have a suggestion, question about, or update to an article.</option>
+              </select>
+
               </div>
               </div>
               <div class="form-group">
@@ -460,21 +465,6 @@ hide_toc: true
                 <input type="text" name="Request_Subject" id="doc_request" maxlength="180" required="required" value="" placeholder="Enter your request" class="form-control" />
               </div>
 
-              <div class="form-group" id="doc_urgent_div">
-              <div class="form-check">
-                <label class="form-check-label" for="doc_urgent" style="display: block;">
-                Priority
-                </label>
-              <select id="doc_urgent" name="Request_Urgent" class="drop-down-sel">
-              <option value="urgent">Urgent — There's an urgent problem that is immediately blocking my work</option>
-              <option value="major">Major — There's a major issue and I can't find a workaround</option>
-              <option value="minor" selected="selected">Minor — There's a minor issue but I have a workaround</option>
-              <option value="trivial" selected="selected">Trivial — I have a question or suggestion</option>
-              </select>
-
-              </div>
-              </div>
-
               <div class="form-group" id="doc_request_url">
                 <label for="doc_request" id="doc_request_url_label">URL</label>
                 <input type="url" name="Request_Url" id="doc_request_url" maxlength="180" required="required" value="" placeholder="e.g., https://www.braze.com/docs/" class="form-control" />

_docs/_hidden/other/support_contact.md

@@ -127,17 +127,34 @@ hide_toc: true
 }
 
 .gradient-line {
-    background: linear-gradient(30deg,#3accdd,#f7918e 64%,#ff9349 90%);
-    height: 2px;
-    width: 108px;
+  background: linear-gradient(90deg, rgba(201,196,255,1) 30%, rgba(128,30,215,1) 60%, rgba(255,165,36,1) 90%);
+  height: 3px;
+  width: 108px;
 }
 
 a {
-  color: #3accdd;
+  font-family: "Aribau Grotesk Regular", "Aribau Grotesk", "Aribau Grotesk Regular", Arial, Helvetica, sans-serif;
+  display: inline;
+  color: rgb(128, 30, 215);
+  font-weight: normal;
+  @media print {
+    font-weight: normal;
+  }
+  transition: all ease 0.2s;
+  -webkit-transition: all ease 0.2s;
+  -moz-transition: all ease 0.2s;
+  border-color: rgb(128, 30, 215);
+  border-bottom-width: 2px;
+  border-bottom-style: solid;
+  line-height: 2.5;
 }
+
 a:hover {
-  color: #333;
+  background-color: rgb(128, 30, 215);
+  text-decoration: none;
+
 }
+
 #ticket_mainform {
   margin-top: 20px;
 }
@@ -191,7 +208,7 @@ a:hover {
   font-size: 14px;
   font-size: 1rem;
   line-height: 1.4;
-  font-family: Sailec W00 Bold, Arial, sans-serif;
+  font-family: "Aribau Grotesk Regular", "Aribau Grotesk", "Aribau Grotesk Regular", Arial, Helvetica, sans-serif;
   text-transform: uppercase;
   padding: 1.14286rem 2.85714rem;
   border-radius: 0;