Skip to content

Commit 4d86d3c

Browse files
committed
Partial Syncs update
1 parent 726ab0e commit 4d86d3c

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

src/connections/reverse-etl/index.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -90,9 +90,6 @@ To add your first destination:
9090
### Step 4: Create mappings
9191
After you’ve added a destination, you can create mappings from your warehouse to the destination. Mappings enable you to map the data you extract from your warehouse to the fields in your destination.
9292

93-
> info ""
94-
> When you add new mappings to an existing model, Segment only syncs changes that have transpired since the last sync, not the entire dataset. For a comprehensive data synchronization, Segment recommends that you first recreate the model, then establish a one-to-one mapping with the new model. This ensures that all data syncs effectively.
95-
9693
To create a mapping:
9794
1. Navigate to **Conections > Destinations** and select the **Reverse ETL** tab.
9895
2. Select the destination that you want to create a mapping for.
@@ -152,7 +149,12 @@ You can opt in to receive email alerts regarding notifications for Reverse ETL.
152149
To subscribe to email alerts:
153150
1. Navigate to **Settings > User Preferences**.
154151
2. Select **Reverse ETL** in the **Activity Notifications** section.
155-
3. Click the toggle for **Reverse ETL Sync Failed** to receive notifications when your Reverse ETL sync fails.
152+
3. Click the toggle on for the notifications you want to receive. You can choose from:
153+
154+
Notification | Details
155+
------ | -------
156+
Reverse ETL Sync Failed | Set toggle on to receive notification when your Reverse ETL sync fails.
157+
Reverse ETL Sync Partial Success | Set toggle on to receive notification when your Reverse ETL sync is partially successful.
156158

157159
### Edit your model
158160

0 commit comments

Comments
 (0)