Your website is a data source that records nothing
It is the first system a company owns and the one it controls completely. Almost all of them log pageviews and throw away everything that would have been useful.
Almost nobody thinks of their website as a data source. It is treated as marketing — a thing that looks a certain way and produces enquiries. Meanwhile it is the only system in the business that records the behaviour of people who have not bought anything yet, which is the population every other system is blind to.
And in practice it records almost none of it.
Pageviews are not behaviour
Analytics is installed nearly everywhere. That is not the same as anything being measured. The default install counts pages: how many people saw one, how long they stayed, where they came from. What it does not capture is what a person did — which of the three calls to action they chose, whether they opened the pricing detail before or after reading the case for it, whether the enquiry came from someone who had been back four times.
A pageview tells you a page was rendered. It does not tell you anything a person decided.
Where it usually breaks
Three failures, and they compound. The first is that no conversion event exists at all, so the funnel ends at a page. The second is that the form posts to an inbox, which means the enquiry arrives as prose with no session behind it — you know somebody wrote to you and nothing about how they got there. The third is the domain boundary: the moment a visitor is handed to a booking tool or a payment page on somebody else's domain, the trail stops unless something deliberately carries the source across.
That last one is the cruel one, because it looks fine from the inside. A broken form announces itself. A funnel that quietly severs at the handoff keeps producing charts, and the charts keep being wrong in a direction nobody notices.
Check yours in ten minutes
- Open your analytics and try to find one event that is not a pageview. Not a goal inherited from a template — an actual named thing a person did. If there isn't one, nothing downstream of traffic is measurable.
- Send yourself an enquiry through your own form. When it arrives, ask what you know about that person's visit. If the answer is 'their email address', that is the finding.
- Follow your primary call to action. If it leaves your domain, check whether anything carries the campaign and session across with it.
None of this requires a data platform. It is a handful of named events and one decision about what is worth recording, made before the site is built rather than retrofitted by whoever inherits it two years later.
Why we wire it at build
Because retrofitting is where this dies. Instrumentation added later is added by whoever inherited the site, under time pressure, without the argument about what matters ever having been had — which is how you end up with an event called button_click_2 and no idea which button.
Deciding what is worth recording takes about an hour, once, before anything is built. It is the cheapest hour in the project and it is the one nobody sells you.
14 questions, fifteen minutes, and you find out which layer is holding the rest up.
The result appears on the page as you answer it — no email required to read it, and it is perfectly capable of telling you that you don’t need us.