Checks whether you can see at all if the ad budget goes to the priority regions of the business. It looks for region names from the Context settings in the names of campaigns with spend. If the region is visible for only a small part of spend, the card asks you to name campaigns by region.
Traffic analysis
Budget by region
The region shows in the name of 2 of 7 campaigns with spend, which is 23.9% of the budget over the last 30 days
Next step: Name campaigns by region (Uusimaa, Pirkanmaa, Varsinais-Suomi), for example “Search Uusimaa”, or enter the regions in Context the way they are already written in campaign names
An example of an insight card. The numbers are made up: in the product, the card shows the numbers of your project. What is inside an insight ↓
When you see this card
The regions from the Context settings appear in the names of only a small part of campaigns with spend
App install and reach campaigns are not counted
What it needs
A connected ad account with spend
Priority regions in the Context settings
Result type
Broken measurement data or tagging does not let you measure the result
Questions it works on
Precondition Where to move the budgetIf regions are not visible in campaigns, moving money between regions is blind.
What is inside an insight
The card is a short conclusion. A click opens the breakdown: what the conclusion stands on and how far you can trust it.
What we know
Facts with numbers and their source: what changed, by how much, compared with what.
Where exactly
The channels, campaigns, managers or stages where the change is strongest, with a link to the report.
Cross-check
The conclusion is checked against a second signal: confirmed, not confirmed or cannot be checked. Plus what else changed on the same days.
We assume
Likely causes. A hypothesis is labelled as one and never passed off as a fact.
We forecast
Where the period ends if nothing changes.
What to do
The step, what it gives, how to check the result, and the cost of doing nothing.
For
Owner, analyst or agency client: each role sees the cards in its own order.
More than one condition behind a card
To raise one card, KO goes through the slices of your project, including the fields of your CRM, and compares them with the norm of your own project, adjusted for season, holidays and working days. The conclusion is checked against a second signal. When KO finds the root cause, its effects do not show up as separate cards: you see the cause, not ten symptoms.
The demo is the project of a made-up company, with ads, website and CRM already connected. Open “What to do now” to see what your insights would look like: each with its breakdown, result type and who it is for.
See what to cut, fix, and scale — using your real data.
VitalyProduct & salesAzatEngineering
You'll meet the founders, not a sales rep — we built KO after years of running growth on broken numbers.
We've received your request!
We'll reach out within one business day to schedule your demo.
We've received your request!
Our team will reach out within one business day to schedule your demo.
We have your request
We will reply within one business day.
We have your request
We will reply within one business day.
We have your request
We will reply within one business day.
May we count your visit? We measure traffic with Google Analytics and our own counter — they set cookies only if you allow it. Nothing here is used for advertising. Cookie Policy