This document will help you to learn how forecasting works in Zoho Analytics and how you can easily set up the same in your charts.
Forecasting is a process of predicting the future based on the past data trend. Zoho Analytics forecasting is based on powerful forecasting algorithms which analyzes your past data deeply and comes up with the best forecast for the future.
Zoho Analytics supports forecasting for the following chart types.
Yes, you can set up forecasting over multiple Y-Axis in a chart.
Forecasting will be enabled when it matches certain conditions, which are briefed below:
Zoho Analytics offers a powerful forecasting engine which predicts future data points based on past data. The forecasting engine offers a range of customizations such as number of units to be forecasted, number of data points to be ignored in the past data and the formatting to be applied over the forecasted data points.
The following points describe how the forecasting engine works in Zoho Analytics:
The chart could have been shared with different filter criteria to the shared users. Number of past data points available in the shared data could very for different shared users, hence the forecasted points are different for shared users.
The forecasted points will not have underlying data generated for each of the forcasted data points. Hence, View Underlying Data and Drill Down options will not be available for forecasted data points.
The Forecast Model dialog will open displaying the following information.
General Information
The General Information section displays the following information:
The Model Information section displays the applied model details.
| Field | Description |
| Common Fields | |
| Forecast Model | One of the four forecast models applied over the chart. |
| {Forecast Model} Model | The sub model that is applied over the chart. |
| Frequency | Frequency of the time series. |
| Data Components | Presence of Trend and Seasonality in the data. |
| ARIMA | |
| Arima Coefficients |
This is the weight of past observations of the data. This will decay or go to zero since the current observation is more closely related to the most recent observations rather than to old observations.
Note: Will be hidden when there is no autoRegressive, movingAverage , seasonalAutoRegressive & seasonalMovingAverage terms. i,e., when p=q=P=Q=0
|
| STL | |
| Decomposed Values | The actual data will be split into three components namely Trend, Seasonality and Residue and will be displayed. |
| ETS | |
| This shows smoothing parameters for Level, Trend, and Seasonality. | |
| Regression | |
| R Square | This indicates how better the model fits the actual data. |
| Adjusted R Squared | This ensures that the model does not overfit. The model with the highest Adjusted R Squared will be applied over your data. |
| F Statistic | This shows how far the X value influences the trend. The higher the value the more it (X value) contributes to the trend. |
| P Value | This shows the probability of the estimator not contributing to the data. This indicates the significance of the Coefficients. The smaller the p-value, the more significant the model is. |
Performance Indicators
The Performance Indicator shows the following information:
Where,
LL -> the model log likelihood estimate,
K -> Number of parameters (e.g., 3 if (alpha, beta & gamma) are used)
n -> sample size
This could happen when the forecast constraints are not met. Please refer to the constraints specified.
This could happen when the design of the chart has been modified, which does not match the forecast constraints.
This could happen if you had set to ignore all the past data points from "Ignore Last" setting.
This could happen when there is no sufficient data produced to forecasting engine to come up with forecasted data points.
When the past data points provided to the forecasting engine has more null values, the forecasted points might be inaccurate. To avoid this, the forecasting engine will discard the process when the null values are more than 40% in the given data.
To produce an accurate forecast, the data points to be considered for forecasting should be more than 5 points. Try changing the time series in X-axis to a more granular function which may result in more data points. For example, If the existing time series is Year, then change to Month & Year.