Advertising4 minJune 25, 2026

Website analytics: from a click to an enquiry and a sale

MikhailUpdated Oct 16, 2026

Google Analytics 4 and Yandex Metrica help measure website activity. They do not automatically know whether a visitor became a suitable customer. Start by separating a visit, a click, a received enquiry and a paid order.

01Understand what the numbers describe

A user is recognised according to the system’s measurement method, not necessarily one uniquely known person everywhere. A session is a visit under its rules. An event records an action. A key event or goal highlights an action you consider important. A source describes where traffic came from when identifiable. GA4 and Metrica have different rules and settings. Define business actions consistently before trying to make every total match.

02Follow one fictional customer

Alisher opens a refrigerator-repair ad, visits the site and clicks Telegram without writing. Later he returns and submits a form. The manager confirms a visit; the order is eventually paid. The Telegram click proves a transition, not a conversation. A received form proves an enquiry, not qualification. A confirmed visit is not yet payment. These can be stages of one customer journey, not five separate leads. Link records where possible and describe gaps honestly.

03Write an event map before adding tags

For each action record its trigger and verification: “Successful enquiry, after server confirmation, visible as an event and in the enquiry system.” Call a telephone click a click unless you have evidence of a call. A tag sends data; a trigger determines when it runs. Publishing Google Tag Manager does not prove correct measurement. Test automatically detected events on your actual form rather than assuming they mean success.

04Test success, failure and repetition

Submit an empty form, a valid form and refresh the success page. Expect one accepted enquiry after the valid submission, without duplicates. Test delivery failure too: the visitor should not see a success message if the enquiry was not accepted. Use GA4 DebugView with debugging enabled, then verify normal visits and processed reports. Debug events, manager receipt and final reporting are separate checks; reporting may be delayed.

05Preserve the source without inventing it

UTM parameters label campaign links. Agree consistent source, medium and campaign names. Preserve available source data and the enquiry time when a record is created. Do not put phone numbers or email addresses into page URLs or ordinary analytics parameters. Use an internal enquiry identifier. A customer may switch devices or contact you directly; “unknown” is better than assigning every unexplained enquiry to advertising.

06Work through a sample calculation

Suppose 100 visits produce 12 Telegram clicks, eight received forms, five suitable form enquiries and two paid orders. These are fictional figures. Form enquiry rate is 8 / 100 × 100% = 8%. Do not simply add the 12 clicks to the eight forms: some may be the same people and some never start a conversation. If the relevant traffic cost 500,000 UZS, spend per suitable enquiry in this confirmed form chain is 500,000 / 5 = 100,000 UZS. Account for other confirmed channels separately.

07Make a weekly decision, not just a chart

Compare the same period, time zone and enquiry definition. Reconcile spend, accepted enquiries, qualification, orders and refusal reasons. If analytics reports ten forms but the manager sees six, investigate duplicates, tests, delivery and processing delay first. UZNEO can connect measurement with advertising and CRM. Send the site, a sample report and the path from enquiry to payment. Agree a test submission, duplicate checks and a reconciliation table. A problem with one form may not require rebuilding the whole system.

Summary

Start with one action you can trust: an accepted enquiry available to the manager. Then add quality and payment. For messaging, see Telegram lead attribution.