Merge pull request #4927 from segmentio/profile-trait-updates-table

Add profile_traits_updates table

Author: rchinn1

src/unify/files/ERD.png

@@ -110,7 +110,7 @@ Profiles Sync sends profiles to your warehouse on an hourly basis, beginning aft
 
 When Segment runs historical backfills:
 
-- The `id_graph_updates` and `external_id_mapping_updates` tables sync your entire historical data to your warehouse.
+- The `id_graph_updates`, `external_id_mapping_updates`, and `profile_traits_updates` tables sync your entire historical data to your warehouse.
 - Profiles Sync gathers the last two months of all events, including those from the `identities`, `page`, `screens`, and `tracks` tables, and syncs them to your warehouse.
 
 Segment lands the data on an internal staging location, then removes the backfill banner. Segment then syncs the backfill data to your warehouse.

src/unify/profiles-sync/index.md

@@ -146,6 +146,19 @@ The anonymous site visits sample used earlier would generate the following event
 
 In this table, Segment shows three observed identifiers. For each of the three identifiers, Segment outputs the Segment ID initially associated with the identifier.
 
+### The profile_traits_updates table
+
+The `profile_traits_updates` table maps each `segment_id` with all associated profile traits. 
+
+Segment updates this table:
+- for each identify call that updates one or more traits for a `segment_id`.
+- for any merge where traits from two previously separated profiles are now combined. 
+
+In the event that two profiles merge, Segment only updates the `profile_traits_updates` table for the `canonical_segment_id`, or the fully merged id.
+
+From the `profile_traits_updates` table, use Segment's [open-source dbt models](https://github.com/segmentio/profiles-sync-dbt){:target="_blank"}, or your own tools to materialize the [`profile_traits`](#the-profile-traits-table) table with all profiles and associated profile traits in your data warehouse. 
+
+
 ### The identifies, page, screens, and track tables
 
 These tables show the instrumented events themselves. Entries in these tables reflect payloads that you instrument according to the Segment spec.
@@ -181,9 +194,11 @@ And two entries in the `identifies` table:
 
 All these events were performed by the same person. If you use these tables to assemble your data models, though, always join them against `id_graph` to resolve each event’s `canonical_segment_id`.
 
+
 > info ""
 > You might see columns appended with `hidden_entry` or `hidden_entry_joined_at` in profile data of users in Journeys. Segment uses these for internal purposes, and they do not require any attention or action.
 
+
 ### Profiles Sync schema
 
 Profiles Sync uses the following schema: `<profiles_space_name>.<tableName>`.