Send Time Optimization
Selects recipient-level send windows based on historical engagement where the model is eligible.
Quick verdict
Where it fits
Emarsys AI is strongest when enough commerce history exists to support its models. Data prerequisites and passed backtests are operating requirements, not implementation footnotes.
Best for
- Enterprise commerce teams using Emarsys customer data
- Programs with enough history to validate predictive lifecycle groups
Not best for
- New programs without historical customer data
- Teams needing a lightweight standalone email generator
AI features
Predictive lifecycle
Smart Insight and Max AI segments depend on data history and model readiness.
Availability
Feature entitlement varies; some predictive segments need at least seven months of suitable data and successful model backtests.
Verified against first-party material on 2026-08-02. Plans and beta access can change; verify the linked vendor page before purchase.
Limitations and tradeoffs
- Predictive capabilities may be unavailable until data and backtest thresholds are met.
- SAP documentation migration can make feature and entitlement research less direct.
Implementation notes
- Run the platform prerequisites report before committing to an AI use case.
- Define the fallback segment or timing rule for contacts without a valid prediction.