Limits to confirm before launch
Salesforce Personalization and Data Cloud enforce per-org limits on things like recommenders, request rates, and data-graph size. Check your expected volume against the current limits before go-live, so you can request an increase from Salesforce in good time if you’re close to one.
Limit areas to check
| Limit area | Scope | Current value |
|---|---|---|
| Recommenders per org | Org-wide, across all data spaces | See Salesforce's current limits documentation |
| Objective-based recommenders using the Personalization Card | Per org | See Salesforce's current limits documentation |
| Recommendation requests per minute | Per tenant | See Salesforce's current limits documentation |
| Recommender objectives | Per org | See Salesforce's current limits documentation |
| Filter conditions per include/exclude filter | Per filter | See Salesforce's current limits documentation |
| Calculated insight values considered per recommendation | Per item data graph | See Salesforce's current limits documentation |
| Direct related objects on an item data graph | Per data graph | See Salesforce's current limits documentation |
| Decisioning API and Ingestion API request rate | Per org/tenant | See Salesforce's current limits documentation |
Discussion
Comments are not configured for local development. They appear once the site owner connects GitHub Discussions (Giscus).