The forecast lives in someone's head
"Last month was this, so this month will be about the same" — and next month's budget gets planned on intuition rather than on data.
Valkiria forecasts impressions, clicks, conversions, revenue, budget, audience, churn and growth from your own history alone, and stores each one with its confidence and source references. When the real numbers arrive, the forecast is compared with them and scored for accuracy.
"Last month was this, so this month will be about the same" — and next month's budget gets planned on intuition rather than on data.
The model states a number with confidence, and a month later nobody comes back to see whether it held. The error is never found, and the same model predicts again.
A tidy figure with no note of which data produced it, or what was missing from that data, can be neither challenged nor defended in front of a client.
The module hands the model your accumulated performance. Its instructions forbid going beyond that data and require listing sources, assumptions and any missing evidence.
One button builds forecasts for the period — 30 days by default. Each record is stored with its type, category, confidence and an unverified-estimate status.
When the period closes, the actual values and an accuracy score are attached, so you see which predictions deserve trust and which do not.
Performance, budget, audience, revenue, CTR, conversions, churn and growth, filtered by category in a single list.
A forecast with no confidence is labelled "needs evidence", and how confidence moves over time is drawn on its own chart.
Forecast and actual sit side by side, accuracy is scored as a percentage, and the average across all forecasts tells you what the model is worth.
The status shows whether sources back the forecast: an unverified estimate can never be applied automatically.
Expected impressions, clicks and conversions for the next 30 days come as a chart you can put behind a spend plan.
The Ollama → z.ai → OpenAI → Anthropic → Qwen chain is configured per install, so nothing is hard-wired to one vendor.
Only on your own historical performance, which is passed to the model with the request. The instructions require it to return predicted values, a confidence score, source references, assumptions and a list of the evidence it was missing.
Confidence is itself an estimate by the model, not a measurement, so it is never the last word. Forecasts are compared with the actual values, and an average accuracy accumulates next to them showing what that confidence is worth in practice.
No. A forecast is stored as an unverified estimate, and that status blocks automatic application. Campaign changes are made by a person in the campaign modules, where anything new is created PAUSED.
Eight types: performance, budget, audience, revenue, CTR, conversions, churn and growth. The list filters by category, so forecasts for one client or one direction can be read on their own.
That depends on your configuration. The module runs through a provider chain set up per install, which can start with a self-hosted Ollama; nothing is hard-wired to a single vendor.
Forecasts are built from your data, labelled as estimates and never applied on their own. You can check the accuracy after the very first cycle.