Skip to content

Commit d146948

Browse files
authored
Unify onboarding edits
1 parent 5249045 commit d146948

File tree

1 file changed

+26
-19
lines changed

1 file changed

+26
-19
lines changed

src/unify/quickstart.md

Lines changed: 26 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Unify Onboarding Guide
33
plan: unify
44
---
55

6-
This guide walks you through the set up process for a simple Unify space, which you can use if your Segment implementation is simple. If your implementation is complex, you can use this to demonstrate and test Unify before working on a more complex configuration.
6+
This guide walks you through the setup process for a simple Unify space, which you can use if your Segment implementation is simple. If your implementation is complex, you can use this to demonstrate and test Unify before working on a more complex configuration.
77

88
> success ""
99
> If you're using Engage, visit the [Engage Foundations Onboarding Guide](/docs/engage/quickstart) for additional steps to create audiences, connect to destinations, and more.
@@ -16,54 +16,61 @@ To configure and use Unify, you need the following:
1616
2. **Events flowing into Connections** from your digital properties where most of your valuable user behavior occurs.
1717
3. **Unify or Engage identity admin access.** You must have edit access to identity resolution rules. You can check your permissions by navigating to [Access Management](https://app.segment.com/goto-my-workspace/settings/access-management){:target="_blank"} in your workspace settings. See the [Segment Access Management documentation](/docs/segment-app/iam/) for more details.
1818

19-
## Step 1: Create a new Developer space
19+
## Step 1: Create a new developer space
2020

21-
When you first start working with Unify, you should start by creating a "Developer" space. This is your experimental and test environment while you learn more about how Unify works. You can validate that identity resolution is working correctly in the Developer space, and then apply those changes to your *Production* space once you're sure everything is working as expected.
21+
When you start working with Unify, begin by creating a "Developer" space. This is your experimental and test environment while you learn more about how Unify works. You can validate that identity resolution is working correctly in the Developer space and then apply those changes to your Production space once you're sure everything is working as expected.
2222

2323
This two-space method prevents you from making untested configuration changes that immediately affect production data.
2424

25-
<!-- TODO: I can't see this in any of the spaces I'm an admin in
2625
To create a Engage space:
27-
1. In your Segment workspace, click **Engage** from the left-navigation.
28-
2. -->
26+
27+
1. In your Segment workspace, click **Engage**.
28+
2. Click **+ Create Space** and set up your space. Select **Dev space** to create a developer space.
29+
3. Follow the instructions to set identity rules, connect sources, and sync Profiles to your warehouse.
2930

3031
## Step 2: Invite teammates to your Segment space
3132

32-
You probably have teammates who help set up your Segment Workspace with the data you need. Invite them to your Unify dev space and grant them access to the space. Navigate to [Access Management](https://app.segment.com/goto-my-workspace/settings/access-management){:target="_blank"} in your workspace settings to add them.
33+
You can grant teammates access to your Segment workspace so they can access and set up data as you need. To invite them to your Unify dev space:
3334

34-
<!-- TODO: actually add steps here -->
35+
1. Navigate to **Settings > [Access Management](https://app.segment.com/goto-my-workspace/settings/access-management){:target="_blank"}**.
36+
2. Click **+ Invite Team Member** and enter the email addresses of the teammates you want to invite to your workspace.
37+
3. Choose the type of access and roles you want to assign them.
38+
4. Click **Invite** to send the invitation.
3539

3640
## Step 3: Connect production sources
3741

38-
1. From your Segment space, navigate to **Unify settings** and click **Profile sources**.
39-
2. On the screen that appears, choose one or two production sources from your Connections workspace.
40-
Segment recommends connecting your production website or App source as a great starting point.
42+
Add production sources to your Unify space:
43+
44+
1. From your Segment workspace, navigate to **Unify > Unify settings**, and click **Profile sources**.
45+
2. Click **+ Connect source** and choose one or two production sources from your Connections workspace. We recommend connecting your production website or App source as a starting point.
4146

4247
> info ""
43-
> 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 in the [Space Setup](/docs/unify/identity-resolution/space-setup/#step-three-set-up-a-connection-policy) docs.
48+
> If the source you want to add doesn't appear on the list, then check if the source is enabled in the source's settings.
49+
>
50+
> 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 in the [Space Setup](/docs/unify/identity-resolution/space-setup/#step-three-set-up-a-connection-policy) docs.
4451
4552
> success ""
46-
> **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.
53+
> Although connecting a production source to a developer space may seem counter-intuitive, production sources contain rich user data required to build and validate user profiles.
4754
4855
Once you select sources, Segment starts a replay of one month of historical data from these sources into your Unify space. Segment does this step first so you have some user data to build your first profiles.
4956

50-
The replay usually takes several hours, but the duration will vary depending on how much data you have sent through these sources in the past one month. When the replay finishes, you are notified in the Sources tab under Settings, shown below.
57+
The replay usually takes several hours, but the duration will vary depending on how much data you have sent through these sources in the past month. When the replay finishes, you are notified in the Sources tab under Settings.
5158

5259
> warning ""
53-
> **Note**: Data replays start with the earliest (oldest) chronological events in the one month window, and finish with the most recent. Don't continue to the next step until all replays are marked complete. If you do, the data in your Unify data will be stale.
60+
> Data replays start with the earliest (oldest) chronological events in the one month window, and finish with the most recent. Don't continue to the next step until all replays are marked complete. If you do, the data in your Unify data will be stale.
5461
5562
Once the Source(s) finish replaying, data from your connected Sources flows into Unify in near real time, just like it does for sources in your Segment workspace.
5663

5764

5865
## Step 4: Check your profile data
5966

60-
Once the replay finishes, you can see the data replayed into Unify using the Profile explorer. You should have a lot! The data should include information from multiple sources and multiple sessions, all resolved into a single profile per user.
67+
Once the replay finishes, you can see the data replayed into Unify using the Profile explorer. The data should include information from multiple sources and multiple sessions, all resolved into a single profile per user.
6168

6269
Before you continue, check a few user profiles to make sure they show an accurate and recent snapshot of your users.
6370

64-
A good test is to look at _your own_ user profile, and maybe some colleagues' profiles. Look in the Profile explorer for your Profile, and look at your event history, custom traits and identifiers. If these identifiers look correct across a few different profiles (and you can verify that they are all correct), then you're ready to create an audience.
71+
To test this, look at _your own_ user profile, and maybe some colleagues' profiles. Look in the Profile explorer for your Profile, and look at your event history, custom traits and identifiers. If these identifiers look correct across a few different profiles (and you can verify that they are all correct), then you're ready to create an audience.
6572

66-
If your user profiles look wrong, or you aren't confident users are being accurately defined and merged, stop here and troubleshoot. It's important to have accurate identity resolution before you continue. See the [detailed Identity Resolution documentation](/docs/unify/identity-resolution/) to better understand how it works, and why you may be running into problems. (Still need help? [Contact Segment](https://segment.com/help/contact/){:target="_blank"} for assistance.)
73+
If your user profiles look wrong, or you aren't confident users are being accurately defined and merged, stop here and troubleshoot. It's important to have accurate identity resolution before you continue. See the [detailed Identity Resolution documentation](/docs/unify/identity-resolution/) to better understand how it works, and why you may be running into problems. If you still need help [contact Segment](https://segment.com/help/contact/){:target="_blank"} for assistance.
6774

6875
> info ""
6976
> Identify events triggered by a user don't appear in the Events tab of their profile. However, the traits from these events are still assigned to the profile. You can view them under the Traits tab.
@@ -72,7 +79,7 @@ If your user profiles look wrong, or you aren't confident users are being accura
7279

7380
## Step 5: Create your production space
7481

75-
Once you validate that your data is flowing through Unify, you're ready to create a Production space. Segment recommends that you repeat the same steps outlined above, focusing on your production use cases and data sources.
82+
Once you validate that your data is flowing through Unify, you're ready to create a Production space. We recommend that you repeat the same steps for [creating a developer space](#step-1-create-a-new-developer-space), with a focus on your production use cases and data sources.
7683

7784
> success ""
7885
> If you're using Engage, view additional steps to complete your space set up in the [Engage Foundations Onboarding Guide](/docs/engage/quickstart).

0 commit comments

Comments
 (0)