Help center

Create a project and set the four things that decide how everything arriving later is recorded — timezone, currency, first day of the week, and how contact details are stored.

The catalog of services KO connects: what each one brings to reports, how it connects and how often it updates, which reports need it and what the project already has.

The two pieces every website connection needs, how to install them whatever the site is built with, and where the setup usually breaks.

Typeform runs on its own domain, so the visitor's source has to travel as a URL parameter. Two settings make that work.

Send leads to KO from any system with a POST request. Request format, response codes, attribution fields and the test mode.

Authorise the ad account, pick the campaigns KO reads, and describe how your ads are tagged — the three things that decide whether spend joins up with leads.

Connect a Google account and pick a property — reports get impressions, clicks, CTR and average position by search query and page.

Connect Bing Webmaster Tools and pick a website — reports get impressions, clicks, CTR and average position in Bing search by query and page.

The day view: the sprint goal and the pace toward it, the agenda for today, what the system found and the hypotheses the team is testing. How to set the sprint length and the goal, move between sprints, add a hypothesis and wrap up a sprint.

A report in KO is a set of sections sharing one filter, each with a period of its own. What the Reports area shows, how to assemble your own report from sections, and how the period, the filter and the standard reports work.

Ready-made reports for common questions: what a template adds — reports, slices and metrics — which sources it needs, how to add a template or an empty report, and what the "already exists" and "won't be added" marks mean.

Cards with the key numbers of a report: value for the period, previous period, plan and a trend chart. What the section shows, how to choose which cards appear, and how to read the marks next to numbers.

A "metric × period" table: the actuals by week or month, the target from the project plan and a forecast of completion. What the section shows, how to choose the grouping and the plan, how to edit a target in the table, and how to read Total, Subtotal, the forecast range and the highlight.

A "segment × metric" table: rows are the values of a chosen field, columns are metrics. How to build a chain of levels, what the Total and Other rows mean, and how to read the top-N, the heat map and row verdicts.

A table whose rows come from the project catalog, not from the data: a manager with no deals and a paused campaign stay in the table as rows of zeros. Attributes as columns, the "outside the directory" row, deleted rows kept with a mark, verdicts on ad rows, lost deals by the stage they reached, search queries with position and change, site events with their source and where the tracker sent them, rejection reasons and campaigns marked with groups.

The method behind row verdicts in Breakdown and Entities: what a row is compared with, why "worse than the norm" is a test and not a comparison of two numbers, the order in which a verdict is chosen, when broken tracking cancels "cut", how overpayment is counted and where the table-wide findings come from.

The CRM funnel as cards in two modes: Flow — how many leads entered each stage over the period, moved on and got stuck; Snapshot — how many deals stand at each stage right now. How to choose a funnel and a mode, and how to mark the winning stage and the intermediate goals.

Findings KO selected from the project data: cards in one grid by priority with the type of finding on a chip, forecasts, "Worth a look" and "What works", and the decision breakdown panel. How to read the selection, how to work on a finding with a hypothesis and why the list is sometimes empty.

The feed of records behind the numbers in a report: leads, visits, product events. A health scan above the feed, a record breakdown on the right, columns and filters of your own, lead contacts and who sees them.

The state of the project's website and connections: what is broken, since when, and what the server answered. Availability, domain and certificate expiry, authorization and incoming data per connection, the CRM winning stage, tags on leads and visits, ad clicks reaching the website.

The project metric catalogue: label, number format, formula, state and the places a metric is already used in. How to edit a standard metric, create your own, and put everything back.

The project dimension catalogue: where fields come from, what "Filled" means, where a field works — filter, breakdown, segments, formulas — and how to switch it on for reports.

Project slices and segments: how to define your own report dimension, what a segment rule is made of, what reach tells you, and why the numbers do not change straight away.

Metric targets for each period: how to create a plan, enter targets, set the sprint goal and KPIs, add and remove a separate goal, set an end date and a review, and group plans. What a plan changes in Plan vs actual, Focus and Pulse.

What KO needs to know about your business for its conclusions to be about your business: project mode, seasonality, what to compare against, priority regions and the brief. What already works and why an honest answer sometimes lowers confidence.

Every lead gets one class by how the deal ended: fast, slow or small sale, lost, no outcome yet. Where the "fast" and "small" thresholds come from, when to change them and why a class is sometimes not separated.

Your own lead path through stages, on top of CRM data: each stage is a condition, and a lead goes to the first stage that matches. How to build a funnel from a copy of a CRM pipeline, check its reach, what "Outside stages" and "Matched several stages" mean, and why Flow is sometimes not available.

Public holidays, shifted days, business and custom dates: what to account for so that a drop on 1 January does not read as a fault. How to pick country calendars, what the business and marketing sets add and where to enter a date of your own.

Reference for the KO counter's browser API: the call shape, event envelope fields, the koLayer queue, counter options, ko.consent and debugging with ko_debug.

How to name your custom events in KO, why differences between cases belong in the data rather than the name, and which fact to hang the call on so the numbers match reality.

How to send user actions to KO from a React, Angular or Vue SPA: the wrapper, your first event, checking it with ko_debug, and turning the event into a metric.

How to send user actions to KO from a multi-page site: a plain script tag in the page template or in a site builder's code field, your first event, checking it, and turning it into a metric.

How to send user actions to KO from a site built with Astro, Hugo, Next or Eleventy: the wrapper in the shared layout, page context computed at build time, checking the built files, and turning the event into a metric.

How to connect a cookie consent banner to the KO counter: loading after consent, a default denial through ko_options, revoking through ko.consent, and checking it in the browser.

Who has access to the project and what they may do: roles, invitation by link, options on top of a role, and the rule about the project owner.

Who gets notified and about what: recipients and channels, address confirmation, subscribing to event types, and what the last-sent column tells you.

A key that opens your project data to an AI assistant: how to issue it, how to connect an agent with a ready-made prompt or set up Claude Code and VS Code by hand, what the assistant can read and how to revoke the key.