An architecture practice gets 500 extra visits to an article about school design, but no more views of its contact page. The traffic increase is real; its value is less clear. Were those visitors looking for the services the practice offers? Could they find relevant project information and a practical way to get in touch?
Analytics can help answer those questions, provided the tracking is sound. Metric names vary between platforms, so first agree what counts as a useful outcome: an enquiry form submission, a request for a feasibility discussion, a brochure download or a visit to a leasing contact page. A guide to setting useful website goals for architecture and property teams can help define those outcomes before the dashboard fills up with numbers.
Reach: users, sessions and views
Users are people or devices identified by an analytics system during a reporting period. The figure is an estimate, not a verified headcount: one person might use several devices, reject tracking or clear their browser data. Sessions group interactions into visits under the platform’s rules, so one user can generate several sessions. Page views count page loads or views; opening three project pages may produce three views in one session.
Read these figures together. If views rise but users do not, visitors might be exploring more pages or repeatedly reloading one—or a measurement error might be inflating the count. Period comparisons need context too. A property launch, planning consultation deadline or paid campaign can change traffic for reasons unrelated to the website’s quality.
New and returning users give a rough sense of whether the site reaches fresh audiences and brings people back. Return visits matter in long building projects, when a client may check credentials and case studies over several months. But the categories cannot reliably trace an individual buyer’s decisions; consent settings and device changes can alter them.
Acquisition: where visitors came from
Traffic-source reports group visits into channels such as organic search, direct, referral, email, social and paid campaigns. The labels are useful, but they need interpretation. “Direct” often means the source was not detected, not necessarily that someone typed the address. Referrals may include genuine mentions by planning organisations or property partners, along with unwanted automated visits.
Judge channels by outcomes as well as volume. Fifty visits from a project newsletter that produce three qualified enquiries may be more valuable than thousands of unrelated social visits. To compare campaigns, use consistent tracking parameters on links your team controls. Do not tag internal links as new campaigns: that can overwrite the original source and distort the reports.
Landing pages reveal the first impression
A landing page is the first page viewed in a session. It could be a service page, a completed-project case study or a technical article rather than the homepage. Look at leading landing pages alongside their traffic sources and what visitors do next. If search visitors reach an article about medical buildings but seldom view healthcare services or relevant projects, the page may answer their question without showing a clear route to the practice’s work. That is not automatically a problem; some visitors only want information.
Engagement: what visitors did
Engagement figures need careful reading because platforms define them differently. An engaged session may depend on time spent, multiple page views or a recorded event, according to the product and its configuration. Average engagement time is generally based on detected activity while a page is in focus. It does not tell you how long someone spent carefully reading a specification.
Bounce rate also depends on the platform. In some systems it means a single-page session; in others it is the share of sessions not classified as engaged. Check the definition before comparing figures or applying a benchmark from elsewhere. Someone who checks opening hours and leaves may have found exactly what they needed. A potential client who abandons a complex appointment form after a few seconds, however, may have hit a snag.
Interpret engagement against the page’s purpose. A detailed planning guide may warrant substantial reading time; a contact page should make the right details easy to find quickly. If the analytics setup permits it, record purposeful actions such as:
- clicks on a phone number or email address;
- downloads of a project brief or leasing document;
- use of a location or project filter;
- starts and successful submissions of an enquiry form.
An event count confirms that an action was recorded, not that it led to a suitable commission. A phone click may never become a call; a student or competitor might download a document. Name important events clearly, then test each one on desktop and mobile before trusting the totals.
Outcomes: conversions and enquiry quality
A conversion is an event chosen as an important outcome. Depending on the platform, a report might count conversion events, converting sessions or users who converted. Say which figure you mean. A simple session conversion rate is converting sessions divided by all measured sessions, multiplied by 100. If 12 of 600 sessions include a completed enquiry form, the rate is 2%. That does not mean 2% of visitors became clients.
Keep primary outcomes, such as consultation requests, separate from supporting actions, such as case-study downloads. Otherwise, several small actions by one visitor can make performance look stronger than the enquiry count warrants. For practices with long sales cycles, record whether enquiries fit the services, location and project scale offered. Aggregate website reports cannot show that a particular article won a contract when meetings, referrals and procurement stages also shape the decision.
Technical context: devices, speed and missing data
Device category reports split measured traffic among desktop, mobile and tablet. Check important actions by device: an acceptable overall form-submission rate can hide a form that fails on a small screen. Use appropriate technical tools as well as analytics to check page performance and errors. A slow-loading image, broken form validation or obscured button might explain abandonment; time on page alone cannot identify the cause.
Before comparing results, check the date range, consent arrangements, internal-traffic filters and any tracking changes. A new cookie banner can reduce measured visits without a matching fall in actual visitors. A revised form event can create an apparent improvement even if enquiries stay flat. Privacy requirements vary by location, so collect only what is needed for a stated purpose, follow applicable consent rules and keep personal details out of page URLs and event names.
A compact monthly review
A useful monthly report need not include every available metric. Keep definitions consistent between periods and note major changes beside the figures:
- Compare users and sessions with a relevant earlier period, accounting for campaigns and seasonal effects.
- Identify the leading landing pages and acquisition channels for useful enquiries.
- Check engagement and key actions on important service, project and contact pages.
- Review conversion counts and rates by device, then assess enquiry suitability separately.
- Check unusual spikes or drops against tracking changes before altering the website.
Suppose a service page receives 240 measured sessions in a month. Visitors start its enquiry form 48 times and submit it six times. The submission rate is 6 ÷ 240, or 2.5% of sessions; the completion rate among recorded starts is 6 ÷ 48, or 12.5%. Before rewriting the service description, send a test enquiry on mobile and confirm that successful sends are recorded correctly. Those checks can help distinguish a content problem from a broken form or faulty event.