Skip to content

Commit 70fd642

Browse files
committed
Update intro
1 parent 33c1c3a commit 70fd642

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

src/unify/profiles-sync/tables.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -222,13 +222,11 @@ Follow the steps below to change your schema name:
222222

223223
## Tables Segment materializes
224224

225-
With Profiles Sync, you can access the following three materialized view tables:
225+
With Profiles Sync, you can access the following three tables that Segment materializes for a more complete view of your profile:
226226
- [`user_traits`](#the-user_traits-table)
227227
- [`user_identifiers`](#the-user_identifiers-table)
228228
- [`profile_merges`](#the-profile_merges-table)
229229

230-
Use these tables that Segment materializes for a more complete view of your profile.
231-
232230
Visit the [selective sync](/docs/unify/profiles-sync/#using-selective-sync) setup page to enable the following materialized tables, which Segment disables by default.
233231

234232
You can also use [historical backfill](/docs/unify/profiles-sync/#using-historical-backfill) with tables Segment materializes.
@@ -294,7 +292,7 @@ The `profile_merges` table contains all mappings from a `segment_id` to a profil
294292

295293
With the `profile_merges` table:
296294
- There's one row per profile associated with the `canonical_segment_id` that represents the profile. This view is a fixed schema.
297-
- When a profile is created, a new row is created with the `segment_id` and `segment_canonical_id` having the same value.
295+
- When a profile is created, a new row is created with the `segment_id` and `canonical_segment_id` having the same value.
298296

299297

300298
When a merge occurs:

0 commit comments

Comments
 (0)