Profiles > Unify fixes

Author: rchinn1

src/unify/faqs.md

@@ -24,7 +24,7 @@ Each incoming event is analyzed and external IDs are extracted (`user_id`, `anon
 2. If Segment finds no matching profile(s), it creates one.
 3. If Segment finds one profile, it merges the incoming event with that profile. (This means that Segment adds the external IDs on the incoming message and resolves the event to the profile.)
 4. If Segment finds multiple matching profiles, Segment applies the identity resolution settings for merge protection. Specifically, Segment uses identifier limits and priorities to add the correct identifiers to the profile.
-5. Segment then applies [Profile limits](/docs/unify/profile-api-limits/) to ensure profiles remain under these limits. Segment doesn't add any further merges or mappings if the profile is at either limit, but event resolution for the profile will continue.
+5. Segment then applies [limits](/docs/unify/profile-api-limits/) to ensure profiles remain under these limits. Segment doesn't add any further merges or mappings if the profile is at either limit, but event resolution for the profile will continue.
 
 {% comment %}
 

src/unify/profiles-sync/index.md

@@ -112,19 +112,6 @@ As you use Profiles Sync, please keep the following limits in mind:
 - For every sync, the total dataset Segment can sync is limited to 20TB.
 
 
-
-### Step 3: Materialize key views using a SQL automation tool
-
-To start seeing unified profiles in your warehouse and build attribution models, you'll need to materialize the tables that Profiles Sync lands into three key views:
-
-  * `id_graph`: the current state of relationships between segment ids
-  * `external_id_mapping`: the current-state mapping between each external identifier you’ve observed and its corresponding, fully-merged `canonical_segment_id`
-  * `profile_traits`: the last seen value for all custom traits, computed traits, SQL traits, audiences, and journeys associated with a profile in a single row
-
-Please visit [Tables you materialize](/docs/profiles/profiles-sync/tables/#tables-you-materialize) for more on how to materialize these views either on your own, or with [Segment's open source dbt models](https://github.com/segmentio/profiles-sync-dbt){:target="blank"}
-
-
-
 ## Working with synced warehouses
 
 <!-- add transition line here -->

src/unify/quickstart.md

@@ -40,7 +40,7 @@ You probably have teammates who help set up your Segment Workspace with the data
    Segment recommends connecting your production website or App source as a great starting point.
 
 > info ""
-> If the source you want to add doesn't appear on the list, then check if the source is enabled. If the source is enabled, verify that you have set up a connection policy which enforces that you can only add sources with specific labels to this space. Read more about Segment's connection policy [here](/docs/profiles/identity-resolution/space-setup/#step-three-set-up-a-connection-policy).
+> If the source you want to add doesn't appear on the list, then check if the source is enabled. If the source is enabled, verify that you have set up a connection policy which enforces that you can only add sources with specific labels to this space. Read more about Segment's connection policy [here](/docs/unify/identity-resolution/space-setup/#step-three-set-up-a-connection-policy).
 
 > success ""
 > **Tip:** It sounds a little counter- intuitive to connect a production source to a developer space, but your production sources have rich user data in them, which is what you need to build and validate user profiles.