Every number in a report is made of records. A journal shows them as a feed: one row per lead, visit or product event, with whatever columns you choose.
A report answers “how much, and how did it change”. A journal answers “which ones exactly”. That is why there are no charts here: trends live in the report, and people come to a journal asking “what came in today” and “why do half of these have no source”.
What you see here
On the left — the project’s journals. Two come built in: Leads — leads with the connection they came from, pipeline stage and owner; Visits — arrivals on the website with source, site and last page. A project can have journals of its own: a journal is a set of settings over a stream of data, and you can create one yourself.
At the top — the section toolbar: period, Filter, quick-filter buttons and search. Everything set here applies to the whole section — to the numbers as well as to the feed.
The Metrics block is a health scan, not a total. It answers “which records can be trusted and what needs fixing”, not “how many in total”:
- Rows and People — the volume;
- No source, No visitor, Unstitchable, Bots, No pipeline stage — how many records failed a check: the share in large type, the count underneath;
- Data health — the share of records with no problem at all.
Which cards appear depends on the stream: Visits count bots and stitching, Leads count the pipeline stage and the owner. What counts as an incomplete record is defined by KO’s data model, not by the project.
The Records block is the feed itself. The first column is Date, and it is pinned: scroll right and the row is still recognisable. The columns of the journal follow. Weekends are dimmed. Click a row to open the breakdown on the right: every value of the record, including those no column shows.
Set it up for your question
Period. “Today” and “yesterday” come first — that is what a journal is most often opened with.
Quick filters are buttons on the fields you need daily: connection, source, device, stage. One click includes a value, a second click excludes it, a third clears it.
Filter takes any field of the catalog and any condition. Values use the same syntax as in
reports: a, b — any of these, !a, b — none of these.
Columns sets what the table shows, from the project’s field catalog. Journal default is pinned at the top of the list — it brings the original set back after you have experimented. The button carries a counter of the columns shown.
View controls how the feed looks:
- Add to the date: weekday, time, seconds, age (
~1d). Each is independent; time and weekday are on to begin with. - Rows per page — 50, 100 or 200; Show more at the bottom adds another batch.
- Row height and Wrap long text.
Journal options (”···” in the section toolbar) holds Journal settings (stream, events, columns, quick filters, outcomes), Rename, the order in the list, Reset to default for a built-in journal and Delete journal for your own. A new one is created from New journal at the bottom of the list on the left.
Everyone with access to the project sees the journal: it is a project setting, not a personal view.
How to read it
A scan card is a way into its own rows. Clicking it leaves exactly the records it counted in the feed; clicking again clears the selection, and the Records toolbar states what is being shown. The cards themselves keep counting the whole period — otherwise the one you picked would instantly read “100%” and the picture the block exists for would be gone.
“No source” includes direct traffic. A direct hit is not a channel, it is a sign the tag was lost on the way — and that is what needs fixing.
A row in Visits is a whole visit, not a single page view: the events of one arrival are assembled into one row, and the columns show the values of the last of them.
A field greyed out in Columns does not disappear from the list — it comes with the reason. Usually there are no values for it in this stream: a visit has no pipeline stage, a lead has no browser.
If there are no records
- “No records for the selected period” — records did not match the conditions rather than not existing. Clear the quick filters and widen the period: Visits start at 7 days, Leads at 30.
- “This project has no journals yet” — the project has no streams of data yet. That is a question of connections, not of this section.
- The Visits feed is empty while the website works — the tracking script is not on the pages, or the website connection is off. Diagnostics shows the state of the connections.
Related
- How a report works — the same data, rolled up into numbers.
- Diagnostics — the neighbouring section: what is broken and since when.
- The field catalog — where columns and filter fields come from.