Merge pull request #4114 from braze-inc/develop

Leftover deploy - October 22, 2022

_docs/_developer_guide/disclosures/innovation_statement.md

@@ -15,15 +15,16 @@ Warning! Don't make any changes to this document without approval from the legal
 
 {% tabs %}
 {% tab English %}
-_Last updated December 2018._
+_Last updated September 2022._
 
-Braze continually strives to enhance existing, and create new, features, functionality, products and services.  To do so, Braze not only seeks feedback from its customers, but also endeavors to anticipate its customers’ needs.
+Braze continually strives to enhance existing, and create new, features, functionality, products and services. To do so, Braze not only seeks feedback from its customers, but also endeavors to anticipate its customers’ needs.
 
-As part of its innovation strategy, Braze analyzes information contained in the Braze Services and how the Braze Services are used (e.g., analysis of User clicks and movements across the dashboard), in order to provide and improve the Services,  as well as to provide consultative and analytical information to its customers generally.
+As part of its innovation strategy, Braze analyzes information contained in the Braze Services and how the Braze Services are used (e.g., analysis of User clicks and movements across the dashboard), in order to provide consultative and analytical information to its customers generally, and in order to build, provide or improve its services, provided that this use does not include building or modifying End User profiles to use in providing services to another customer, or correcting or augmenting data acquired by Braze from another source.
 
-Braze also communicates with (dashboard) Users to educate and inform them of ways to optimize their use of the Services and to share Braze’s innovation efforts. Braze may send emails to (dashboard) Users or communicate with them through the dashboard. Customers can also subscribe to Braze’s GitHub repositories to receive notifications when new releases are made.   
+Braze also communicates with (dashboard) Users to educate and inform them of ways to optimize their use of the Services and to share Braze’s innovation efforts. Braze may send emails to (dashboard) Users or communicate with them through the dashboard. Customers can also subscribe to Braze’s GitHub repositories to receive notifications when new releases are made.
 
 Braze owns all right, title and interest in and to any material resulting from such activities.
+
 {% endtab %}
 {% tab Japanese %}
 {% raw %}

_docs/_developer_guide/platform_integration_guides/ios/in-app_messaging/customization/custom_triggering.md

@@ -69,7 +69,7 @@ In the following example, the specific in-app message to be triggered has been c
 
 ![An action-based delivery in-app message campaign that will be delivered to users who perform the custom event "In-app message trigger" where "campaign_name" equals "In-app message name example".][42]
 
-Due to a push message being used to record an SDK logged custom event, Braze will need to store a push token for each user to enable this solution. For iOS users, Braze will only store a token from the point that a user has been served the OS's push prompt. Before this, the user will not be reachable using push, and the preceding solution will not be possible.
+Due to a push message being used to record an SDK logged custom event, Braze will need to store a push token for each user to enable this solution. For both iOS and Android, Braze will only store a token from the point that a user has been served the OS's push prompt. Before this, the user will not be reachable using push, and the preceding solution will not be possible.
 
 [39]: {{site.baseurl}}/developer_guide/platform_integration_guides/ios/push_notifications/silent_push_notifications/
 [40]: {% image_buster /assets/img_archive/iosServerSentPush.png %}

_docs/_developer_guide/platform_wide/tv_and_ott.md

@@ -96,13 +96,14 @@ The following lists features and messaging channels supported today.
             <td for="data-analytics"><i class="fas fa-check text-success"></i></td>
             <td for="iam"><i class="fas fa-check text-success"></i></td>
             <td for="content-cards"><i class="fas fa-check text-success"></i></td>
-            <td for="push"><i class="fas fa-check text-success"></i></td>  
+            <td for="push"><i class="fa-solid fa-minus"></i></td>  
             <td for="canvas"><i class="fas fa-check text-success"></i></td>
         </tr>
     </tbody>
 </table>
 
 - <i class="fas fa-check text-success"></i> = Supported
+- <i class="fa-solid fa-minus"></i> = Partial support
 - <i class="fas fa-times text-warning"></i> = Not supported by Braze
 - N/A = Not supported by OTT platform
 
@@ -158,13 +159,13 @@ Make sure to create a new Android app in the dashboard for your Android OTT inte
 
 ### LG webOS
 
-Use Braze's Web SDK to integrate with [LG webOS TVs](http://webostv.developer.lge.com/discover/discover-webos-tv/).
+Use Braze's Web SDK to integrate with [LG webOS TVs](https://webostv.developer.lge.com/discover).
 
 Features include:
 
 - Data and analytics collection for cross-channel engagement
