Skip to content

Commit 10e2845

Browse files
markzegarellimarkzegarelli
committed
DOC-183 restructure
1 parent 90715aa commit 10e2845

File tree

5 files changed

+59
-35
lines changed

5 files changed

+59
-35
lines changed

‎src/_data/sidenav/main.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -276,6 +276,8 @@ sections:
276276
title: Journeys Best Practices and FAQ
277277
- path: /personas/journeys/use-cases
278278
title: Example Journeys Use Cases
279+
- path: /personas/journeys/key-terms
280+
title: Journeys Glossary
279281
- path: /personas/using-personas-data
280282
title: Using Personas data
281283
- path: /personas/warehouses

‎src/personas/journeys/images/journeys-teaser.mp4

5.02 MB
Binary file not shown.

‎src/personas/journeys/images/journeys-teaser.webm

2.4 MB
Binary file not shown.

‎src/personas/journeys/index.md

Lines changed: 18 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -2,52 +2,35 @@
22
title: Journeys Overview
33
---
44

5-
Journeys, a feature of Segment Personas, provide a way for marketers to personalize experiences through planning how and when to engage customers with the right campaigns and messages.
5+
Journeys, a feature of Segment Personas, provides a way for marketers to personalize experiences through planning how and when to engage customers with the right campaigns and messages.
66

7-
Journeys enable you to define steps in a user's journey based on event behavior and traits. You can build Journeys from your tracking events, traits, computed traits, or audiences. At each step of a journey, you can send your list of users to any personas-compatible destination.
8-
9-
## Key terms
10-
11-
Keep the following terms in mind as you begin to explore Journeys.
7+
<video width="690px" controls autoplay>
8+
<source src="images/journeys-teaser.webm" type="video/webm">
9+
<source src="images/journeys-teaser.mp4" type="video/mp4">
10+
</video>
1211

13-
### General
14-
15-
| Term | Definition |
16-
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
17-
| Journey | A multi-step workflow that progresses users through steps based on time logic, real-time customer interactions, and customer traits. |
18-
| Journey list view | The Journeys tab shows all Journeys in the selected Personas space. |
19-
| Journey builder | A visual canvas where you can view and edit step definitions and types. |
20-
| Journey overview | A visual canvas where you can view all steps and definitions. |
21-
22-
### Steps
12+
Journeys enable you to define steps in a user's journey based on event behavior and traits. You can build Journeys from your tracking events, traits, computed traits, or audiences. At each step of a journey, you can send your list of users to any personas-compatible destination.
2313

