Skip to content

Update Predictions service limits #7489

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 12, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/unify/Traits/predictions/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,7 @@ This table lists the requirements for a trait to compute successfully:
| Event Types | Track at least 5 different event types in the Feature Window. |
| Historical Data | Ensure these 5 events have data spanning 1.5 times the length of the Target Window. For example, to predict a purchase propensity over the next 60 days, at least 90 days of historical data is required. |
| Subset Audience (if applicable) | Ensure the audience contains more than 1 non-anonymous user. |
| User Limit | Ensure that you are making a prediction for fewer than 100 million users. If you track more than 100 million users in your space, define a smaller audience in the **Make a Prediction For** section of the custom predictions builder. |
| User Limit | Ensure that you are making a prediction for fewer than 20 million users. If you track more than 20 million users in your space, define a smaller audience in the **Make a Prediction For** section of the custom predictions builder. |
| User Activity | At least 100 users performing the Target Event and at least 100 users not performing the Target Event. |

#### Selecting events (optional)
Expand Down
Loading