Skip to content

Commit 20c369d

Browse files
committed
Update Build a Predictive Trait Page
1 parent e9b9046 commit 20c369d

File tree

1 file changed

+22
-22
lines changed
  • src/engage/audiences/predictive-traits

1 file changed

+22
-22
lines changed

src/engage/audiences/predictive-traits/index.md

Lines changed: 22 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -3,17 +3,17 @@ title: Predictive Traits
33
plan: engage-foundations
44
---
55

6-
Predictions, Segment's artificial intelligence and machine learning feature, lets you predict the likelihood that users will perform any event tracked in Segment.
6+
Predictive Traits, Segment's artificial intelligence and machine learning feature, lets you predict the likelihood that users will perform any event tracked in Segment.
77

8-
With Predictions, you can identify users with, for example, a high propensity to purchase, refer a friend, or use a promo code. Predictions also lets you predict a user's lifetime value (LTV).
8+
With Predictive Traits, you can identify users with, for example, a high propensity to purchase, refer a friend, or use a promo code. Predictive Traits also lets you predict a user's lifetime value (LTV).
99

10-
Segment saves Predictions to user profiles, letting you build Audiences, trigger Journeys, and send data to downstream Destinations.
10+
Segment saves Predictive Traits to user profiles, letting you build Audiences, trigger Journeys, and send data to downstream Destinations.
1111

1212
On this page, you'll learn how to build a Predictive Trait.
1313

14-
## Access and build a Prediction
14+
## Access and build a Predictive Trait
1515

16-
To create a Prediction, you'll first request demo access, then build a Predictive Trait.
16+
To create a Predictive Trait, you'll first request access, then build a Predictive Trait.
1717

1818
![The Predictive Trait builder in the Segment UI](../../images/trait_builder.png)
1919

@@ -22,14 +22,14 @@ To create a Prediction, you'll first request demo access, then build a Predictiv
2222
Follow these steps to access Predictive Trait:
2323

2424
1. Navigate to **Engage > Audiences > Computed Traits**. Select **Create computed trait**.
25-
2. Select **Request Demo** to access Predictive Traits.
25+
2. Select **Request Access** to access Predictive Traits.
2626

2727
### Build a Predictive Trait
2828

2929
Once your Workspace is enabled for Predictive Traits, follow these steps to build a Predictive Trait:
3030

3131
3. In the Trait Builder, select **Predictive Traits**, choose the Trait you want to create, then click **Next**.
32-
- Choose **Custom Predictive Goal**, **Likelihood to Purchase**, or **Predicted Lifetime Value**.
32+
- Choose **Custom Predictive Goal**, **Likelihood to Purchase**, **Predicted Lifetime Value**, or **Likelihood to Churn**.
3333
4. (For custom Predictive Goals) Add a condition(s) and event to predict, then select **Calculate**. If you're satisfied with the available data, select **Next**.
3434
5. (Optional) Connect a Destination, then select **Next**.
3535
6. Add a name and description for the Trait, then select **Create Trait**.
@@ -38,7 +38,7 @@ In the next section, you'll learn more about the four available Predictive Trait
3838

3939
## Choosing a Predictive Trait
4040

41-
Segment offers four Predictive Traits: Custom Predictive Goals, Likelihood to Purchase, and Predicted LTV.
41+
Segment offers four Predictive Traits: Custom Predictive Goals, Likelihood to Purchase, Predicted LTV, and Likelihood to Churn.
4242

4343
### Custom Predictive Goals
4444

@@ -50,39 +50,39 @@ When you build a Custom Predictive Goal, you'll first need to select a cohort, o
5050

5151
#### Target event
5252

53-
The target event is the Segment event that you want to predict a user's likelihood to perform. Predictions work better when many customers have performed the event.
53+
The target event is the Segment event that you want to predict. In creating a Prediction, Segment determines the likelihood of the user performing the target event. Predictions work better when many customers have performed the event.
5454

5555
#### Data requirements
5656

57-
Segment doesn't enforce data requirements for predictions. In machine learning, however, data quality and quantity are critical. Segment recommends that you make predictions for at least 50,000 users and choose a target event that at least 5,000 users have performed in the last 30 days.
57+
Segment doesn't enforce data requirements for Predictions. In machine learning, however, data quality and quantity are critical. Segment recommends that you make Predictions for at least 50,000 users and choose a target event that at least 5,000 users have performed in the last 30 days.
5858

59-
You can create predictions outside of these suggestions, but your results may vary.
59+
You can create Predictions outside of these suggestions, but your results may vary.
6060

6161
### Likelihood to Purchase
6262

63-
Likelihood to Purchase is identical to Custom Predictive Goals, but Segment prefills the **Order Completed** event, assuming it's tracked in your Segment instance.
63+
Likelihood to Purchase is identical to Custom Predictive Goals, but Segment prefills the **`Order Completed`** event, assuming it's tracked in your Segment instance.
6464

65-
If you don’t track Order Completed, choose a target event that represents a customer making a purchase.
65+
If you don’t track `Order Completed`, choose a target event that represents a customer making a purchase.
6666

6767
### Predicted Lifetime Value
6868

69-
Predicted Lifetime Value predicts a customer's future spend over the next 90 days. To create this prediction, select a purchase event, revenue property, and the currency (which defaults to USD). The following table contains details for each property:
69+
Predicted Lifetime Value predicts a customer's future spend over the next 90 days. To create this Prediction, select a purchase event, revenue property, and the currency (which defaults to USD). The following table contains details for each property:
7070

71-
| Property | Description |
72-
| --------------- | ---------------------------------------------------------------------------------------------------------------------------- |
73-
| Purchase event | Choose a target event that represents a customer making a purchase. For most companies, this is usually **Order Completed**. |
74-
| Purchase amount | Select the purchase event property that represents the total amount. For most companies, this is the **Revenue** property. |
75-
| Currency | Segment defaults all currencies to USD. |
71+
| Property | Description |
72+
| --------------- | -------------------------------------------------------------------------------------------------------------------------- |
73+
| Purchase event | Choose a target event that represents a customer making a purchase. For most companies, this is usually `Order Completed`. |
74+
| Purchase amount | Select the purchase event property that represents the total amount. For most companies, this is the `Revenue` property. |
75+
| Currency | Segment defaults all currencies to USD. |
7676

7777
### Likelihood to Churn
7878

79-
Likelihood to Churn proactively identifies customers who are likely to stop using your product. Segment builds this trait by determining whether or not a customer will perform a certain action.
79+
Likelihood to Churn proactively identifies customers likely to stop using your product. Segment builds this Prediction by determining whether or not a customer will perform a certain action.
8080

8181
To use Likelihood to Churn, you'll need to specify a customer event, a future time frame for which you want the prediction to occur, and if you want to know whether the customer will or won't perform the event.
8282

83-
For example, suppose you wanted to predict whether or not a customer would view a page on your site over the next three months. You would select `not perform`, `Page Viewed`, and at least one time within `90 days`.
83+
For example, suppose you wanted to predict whether or not a customer would view a page on your site over the next three months. You would select `not perform`, `Page Viewed`, and `at least 1 time within 90 days`.
8484

85-
Segment would then build the trait from this criteria and create specific percentile cohorts. You can then use these cohorts to target customers with retention flows, promo codes, or one-off email and SMS campaigns.
85+
Segment would then build the Prediction from this criteria and create specific percentile cohorts. You can then use these cohorts to target customers with retention flows, promo codes, or one-off email and SMS campaigns.
8686

8787
#### Data requirements
8888

0 commit comments

Comments
 (0)