Skip to content

Commit 3f747ea

Browse files
committed
edits
1 parent 93f8208 commit 3f747ea

File tree

3 files changed

+19
-13
lines changed

3 files changed

+19
-13
lines changed

src/_data/sidenav/main.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -243,7 +243,7 @@ sections:
243243
title: Regional Segment
244244
- section_title: Reverse ETL
245245
section:
246-
- path: /reverse-etl/reverse-etl
246+
- path: /reverse-etl
247247
title: Reverse ETL Overview
248248
- path: /reverse-etl/bigquery-setup
249249
title: Bigquery Reverse ETL Setup
1.6 MB
Loading

src/reverse-etl/reverse-etl.md renamed to src/reverse-etl/index.md

Lines changed: 18 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -4,27 +4,27 @@ beta: true
44
---
55

66
> info ""
7-
> Reverse ETL is currently in beta and Segment is actively working on this feature. Segment's [First-Access and Beta terms](https://segment.com/legal/first-access-beta-preview/) govern this feature. If you’d like to join the beta, please reach out to your CSM, AE, or SE to learn more.
7+
> Reverse ETL is currently in beta and Segment is actively working on this feature. Segment's [First-Access and Beta terms](https://segment.com/legal/first-access-beta-preview/) govern this feature. If you’d like to learn more reach out to your CSM, AE, or SE.
88
9-
Reverse ETL (Extract, Transform, Load) is a directional version of ETL that extracts data from a data warehouse and loads it into a 3rd party destination. Reverse ETL allows you to connect your data warehouse to the tools that Marketing, Sales, Support, Product, Analytics, and other business teams use. For example, with Reverse ETL, you can sync rows from Snowflake to Salesforce. This enables your warehouse to remain the single source of truth in which all data is collected, operated on, and enriched.
9+
Reverse ETL (Extract, Transform, Load) extracts data from a data warehouse and loads it into a 3rd party destination. Reverse ETL allows you to connect your data warehouse to the tools that Marketing, Sales, Support, Product, Analytics, and other business teams use. For example, with Reverse ETL, you can sync rows from Snowflake to Salesforce. This enables your warehouse to remain the single source of truth in which all data is collected, operated on, and enriched.
1010

1111
As Segment is actively developing this feature, Segment welcomes your feedback on your experience with Reverse ETL. Click the button below to submit your feedback.
1212

1313
{% include components/button-fill.html modifier="expand" text="Submit feedback" href=" https://airtable.com/shrdu5cW06LsuZvXN" %}
1414

15-
## Use cases
15+
## Example use cases
1616
Use Reverse ETL when you want to:
17-
* Sync lead scores created in the warehouse to Salesforce
18-
* Connect Google Sheets to a view in the warehouse for up-to-date reports that can also be downloaded as CSVs.
19-
* Sync enriched data to Amplitude or Mixpanel for a more complete view than what Segment events provides.
20-
* Sync audiences and other data built in the warehouse to Braze, Iterable, or Hubspot or Salesforce Marketing Cloud for marketing campaigns.
21-
* Turn data in the warehouse from sources that can’t be instrumented by Segment back into Segment as events for Personas and other use cases.
17+
* Sync lead scores created in the warehouse to Salesforce to customize interactions with prospects and optimize sales opportunities
18+
* Connect Google Sheets to a view in the warehouse for other business teams to have access to up-to-date reports.
19+
* Sync enriched data to Mixpanel for a more complete view.
20+
* Sync audiences and other data built in the warehouse to Braze, Iterable, or Hubspot or Salesforce Marketing Cloud for personlized marketing campaigns.
21+
* Send data in the warehouse back into Segment as events that can be activated in all supported destinations, including Twilio Engage and other platforms.
2222
* Pass offline or enriched data to conversion APIs like Facebook, Google Ads, TikTok, Snapchat.
2323

2424
## Getting started
2525
There are four components to Reverse ETL: Sources, Models, Destinations, and Mappings.
2626

27-
![image from Charmaine to go here]
27+
![image from Charmaine to go here](images/RETL_Doc_Illustration.png)
2828

