Yandex Metrica for Bitrix: Setup, Goals and Order Tracking

What Metrica gives a Bitrix website

Metrica shows where a visitor came from, which pages they opened, where they dropped off and which channel eventually produced a lead or a payment. For a shop owner in Tashkent or a service business in a regional city, that is the difference between "we have a lot of traffic" and "these three sections bring money."

It matters most for SEO. Higher rankings and more search visits are worth little if those people do not call, write to your Telegram or place an order. With goals in place, Metrica shows which organic landing pages produce results and which only look busy.

Where to place the counter code

Create the counter in Metrica, enter your main domain and switch on the options you need: Webvisor, click map and ecommerce. The code must then load on every page. The usual routes are:

• the shared part of your Bitrix site template, in the head area of the pages: the most predictable option;
• a tag manager, if one is already running on the site;
• a ready-made module from the Bitrix marketplace: fast, but it needs checking.

Common installation traps

The first trap is multiple templates. If the home page, catalog and customer account use different templates, the counter may be missing somewhere. The second is a double install: the code sits in the template and in the tag manager, so every visit is counted twice. The third is Bitrix composite mode, where a script that lands in the dynamic part can fail or fire twice. Keep the counter in the static part of the template.

Also confirm the counter runs on the live domain and not only on a test one, and that the code survived the last template update.

Goals: deciding what counts as a result

A goal is an action that matters to your business. For a Bitrix site in Uzbekistan a short list is usually enough:

• a lead or callback form submitted;
• a click on the phone number;
• a jump to a Telegram chat or bot;
• a product added to the cart;
• an order placed, including payment through Click or Payme.

How to avoid false goals

The most common mistake is tying a goal to a click on the Submit button. The visitor may have skipped a required field, the form returned an error and the goal has already been counted. Fire a JavaScript event after the form is successfully sent instead. If the form works without reloading the page, a goal based on visiting a thank-you page will not fire at all.

Orders follow the same logic. A purchase should be recorded once, on the order confirmation page, and must not be resent when the customer refreshes it or returns through a link from a messenger.

Ecommerce data: module or manual setup

For an online shop it is worth sending product views, cart additions and purchases with order number, items and amount. The data is output through a dataLayer array in the product, cart and confirmation templates. Watch the currency: if the amount is wrong, your revenue report is useless.

A ready-made module saves time but can clash with a custom cart. One-click orders, pre-orders and checkout through a Telegram bot are often missed. Manual setup needs a developer, but you know exactly what goes to Metrica and when.

Testing and SEO reports

Before trusting any figures, run a checklist: open the site and watch which events fire in the browser console, send a test lead, place a test order and find it in the reports, filter out staff visits and delete test orders so they do not distort revenue.

Then use the sources report: keep only search engines, look at landing pages and see goal conversion for each one. If leads go into a CRM, pass the Metrica visitor ID along with them. You can then upload offline conversions and see which search pages bring real customers rather than just enquiries.

If your Metrica numbers do not match your CRM, or SEO work feels like guesswork, the markdev team can review the setup and find where the data is lost. Tell us about your site and goals, and we will discuss where to start.