Merge branch 'retl-docs-refresh' into automatic-retry-handling

Author: forstisabella

src/_data/sidenav/main.yml

@@ -183,15 +183,13 @@ sections:
     - path: /connections/reverse-etl
       title: Reverse ETL Overview
     - path: /connections/reverse-etl/setup
-      title: Set up Reverse ETL
-    - path: /connections/reverse-etl/mappings
-      title: Reverse ETL Mappings
-    - path: /connections/reverse-etl/observability
-      title: Reverse ETL Observability
+      title: Set Up Reverse ETL
+    - path: /connections/reverse-etl/manage-retl
+      title: Manage Reverse ETL Syncs
     - path: /connections/reverse-etl/system
       title: Reverse ETL System
     - path: /connections/reverse-etl/reverse-etl-catalog
-      title: Reverse ETL Catalog
+      title: Reverse ETL Destination Catalog
     - section_title: Reverse ETL Source Setup Guides
       slug: connections/reverse-etl/reverse-etl-source-setup-guides
       section:

src/connections/reverse-etl/index.md

@@ -1,6 +1,7 @@
 ---
 title: Reverse ETL
 beta: false
+hide_toc: true
 redirect_from:
   - '/reverse-etl/'
 ---
@@ -9,10 +10,10 @@ Reverse ETL (Extract, Transform, Load) extracts data from a data warehouse using
 
 Use Reverse ETL when you want to:
 * **Enable your marketing teams**: Sync audiences and other data built in the warehouse to Braze, Hubspot, or Salesforce Marketing Cloud for personalized marketing campaigns.
-* **Enrich your customer profiles**: Sync enriched data to Mixpanel for a more complete view of the customer, or enrich Segment Unify with data from the warehouse.
-* **Activate data in Twilio Engage**: Send data in the warehouse back into Segment as events that can be activated in all supported destinations, including Twilio Engage.
+* **Enrich your customer profiles**: Sync enriched data to Mixpanel for a more complete view of the customer, or enrich Segment Unify with data from your warehouse.
+* **Activate data in Twilio Engage**: Send data in the warehouse back into Segment as events that can be activated in all supported destinations, including Twilio Engage destinations.
 * **Strengthen your conversion events**: Pass offline or enriched data to conversion APIs like Facebook, Google Ads, TikTok, or Snapchat.
-* **Empower business teams**: Connect Google Sheets to a view in the warehouse for other business teams to have access to up-to-date reports.
+* **Empower business teams**: Connect Google Sheets to a view in the warehouse to create up-to-date reports for other business teams.
 
 > info "Reverse ETL supports event and object data"
 > Event and object data includes customer profile data, subscriptions, product tables, shopping cart tables, and more.
@@ -29,50 +30,49 @@ Use Reverse ETL when you want to:
   %}
 
   {% include components/reference-button.html
-    href="/docs/connections/reverse-etl/reverse-etl-catalog"
+    href="/docs/connections/reverse-etl/manage-retl"
     icon="reverse-etl.svg"
-    title="Destination catalog"
-    description="View the 30+ destinations with native Reverse ETL support and learn how you can use the Segment Connections and Segment Profiles to send data to the rest of the Segment catalog."
+    title="Manage Reverse ETL Syncs"
+    description="View your sync history, gain insights into sync statuses, and restart or replay failed or partially successful syncs."
   %}
 </div>
 
 ## Learn more
 
-Learn more about the system that powers Reverse ETL, the mappings that power the flow of data to your downstream destinations, and observability tools you can use to manage your syncs.
-
+Learn more about the system that powers Reverse ETL, supported destinations, and frequently asked questions.
 <div class="flex flex--wrap gutter gutter--large">
   <div class="flex__column flex__column--12 flex__column--4@medium">
     {% include components/reference-button.html
-      href="/docs/connections/reverse-etl/observability"
-      title="Reverse ETL Observability"
-      description="View the state of your Reverse ETL syncs and get alerted when things go wrong."
+      href="/docs/connections/reverse-etl/system"
+      title="Reverse ETL System"
+      description="Reference material about system limits and how Segment detects data changes."
     %}
   </div>
 
   <div class="flex__column flex__column--12 flex__column--4@medium">
     {% include components/reference-button.html
-      href="/docs/connections/reverse-etl/mappings"
-      title="Reverse ETL Mappings"
-      description="Supported objects and arrays along with ways to manage your syncs."
+      href="/docs/connections/reverse-etl/reverse-etl-catalog"
+      title="Destination catalog"
+      description="View the 30+ destinations with native Reverse ETL support and learn how to send data to the rest of the Segment catalog using Segment Connections."
     %}
   </div>
 
   <div class="flex__column flex__column--12 flex__column--4@medium">
     {% include components/reference-button.html
-      href="/docs/connections/reverse-etl/system"
-      title="Reverse ETL System"
-      description="Reference material about system limits and how Segment detects data changes."
+      href="/docs/connections/reverse-etl/faq"
+      title="Reverse ETL FAQ"
+      description="Frequently asked questions about Reverse ETL."
     %}
   </div>
 </div>
 