-- Content Cards (via [Custom UI](#custom-ui))
-- In-app messages (via [Custom UI](#custom-ui))
+- Content Cards (via [Headless UI](#custom-ui))
+- In-app messages (via [Headless UI](#custom-ui))
 
 For more information, visit the [Web Smart TV integration guide][8].
 
@@ -175,8 +176,8 @@ Use Braze's Web SDK to integrate with the [Samsung Tizen TVs](https://developer.
 Features include:
 
 - Data and analytics collection for cross-channel engagement
-- Content Cards (via [Custom UI](#custom-ui))
-- In-app messages (via [Custom UI](#custom-ui))
+- Content Cards (via [Headless UI](#custom-ui))
+- In-app messages (via [Headless UI](#custom-ui))
 
 For more information, visit the [Web Smart TV integration guide][8].
 
@@ -187,7 +188,7 @@ Use Braze's Roku SDK to integrate with [Roku TVs](https://developer.roku.com/doc
 Features include:
 
 - Data and analytics collection for cross-channel engagement
-- In-app messages (via [Custom UI](#custom-ui))
+- In-app messages (via [Headless UI](#custom-ui))
 
 For more information, visit the [Roku integration guide][3].
 
@@ -199,10 +200,10 @@ For more information, visit the [iOS Swift SDK integration guide][4].
 
 Features include:
 
-- Data and Analytics collection for cross-channel engagement
-- Content Cards (via [Custom UI](#custom-ui))
-- In-app messages (via [Custom UI](#custom-ui))
-- Silent Push Notifications
+- Data and analytics collection for cross-channel engagement
+- Content Cards (via [Headless UI](#custom-ui))
+- In-app messages (via [Headless UI](#custom-ui))
+- Silent push notifications and update badging
 
 **Note**: To avoid showing mobile in-app messages to your TV users, be sure to set up either [App Targeting](#app-targeting) or use key-value pairs to filter out messages. For example, only displaying tvOS messages if they contain a special `tv = true` key-value pair.
 
@@ -212,9 +213,9 @@ To target OTT apps for messaging, we recommend creating a segment specific to yo
 
 ![A segment created using the Android OTT app.][1]
 
-## Custom UI {#custom-ui}
+## Headless UI {#custom-ui}
 
-For platforms that support in-app messages or Content Cards via Custom UI, Braze will deliver a data model (i.e. JSON) that your app can read and use within a UI your app controls. These platforms don't include any out-of-the-box UI or Views.
+For platforms that support in-app messages or Content Cards via headless UI, Braze will deliver a data model (i.e. JSON) that your app can read and use within a UI your app controls. These platforms don't include any out-of-the-box UI or Views.
 
 This data will contain the fields configured in the dashboard (title, body, button text, colors, etc.) which your app can read and display accordingly.
 
@@ -241,4 +242,4 @@ Read more about custom handling messaging:
 [6]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android_tv_push/
 [7]: https://developer.amazon.com/docs/fire-tv/notifications.html#headsup
 [8]: {{site.baseurl}}/developer_guide/platform_integration_guides/web/smart_tvs/
-[android-tv-html]: https://github.com/Appboy/appboy-android-sdk/blob/master/CHANGELOG.md#2310
+[android-tv-html]: https://github.com/Appboy/appboy-android-sdk/blob/master/CHANGELOG.md#2310

_docs/_help/release_notes.md

@@ -50,7 +50,7 @@ guide_featured_list:
 ## September 20, 2022 release
 
 ### API guide
-Check out the [Braze API Guide]({{site.baseurl}}/docs/api/home) to search for endpoints based on endpoint types, helping you narrow down the glossary 
+Check out the [Braze API Guide]({{site.baseurl}}/docs/api/home) to search for endpoints based on endpoint types, helping you narrow down the glossary.
 
 ### Personalized variants
 Use [personalized variants]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/create_multivariate_campaign/#optimizations) to send each user in your target segment the variant they're most likely to engage with.

_docs/_help/release_notes/2022/9_20_22.md

@@ -9,7 +9,7 @@ description: "This article contains release notes for 9/20/2022."
 # September 20, 2022 release
 
 ## API guide
-Check out the [Braze API Guide]({{site.baseurl}}/docs/api/home) to search for endpoints based on endpoint types, helping you narrow down the glossary 
+Check out the [Braze API Guide]({{site.baseurl}}/docs/api/home) to search for endpoints based on endpoint types, helping you narrow down the glossary.
 
 ## Personalized variants
 Use [personalized variants]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/create_multivariate_campaign/#optimizations) to send each user in your target segment the variant they're most likely to engage with.

_docs/_hidden/private_betas/shopify_subscription_states.md

@@ -51,7 +51,7 @@ Next, you are prompted by Braze's setup wizard. Within this flow, you must enter
 #### Shopify setup within Braze
 <br>![Workflow of setting up Shopify within Braze by entering the store name and navigating to Shopify to install the Braze app.][3]{: style="max-width:80%;"}
 
-#### Collect email or SMS subscribers
+### Step 3: Collect email or SMS subscribers
 
 At this step, select whether you want to collect email and SMS opt-ins from your Shopify store to sync to Braze.
 

_docs/_home/templates/get_endpoint.md

@@ -4,6 +4,7 @@ article_title: "GET: [Endpoint Name]"
 search_tag: Endpoint
 
 page_order: 1
+excerpt_separator: ""
 
 layout: api_page
 page_type: reference

_docs/_home/templates/post_endpoint.md

@@ -5,6 +5,7 @@ search_tag: Endpoint
 page_order: 4
 layout: api_page
 page_type: reference
+excerpt_separator: ""
 
 description: "This article outlines details about and using this POST [endpoint name] Braze endpoint."
 

_docs/_partners/message_orchestration/channel_extensions/loyalty/extole.md

@@ -75,9 +75,12 @@ Any event that Extole tracks can be sent to Braze. Work with your Extole impleme
 
 To start sending data from your Extole programs into Braze, create a new webhook integration in Extole’s outbound webhook center.
 
-1. In the Extole dashboard, navigate to **Tech Center > Outbound Webhooks** and select **+ New Integration**.
-2. Enter a name for the key and select **Webhook** as the key type. 
-3. Add your Braze REST API key in the **Partner Key ID** field, select `HTTP_BASIC` as the **Algorithm**, and click **Create Key**.<br><br>![][4]{: style="max-width:80%;"}
+
+1. Navigate to **Tech Center > Outbound Webhooks** in your My Extole account and click on the **+ New Integration** button.
+2. Enter a key name (i.e., how you'd like to refer to the key in Extole) and select **Webhook** as the key type. 
+3. In the partner key ID field, add a value that you will recognize for this credential (e.g., your account ID, email address, or user ID).
+4. Select `PASSWORD` from the algorithm drop-down.
+5. Add your Braze REST API key to the key field and click **Create Key**.<br><br>![][4]{: style="max-width:80%;"}
 
 Next, work with your Extole success or implementation manager to create a new webhook. They will configure the webhook for you using your newly generated key and Braze instance URL.<br><br>![][5]{: style="max-width:80%;"}
 

_docs/_user_guide/administrative/company_settings/security_settings.md

@@ -79,6 +79,8 @@ The Security Event report is a CSV report of security events such as account inv
 
 This section covers a permission only accessible to a few select Braze users. For the existing team permission capabilities, see [Setting user permissions]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/user_permissions/#available-limited-and-team-role-permissions).
 
+By default, all admins will have their **View PII** permission enabled. This means they can see the following standard and custom attributes throughout the dashboard. When this permission is disabled for users in [user permissions]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/user_permissions/#available-limited-and-team-role-permissions), those users will not be able to see this information.
+
 ### Define PII
 
 Braze allows you to define which fields are designated as personally identifiable information (PII) in your dashboard. To do this, navigate to **Company Settings > Security Settings**.
@@ -90,8 +92,6 @@ The following fields can be hidden from Braze users who don't have **View PII**
 | - Email address<br>- Phone number<br>- First name<br>- Last name<br>- Gender<br>- Birthday<br>- Device IDs<br>- Most recent location | - All custom attributes |
 {: .reset-td-br-1 .reset-td-br-2}
 
-By default, all admins will have their **View PII** permission enabled. This means they can see all standard and custom attributes throughout the dashboard. When this permission is disabled for users in [user permissions]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/user_permissions/#available-limited-and-team-role-permissions), those users will not be able to see this information.
-
 ### Limited areas
 
 The following assumes all fields are set as PII and that the users mentioned are those that use the Braze platform.

_docs/_user_guide/administrative/manage_your_braze_users/user_permissions.md

@@ -44,8 +44,8 @@ You can manage user permissions by group or on an individual basis using the Use
 |---|---|
 |Admin|Has access to all available features, default setting for all new users. Can update company settings (company name and time zone), which Limited Users are unable to do.|
 |Access Campaigns, Canvases, Cards, Segments, Media Library| User can view campaign and Canvas performance metrics, create and duplicate drafts of campaigns and Canvases, view drafts of News Feed, segments, templates and media, create templates, upload media, and view engagement reports. However, users with this permission cannot view existing live content. |
-|Send Campaigns, Canvases| Allows user to edit, archive, and stop campaigns and canvases, create campaigns, launch canvases. To launch existing content blocks, both **Send campaigns, Canvases** and **Publish Cards** permissions are required. |
-|Publish Cards| Allows user to create and edit News Feed cards. You can still view cards without this permission. To launch existing content blocks, both **Publish Cards** and **Send campaigns, Canvases** permissions are required. |
+|Send Campaigns, Canvases| Allows user to edit, archive, and stop campaigns and Canvases, create campaigns, and launch Canvases. To launch existing Content Blocks, **Send campaigns, Canvases** permission is required. |
+|Publish Cards| Allows user to create and edit News Feed cards. You can still view cards without this permission. To launch existing Content Blocks, both **Publish Cards** and **Send campaigns, Canvases** permissions are required if your account is enabled for News Feed. |
 |Edit Segments| Allows user to create and edit segments. You can still create campaigns with existing segments and filters without this permission. You need this permission to generate a segment from users in a CSV or retarget the group of users in the CSV.|
 |Export User Data| Allows user to export your user data from Segments, campaigns and Canvases. |
 |View PII | Allows user to view personally identifiable information within the dashboard. Note that both email addresses and phone number will be visible. |