Simple website analytics: what to track first
If you run a small website or micro-SaaS, start with the decisions you need to make this week. You may need to know where visitors arrive, what they read and whether they complete one useful action. A large event catalogue can wait until you have questions it will answer.
- Three questions before any event plan
- Live checks and mature reports are different tasks
- A practical checklist for what you send to an analytics vendor
Begin with three questions
Where do useful visits come from?
Review traffic sources alongside the pages people reach. Visits from a campaign are a signal to investigate; they do not by themselves prove signups or sales.
What do visitors do next?
Look at the path from an entry page to the next useful step. A marketing website and the application behind its login can need different kinds of analytics.
Did the intended outcome happen?
Choose an outcome you can verify, such as a completed signup or a successful enquiry. A button click can show intent, but it does not prove a form submitted or an account was created.
Start with one outcome your team will review. Add an event when it answers a new question, and give it a name that explains what happened. If nobody uses the answer, reconsider collecting it.
Use live reporting for immediate checks
After changing a landing page, you may want to check whether a visit appears and whether visitors reach the next page. That is a different task from evaluating a mature campaign's signups or revenue.
GA4 has a Realtime view. Google describes its typical freshness as a few minutes, with fewer dimensions and metrics than its other reporting intervals. Standard intraday processing is typically two to six hours, and report processing can take 24 to 48 hours. These are typical intervals, not a fixed delay for every report.
Choose the analytics scope you will use
For an early marketing site, start with visits, pages, sources and the outcome you want visitors to complete. You do not need to model every click before asking those questions.
When your question becomes how people adopt features inside an application, return to it with a deliberate event plan. That plan should describe the question, the event that answers it and who will use the report. The useful distinction is the work you need to understand: a website visit, a completed marketing outcome or behaviour inside your product.
Hitsteps also supports custom Actions when you need to record a specific interaction. Those Actions require implementation: sending a generic click event does not automatically identify a successful business outcome.
Check what you send to your analytics vendor
Analytics tools receive data about your visitors. Reviewing what reaches each vendor is part of choosing and configuring a tool.
- Review URLs, event properties and any identity fields before you add them.
- Keep passwords, access tokens and unnecessary contact details out of page URLs and event labels.
- Check who can access reports and what information your website needs to explain to visitors.
- Evaluate the actual implementation and your site's requirements before making a consent or exemption claim.
A cookie set on your own domain does not mean the data stays on your server. Equally, a cookieless label does not answer every question about the information collected.
Hitsteps uses cookies and persistent identifiers; it should not be selected on the assumption that it is cookieless or that it automatically removes a site's consent obligations. Review its privacy information alongside the tracking you intend to enable.
Start with a question, then check a real visit
Write down the decision your analytics should help you make. Install the tracking code with the WordPress plugin, the Shopify app or a single script tag, check that an accepted visit appears, and verify the outcome separately. Add detail as your questions become more specific.
Start with Hitsteps
Track visits, sources and outcomes on your website, then check the result.
Notes and sources
- Reporting intervals cited from Google Analytics: Data freshness.