Skip to content

Commit 634a19f

Browse files
committed
More edits
1 parent ba04d97 commit 634a19f

File tree

2 files changed

+8
-10
lines changed

2 files changed

+8
-10
lines changed

src/unify/profiles-sync/index.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -16,13 +16,13 @@ Before you begin, prepare for setup with these tips:
1616

1717
- To connect your warehouse to Segment, you must have read and write permissions with the warehouse Destination you choose.
1818
- During step 2, you’ll copy credentials between Segment and your warehouse Destination. To streamline setup, open your Segment workspace in one browser tab and open another with your warehouse account.
19-
- Make sure to copy any IP addresses Segment asks you to allowlist in your warehouse Destination.
19+
- Make sure to copy any IP addresses Segment asks you to allowlist in your warehouse destination.
2020

2121
### Step 1: Select a warehouse
2222

23-
You’ll first choose the Destination warehouse to which Segment will sync profiles. Profiles Sync supports the Snowflake, Redshift, BigQuery, Azure, and Postgres warehouse Destinations. Your initial setup will depend on the warehouse you choose.
23+
You’ll first choose the destination warehouse to which Segment will sync profiles. Profiles Sync supports the Snowflake, Redshift, BigQuery, Azure, and Postgres warehouse Destinations. Your initial setup will depend on the warehouse you choose.
2424

25-
The following table shows the supported Profiles Sync warehouse Destinations and the corresponding required steps for each. Select a warehouse, view its Segment documentation, then carry out the warehouse’s required steps before moving to step 2 of Profiles Sync setup:
25+
The following table shows the supported Profiles Sync warehouse destinations and the corresponding required steps for each. Select a warehouse, view its Segment documentation, then carry out the warehouse’s required steps before moving to step 2 of Profiles Sync setup:
2626

2727
| Warehouse Destination | Required steps |
2828
| ------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -67,15 +67,15 @@ To connect your warehouse:
6767

6868
1. Configure your database.
6969
- Be sure to log in with a user who has read and write permissions so that Segment can write to your database.
70-
- Segment shows an IP address to allowlist. Copy it to your warehouse Destination.
70+
- Segment shows an IP address to allowlist. Copy it to your warehouse destination.
7171
2. Enter a schema name to help you identify this space in the warehouse, or use the default name provided.
7272
- The schema name can't be changed once the warehouse is connected.
7373
4. Enter your warehouse credentials, then select **Test Connection**.
7474
5. If the connection test succeeds, Segment enables the **Next** button. Select it.
7575
* If the connection test fails, verify that you’ve correctly entered the warehouse credentials, then try again.
7676

7777

78-
### Step 3: Set Selective Sync
78+
### Step 3: Set up Selective Sync
7979

8080
Set up Selective Sync to control the exact tables and columns that Segment will sync to your connected data warehouse.
8181

@@ -140,7 +140,7 @@ Reach out to [Segment support](https://app.segment.com/workspaces?contact=1){:ta
140140

141141
During setup, you can optionally materialize views on your own, or use Segment's open source dbt models.
142142

143-
You might use this option if, for example, you want to transform additional data or join Segment profile data with external data before materialization.
143+
You might want to materialize your own tables if, for example, you want to transform additional data or join Segment profile data with external data before materialization.
144144

145145
> success ""
146146
> You can alternatively use [tables that Segment materializes](/docs/unify/profiles-sync/tables/#tables-segment-materializes) and syncs to your data warehouse.

src/unify/profiles-sync/tables.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -351,10 +351,6 @@ This table has the following columns:
351351
| `timestamp` | The UTC-converted timestamp set by the Segment library. |
352352

353353

354-
<!--
355-
To do: add some info here about when customers might want to materialize tables themselves
356-
357-
-->
358354
## Tables you materialize
359355

360356
You can materialize the following tables with your own tools, or using Segment's [open-source dbt models](https://github.com/segmentio/profiles-sync-dbt){:target="_blank"}:
@@ -363,6 +359,8 @@ You can materialize the following tables with your own tools, or using Segment's
363359
- [`external_id_mapping`](#the-externalidmapping-table)
364360
- [`profile_traits`](#the-profiletraits-table)
365361

362+
You might want to materialize your own tables if, for example, you want to transform additional data or join Segment profile data with external data before materialization.
363+
366364
> success ""
367365
> You can alternatively use tables that Segment materializes and syncs to your data warehouse. [Learn more](/docs/unify/profiles-sync/tables/#tables-segment-materializes) about the tables Segment materializes.
368366

0 commit comments

Comments
 (0)