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.

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

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, and how to read Total, Selected and the heat map.

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 and the heat map.

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 catalog" row, deleted rows kept with a mark.

The CRM funnel as cards: how many deals sit at each stage right now, for what amount, what share they hold and how old they are. What the section shows, how to choose a funnel, and why this is a snapshot rather than a path.

Priority actions KO selected from the project data: cards with confidence and the cost of ignoring, a rail of signals and a decision breakdown panel. How to read the selection, how to move an action through statuses 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.

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 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.

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.

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 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.

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.