Every second business owner has sat through this unpleasant conversation. The PPC specialist sends an upbeat report: last week brought 85 conversions at a quite reasonable 1,200 rubles each. Yet when the executive opens the corporate CRM, the sales team shrugs: "At most twenty real leads came in all week—where the other sixty-five in the report came from, we have no idea."
The reverse anomaly happens too: managers answer incoming calls nonstop while web analytics shows zero performance. Marketer Dmitry Elov showed that most such mismatches stem not from contractor malice, but from basic technical confusion between a user's attempt and an actual result.
Separating Goals: Why a Button Click Doesn't Equal a Lead
The biggest mistake in web analytics is equating any click with commercial success. Yandex Metrica actively promotes so-called "Auto-goals," created automatically by the counter without a webmaster's involvement. The system cheerfully logs every press on a button labeled "Submit," every click on a tel: phone link, or every click on an email address.
But look at this through the user's eyes:
- Someone clicked the phone number on the site from a desktop computer. No call physically took place, yet the auto-goal recorded a "conversion."
- A visitor clicked the form submit button without filling in the required phone number field. The site flashed a red "Enter a valid number" notice, no submission occurred, nothing entered the database—yet the Metrica counter already scored a victory point.
- A user started typing into a field, changed their mind, and closed the browser tab.
All of these actions are attempt goals. They reflect curiosity, not commercial weight. When an inexperienced PPC specialist feeds such goals to Yandex Direct's automated strategies, the ad robot doubles down on buying people in the auction who love clicking buttons at random but never buy anything. In a separate piece, we broke down how a practical ad audit for a business owner helps spot agency padding and broken site scripts.
A true commercial conversion is strictly an outcome goal: a reachGoal event sent to analytics only after the server confirms successful database recording (HTTP 200 OK) or the user is redirected to a dedicated thank-you URL (/thank-you/).
Step-by-Step Audit with the _ym_debug=2 Debugger
To isolate the technical error and clean up your analytics, you don't need programmers. Just set aside one hour and run an express check:
- Reconcile a weekly window. Export unique deals from your CRM for the last 7–14 days and compare them with target visits in Metrica. A delta above 15–20% is a sure sign of a technical breakdown.
- Run a debugger stress test. Open your homepage in incognito mode and append
?_ym_debug=2to the URL. Metrica's official debug panel will appear in the bottom-right corner of the browser. Switch to the Events tab and click "Submit request" with completely empty fields. If the panel happily logs a goal completion, congratulations: the conversion script is bound to a mouse click (onClick) rather than a successful server response (onSuccess). - Check mobile responsiveness. Repeat the test from a smartphone. Responsive layouts often use separate pop-up modal windows where goal scripts are forgotten altogether.
Ask your marketer directly: "Which exact goal is the current Direct campaign optimizing for: a Yandex auto-goal on button click or a server-side JavaScript event for successful submission?" If the contractor is optimizing on button clicks, demand an immediate switch to the thank-you page or a confirmed CRM status.
Clear your goals of phantom clicks, and your ads will stop feeding bots and shift toward real customers.

