Setting up conversions in Google Analytics 4 for Uzbek websites
Out of the box, GA4 counts everything and nothing that matters. Here is which events to create, how to name them, and how to avoid drowning in false conversions.
Deciding what counts as a conversion
Start with a list, not the interface. Write down every action that leaves you with someone's contact details: form submission, Telegram tap, phone tap, WhatsApp tap, callback request, completed order, price list download.
Split them into macro and micro. Macro directly produces a lead: a submitted form, a completed order. Micro precedes it: viewing contacts, scroll depth, opening a price list. Mark only macro events as key events in GA4, or your conversion reports become meaningless.
Decide separately what a conversion means on each language version. The Russian and Uzbek versions often behave differently, and merging them into one report throws away half the insight.
Naming events
Agree the scheme before you configure anything: lowercase Latin with underscores, action first — form_submit, click_telegram, click_phone, order_complete. You cannot rename an event retroactively, and historical data is not recalculated.
Add parameters instead of new events. Do not create form_submit_home and form_submit_services; create one form_submit with a form_location parameter so you can slice the data any way you like.
Keep an event table in a shared document: name, meaning, where it fires, which parameters it carries. Six months later nobody remembers how two similar events differ.
Configuring through Google Tag Manager
Hard-coding events is awkward: every change becomes a developer ticket. Through a tag manager you build a trigger on a click or a form submission and push the event to GA4 without touching the site.
For forms, it is more reliable to catch the thank-you page or block appearing rather than the button click. A click fires even on an empty form with an invalid phone number, and you end up with twice as many 'enquiries' in reports as in your inbox.
For Telegram and phone taps, use a link-click trigger filtered by URL prefix: t.me for the messenger and tel: for the number. These are the two most important conversions for local sites and the two most often missed.
Counting Telegram enquiries
A tap on the Telegram button is intent, not an enquiry. Analytics sees the exit and stops there. To link the tap to a conversation, add a bot start parameter to the link so the bot receives a label identifying the source page.
Track two metrics separately: button taps in GA4 and actual conversations in the bot or chat. The gap between them is your follow-through rate, and it tells you whether the button sits in the right place.
If a manager handles conversations by hand, agree a simple way to record the source in the CRM or a spreadsheet. Otherwise Telegram stays a black box, even though in local niches it often produces more leads than the form.
Junk events and how to remove them
First, your own traffic. Add office IP addresses to the internal traffic list, or form tests land in reports as conversions.
Second, bots and spam submissions. If the form collects junk, conversions inflate and cost per lead looks better than it is. Protect the form and compare GA4 event counts with CRM records at least weekly.
Third, repeat firing when a thank-you page is reloaded. Limit the trigger to once per session, or a single customer records three conversions.
Reports worth building immediately
First: conversions by traffic source, which shows which channel actually produces enquiries rather than visits. Second: conversions by landing page, which shows which pages work and which only spend budget.
Third: a breakdown by page language and device type. Mobile share is high in Uzbekistan, and a gap between mobile and desktop conversion usually points at a specific break in the mobile layout.
Link GA4 to Search Console and to your ad account. Without those links you will reconcile data by hand and get different numbers every time.