Test networks are unable to provide forecasts that would be comparable to the production environment because forecasts require traffic history. In the sandbox environment, a consistent behavior can be expected for forecast requests, according to the following rules:
Inputs ( {@code LineItem} Fields) | Outputs ( {@code Forecast} Fields) | ||||
---|---|---|---|---|---|
{@link LineItem#lineItemType lineItemType} | {@link LineItem#unitsBought unitsBought} | {@link Forecast#availableUnits availableUnits} | {@link Forecast#forecastUnits forecastUnits (matchedUnits)} | {@link Forecast#deliveredUnits deliveredUnits} | Exception |
Sponsorship | 13 | –– | –– | –– | {@link ForecastError.Reason#NO_FORECAST_YET NO_FORECAST_YET} |
Sponsorship | 20 | –– | –– | –– | {@link ForecastError.Reason#SERVER_NOT_AVAILABLE SERVER_NOT_AVAILABLE} |
Sponsorship | 50 | 1,200,000 | 6,000,000 | 600,000 For prospective: 0 | –– |
Sponsorship | != 20 and != 50 | 1,200,000 | 1,200,000 | 600,000 For prospective: 0 | –– |
Not Sponsorship | <= 1,000,000 | unitsBought * 2 | availableUnits * 3 | 600,000 For prospective: 0 | –– |
Not Sponsorship | > 1,000,000 | unitsBought / 2 | availableUnits * 3 | 600,000 For prospective: 0 | –– |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|