2929
Follow these 4 steps to set up Reverse ETL and learn what each component is about:
3030
1. [Add a Source](#step-1-add-a-source)
@@ -36,7 +36,7 @@ Follow these 4 steps to set up Reverse ETL and learn what each component is abou
3636
A Source is where your data originates from. Traditionally in Segment, a [Source](/docs/connections/sources/#what-is-a-source) is a website, server library, mobile SDK, or cloud application which can send data into Segment. In Reverse ETL, your data warehouse acts as the Source.
3737

3838
> info ""
39-
> Reverse ETL currently only supports BigQuery and Snowflake as sources.
39+
> Reverse ETL currently only supports BigQuery and Snowflake as sources and is actively working on adding more. If you'd like to request Segment to add a particular source, please note it on the [feedback form](https://airtable.com/shrdu5cW06LsuZvXN){:target="_blank"}.
4040
4141
To add your warehouse as a source:
4242

@@ -74,11 +74,14 @@ To add a model:
7474
* For a **Day and time** schedule type, you can choose the day(s) you’d like the schedule to run as well as the time. You can only choose to run the extraction at the top of the hour.
7575
10. Click **Create Model**.
7676

77+
You can add multiple models to your source. Repeat steps 1-10 above to add more.
78+
7779
### Step 3: Add a Destination
7880
Once you’ve added a model, you need to add a destination. In Reverse ETL, destinations are the business tools or apps you use that Segment syncs the data from your warehouse to.
7981

8082
> info ""
81-
> Reverse ETL only supports [Actions destinations](/docs/connections/destinations/actions/). Depending on the destination, you may need to know certain endpoints and have specific credentials to add the destination.
83+
> Reverse ETL only supports [Actions destinations](/docs/connections/destinations/actions/). If you'd like to request Segment to add a particular destination, please note it on the [feedback form](https://airtable.com/shrdu5cW06LsuZvXN){:target="_blank"}.
84+
> Depending on the destination, you may need to know certain endpoints and have specific credentials to add the destination.
8285
8386
To add a destination:
8487
1. Navigate to **Reverse ETL > Destinations**.
@@ -95,19 +98,22 @@ To create a mapping:
9598
1. Go to the **Mappings** tab of the destination and click **Add Mapping**.
9699
2. Select the model to sync from.
97100
3. Select the **Action** you want to sync and click **Next**.
98-
* Actions determine the information sent to the destination. You map the fields that come from your source, to fields that the destination expects to find. Fields on the destination side depend on the type of action selected.
101+
* Actions determine the information sent to the destination. The list of Actions will be unique to each destination.
99102
4. In the **Select record to map and send** section, select which records to send to your destination after Segment completes extracting data based on your model. You can choose from:
100103
* Added records
101104
* Updated records
102105
* Added or updated records
103106
* Deleted records
104107
5. Select a test record to preview the fields that you can map to your destination in the **Add test record** field.
105108
6. Define how to map the record columns from your model to your destination in the **Select Mappings** section.
109+
* You map the fields that come from your source, to fields that the destination expects to find. Fields on the destination side depend on the type of action selected.
106110
7. Click **Create Mapping**.
107111
8. Select the destination you’d like to enable on the **My Destinations** page under **Reverse ETL > Destinations**.
108112
9. Turn the toggle on for the **Mapping State** to enable the destination. Events that match the trigger condition in the mapping will be sent to the destination.
109113
* If you disable the mapping state to the destination, events that match the trigger condition in the mapping won’t be sent to the destination.
110114

115+
You can add multiple mappings from your warehouse to your destination. To add more mappings, repeat steps 1-9 above.
116+
111117
## Using Reverse ETL
112118
After you've followed [all four steps](/docs/reverse-etl/reverse-etl/#getting-started) and set up your source, model, destination, and mappings for Reverse ETL, your data will extract and will sync to your destination(s) right away if you chose an interval schedule. If you set your data to extract at a specific day and time, the extraction will take place then.
113119

0 commit comments

Comments
 (0)