You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/unify/Traits/predictions/using-predictions.md
+21-23Lines changed: 21 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,49 +70,47 @@ Predictions may not be as beneficial in the following situations:
70
70
-**When you sell limited but highly-priced items**, like enterprise software, complex medical machines, and so on; this also applies if you're in the B2B sector.
71
71
-**When you don't yet have enough data**; your model could produce errors if, for example, your target is too new and lacks sufficient data. Waiting a month could allow Segment to gather more predictive data.
72
72
73
-
## Frequently asked questions
73
+
## FAQs
74
+
75
+
#### What type of machine learning model do you use?
74
76
75
-
{% faq %}
76
-
{% faqitem What type of machine learning model do you use? %}
77
77
Segment uses a binary classification model that uses decision trees.
78
-
{% endfaqitem %}
79
78
80
-
{% faqitem What level of confidence can I have in my predictions? %}
79
+
#### What level of confidence can I have in my predictions?
80
+
81
81
Once Segment creates your prediction, you can check the model statistics page, where Segments shows you how the model was created. Segment also maintains automated systems that monitor model performance and will alert you if your model is not predictive.
82
-
{% endfaqitem %}
83
82
84
-
{% faqitem How long do predictions take to create? %}
83
+
#### How long do predictions take to create?
84
+
85
85
Trait creation depends on the amount of data, but Segment expects predictions to be completed in around 24 hours. For larger customers, however, this could take 48 hours. Predictions shows a status of `In Progress` while computing; Segment updates this status when customers are scored.
86
-
{% endfaqitem %}
87
86
88
-
{% faqitem What are AUC, log loss, and lift quality? %}
87
+
#### What are AUC, log loss, and lift quality?
88
+
89
89
These data science statistics measure the effectiveness of Segment's predictions when tested against historical data. For more information, refer to [ROC Curve and AUC](https://developers.google.com/machine-learning/crash-course/classification/roc-and-auc){:target="_blank"}, [The Lift Curve in Machine Learning](https://howtolearnmachinelearning.com/articles/the-lift-curve-in-machine-learning/){:target="_blank"}, and [Intuition behind log-loss score](https://towardsdatascience.com/intuition-behind-log-loss-score-4e0c9979680a){:target="_blank"}.
90
-
{% endfaqitem %}
91
90
92
-
{% faqitem What is the Prediction Quality Score? %}
91
+
#### What is the Prediction Quality Score?
92
+
93
93
The Prediction Quality Score factors AUC, log loss, and lift quality to determine whether Segment recommends using the prediction. A model can have a score of Poor, Fair, Good, or Excellent.
94
-
{% endfaqitem %}
95
94
96
-
{% faqitem How do you store trait values? %}
95
+
#### How do you store trait values?
96
+
97
97
The created trait value represents the user's percentile cohort. This value refreshes every seven days. If you see `0.85` on a user's profile, this means the user is in the 85th percentile, or the top 15% for the prediction.
98
-
{% endfaqitem %}
99
98
100
-
{% faqitem How frequently do you re-train the model? %}
99
+
#### How frequently do you re-train the model?
100
+
101
101
Segment rebuilds the machine learning model every 30 days.
102
-
{% endfaqitem %}
103
102
104
-
{% faqitem How frequently do you update trait values? %}
103
+
#### How frequently do you update trait values?
104
+
105
105
Every seven days.
106
-
{% endfaqitem %}
107
106
108
-
{% faqitem How many predictions can I have? %}
107
+
#### How many predictions can I have?
108
+
109
109
You get five predictions as part of Engage Foundations or Unify Plus. To purchase more predictions, reach out to your CSM.
110
-
{% endfaqitem %}
111
110
112
-
{% faqitem Are there any known Predictions limitations? %}
111
+
#### Are there any known Predictions limitations?
112
+
113
113
Yes. Keep the following in mind when you work with Predictions:
114
114
115
115
-**Predictions made for more than 100 million users will fail.** Segment recommends making predictions only for non-anonymous users, or, as an alternative, use the Starting Cohort to narrow down the audience for which you want to make a prediction.
116
116
-**Predictions may not work as intended if you track more than a thousand unique events in your workspace.** If this applies to your use case, [contact Segment Support](https://segment.com/help/contact/){:target="_blank"} for help with removing unused events, which will allow you to create predictions.
Copy file name to clipboardExpand all lines: src/unify/identity-resolution/index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,9 +26,9 @@ Identity Resolution sits at the core of Segment. The Identity Graph merges the c
26
26
4.**Maintains persistent ID** - multiple external IDs get matched to one persistent ID
27
27
28
28
29
-
## Frequently asked questions
29
+
## FAQs
30
30
31
-
### Can I use the Profile API on the client-side?
31
+
####Can I use the Profile API on the client-side?
32
32
For security reasons, Segment requires that the [Profile API](/docs/unify/profile-api/) only be used server-side. The Profile API allows you to look up data about any user given an identifier (for example, email, `anonymousId`, or `userId`) and an authorized access secret. While this enables powerful personalization workflows, it could also let your customers' data fall into the wrong hands if the access secret were exposed on the client.
33
33
34
34
Instead, by creating an authenticated personalization endpoint server-side backed by the Profile API, you can serve up personalized data to your users without the risk of their information falling into the wrong hands.
0 commit comments