-## More Segment resources
+## More Reverse ETL resources
 
 {% include components/reference-button.html
   icon="guides.svg"
   href="https://segment.com/blog/reverse-etl/"
-  title="What is reverse ETL? A complete guide"
-  description="In this blog from Segment, learn how reverse ETL helps businesses activate their data to drive better decision-making and greater operational efficiency."
+  title="What is Reverse ETL? A complete guide"
+  description="In this blog from Segment, learn how Reverse ETL helps businesses activate their data to drive better decision-making and greater operational efficiency."
 %}
 
 {% include components/reference-button.html

src/connections/reverse-etl/mappings.md renamed to src/connections/reverse-etl/manage-retl.md

@@ -1,13 +1,60 @@
 ---
-title: Reverse ETL Mappings
-beta: false 
+title: Manage Reverse ETL Syncs
+beta: false
 ---
 
-Learn which mapping fields support object and array values in your mappings and how you can reset or replay your syncs. 
+View your sync history, gain insights into sync statuses, and restart or replay failed or partially successful syncs.
+
+## Sync history
+Check the status of your data extractions and see details of your syncs. Click into failed records to view additional details on the error, sample payloads to help you debug the issue, and recommended actions.
+
+To check the status of your extractions:
+1. Navigate to **Connections > Destinations** and select the **Reverse ETL** tab.
+2. Select the destination you want to view.
+3. Select the mapping you want to view.  
+4. Click the sync you want to view to get details of the sync. You can view:
+    * The status of the sync.
+    * Details of how long it took for the sync to complete.
+    * How many total records were extracted, as well as a breakdown of the number of records added, updated, and deleted.
+    * The load results - how many successful records were synced as well as how many records were updated, deleted, or are new.
+5. If your sync failed, click the failed reason to get more details on the error and view sample payloads to help troubleshoot the issue.
+
+> info "Segment automatically retries events that were extracted but failed to load"
+> Segment retries events for 14 days following a total or partial sync failure. Before loading the failed records on a subsequent sync, Segment checks for the latest changes in your data to ensure the data loaded into your warehouse isn't stale. If the error causing the load failure is coming from an upstream tool, you can fix the error in the upstream tool to ensure the record loads on the next sync. 
+
+## Reset syncs
+You can reset your syncs so that your data is synced from the beginning. This means that Segment resyncs your entire dataset for the model.
+
+To reset a sync:
+1. Select the three dots next to **Sync now**.
+2. Select **Reset sync**. 
+3. Select the checkbox that you understand what happens when a sync is reset.
+4. Click **Reset sync**.
+
+## Replays
+You can choose to replay syncs. To replay a specific sync, contact [[email protected]](mailto:[email protected]). Keep in mind that triggering a replay resyncs all records for a given sync.
+
+## Alerting
+You can opt in to receive email, Slack, and in-app alerts about Reverse ETL sync failures and partial successes. 
+
+To subscribe to alerts: 
+1. Navigate to **Settings > User Preferences**. 
+2. Select **Reverse ETL** in the **Activity Notifications** section.
+3. Click the Reverse ETL sync status that you'd like to receive notifications for. You can select one or more of the following sync statuses:
+    - **Reverse ETL sync failed**: Receive a notification when your Reverse ETL sync fails.
+    - **Reverse ETL sync partial success**: Receive a notification when your Reverse ETL sync is partially successful.
+4. Select one or more of the following alert options: 
+    - **Enable email notifications**: Enter an email address or alias that should receive alerts.
+    - **Enable Slack notifications**: Enter a Webhook URL and Slack channel name.
+    - **Enable in-app notifications**: Select this option to see an in-app notification.
+5. Click **Create alert**.
+
+> success ""
+> If you opted to receive notifications by email, you can click **View active email addresses** to see the email addresses that are currently signed up to receive notifications. 
 
 ## Supported object and arrays 
 
-When you set up destination actions in Reverse ETL, depending on the destination, some [mapping fields](/docs/connections/reverse-etl/setup/#step-4-create-mappings) may require data to be in the form of an [object](/docs/connections/reverse-etl/mapping/#object-mapping) or [array](/docs/connections/reverse-etl/mapping/#array-mapping). 
+When you set up destination actions in Reverse ETL, depending on the destination, some [mapping fields](/docs/connections/reverse-etl/setup/#step-4-create-mappings) may require data to be in the form of an [object](/docs/connections/reverse-etl/manage-retl/#object-mapping) or [array](/docs/connections/reverse-etl/manage-retl/#array-mapping). 
 
 ### Object mapping
 You can send data to a mapping field that requires object data. An example of object mapping is an `Order completed` model with a `Products` column that’s in object format. 
@@ -68,16 +115,4 @@ Select array | This enables you to send all nested properties within the array.
 > success ""
 > Certain array mapping fields have a fixed list of properties they can accept. If the names of the nested properties in your array don't match the destination properties, the data won't send. Segment recommends you to use the **Customize array** option to ensure your mapping is successful.
 
-Objects in an array don't need to have the same properties. If a user selects a missing property in the input object for a mapping field, the output object will miss the property. 
-
-## Reset syncs
-You can reset your syncs so that your data is synced from the beginning. This means that Segment resyncs your entire dataset for the model.
-
-To reset a sync:
-1. Select the three dots next to **Sync now**.
-2. Select **Reset sync**. 
-3. Select the checkbox that you understand what happens when a sync is reset.
-4. Click **Reset sync**.
-
-## Replays
-You can choose to replay syncs. To replay a specific sync, contact [[email protected]](mailto:[email protected]). Keep in mind that triggering a replay resyncs all records for a given sync.
+Objects in an array don't need to have the same properties. If a user selects a missing property in the input object for a mapping field, the output object will miss the property.

src/connections/reverse-etl/observability.md

@@ -3,9 +3,12 @@ title: Reverse ETL Catalog
 beta: false
 ---
 
-Reverse ETL supports most of the Segment destination catalog - 30+ Actions destinations are natively supported, Segment Classic destinations are supported through the [Segment Connections](#segment-connections-destination) destination, and Twilio Engage Premier Subscriptions users can use the Segment Profiles destination to sync subscription data from warehouses to destinations. 
+Reverse ETL supports the entire Segment destination catalog - 30+ Actions destinations are natively supported and all other destinations are supported through the [Segment Connections](#segment-connections-destination) destination. 
 
-These destinations support [Reverse ETL](/docs/connections/reverse-etl/). If you don’t see your destination listed in the Reverse ETL catalog, use the [Segment Connections destination](/docs/connections/destinations/catalog/actions-segment/) to send data from your Reverse ETL warehouse to other destinations listed in the [catalog](/docs/connections/destinations/catalog/).  
+> success ""
+> Twilio Engage Premier Subscriptions users can use the [Segment Profiles](/docs/connections/destinations/catalog/actions-segment-profiles/) destination to enrich their warehouse data.  
+
+The following destinations natively support [Reverse ETL](/docs/connections/reverse-etl/). If you don’t see your destination listed in the Reverse ETL catalog, use the [Segment Connections destination](/docs/connections/destinations/catalog/actions-segment/) to send data from your Reverse ETL warehouse to other destinations listed in the [catalog](/docs/connections/destinations/catalog/).  
 
 <div class="destinations-catalog">
       <div class="flex flex--wrap waffle waffle--xlarge">

src/connections/reverse-etl/reverse-etl-catalog.md

@@ -61,7 +61,7 @@ To set up Azure as your Reverse ETL source:
 5. Navigate to **Connections > Sources** and select the **Reverse ETL** tab. 
 6. Click **+ Add Reverse ETL source**. 
 7. Select **Azure** and click **Add Source**. 
-8. Enter the configuration settings for you Azure source based on the information from Step 3. 
+8. Enter the configuration settings for your Azure source based on the information from Step 3. 
     * Hostname: 
         * Use `xxxxxxx.sql.azuresynapse.net` if you’re connecting to a dedicated SQL pool in Synapse workspace. 
         * Use `xxxxxxx.database.windows.net` if you’re connecting to a dedicated SQL pool (formerly SQL DW)

src/connections/reverse-etl/reverse-etl-source-setup-guides/azure-setup.md

@@ -33,7 +33,7 @@ To set up Postgres with Reverse ETL:
     GRANT CREATE ON DATABASE "<enter database name here>" TO "segment";
     ```
 4. Make sure the user has correct access permissions to the database.
-5. Follow the steps listed in the [Add a source](/docs/connections/reverse-etl/#step-1-add-a-source) section to finish adding Postgres as a source. 
+5. Follow the steps listed in the [Add a source](/docs/connections/reverse-etl/setup/#step-1-add-a-source) section to finish adding Postgres as a source. 
 
 ## Extra permissions
 * Give the `segment` user read permissions for any resources (databases, schemas, tables) the query needs to access. 

src/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup.md

@@ -22,7 +22,7 @@ To set up Redshift with Reverse ETL:
     -- allows the "segment" user to create new schemas on the specified database. (this is the name you chose when provisioning your cluster)
     GRANT CREATE ON DATABASE "<enter database name here>" TO "segment";
     ```
-4. Follow the steps listed in the [Add a source](/docs/connections/reverse-etl#step-1-add-a-source) section to finish adding Redshift as your source.
+4. Follow the steps listed in the [Add a source](/docs/connections/reverse-etl/setup/#step-1-add-a-source) section to finish adding Redshift as your source.
 
 ## Extra Permissions
 Give the `segment` user read permissions for any resources (databases, schemas, tables) the query needs to access.