← All posts
Analytics steps from a service-page visit to a contact click and an accepted form.

technology

Umami: follow the steps towards a website enquiry

  • A click on “Contact” hasn’t sent you an enquiry.
  • Umami can record pageviews and named events, so you can examine the steps towards a useful action.
  • Your own testing affects the numbers unless you exclude it from the browsers you use.

If you run a service business, a useful website question is whether visitors reach the work, understand the offer and get in touch. A total at the top of a dashboard only answers part of that.

I use self-hosted Umami for the studio website’s page and event analytics. The interesting work is choosing what to record and deciding what each event lets us conclude.

Name the action you care about

Umami’s tracker collects pageviews and supports custom events. You can give a button click a name and attach details such as the page where it happened. The tracker documentation describes both.

On lyfar.com, the tracking code distinguishes a service-page visit, a contact-button click and an accepted contact-form submission associated with a guide. These events answer different questions:

Event in the site codeWhat it recordsWhat it doesn’t establish
service-viewA visit to a service pageWhether the visitor wants that service
cta-clickA click on a tracked call to actionWhether a message was submitted
guide-contact-acceptedThe form endpoint accepted a submission after a guide visit in that browser tabWhether it is a qualified lead or a sale

That last event has a specific limit: the guide context lasts for 30 minutes in the same browser tab. The analytics event carries the guide, category and source, without the form’s name, email or message fields. The contact form handles the enquiry itself.

You can design a similar path for a booking, a download or a signup. Start by naming the action that matters to your business, then work backwards through the steps a visitor takes. Recording everything makes the review harder.

Account for the person building the site

My own visits can appear in the same figures as everyone else’s. I open pages to check a layout, follow links and test a form. Those actions don’t represent new demand for the studio.

The site has an internal-traffic switch that stops loading the tracker in a marked browser. It applies to that browser and hostname, and it doesn’t remove earlier visits. A phone, a different browser or a private window needs separate attention.

This is why I can’t take a pageview increase and call it more potential clients. The tracker also depends on the browser loading its script; Umami documents that blockers can prevent collection . Treat the figures as recorded activity and compare them with the enquiries you received.

Make the review small enough to use

Umami supports self-hosting and an API for retrieving analytics . That gives you a choice: read the dashboard or build a report around the few questions you need answered. A scheduled digest is one possible use of that API.

For a client site, I’d begin with the main contact path and check it using known test actions. Then I’d review which pages people reach, where they click next, and what the contact inbox confirms. It’s the difference between counting people through a shop door and checking what happened at the counter.

Tell me what visitors should do on your website . We can build the page, the action and the measurement around that decision.

Interested in this?

Learn about Technology →