Google Analytics
What Koho reads from Google Analytics, and why some numbers look the way they do
Koho reads your website's Google Analytics 4 (GA4) reports every day: where visits come from, which campaigns bring enquiries, which pages people land on, and which devices and places they use. This page explains the numbers that most often look odd, and what to do when Koho can't read a property.
How the connection works
You add Koho's address to your Analytics property as a Viewer, then give Koho the property's Property ID. Koho only ever reads. It can't change anything in your Analytics.
Koho reads each property you name, as the property reports it: in the property's own time zone and currency.
Why Koho's numbers can differ from Google's screens
Recent days change
Google keeps revising the last few days of figures, and it can move an enquiry from "direct" to the campaign that earned it up to about 12 days later. Koho re-reads the last 7 days on every sync (14 days for enquiries by source), so a recent day can change after you first see it. Older days settle.
The three "source" reports don't add up
Traffic sources, first-touch sources and enquiries by source each credit a visit differently: by the session, by what first brought the visitor to your site, and by the event itself. They are three honest answers to three different questions. They won't match each other, and they aren't meant to be added together.
Visitor counts are estimates
Google counts users and sessions approximately, usually to within 1%. Breakdowns (by channel, by page) won't add up exactly to the total.
"(other)" rows
When a report has more distinct values than Google keeps for a day, for example thousands of rarely visited pages, Google merges the rarest into a single row labelled (other). It is real traffic under one label, and the detail can't be recovered from Google.
"(not set)" values
(not set) means Google had no value for that field, such as a visit with no campaign. Those visits are real and are counted.
Small numbers left out
To protect visitor privacy, Google sometimes withholds rows with very small counts, most often by city. Nothing marks where they were, so totals built from those reports can come out a little low.
No revenue, when you know there is revenue
If revenue or cost figures are missing, the most likely reason is a data restriction on Koho's access. In Google Analytics, open Admin, then Property access management, choose Koho's address, and remove the "No revenue metrics" or "No cost metrics" restriction.
When Koho can't read a property
| What you see | What it means | What to do |
|---|---|---|
| "Koho can't see a property you entered yet" | Koho's address isn't on that property, or the Property ID is for a different property | Add Koho's address as a Viewer under Admin, then Property access management, and check the Property ID under Admin, then Property details |
| "…is in the trash in Google Analytics" | The property is in your Analytics trash, and Google deletes trashed properties after 35 days | Restore it in Google Analytics, or leave it out |
| "…already connected to another Koho account" | Another Koho account already reads that property | Contact Koho support |
| "Koho can't read Google Analytics property …" | Koho's address was removed from the property | Add it back as a Viewer. The message clears on the next sync |
| "No traffic recorded on Google Analytics property … since …" | The property has recorded no visits for three full days | Check that your website's Google tag is still installed and firing |
Adding a user to a property needs the Administrator role on it. If you don't have it, send Koho's address to your Analytics administrator to add for you.
What happens to data Koho has already read
Koho keeps the data it has already read when you:
- remove a property from the connection
- remove Koho's address from a property in Google Analytics
- disconnect Google Analytics
Koho stops reading new data in each case. To have data Koho already holds deleted, contact Koho support.