24-
| Term | Definition |
25-
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
26-
| Step | An individual point in the Journey that can be any of the following: **Wait for condition**, **Wait for duration**, **True/false split**, **Multi-branch split**, **Send to destinations**. |
27-
| Branch | Paths that lead users away from a step. For example, A True/false split creates one True branch and one False branch. |
28-
| Entry condition | The first step in the Journey where you define the entry criteria. In this step, you can backfill historical data and preview users before you publish the Journey. |
29-
| Wait for condition | A step in which you define one or more conditions which a user must fulfill to move to this step. |
30-
| Wait for duration | A step in which you define the amount of time before the user moves to the next step. |
31-
| True/false split | A step in which you define a condition to direct a user to A step in which you define a condition to direct user to one of two steps. <br /> <br />Users who fulfill the condition move to the `true` branch. Users who do not move to the `false` branch. |
32-
| Multi-branch split | A step in which you define any number of conditions. Each condition represents a separate branch leading away from the step. Users travel down the branch of the condition they meet. <br /> <br /> Journeys does not enforce mutual exclusivity in branch conditions . For more information, see [Best Practices](#). |
33-
| Send to destinations | A step in which you can send track or identify calls to Event destinations, or a list of users to a List destination. |
34-
| Step name | The name of the step that displays in the Journey builder and overview. |
35-
| Key | Name of the Send to Destination step used to identify the step users are on when Journeys sends information to the destination. For Track events, the property name uses this key. For Identify events, the trait name uses this key. <br /><br />For more information, see [Send data to Destinations](#). |
14+
## Get started
3615

37-
### Statuses
16+
Start with the visual builder to define entrance criteria, build out conditional branching logic, then focus messaging to drive conversion. Cart abandonment campaigns, trial conversions, and onboarding flows are great examples to get started from. For more information, see [Build a Journey](/docs/personas/journeys/build-journey.md).
3817

39-
| Term | Definition |
40-
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------- |
41-
| Draft Journey | A Journey which is not yet computing nor sending data to destinations. <br /><br />For more information, see [Draft Journeys](#draft-journeys). |
42-
| Published (live) Journey | A Journey that is computing and sending data to destinations. <br /><br />For more information, see [Published Journeys](#published-journeys). |
18+
## Send data to your destinations
4319

20+
Connect destinations to your Journey to send events or user lists when users reach the corresponding step in the Journey. For more information, see [Send Journeys data to a Destination](/docs/personas/journeys/send-data).
4421

45-
### Journeys Product Limits
22+
## Best practices and FAQ
4623

47-
For information about Product Limits related to journeys, see [Product Limits - Journeys](/docs/personas/product-limits#journeys).
24+
For information about best practices for getting started with Journeys, and to view frequently asked questions about Journeys, see [Best Practices and FAQ](/docs/personas/journeys/faq-best-practices).
4825

26+
## Journeys use cases
4927

28+
See [Examples Journeys Use Cases](docs/personas/journeys/use-cases/) for examples of ways you can use Journeys in your marketing workflow.
5029

30+
## Journeys glossary
5131

32+
For a list of key terms related to Journeys, see [Journeys Key Terms](/docs/personas/journeys/key-terms).
5233

34+
## Journeys Product Limits
5335

36+
For information about Product Limits related to journeys, see [Product Limits - Journeys](/docs/personas/product-limits#journeys).

‎src/personas/journeys/key-terms.md

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
---
2+
title: Journeys Key Terms
3+
---
4+
5+
Keep the following terms in mind as you begin to explore Journeys.
6+
7+
## General
8+
9+
| Term | Definition |
10+
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
11+
| Journey | A multi-step workflow that progresses users through steps based on time logic, real-time customer interactions, and customer traits. |
12+
| Journey list view | The Journeys tab shows all Journeys in the selected Personas space. |
13+
| Journey builder | A visual canvas where you can view and edit step definitions and types. |
14+
| Journey overview | A visual canvas where you can view all steps and definitions. |
15+
16+
## Steps
17+
18+
| Term | Definition |
19+
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
20+
| Step | An individual point in the Journey that can be any of the following: **Wait for condition**, **Wait for duration**, **True/false split**, **Multi-branch split**, **Send to destinations**. |
21+
| Branch | Paths that lead users away from a step. For example, A True/false split creates one True branch and one False branch. |
22+
| Entry condition | The first step in the Journey where you define the entry criteria. In this step, you can backfill historical data and preview users before you publish the Journey. |
23+
| Wait for condition | A step in which you define one or more conditions which a user must fulfill to move to this step. |
24+
| Wait for duration | A step in which you define the amount of time before the user moves to the next step. |
25+
| True/false split | A step in which you define a condition to direct a user to A step in which you define a condition to direct user to one of two steps. <br /> <br />Users who fulfill the condition move to the `true` branch. Users who do not move to the `false` branch. |
26+
| Multi-branch split | A step in which you define any number of conditions. Each condition represents a separate branch leading away from the step. Users travel down the branch of the condition they meet. <br /> <br /> Journeys does not enforce mutual exclusivity in branch conditions . For more information, see [Best Practices](#). |
27+
| Send to destinations | A step in which you can send track or identify calls to Event destinations, or a list of users to a List destination. |
28+
| Step name | The name of the step that displays in the Journey builder and overview. |
29+
| Key | Name of the Send to Destination step used to identify the step users are on when Journeys sends information to the destination. For Track events, the property name uses this key. For Identify events, the trait name uses this key. <br /><br />For more information, see [Send data to Destinations](#). |
30+
31+
## Statuses
32+
33+
| Term | Definition |
34+
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------- |
35+
| Draft Journey | A Journey which is not yet computing nor sending data to destinations. <br /><br />For more information, see [Draft Journeys](#draft-journeys). |
36+
| Published (live) Journey | A Journey that is computing and sending data to destinations. <br /><br />For more information, see [Published Journeys](#published-journeys). |
37+
38+
39+

0 commit comments

Comments
 (0)