Leftover Deploy - April 20, 2023

_docs/_api/errors.md

@@ -58,7 +58,7 @@ The status code element of a server response is a 3-digit number where the first
 
 - The **2XX class** of status code (non-fatal) indicates that **your request** was successfully received, understood, and accepted.
 - The **4XX class** of status code (fatal) indicates a **client error**. Refer to the fatal errors chart for a full list of 4XX error codes and descriptions.
-- The **5XX class** of status code (fatal) indicates a **server error**. There are several potential causes, e.g., the server you're trying to access is unable to execute the request, the server is undergoing maintenance making it unable to execute the request, or the server is experiencing high levels of traffic. When this happens, we recommend you retry your request with exponential backoff.
+- The **5XX class** of status code (fatal) indicates a **server error**. There are several potential causes, e.g., the server you're trying to access is unable to execute the request, the server is undergoing maintenance making it unable to execute the request, or the server is experiencing high levels of traffic. When this happens, we recommend you retry your request with exponential backoff. In the event of an incident or outage, Braze is not able to replay any REST API call that failed during the incident window. You will need to retry any calls that failed during the incident window.
 
 ### Fatal errors
 

_docs/_help/help_articles/campaigns_and_canvas/know_before_send.md

@@ -30,7 +30,7 @@ While we provide an extensive list of resources for customers to reference pre-s
 ## Email
 
 #### Things to check
-- **Customer consent**: Before sending out your initial emails, it's important to get permission from your customers first. Refer to [Consent and address collection]({{site.baseurl}}/user_guide/onboarding_with_braze/email_setup/consent_and_address_collection/) and our [Braze Acceptable Use Policy]({{site.baseurl}}/company/legal/aup) for more information.
+- **Customer consent**: Before sending out your initial emails, it's important to get permission from your customers first. Refer to [Consent and address collection]({{site.baseurl}}/user_guide/onboarding_with_braze/email_setup/consent_and_address_collection/) and our [Braze Acceptable Use Policy](https://www.braze.com/company/legal/aup) for more information.
 - **Anticipated volume**: 2 million emails per day for a single IP is the general recommendation as long as that volume has been [properly warmed]({{site.baseurl}}/user_guide/onboarding_with_braze/email_setup/ip_warming#ip-warming). 
   - If you plan on consistently sending a higher volume than this, to avoid providers throttling receipt of emails resulting in a high amount of soft bounces, lowered deliverability rate, and a decreased IP reputation, consider using multiple IP addresses bundled into an IP pool. 
   - If you are looking to send in a shorter time frame only, we recommend looking into how quickly different providers accept mail to gauge the appropriate number of IPs to send from. 

_docs/_user_guide/data_and_analytics/analytics.md

@@ -21,5 +21,8 @@ guide_featured_list:
   - name: Conversions Dashboard
     link: /docs/user_guide/data_and_analytics/analytics/conversions_dashboard/
     fa_icon: fas fa-chart-simple
+  - name: Deliverability Center
+    link: /docs/user_guide/data_and_analytics/analytics/deliverability_center/
+    fa_icon: fas fa-location-arrow
 ---
 <br><br>

_docs/_user_guide/data_and_analytics/analytics/deliverability_center.md

@@ -0,0 +1,54 @@
+---
+nav_title: Deliverability Center
+article_title: Deliverability Center
+page_order: 4
+description: "This reference article covers how to set up the Deliverability Center, a feature that allows marketers to view their email sending domains and IP reputations, and understand their email deliverability."
+channel:
+  - email
+
+---
+
+# Deliverability Center
+
+> The Deliverability Center provides more insight for your email performance by supporting the use [Gmail Postmaster Tools][1] to track data on emails sent and gather data about your sending domain.
+
+Email deliverability is at the core when it comes to measuring the success of a messaging campaign. Using the Deliverability Center in the Braze dashboard, you can view your domains by **IP Reputation** or **Delivery Errors** to discover and troubleshoot any potential issues with email deliverability. 
+
+{% alert important %}
+The Deliverability Center is currently in early access. Contact your Braze customer success manager if you're interested in participating in the early access.
+{% endalert %}
+
+## Integrate with Google Postmaster
+
+Before setting up your Deliverability Center, check that your domains have been [added to the Gmail Postmaster Tools][4].
+
+Follow these steps to integrate with Google Postmaster and set up your Deliverability Center:
+
+1. Go to the **Overview** page in the Braze dashboard.
+2. Click **Email Performance** and select the **Deliverability Center** tab. <br>![][3]
+3. Click **Connect with Google Postmaster**. Select your Google Account, and click the **Allow** button to allow Braze to view email traffic metrics for the domains registered with the Postmaster Tools.
+4. Your verified domains will display in the Deliverability Center. <br>![][5]
+
+You can also access Google Postmaster in the Braze dashboard by navigating to **Technology Partners > Google Postmaster**. After integrating, Braze pulls reputation and error data for the last 30 days. The data may not be immediately available and could take several minutes to populate.
+
+#### About IP reputation
+
+To help understand the ratings for IP reputation, refer to this table:
+
+| Repuation Level | Definition |
+| ----- | ---------- |
+| High | Has a good track record of a very low spam rate. Complies with [Gmail's sender guidelines][2]. Emails are rarely marked by the spam filter. |
+| Medium | Known to send good email, but has occasionally sent a low volume of spam. Most of the email from this domain will have a fair deliverability rate (except when there is a notable increase in spam levels). |
+| Low | Known to send a considerable volume of spam regularly and mail from this sender will likely be marked as spam. |
+| Bad | Has a history of sending a high volume of spam. Emails coming from this domain will almost always be rejected at connection time or marked as spam. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+For more ideas on improving deliverability, read [Deliverability pitfalls and spam traps][6]. Be sure to also reference our [Email best practices][7] for things you should check for before sending an email campaign.
+
+[1]: https://www.gmail.com/postmaster/
+[2]: https://developers.google.com/gmail/markup/registering-with-google
+[3]: {% image_buster /assets/img_archive/deliverability_center1.png %}
+[4]: https://support.google.com/mail/answer/9981691?hl=en
+[5]: {% image_buster /assets/img_archive/deliverability_center2.png %}
+[6]: {{site.baseurl}}/user_guide/onboarding_with_braze/email_setup/deliverability_pitfalls_and_spam_traps/#deliverability-pitfalls-and-spam-traps
+[7]: {{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices/

_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events.md

@@ -341,6 +341,4 @@ Note that this Currents event is only available for customers that have purchase
 <br><br>To get this event enabled and to schedule the backfill for existing users' random bucket numbers in your app group, contact your customer success manager.
 {% endalert %}
 
-{% endapi %}
-
-
+{% endapi %}