Analytics that distinguishes a visit from an enquiry

A visit to the contact page is not an enquiry. We help organise accounts, events and reports so the team can distinguish what has actually been measured from what the available information does not establish.

Tell us what you need to measure

Three different signals
Visit

A page was opened

Event

A defined action

Enquiry

Confirmed storage

Interpretation depends on configuration

Opening Contact does not prove a form was submitted.

Three things worth distinguishing in website analytics.

Accounts controlled by your business

We establish service ownership, permissions and the scope of work with GA4 and Google Search Console. Google Business Profile and Google Workspace configuration can also be agreed. These are different tasks: profile visibility, website measurement and workplace tools should not be presented as one automatic setup. Access is granted through appropriate permissions, without sharing passwords in a form.

Page views, clicks and accepted submissions

We define what each event means and which fact allows it to be recorded. A button click may be followed by a validation error. A website message may not confirm durable storage. Receipt of a notification is another separate stage. These distinctions belong in the measurement specification.

Demonstration example: a contact-page visit is a page view, while an accepted enquiry is counted once. Reloading the thank-you page should not create another lead.

Consent, language versions and duplicates

We check measurement under the agreed consent states and distinguish Polish and English journeys. We assess whether several integrations record the same event. Parameters are defined without message content, personal details or other information that should not be passed to analytics.

Reports should answer a defined question

We connect a business question with an available report: where visitors come from, which content they reach and where the verified journey ends. Visibility data and on-site behaviour have different meanings. Where there is no reliable connection to an enquiry or sale, we state that limitation rather than invent a result.

Trials and their limits

We compare the state before and after an agreed change. Scenarios cover a normal journey, retries, errors and the agreed consent states. Findings describe the checks and conditions involved. Correct configuration does not establish indexing, AI citations, increased traffic or sales effectiveness.

Preparation and deliverables

Prepare your objectives, services, account owners and authorised access to reports. We need the rules for accepting submissions and a person who can confirm what the team considers an enquiry. You receive an event map, findings, the agreed configuration, a trial record and recommendations. Checks not performed remain explicitly identified.

Areas we can check

  • Analytics measurement, selected events, traffic sources and data quality.
  • Search Console ownership, indexing, queries, sitemap and technical issues.
  • Business Profile details, categories, services, photographs and local information.
  • Workspace and Gmail accounts, permissions and the organisation of access.
  • A concise report of what works, what needs correction and what to monitor.

Next step

Tell us which question the report should answer and what your team currently counts as an enquiry.

Tell us what you need to measure

Have a quick question? Get in touch.