When getting started with Growblocks, you might encounter areas of your GTM engine that are missing data, or you know the data quality in that part of the engine is not great. This is where Overrides come in.
For your projections to work, you need to make sure you have data across all of your key metrics, for each of the dimensions you are setting up for your engine. Speak to your Solutions Engineer if you need insight on where you have missing data.
Overrides allow you to set a default value for a specific metric, which will be used as the base value for your projections instead of any actuals you have for this metric.
This is normally recommended when you have either missing or poor-quality historical data which results in no or erratic projections.
- Overrides can be:
- Global (apply to all of your plans*)
- Plan specific (only applies to the plan you create it in)
- You can define for different segments of your metrics.
- Any initiatives or assumptions you create for this metric will be applied on top of the override.
- An override has an Impact period (start and end date) which specifies when the projection calculation should use the override value instead of actuals in it’s calculation.
*If the plan duration has an overlap with the Impact period of an override.