In short
Compared with Google AdsMeta AdsGA4CRM reports
What built-in analytics does well
An ad account knows its own ads best: impressions, clicks, bids, audiences, creatives and spend to the cent. That is where you manage a campaign. A CRM knows deals, stages, amounts and sales reps. Site analytics knows visits, pages and where people leave. If a question lives inside one tool, look for the answer there. You do not need KO for it.
It gets harder with the question “which ads bring sales”. Spend is in the ad account, the visit is in site analytics, and the money is in the CRM. Each tool will answer, but in its own way, and the answers will not match.
Where built-in analytics ends
The ad account counts conversions by its own rules. The platform counts what its pixel saw, in its own attribution window, before cancellations and often with VAT. That number is honest, but it is not a CRM sale. If two platforms claim the same deal, each counts it, and the sum of conversions across ad accounts is higher than the number of sales.
The CRM has no source. A deal knows its amount and stage. It does not know which ad the person came from, unless the form passed the tag. The CRM report by source shows what someone typed in or what the site passed.
Site analytics has no money. It sees the visit and the form submission. It does not know whether the lead was paid for, or how much it brought.
Each tool has its own days and currency. The ad account keeps spend in the time zone and currency of the account, and the CRM uses its own. The day boundary and the exchange rate differ, and over a week the gap becomes visible.
Bots are removed differently. Each tool cleans traffic by its own rule, or not at all. The visit to lead conversion rate depends on whose filter was on.
Joining it all is manual work. Export three reports, align the dates, find the campaign for each deal. An analyst does it once a month, and each time a little differently.
What KO adds
A lead finds its visit. The KO tracker gives each visit a touch number. The form sends it with the lead, and the lead is linked to the visit it was sent from. How this works is in How a lead finds its visit. Leads without a visit are shown as a share, not hidden behind a “similar” visit.
The source is the tag, or KO’s own inference. KO keeps the UTM tag set by the advertiser apart from the source it worked out itself: a search click, a link from another site, a direct visit. The report shows who named the source.
A lead has one source. By default a lead is credited to the last source, and a direct visit does not replace it. A lead is never split into parts. The total is unique leads, not the sum of ad account conversions. The models, and why others were rejected, are in Attribution models.
Revenue comes from the CRM. KO sums the income field of deals that reached a won stage. Which stages count as won is set in the project. KO takes spend from the ad account, so ROMI is counted from the money recorded on the deal, not from the platform’s conversion value.
One set of rules for the whole report. Days are cut by the project time zone. Spend is converted to the project currency, and the original amount is kept. KO removes bots by default, with one rule for all sections. Each metric has its own date: sales by lead date, purchases by payment date, and the report says which. One metric for one period has the same value in every report section.
A gap with the ad account is visible. Every day KO checks spend, clicks and impressions against the ad account. Every hour it counts leads without tags, paid visits without a campaign, and ad clicks that never reached the site. All of this is in Diagnostics.
On top of a tool’s data, KO counts what the tool itself does not have. This applies to different things that come from your connections, for example:
- A search query. From Search Console KO takes the same clicks, impressions and positions, and counts more on top of them: the current position of a query and how it moved over the period, brand and non-brand queries, their intent, pages that dropped out of search, and search demand, to tell whether the market fell or the site’s visibility did.
- An ad campaign. It gets a verdict: cut, too early, scale, or check the tracking first. KO gives it by the cost of a result from the CRM against the project norm, corrected for small numbers. More in How KO gives a row its verdict.
- A loss reason from the CRM. You see which funnel stage the lost deals reached.
What KO adds to each entity — a campaign, a lead, a deal, a visit, a search query, a manager, a buyer and open deals — is collected in Beyond the source.
Side by side
| KO | Built-in analytics of your tools | |
|---|---|---|
| What counts as a sale | a deal from the CRM | a conversion by the platform’s rules, in its window |
| Revenue | income of deals at a won stage | conversion value, before cancellations |
| Source of a deal | the lead’s visit: the tag, or KO’s inference | in the CRM, if the form passed the tag |
| One deal, two channels | one source by the report model | each platform counts it |
| Days and currency | the project’s time zone and currency | each tool has its own |
| Bots | ”No bots” by default, one rule | each tool its own way |
| Check against the ad account | every day, in Diagnostics | by hand |
| What to do with a campaign | a verdict based on the cost of a CRM result | platform recommendations based on its own conversions |
| Loss reason | also which stage the deals reached | number of lost deals |
| Search | also position change, query intent and brand, dropped pages, demand | clicks, impressions, average position |
| Bids, creatives, audiences | no, these stay in the ad account | yes |
When built-in analytics is enough
One channel and a question about it: which campaign is cheaper, which creative works, where to raise a bid. That is the ad account. The sales pipeline and the work of sales reps are the CRM. Behaviour on pages is site analytics.
You need KO when the question joins ads with money in the CRM: which channel pays off, what a sale costs in each channel, why the ad account shows one number and the CRM another.
If your reports are already set up
During onboarding, we move the reports you built in your ad account, CRM or site analytics to KO for you. The breakdowns you use become a report, your own calculations become project metrics, and your traffic grouping rules become segments. If KO is missing a section or a metric for your calculation, we can add it to the product on request.
Write to us: which reports you look at now and where.
Updated