Goal completions and goal visits in Metrica answer different questions. The first is how many times the goal condition was met, the second is in how many visits there was at least one such completion. Neither metric on its own equals the number of unique buyers.
Break down a single visit
Let's imagine a training situation: a visitor clicked a button configured as a goal twice within a single visit. With both events registered correctly, that is two completions and one goal visit. If the button merely opens a form, the event does not yet confirm that the request was submitted.
Before comparing reports, write down exactly what the goal measures: a click, a successful submission, or another condition. Do not call it a "purchase" if it fires before the result is confirmed. Check whether a single action is causing repeated event sends from different handlers.
Compare the metrics under the same conditions
Choose one goal, period, and segment. Look at the number of completions and goal visits side by side, then examine the reason for the difference. Repeats may be a normal part of the scenario, for example several uses of a calculator, or they may indicate a setup error.
To check form submission, perform a controlled action with agreed test data and trace the entire path. Do not count the test as a real request. If a successful event occurs even when the form is filled in incorrectly, first fix the goal condition and note the date of the change in the work log.
How to phrase the conclusion
Write specifically: "in the selected period there were such-and-such visits with a completion of this goal," stating the actual value from the report. Do not replace the word "visit" with the word "client." For the number of orders and payments, a separate reconciliation with confirmed business records is needed.
If there is no order data, state that limitation as such. A rise in events may mean the same people repeating the action more often; it does not prove sales growth. Purchased activity also cannot automatically be included in an assessment of an interested audience.
Related task: Repeat messages or new requests: how to link records in the registry.
Sources
Metrica: metric definitions. Verified 23 September 2026. Practical scenarios are an editorial methodology; the training examples are not client data.
If a separate public announcement for this work has been prepared on Telegram, you can look at the terms for post views. The form below applies only to such an announcement. The service does not set up goals and does not confirm payments. Purchased activity does not confirm organic interest, requests, or revenue.