Checking a goal

Note. Check the Don't count my sessions option (Settings → Filters). If it is enabled, follow these steps in private browsing mode (for example, Incognito mode in Yandex Browser.)

Append the ym_debug parameter with the value 1 to the page URL in the browser's address bar, and reload the page.
```
http://example.com/?_ym_debug=1
```
Open the browser console with the keyboard shortcut Ctrl + Shift + J (⌥ + ⌘ + J for Apple OS).
Perform the targeted action on the page. In the console, you will see the number of your tag and information about the completed action. The action differs depending on the type of goal being checked:
- “Page view”. In this case, PageView is displayed, notifying you when the page is viewed or updated.
- “JavaScript event”. In this case it displays Reach goal and notifies you when the reachGoal method used on the page is called.

To make sure Yandex.Metrica registers the goal, go to the page Reports → Standard reports → Conversions. Yandex.Metrica starts collecting data a few minutes after a goal is created.

If the console or interface doesn't show any data, it means the goal wasn't registered by Yandex.Metrica for any of a number of reasons.

Why aren't my goals registering?

Yandex.Metrica can't register conversions in the following cases:

The tag isn't installed on the target page. If you believe the tag is installed, make sure it is installed correctly. If some of the site's content is displayed in a frame, set the tag code inside the frame, too.
Other scripts are blocking the tag on the site.
The tag is blocked by the Adblock Plus extension.
The user left the page before the tag loaded.

The following issues may also occur depending on the type of goal:

The goal identifier in the reachGoal method does not match the identifier in the tag settings.
The code for calling the reachGoal method is missing.
The reachGoal method was added correctly, but the event that triggers this method doesn't occur (for example, if the onsubmit event for submitting form data didn't take place).
The reachGoal method was called before the code snippet initialized. In this case, the browser console shows the error “yaCounterХХХХХХ is not defined”. We recommend adding the triggerEvent parameter to the code snippet and also making it possible to complete the goal after checking for tag initialization.

The URL of the target page isn't specified in the goal settings, or is specified incorrectly.
The conditions in the goal settings are too strict (for example, the condition is “url: matches” instead of “url: contains”).
Webpage URLs contain the # symbol. In this case, if the page doesn't refresh on a click, data isn't transmitted to the tag. We recommend enabling the Hash tracking in the browser address bar option in the tag settings, and then updating the code snippet on all the site's pages.
The page has a redirect loop.

One or more of the steps can't be completed. Make sure that all the goal steps are configured correctly.
Make sure that each step can't be completed without completing the previous one.