Skip to content

Commit f37143c

Browse files
authored
minor rewording
1 parent 1b61199 commit f37143c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/unify/Traits/predictions/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ The target event is the Segment event that you want to predict. In creating a pr
5656

5757
#### Selecting events (optional)
5858

59-
Some customers want to specifically include or exclude events that get fed into the model. For example, if you track different events from an EU vs US storefront, and you only want to make predictions using data from the US, you could unselect the events from the EU space. This step is entirely optional, so we only suggest using it if you have a clear reason in mind for removing events from becoming a factor in the model
59+
Some customers want to specifically include or exclude events that get fed into the model. For example, if you track different events from an EU storefront compared to a US storefront and you only want to make predictions using data from the US, you could unselect the events from the EU space. This step is optional, Segment only recommends using it if you have a clear reason in mind for removing events from becoming a factor in the model.
6060

6161

6262
#### Data requirements
@@ -92,9 +92,9 @@ To use Likelihood to Churn, you'll need to specify a customer event, a future ti
9292

9393
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`.
9494

95-
Churn predictions are only made for customers that are eligible. In the example above, only the customers that have performed Page Viewed in the last 90 days would be eligible to recieve this prediction. The in app UI will tell you which customers are eligibile to recieve this prediction.
95+
Churn predictions are only made for eligible customers. In the previous example, only customers that have performed `Page Viewed` in the last 90 days would be eligible to recieve this prediction. The Segment app shows you which customers are eligibile to recieve this prediction.
9696

97-
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.
97+
Segment then uses this criteria to build the prediction 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.
9898

9999

100100
## Use cases

0 commit comments

Comments
 (0)