Skip to content

Commit e1b8986

Browse files
committed
reverse etl ga edits
1 parent 06de547 commit e1b8986

File tree

6 files changed

+47
-8
lines changed

6 files changed

+47
-8
lines changed

src/_data/sidenav/main.yml

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -142,10 +142,19 @@ sections:
142142
- path: /connections/sources/catalog
143143
title: Sources Catalog
144144
menu_icon: read-more
145-
- path: /connections/sources/debugger
146-
title: Using the Source Debugger
147145
- path: /connections/sources/about-cloud-sources
148146
title: Cloud Sources
147+
- section_title: Reverse ETL
148+
slug: /connections/sources/reverse-etl
149+
section:
150+
- path: /connections/sources/reverse-etl
151+
title: Reverse ETL Overview
152+
- path: /connections/sources/reverse-etl/bigquery-setup/
153+
title: BigQuery Reverse ETL Setup
154+
- path: /connections/sources/reverse-etl/snowflake-setup/
155+
title: Snowflake Reverse ETL Setup
156+
- path: /connections/sources/debugger
157+
title: Source Debugger
149158
- path: /connections/sources/custom-domains
150159
title: Set Up a Custom Domain Proxy in Segment
151160
- path: /connections/sources/visual-tagger
@@ -243,6 +252,7 @@ sections:
243252
title: Rate Limits
244253
- path: /connections/regional-segment
245254
title: Regional Segment
255+
<<<<<<< HEAD
246256
- section_title: Reverse ETL
247257
section:
248258
- path: /reverse-etl
@@ -253,6 +263,8 @@ sections:
253263
title: Redshift Reverse ETL Setup
254264
- path: /reverse-etl/snowflake-setup
255265
title: Snowflake Reverse ETL Setup
266+
=======
267+
>>>>>>> 892582b7c (reverse etl ga edits)
256268
- section_title: Profiles
257269
section:
258270
- path: /profiles
File renamed without changes.

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

Lines changed: 23 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,6 @@ title: Reverse ETL
33
beta: true
44
---
55

6-
> info ""
7-
> Reverse ETL is 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.
8-
96
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. Reverse ETL supports event and object data. This includes customer profile data, subscriptions, product tables, shopping cart tables, and more.
107

118
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.
@@ -36,16 +33,20 @@ Follow these 4 steps to set up Reverse ETL and learn what each component is abou
3633
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 is the Source.
3734

3835
> info ""
39-
> Reverse ETL supports BigQuery and Snowflake as sources and Segment 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/shriQgvkRpBCDN955){:target="_blank"}.
36+
> Reverse ETL supports [these sources] and Segment 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/shriQgvkRpBCDN955){:target="_blank"}.
4037
4138
To add your warehouse as a source:
4239

4340
> warning ""
4441
> You need to be a user that has both read and write access to the warehouse.
4542
46-
1. Navigate to **Reverse ETL** in the Segment app.
43+
1. Navigate to **Connections > Sources** and select the **Reverse ETL** tab in the Segment app.
4744
2. Click **Add Source**.
45+
<<<<<<< HEAD:src/reverse-etl/index.md
4846
3. Select the source you want to add. You can choose between **BigQuery**, **Snowflake**, and **Redshift**.
47+
=======
48+
3. Select the source you want to add.
49+
>>>>>>> 892582b7c (reverse etl ga edits):src/connections/sources/reverse-etl/index.md
4950
* If you choose to use Snowflake, run the queries listed in the [Snowflake Reverse ETL setup guide](/docs/reverse-etl/snowflake-setup/) to set up the Segment Snowflake connector. Segment recommends using the `ACCOUNTADMIN` role to execute all the commands.
5051
* If you choose to use BigQuery, use the permissions outlined in the [BigQuery Reverse ETL setup guide](/docs/reverse-etl/bigquery-setup/), to create a Service Account and generate JSON credentials that will then be copied into the Segment UI when creating a Reverse ETL Source.
5152
4. Add the account information for your source.
@@ -59,7 +60,7 @@ After you add your data warehouse as a source, you can [add a model](#step-2-add
5960
Models are SQL queries that define sets of data you want to synchronize to your Reverse ETL destinations. After you add your source, you can add a model.
6061

6162
To add your first model:
62-
1. Navigate to **Reverse ETL > Sources**. Select your source and click **Add Model**.
63+
1. Navigate to **Connections > Sources** and select the **Reverse ETL** tab. Select your source and click **Add Model**.
6364
2. Click **SQL Editor** as your modeling method. (Segment will add more modeling methods in the future.)
6465
3. Enter the SQL query that’ll define your model. Your model is used to map data to your Reverse ETL destinations.
6566
4. Choose a column to use as the unique identifier for each row in the **Unique Identifier column** field.
@@ -147,3 +148,19 @@ To edit your mapping:
147148
1. Navigate to **Reverse ETL > Destinations**.
148149
2. Select the destination with the mapping you want to edit.
149150
3. Select the **...** three dots and click **Edit mapping**. If you want to delete your mapping, select **Delete**.
151+
152+
## Usage limits
153+
Processed Reverse ETL records are the total number of records Segment attempts to load to your downstream destinations, including those that fail to load. Your plan determines how many Reverse ETL records you can process in one monthly billing cycle.
154+
155+
Plan | Number of Reverse ETL records you can process to each destination per month |
156+
---- | ---------------------------------------------------------------------------
157+
Free | 500K
158+
Teams | 1 million
159+
Business | 50 x the number of [MTUs](/docs/guides/usage-and-billing/mtus-and-throughput/#what-is-an-mtu) <br>or .25 x the number of monthly API calls
160+
161+
When your limit is reached before the end of your billing period, your syncs will pause and then resume on your next billing cycle. To increase the number of processed Reverse ETL records, connect with your sales representative to upgrade your plan. If you're on a Free plan, upgrade to the Teams plan in the Segmet app.
162+
163+
To see how many records you’ve processed using Reverse ETL, navigate to **Settings > Usage & billing** and select the **Reverse ETL** tab.
164+
165+
166+
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
title: Redshift Reverse ETL Setup
3+
beta: true
4+
---
5+
6+
Set up Redshift as your Reverse ETL source.
7+
8+
To set up Redshift with Reverse ETL:
9+
1. Navigate to **Conections > Sources** and select the **Reverse ETL** tab.
10+
2. Click **Add Source**.
File renamed without changes.

0 commit comments

Comments
 (0)