Changelog

2025

July 22

The tag creation scenario in Yandex Metrica has been updated with a new design, a revised set of options and fields, and an added step for completing a profile.
We've added a new Site profile section to help you find the best Yandex Metrica settings and tools for your business. This will also improve the relevance of our recommendations in the interface.

July 18

Tag settings now have two new options: Allow vendors to use e-commerce events in their ads and Save masked data.

July 14

Added the Yandex Metrica opt-out add-on for Google Chrome.

July 9

Yandex Metrica Pro now offers enhanced robot detection in sessions: isRobotPro in Logs API and Data Streaming.

July 1

Fully updated the Customers report section.

June 30

Improved the updated algorithm for counting pageviews within a session: repeated sessions from external sources are now excluded only when they come from the same ad. For all other traffic sources (search engines, recommendation systems, email, messengers, direct traffic, and more), repeat sessions are included in the session and counted toward page depth, session duration, and bounce rate metrics, just as before the April 30 changes.

June 19

The Market Averages tool has been updated.
Added a new dashboard: Market average sales metrics.

June 16

A new option in the additional tag settings: Delete duplicate events. It deletes duplicate e-commerce purchase events if they have the same user and purchase amount and ID, even if these events are attributed to different sessions.

May 27

Added the Page depth (obsolete), Time on site (obsolete), and Bounces (obsolete) metrics. These metrics are calculated using the algorithm that was in effect before April 30, 2025.

April 30

Updated the method for counting pageviews within a session. Only website internal traffic now counts toward session pageviews while repeated clicks from external sources are excluded from these statistics. This change may affect metrics like page depth, session duration, and the bounce rate.

April 8

The "Ad systems" report page now includes new UTM tag values for Telegram: tg_ads and tgads.
We also added a note to the Automatic goals page: after you delete a goal, it's not automatically recreated, but you can create it again manually.

April 4

The Transfer of costs page now specifies the time period for sending data to Yandex Metrica using a CSV file. You can upload your costs for the last 360 days and no more than 30 days ahead.

April 1

Added a limitation on updating web sessions using Measurement Protocol. If user sessions ended more than 12 hours ago, you need to create a new session to add events to a user's history.

March 31

The major version of Session Replay is now 2.0. Version 1.0 is no longer used.

March 28

Added the How to exclude robot sessions section to the Displaying robots in Yandex Metrica page.

March 21

Yandex Metrica can now receive revenue data for the button click and form submission goals. You can specify your revenue when setting up these goals.
Updated conditions for setting up funnels.

March 12

The Yandex Tickets Goals page now features a feedback form.

March 10

Added a note about the Don't count my sessions filter to the Filters and actions page. This filter works for browsers where you've logged in to Yandex Metrica with the tag owner's account.

March 3

Increased the limit on the number of scheduled reports for Yandex Metrica Pro tags to 200.
The standard limit is 100 reports.

February 21

On the Transmitting data from a CRM page, we described the order ID duplication issue that might occur after migrating to a new CRM. To ensure that orders are linked to sessions correctly, don't use same IDs for orders from different CRMs.
The maximum size of a CSV file you can upload to Yandex Metrica is now set to 1 GB.

February 7

Updated the example of the notice about collecting statistics.

January 13

Added new reports to Yandex Metrica. The Orders by time of day, Orders by day of the week, and Orders by month reports show how customer behavior on your site changes based on the time of day, day of the week, or month. And the Traffic by day of the week and Traffic by month reports show site traffic distribution across the week or year.

Updates in 2024

2024

December 12

Added a new article to the Basics of working with reports section: Undefined. This line indicates that there’s no data for certain cross-sections of the dimension selected in the report.

November 27

Added the instructions to the Dashboards page on how to exclude robot session data from a widget report.

November 19

New section in Yandex Metrica Pro — Changelog. You can use it to track changes in tags linked to your organization.

November 15

Added a note about passing parameters using the reachGoal method to the Transmitting events page: if you haven't created a JavaScript goal for the tag or only created it as part of a multi-step goal, the data won't appear in the Event parameters report.

November 5

For the Page views goal, you can now use matching similar URLs as a trigger. To make sure the goal is only completed on the desired pages, specify as much of the URL as possible.

October 31

New reports in Yandex Metrica: Funnel shows how users complete a specified set of steps over a certain period, while E-commerce funnel shows how a user completes specific steps relative to all other users.

October 25

The My Reports section has been renamed to Saved to Account, and Shared Reports to Saved to Tag.

October 11

New tool for data collection: Measurement Protocol. It allows you to send user interaction data directly from your server to Yandex Metrica servers via HTTP requests.

October 3

When you transfer offline conversions to Yandex Metrica, the data is now processed within 2 hours of uploading a CSV file.

October 2

New role in Yandex Metrica: Analyst.
A user in this role can create goals and segments and save reports, but cannot edit the tag settings, saved segments, goals, or reports.
Tag data access filters now available for all tags.

September 26

The Market Averages tool has been updated.
The Dashboards page has been updated with descriptions of widgets comparing market averages.
The Offline Data Tracking section has been updated, adding the ability to connect to amoCRM for exporting client and order data.

September 24

Added a new page: "Prebid events" report.

September 20

List of Exportable Data Fields — Hits (Views) has been updated: IsMobile, isTablet, isTV fields have been changed.
Updated the page How to work with data: added the sections "Popular" report, How to match a session with its hits, How to export hits. The How to export hits section was updated with the information that hits are now updatable just like sessions.

