Analytics & Performance
Visitors, where they came from, how fast the site loaded for them and which of them became customers, read from one set of numbers in the business's own install. What the usual analytics stack cannot answer, and the question this lets an owner ask.

The question I asked first when shaping Canopy's analytics: what changes when the visitor numbers and the sales numbers live in the same place. The answer is the kind of question an owner can finally ask. A typical analytics tool is good at 'what was my bounce rate last week.' It cannot answer 'of the prospects who became paying customers last quarter, where did they first find me, and how long did they take to decide.' The visits live in one company's software, the sales in another's, and the reports between them never quite agree. Bounce rate is a gauge. Which source produced paying customers is a decision about where the next marketing dollar goes, and the usual stack cannot make it. The usual answer is more software: an analytics tool, a CRM, a connector between them, an attribution tool over the connector and a dashboard over that. Several products, a bill for each, and a connector between them that is the first thing to break. When a vendor changes its terms or retires a feature, the owner's view of their own funnel goes dark until somebody rebuilds it. In Canopy the visitor and the customer are in the same install. Who arrived, where they came from, what they searched for, which pages they read, how fast those pages loaded for them, which form they sent and which deal it became are one continuous history. The marketing question, the speed question and the sales question are answered by the same numbers, in the same place, behind the same sign-in. The numbers are honest about who is a person. Crawlers and bots are counted apart from people, so the headline is prospects and customers rather than robots, and the bot traffic is still there when a number looks strange and somebody wants to know why. Speed is kept page by page, so one slow page cannot hide inside a healthy average, and a slowdown after a change to the site shows up next to the leads it might be costing. Search results are read in the same place, so the queries that bring people in sit beside what those people went on to do. And a client's launched website can report its visits and form submissions back onto that client's own deal, so a case study shows real outcomes rather than a screenshot of somebody else's chart. Privacy is the default rather than an option. Nothing is shared with any other business, there is no cross-site tracking network behind it, and visitor addresses are not kept. That is partly about defending the business under privacy law and partly about the owner never being surprised by what is in their own records. The honest exclusion: Canopy is built for a small business with thousands to tens of thousands of visits a day, where knowing which visitor became which customer matters more than counting billions of events. A consumer app at that scale needs a different product, and a different team to run it. The consequence the owner feels: there is no quarterly conversation about whose numbers are right, because there is only one set of numbers.