View legacy technology usage details

For administrators who manage Chrome browser for a business or school.

As an admin, you can use the legacy technology report in your Google Admin console to see details about enterprise sites, visited by managed browsers, that are using the legacy web platform API and features.

Legacy technology refers to features that may be based on outdated technologies, due to the deprecation and removal of Chrome Web Platform features. Feature deprecation and removal happen as the web is evolving, you can find out more about feature deprecations and their impact on this Chromium page.

The legacy technology reporting feature proactively reports websites, both internal and external, that are using technology that will be deprecated. For example, third-party cookies, SameSite cookie changes, and older security protocols like TLS 1.0/1.1 and third-party cookies. Learn more.

This information enables you to work with developers to plan required tech migrations before the deprecation feature removals go into effect.

Before you begin

Before you can see any of the legacy technology usage details, you must set up the report.

Turn on the Legacy technology reporting policy.
1. Sign in with an administrator account to the Google Admin console.
  If you aren’t using an administrator account, you can’t access the Admin console.
2. Go to Menu Chrome browser > Settings. The User & browser settings page opens by default.
  Requires having the Mobile Device Management administrator privilege.
3. To apply the setting to all enrolled browsers, leave the top organizational unit selected. Otherwise, select a child organizational unit.
4. Go to and select Legacy technology reporting.
5. In the Configuration field, add any URLs you want to allow for the legacy technology report. The following applies:
  - Supports a max of 100 URLs, including all paths and sub-domains with a max of 256 characters per URL.
  - IP addresses and ranges are supported.
  - Wildcard, schema, port, and query are not supported.
6. Click Save.
Organizational units must have a minimum of 5 browsers, that have been active for a minimum of 28 days, enrolled to return the results for the report. It can take a few minutes for data to show up in reports.

View the report

Sign in with an administrator account to the Google Admin console.
If you aren’t using an administrator account, you can’t access the Admin console.
Go to Menu Devices > Chrome > Reports > Legacy technologies.
Requires having the Chrome administrator privilege.
(Optional) On the left, select an organizational unit.

Note: If no events are displayed, check that filters are not applied or choose different organizational units.

How does the report work?

When you add a list of URLs to the Configuration field, Chrome captures legacy technology events every time a user on a managed browser or device visits an allowlisted site where a legacy technology feature is used. The report aggregates the results based on the number of device visits. See Events.

URL Matching

By default, the legacy technology report captures events when the allowlisted URLs match the top-level site URL.
- If you want to capture events in the inline frame (embedded URLs), you need to input the frame URL in the allowlist.
- The URL allowlisted matches both top-level and iFrame URLs.
URL paths
- Paths are matched as prefixes, meaning that the legacy technology report captures legacy technology events on all URL paths that start with the URL provided. For example:
  - Policy allowlist input: https://example.com
  - All the URL paths of https://example.com such as:
    - https://example.com/path1
    - https://example.com/path2/path3
Sub-domains
- Subdomains are all matched. For example:
  - Policy allowlist input: example.com
  - All the sub-domains and their paths are matched:
    - https://sub1.example.com
    - https://sub1.example.com/path1
    - https://sub2.example.com/path3
    - https://sub3.example.co
Scheme, post, and query are ignored.

Event times

Events that happened in the last 7 days are captured in the report. Events that happened more than 7 days ago are deleted.

Filtering

The legacy technology report supports the following types of filtering:

URL filtering
- You can filter the report using any URLs from your allowlist as well as any URL and path from your allowlist.
  - For example:
    - URL allowlist: acme.com
    - You can filter the report for a specific sub-path of the acme.com such as acme.com/path

Review legacy technology information

In the report, you can view the following details for the legacy features that are part of the Web Platform Status.

Feature information	Description
Feature name	The name of the feature that is deprecated or removed.
URLs	URLs are shown in the report when an event occurred during the selected period. Important: Each feature displays the top 20 URLs with the most visits. Use the URL filter to narrow down the results.
Browser count	The total number of managed browsers where at least one deprecation event has occurred in the past 7 days. Example: Policy allowlist input: example.com Device A visits example.com/path1 in the past 7 days = 1 browser count Device A visits example.com/path2 in the past 7 days = 1 browser count
Chrome release	(If available) The deprecation date of the feature or the removal date of the feature.
Description	(If available) The detailed description and more information about the deprecation.

How to use the legacy technology reporting data

When you’ve identified that a legacy technology feature or API is used on a site, you can reach out to site owners and developers to evaluate if they want to use it. In most cases, you cannot fix these issues for a specific browser or user, the changes must be made on the site.

Google and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.

Was this helpful?

How can we improve it?