August 29

The Enabling Yandex Direct Reports page has been updated with information on report and advertising subscriptions settings in the Yandex Metrica interface in Attraction.

August 13

The Offline Data Tracking and Transmitting data from a CRM sections have been updated.

August 8

Added the Sending contact information auto-goal to the list.

July 31

New feature: transferring costs by traffic sources.

July 24

The Transfer events feature and new reports Event Parameters and Goal Parameters have been added to Yandex Metrica.
New parameters have been added to the list of hits in Yandex Metrica Pro: pageViewID, ecommerce, and params.

July 22

Interface operation restrictions (Dashboards, Reports, Settings, and Navigation) have been added to the Yandex Metrica Data Transfer Restrictions page and Yandex Metrica Pro Data Transfer Restrictions page.

July 10

The utm_source parameter values for advertising sources have been added: Gde Slon?, ADV.Cake, CityAds Media, Flocktory, Perfluence, E.PN.

July 3

The list of auto-goals for services has been expanded: transitions to payment via Yandex Pay and Yandex Split have been added.

June 21

The list of restrictions when creating a multi-step goal has been expanded: session duration cannot be used as a step.

June 20

An important note has been added: report on a group of tags is available only to the account owner and users with representative access.

June 18

Examples in the Goal Tracking Conditions table have been updated.

June 13

New report: Third-party cookies. It shows whether users have third-party cookies enabled.
New auto-goal: Logged in Yandex ID. It tracks user authorization in the Yandex ID account.

June 7

The list of temporary cookie files has been updated with _ym_sup_debug. Used for debugging Yandex Metrica tags.

May 30

The Data Processing and Storage section has been updated with clarification on processing time: usually 10–15 minutes after the event, sometimes a bit longer.

May 29

The list of temporary files set by Yandex Metrica has been updated: sessionStorage section and new files in the Cookies and localStorage sections have been added.

May 28

How to Unlink a Yandex Metrica tag from a Google Account has been supplemented: you need to remove the connection in the Google Ads connector settings.
The address has been removed from the user’s contact data in advanced matching. It is not transferred in hashed form.

May 27

Update to the list of temporary cookie files: yabs-sid now expire during the browser session.

May 17

Ozon has been added to the list of advertising systems for UTM tags.

May 15

The information on linking CRM data to sessions has been supplemented: when transferring order information from the CRM, you need to match their statuses with the statuses in Yandex Metrica using the connector or the Yandex Metrica API.
A note has been added to the Call Goals section: such goals cannot be created manually by default. It will appear in the list of available goals only after call data is transferred to Yandex Metrica.

May 14

The description of temporary cookies files set by Yandex Metrica has been corrected: is_gdpr and is_gdpr_b are set on all domains; _ym_debug, ym_visorc, and _ym_hostIndex, on the Yandex domain.

May 13

New feature for the organization’s personal account in Yandex Metrica Pro: Monitoring Access to Tags. It allows you to track which logins have access to your tags.

May 7

A clarification has been added that everyone who has access to the tag can receive the Telegram weekly report, except for users with representative rights.

April 27

The description and screenshot of switching to a representative account have been updated.
The list of temporary localStorage files has been updated with _ym_uid. Used for identifying site users.

April 22

The example and descriptions of the fields of the parameters object in firstPartyParams have been updated.

April 15

Information about the Digital Services Act (DSA) has been added to the page Compliance with the General Data Protection Regulation (GDPR).

April 9

A clarification has been added that ordering a scheduled report is available to the tag owner or a user with any level of access.

April 1

A new feature in Yandex Metrica Pro: Data Access Filters for Tags. It allows you to select which data on website traffic will be available to a Yandex Metrica user.
New tool in the Yandex Metrica interface: Favorite Goals. It allows you to select one or more goals important for your business.

March 27

The Yandex Metrica interface has been overhauled to make navigation between reports faster and provide more options for data display customization.
The Summary section has been updated and renamed to Dashboards.
The description of the url: matches condition in the Goal Tracking Conditions table has been changed.
A clarification has been added that when submitting a form, validation must be set up for the auto-goal to work correctly.

March 26

In the hit method, the url parameter has become optional.

March 22

The Automatic Goals for E-commerce section has been updated.

March 21

The list of reports not visible to users with public access has been expanded.

March 20

In Session Replay 1.0 Requirements and Limitations, Support for Pages with Canvas section has been added.
Information about Turbo Pages for Stores in Yandex Metrica has been removed, and they have been shut down.

March 19

New goal in Yandex Metrica: Session duration. It allows to track sessions where users stayed on the website longer than the set time.

March 15

The Quota section has been updated: different quotas exist for the web interface and the API, and the web interface can use API methods.

March 14

"Accuracy" of history data renamed to "Sampling".
On the Sampling page, a clarification has been added that the ability to build any report on 100% data is available to YAN partners if the volume of visible impressions consistently amounts to at least 10 million per month.

March 13

Information about the robot switch has been removed from the interface.

March 11

Added the Type column to the temporary cookie files table. The possible values of this new column are “analytical” and “technical”.

March 7

On the "Yandex Direct, summary" Report page, information on how to remove statistics for other people’s campaigns in Yandex Direct reports has been updated.

Useful links

Online training

Was the article helpful?

Previous

Next