meacer@chromium.org trusty-transport@chromium.org Records whether the user has Advanced Protection enabled on desktop. Logged on startup when the enabled status changes. Can be logged multiple times for a user. In practice, this counts the number of Chrome startups with Advanced Protection enabled/disabled, rather than the actual user count. pkotwicz@google.com chrome-counter-abuse-alerts@google.com Records whether the user has Advanced Protection enabled in Android settings. Logged on startup. In practice, this counts the number of Chrome startups with Advanced Protection enabled/disabled, rather than the actual user count. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Records whether LoadFromDisk is attempting to read an empty pb file path. Logged whenever a component update or initial component load occurs for the RealTimeUrlChecksAllowlist component. Warning: this histogram was expired from 2025-10-31 to 2025-12-23; data may be missing. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Measures the result from performing an allowlist check when the {AllowlistSource}. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Measures the time it takes to perform a real time url allowlist check. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Measures the outcome of populating the allowlist, when the {AllowlistSource}. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Measures the number of entries in the allowlist when the {AllowlistSource}. This metric is only recorded when populating the allowlist is successful. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Records the version of the allowlist when the {AllowlistSource}. This metric is only recorded when populating the allowlist is successful. Warning: this histogram was expired from 2025-10-31 to 2025-12-15; data may be missing. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Measures the time it takes to initialize a real time url allowlist. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records if the telemetry ping sent for APK download contained a full referrer chain, or if there was an error collecting the referrer chain. Logged each time a user opted into extended reporting downloads an APK file from a normal window on Android. In M123, this was expanded to cover new kinds of failure leading to incomplete referrer chains. Warning: this histogram was expired from 2023-06-10 to 2023-08-16; data may be missing. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records whether a telemetry ping for APK download was sent, or if not, then why not. Logged each time a user downloads an APK file on Android. Warning: this histogram was expired from 2023-07-09 to 2023-08-16; data may be missing. yawfrempong@google.com chrome-counter-abuse-alerts@google.com This records whether an APK download on Android was triggered by an intent. It is true even when the intent URL does server-side redirects to the final redirect URL. It is false however in the case of any client-side navigation, whether triggered by the user or not. This is logged on every suspicious APK download. minap@chromium.org chrome-counter-abuse-alerts@google.com This records events that change application-wide Advanced Protection status to {ApplicationAPStatus}. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com The size of committed navigation ids stored in async check tracker. Logged each time DidFinishNavigation is called. The size keeps growing until the tab is closed, so this histogram helps us track if we should clean up the ids at some point. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs whether post commit interstitial is skipped when the check is completed and the result is don't proceed. Skipped means the check is completed before the navigation is finished, so the delay of the warning is minimum. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com The size of pending checkers stored in async check tracker. Logged each time TransferUrlChecker is called. This histogram helps us track if we leak any pending checker. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the threat type that triggers the safe browsing blocking page. Logged each time a safe browsing blocking page is created. Note that this metric may be biased towards SB_THREAT_TYPE_SAFE, the default threat type. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the interval between when the browser URL loader starts a request and when the browser URL loader is ready to process the response {ResponseType}. Logs each time the URL loader is ready to process the response and the start request function is previously called. During this interval, Safe Browsing checks are performed in parallel. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs whether the async checker is transferred to the tracker when it can be transferred (sync check is completed and WillProcessResponse is called). If false, it means the async check is already completed. Only logged when async check is eligible for this URL loader. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs true if the browser throttle's async checks completed faster than its sync checks, and false if the sync checks completed faster. Is not logged if there is a tie, which can happen for skipped checks. Logged when the browser throttle destructs. Only logged if async checks are eligible. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs whether the async check tracker is alive when the async checker is about to be transferred from the browser throttle to the tracker. Only logged when async check is eligible for this URL loader. The majority of the time the tracker should be alive, this metric is used to detect if the tracker is destroyed unexpectedly (i.e. the throttle outlives the tracker). xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs whether the Safe Browsing check is completed when the URL loader starts to process a response. If not, the URL loader will be deferred until the Safe Browsing check is completed. Logs each time the URL loader dispatches WillProcessResponse() and the Safe Browsing check doesn't block the URL. This metric is used to populate a dashboard on go/crsb-site. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the request destination of the URL that is checked by the browser URL loader throttle, and whether the URL check was {RequestedSkippedOrChecked}. Logged each time WillStartRequest is called. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the latency between when the browser URL loader was deferred by Safe Browsing check and when the check is completed, for URL loaded {ResponseType}. This metric logs for each request, recording zero delay when the request is not deferred. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the latency between when the browser URL loader was deferred by Safe Browsing check and when the check is completed, for {UserCategory} URL check request. This metric logs for each request, recording zero delay when the request is not deferred. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs whether the Safe Browsing check via CheckBrowseUrl method matched any local hash prefixes. Logged each time the Safe Browsing reputation of a URL is checked using local blocklists. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com The action of URL check conducted by the Safe Browsing reputation lookup. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The threat type result of the Safe Browsing local blocklist check. Logged each time a local browse URL check in DatabaseManagerMechanism completes. vakh@chromium.org chrome-counter-abuse-alerts@google.com Counts the number of times the Safe Browsing reputation lookup timeout happens. Logged each time the Safe Browsing reputation of a URL is checked. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records how long a Safe Browsing {CheckType} lookup took. Logged each time this kind of check completes, even if it times out. Note: This is the check that was initially attempted, even if it ended up falling back to a different type of check. zackhan@chromium.org chrome-counter-abuse-alerts@google.com Records whether a background hash real-time lookup was triggered within the UrlRealTimeMechanism for the real-time URL checks. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the scheme of the URL whose Safe Browsing reputation is about to be checked. Logged before it has been determined whether or not the scheme is valid for Safe Browsing. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the report type of client safe browsing reports that failed due to HTTP error 400: BAD_REQUEST. Logged each time the response is received once a report has been sent. yawfrempong@google.com chrome-counter-abuse-alerts@google.com The size of a download client Safe Browsing report. Logged each time before a download report is sent. yawfrempong@google.com chrome-counter-abuse-alerts@google.com Counts the length of the download_warning_actions field in a client Safe Browsing report. Logged each time the field is populated before a report is sent. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records whether a threat details job is in progress before sending client safe browsing report for blocking page triggered by mainframe. If it is false, no report will be sent. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records whether a threat details job is running on the current tab before sending security interstitial client safe browsing report. The job can be already deleted if the current tab is closed directly before the report is sent. Only log if the report should be sent. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the network result for a client safe browsing report request for report type {ReportType}. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the network result for a client safe browsing report request when the request {IsAccessTokenIncluded}. nwokedi@chromium.org chrome-counter-abuse-alerts@google.com After a user has interacted with a PhishGuard UI, record whether the user has visited the page before. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the result of the call to persisting a download report on disk. Logged each time a download report needs to be persisted at shutdown. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records whether reading a persisted report is successful. Logged each time a persisted report is found on startup. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Record the number of persisted report on startup. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the result of persisting a report on disk. Logged each time the persister write a report on disk. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the report type of client safe browsing reports. Logged each time a report is about to be sent. It's not logged on failed cases (e.g. serialization error or empty report). thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records whether a sent client safe browsing report request contains a GAIA-tied OAuth2 token. This token is sent only for signed-in Enhanced Safe Browsing users. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs per report type when the network request to send the report completes. Logged each time the response is received once a report has been sent. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs per report type when the network request to send the report completes when the response was 200 OK and no net error. Logged each time the response is received once a report has been sent. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs the result of an asynchronous CSD allowlist lookup in AllowlistCheckerClient. Recorded when an async lookup completes or times out. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the duration of checking a URL against the local client-side phishing detection allowlist in AllowlistCheckerClient. Recorded when the check completes, whether synchronously (immediate match/no match) or after an asynchronous lookup completes. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs the result of checking a URL against the local client-side phishing detection allowlist. This is triggered whenever the allowlist is checked, which applies both to client-side detection checks and password protection requests. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the total number of bypass events in the last 28 days. Recorded for all non-Incognito profiles that are under {UserState} every 24 hours and at startup if the last recording was more than 24 hours ago. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the total number of security sensitive events in the last 28 days. Recorded for all non-Incognito profiles that are under {UserState} every 24 hours and at startup if the last recording was more than 24 hours ago. pkotwicz@google.com chrome-counter-abuse-alerts@google.com Records whether the user's signed-in account is enrolled in the Google Advanced Protection Program. Records false if the profile is not signed-in. Logged on startup. In practice, this counts the number of Chrome startups with Advanced Protection enabled/disabled, rather than the actual user count. jacastro@chromium.org chrome-counter-abuse-alerts@google.com Records whether an ESB user has sent a Protego ping to the Safe Browsing consumer API servers within the last 24 hours. If a ping was sent since the last time this metric was logged, then this metric will report the type of that ping, otherwise it will report that none was sent. If the user has sent a ping of multiple types since the last time this metric was logged, then only the type of the most recent ping will be reported. This metric is logged at most once per day and only for users that have enhanced protection enabled. zackhan@chromium.org chrome-counter-abuse-alerts@google.com Similar to the metric SafeBrowsing.Enhanced.ProtegoRequestSentInLast24Hours. Records whether an ESB user has sent a Protego ping to the Safe Browsing consumer API servers within the last 24 hours. If a ping was sent since the last time this metric was logged, then this metric will report the type of that ping, otherwise it will report that none was sent. Different from ProtegoRequestSentInLast24Hours, if the user has sent a ping of multiple types since the last time this metric was logged, kWithToken will be reported. This metric is logged at most once per day and only for users that have enhanced protection enabled. zackhan@chromium.org chrome-counter-abuse-alerts@google.com Similar to the SafeBrowsing.Enhanced.ProtegoRequestSentInLast7Days metric, records whether an ESB user has sent a Protego ping to the Safe Browsing consumer API servers within the last 28 days. If a ping was sent since the last time this metric was logged, then this metric will report the type of that ping, otherwise it will report that none was sent. Pings that had a token are logged preferrentially over pings without a token. This metric is logged at most once per day and only for users that have enhanced protection enabled. jacastro@chromium.org chrome-counter-abuse-alerts@google.com Similar to the SafeBrowsing.Enhanced.ProtegoRequestSentInLast24Hours2 metric, records whether an ESB user has sent a Protego ping to the Safe Browsing consumer API servers within the last 7 days. If a ping was sent since the last time this metric was logged, then this metric will report the type of that ping, otherwise it will report that none was sent. Pings that had a token are logged preferrentially over pings without a token. This metric is logged at most once per day and only for users that have enhanced protection enabled. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the last bypass event type before a user disables Enhanced Safe Browsing. Logged each time a user disables Enhanced Safe Browsing. Logged at most three times a week. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the time interval between the last time Enhanced Safe Browsing was enabled and the current disabling event. Logged each time a user disables Enhanced Safe Browsing. Logged at most three times a week. If Enhanced Safe Browsing was enabled more than 30 days go, no metric is logged. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the last security sensitive event type before a user disables Enhanced Safe Browsing. Logged each time a user disables Enhanced Safe Browsing. Logged at most three times a week. jacastro@chromium.org chrome-counter-abuse-alerts@google.com Records the number of times Enhanced Safe Browsing was disabled the last 28 days. Logged each time a user disables ESB. The length of the interval that ESB was enabled is summarized by {EnabledDuration}. The maximum number of times ESB is disabled is tracked is 30, so anything above that is not logged. awado@google.com chrome-counter-abuse-alerts@google.com Records the outcome of showing an ESB promotion on a download item on the chrome://downloads page. Promotions are only shown on downloads that have been determined to be dangerous and only when the user is able to enable enhanced protection. The histogram outcome is recorded on display and on every click on the promotion. awado@google.com chrome-counter-abuse-alerts@google.com Records the amount of times the In-Product-Help (IPH) bubble is triggered on the Chrome security settings page from one of the three Enhanced Safe Browsing referral/promotion methods. richche@google.com chrome-counter-abuse-alerts@google.com Records if a persisted file is older than 3 days. Every file that is found on disk will have its age checked. richche@google.com chrome-counter-abuse-alerts@google.com Records the number of persisted files on disk when the telemetry persister is first initiated. The cache size is only checked when the persister init function is run. richche@google.com chrome-counter-abuse-alerts@google.com The size of a persisted file in bytes. This is recorded for any file found on disk, regardless of if it was successfully read. richche@google.com chrome-counter-abuse-alerts@google.com Whether the read request succeeded or not. This is recorded once for every time the persister attempts to read from a file. Read requests happen when the telemetry service successfully uploads a file. If the persister attempts to read from an empty filepath, it will be marked as a failure. richche@google.com chrome-counter-abuse-alerts@google.com Whether the write request succeeded or not. This is recorded once for every file written{Trigger}. Write requests happen on Chrome shutdown and when an extension telemetry upload is not successful. richche@google.com chrome-counter-abuse-alerts@google.com Extensions that trigger a safety check review are displayed to the user via a panel on the chrome://extensions/ page. If a user clicks the three dot menu's get more details button, we record it here. richche@google.com chrome-counter-abuse-alerts@google.com Extensions that trigger a safety check review are displayed to the user via a panel on the chrome://extensions/ page. These extensions should be reviewed by the user and acknowledged or removed. This metric records when an extension is {Action} in the extension review panel on the chrome://extensions/ page. richche@google.com chrome-counter-abuse-alerts@google.com The size of an enterprise telemetry report. This is recorded once for each send to Chrome Enterprise Reporting server, regardless of whether it was successful. Sending attempts occur periodically (default period is 5 minutes). richche@google.com chrome-counter-abuse-alerts@google.com Records the extension telemetry signal type. Logged each time a signal is triggered (eg. a cookies.get API call is invoked). Applicable only to enterprise. richche@google.com chrome-counter-abuse-alerts@google.com Extension telemetry includes file data such as file hashes for off-store extension files. This histogram measures how long it takes to collect file data for all the offstore extensions installed. It is emitted after each pass of the collection process completes which occurs periodically (every 2 hours by default). The histogram is not emitted if there are no off-store extensions installed or if the collection process is interrupted due to the browser session ending or disabling Enhanced Safe Browsing for the profile. richche@google.com chrome-counter-abuse-alerts@google.com Extension telemetry includes file data such as file hashes for off-store extension files. This histogram records the largest file size observed while collecting files to process (regardless of whether it exceeds the file size limit). Logged by the FileProcessor at periodic intervals (default: once per day) for each off-store extension installed. richche@google.com chrome-counter-abuse-alerts@google.com Extension telemetry includes file data such as file hashes for off-store extension files. This histogram records the number of applicable files found in an extension's directories. An applicable file must be non-empty, within the max size limit, and among the applicable types (eg. JS, HTML, CSS). The manifest.json file is also included. Logged by the FileProcessor at periodic intervals (default: once per day) for each off-store extension installed. richche@google.com chrome-counter-abuse-alerts@google.com Extension telemetry includes file data such as file hashes for off-store extension files. This histogram records the number of files not processed because they exceeded the max files to process per extension limit. Logged by the FileProcessor at periodic intervals (default: once per day) for each off-store extension installed. richche@google.com chrome-counter-abuse-alerts@google.com Extension telemetry includes file data such as file hashes for off-store extension files. This histogram records the number of files not processed because they exceeded the size limit for processing. Logged by the FileProcessor at periodic intervals (default: once per day) for each off-store extension installed (if applicable). richche@google.com chrome-counter-abuse-alerts@google.com Extension telemetry includes file data such as file hashes for off-store extension files. This histogram records the number of successfully processed files, including the manifest.json file. Logged by the FileProcessor at periodic intervals (default: once per day) for each off-store extension installed. richche@google.com chrome-counter-abuse-alerts@google.com Extension telemetry includes file data such as file hashes for off-store extension files. This histogram records the number of off-store extensions installed in a user profile. It is emitted at the start of each pass of the collection process which occurs periodically (every 2 hours by default). The histogram is emitted even if there are no off-store extensions installed. richche@google.com chrome-counter-abuse-alerts@google.com Extension telemetry includes file data such as file hashes for off-store extension files. This histogram records the size of a successfully processed file. Logged by the FileProcessor at periodic intervals (default: once per day) for each off-store extension installed. richche@google.com chrome-counter-abuse-alerts@google.com Extension telemetry includes file data such as file hashes for off-store extension files. This histogram records true for a valid extension, and false if the extension root directory or manifest.json file is invalid. Logged by the FileProcessor at periodic intervals (default: once per day) for each off-store extension installed. richche@google.com chrome-counter-abuse-alerts@google.com Records if the extension telemetry service is persisting a report at a write interval. True represents a persist event during a write interval, false represents a persist event during Chrome shutdown. Recorded when the extension telemetry service persists a telemetry report to disk. anunoy@chromium.org chrome-counter-abuse-alerts@google.com The HTTP response code or net error from each upload attempt. This is recorded once for each network request made as part of an upload, i.e. if an upload fails the first time, but a retry succeeds, this metric is recorded twice. Upload attempts occur periodically (default period is 1 hour) and there are multiple retries attempted (if necessary) after every upload interval. richche@google.com chrome-counter-abuse-alerts@google.com Records the reason an off-store extension is disabled. This histogram is emitted when Chrome disables an off-store extension based on a verdict received from the Extension Telemetry Server. richche@google.com chrome-counter-abuse-alerts@google.com Records the previous blocklist state for an off-store extension when it is re-enabled. This histogram is emitted when Chrome re-enables a previously disabled off-store extension based on a new verdict from the Extension Telemetry Server that un-blocklists the extension. anunoy@chromium.org chrome-counter-abuse-alerts@google.com Counts how many retries were needed to successfully complete the upload request. This is emitted only for a successful upload. Upload attempts occur periodically (default period is 1 hour) and there are multiple retries attempted (if necessary) after every upload interval. anunoy@chromium.org chrome-counter-abuse-alerts@google.com Records whether the search hijacking detector's heuristic has been matched. A match is triggered when the number of omnibox searches exceeds the number of search engine results page (SERP) landings by a certain threshold within a given time interval. This is logged each time the heuristic check is performed. anunoy@chromium.org chrome-counter-abuse-alerts@google.com Records a comparison of the omnibox search and search engine results page (SERP) landing counts at a given time interval. This is logged each time the heuristic check is performed if at least one of the two counts is greater than 0. anunoy@chromium.org chrome-counter-abuse-alerts@google.com Records discarded extension telemetry signals by type. Logged each time a signal is discarded because it contains invalid data (e.g., invalid extension id). The signal type recorded here only corresponds to a a raw signal that is created externally and passed to extension service. The count for a combined signal (that is created internally and derived from other raw signals) should always be 0 since the internally generated signal data should always be valid. anunoy@chromium.org chrome-counter-abuse-alerts@google.com Records the extension telemetry signal type. Logged each time a signal is triggered (eg. a tabs.executeScript API call is invoked). The signal can be a raw signal that is created externally and passed to extension service or a combined signal that is created internally and derived from other raw signals. Applicable only to ESB. anunoy@chromium.org chrome-counter-abuse-alerts@google.com The size of the upload request body. This is recorded once for each upload, regardless of whether it was successful. Upload attempts occur periodically (default period is 1 hour). richche@google.com chrome-counter-abuse-alerts@google.com The data size of the {SignalType} generated for an extension. The size is recorded at the time of telemetry report creation, regardless of whether the report is uploaded or not. anunoy@chromium.org chrome-counter-abuse-alerts@google.com Whether the overall upload request succeeded or not. This is recorded once for an upload request, regardless of how many retries were needed to complete the upload. Upload attempts occur periodically (default period is 1 hour) and there are multiple retries attempted (if necessary) after every upload interval. anunoy@chromium.org chrome-counter-abuse-alerts@google.com Measures the total duration (including delay due to retries) of a {Result} upload request. This is recorded after the last retry on every {Result} upload. Upload attempts occur periodically (default period is 1 hour) and there are multiple retries attempted (if necessary) after every upload interval. drubery@chromium.org chrome-counter-abuse-alerts@google.com The result of reading/parsing/accepting a new proto for the FileTypePolices repo of file extensions and their meta data. This is for the file types loaded from the component-update system. This includes both those loaded from disk shortly after startup, and those received over the network when the component version changes yawfrempong@google.com chrome-counter-abuse-alerts@google.com Integer version number citing which version of the proto data chrome just loaded. Latest version is in download_file_types.asciipb. This is for the file types loaded from the component-update system. This includes both those loaded from disk shortly after startup, and those received over the network when the component version changes drubery@chromium.org chrome-counter-abuse-alerts@google.com Records the new config version when we fail to update due to the new version being lower than the current version. drubery@chromium.org chrome-counter-abuse-alerts@google.com Records the current config version when we fail to update due to the new version being lower than the current version. drubery@chromium.org chrome-counter-abuse-alerts@google.com The result of reading/parsing/accepting a new proto for the FileTypePolices repo of file extensions and their meta data. This is for the file types loaded from the resource bundle packaged with Chrome, which is always loaded at startup. drubery@chromium.org chrome-counter-abuse-alerts@google.com Integer version number citing which version of the proto data chrome just loaded. Latest version is in download_file_types.asciipb. This is for the file types loaded from the resource bundle packaged with Chrome, which is always loaded at startup. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Records whether the history service was able to determine the number of visits to the URL. If the history service was not able to determine the number of visits, we don't need to run Gemini. Logged when the history service checks if the URL has been visited, before possibly running Gemini. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Records whether the URL has been visited before. If the URL has been visited before, we don't need to run Gemini. Logged when the history service checks if the URL has been visited, before possibly running Gemini. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Records the scam score (or probability of the page being a scam). Logged when the Gemini model response is parsed, the scam score is extracted from the response, and the content category is {GeminiAntiscamProtectionContentCategory}. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Records the latency of receiving a response from the Gemini Antiscam Protection request. Log when the response is received and {GeminiAntiscamProtectionResponseStatus}. nwokedi@chromium.org chrome-counter-abuse-alerts@google.com Records the duration GetReferringAppInfo. Recorded on downloads in Clank, PG pings, and viewing the Referrer Chain tab of chrome://safe-browsing. chlily@chromium.org chrome-counter-abuse-alerts@google.com Records the elapsed time in GetReferringAppInfo() when requesting WebAPK info to be retrieved from Java. This is recorded on a subset of calls for which SafeBrowsing.GetReferringAppInfo.Duration is recorded. chlily@chromium.org chrome-counter-abuse-alerts@google.com Records whether GetReferringAppInfo(), when requesting WebAPK info to be retrieved from Java, found a valid WebAPK start_url. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the status code from SafeBrowsing API. Only logged if the API throws an ApiException. The code definition can be found in https://developers.google.com/android/reference/com/google/android/gms/common/api/CommonStatusCodes. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com The microseconds between sending the SafeBrowsing API {Protocol} call and receiving the response. The end time is fixed in java code and does not include any thread hops or extra work. Note that this does include task queue time to respond to the IPC (and that queue time is often non-trivial). This is logged each time a response is received from SafeBrowsing API. This histogram is comparable with SB2.RemoteCall.CheckDelta which measures a similar duration for SafetyNet API calls. This histogram only records metrics on machines with high-resolution clocks. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records whether the Safe Browsing API throws an unknown exception type. Only logged if the API throws an exception. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records whether the SafeBrowsing API is available. The API can be unavailable if a non-recoverable error was encountered in a previous call. This is logged when a SafeBrowsing API {Protocol} URL check starts. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the result after validating the response from SafeBrowsing API. The result can be invalid if there is a version mismatch bewteen Chrome and GMSCore. This histogram is logged exactly once after a {Protocol} response is received from SafeBrowsing API. If there are multiple invalid values, they will be logged in the following order: lookup result, threat type, threat attribute and response status. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the {Protocol} lookup result from SafeBrowsing API. In rare circumstance (e.g. version mismatch), there may be out of range samples in this histogram. This histogram may be skewed towards success or recoverable failure buckets, because Chrome will not retry after a non-recoverable failure is encountered. Check SafeBrowsing.GmsSafeBrowsingApi.IsAvailable to see how often that happens. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the {Protocol} response status from SafeBrowsing API if the lookup result is successful. In rare circumstance (e.g. version mismatch), there may be out of range samples in this histogram. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the length of threat attributes from SafeBrowsing API if the {Protocol} lookup result is successful. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records each threat attribute from SafeBrowsing API if the {Protocol} lookup result is successful. May be logged more than once in one single response when there are multiple threat attributes. In rare circumstance (e.g. version mismatch), there may be out of range samples in this histogram. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the threat type from SafeBrowsing API if the {Protocol} lookup result is successful. In rare circumstance (e.g. version mismatch), there may be out of range samples in this histogram. The second version is introduced because SOCIAL_ENGINEERING is switched from 2 to 5. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs whether the size of the high confidence allowlist is too small. It can happen if it is misconfigured on the server-side, or the local file is corrupted on the disk. If too small, the allowlist is considered as unavailable. Logged each time a top frame URL navigation happens for users who have hash-prefix real-time lookups enabled. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs whether the local Safe Browsing stores are available. If not, all URLs are marked as safe during the lookup. Logged each time a top frame URL navigation happens for users who have hash-prefix real-time lookups enabled. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Response or error codes from SafeBrowsing hash-prefix real-time lookups when the service is in backoff mode. This is the network result that was present when we entered backoff mode. Logged when a lookup check is attempted while in backoff. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the operation outcome for hash-prefix real-time lookups when the service is in backoff mode. This is the operation outcome that was present when we entered backoff mode. Logged when a lookup check is attempted while in backoff. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs if the hash-prefix real-time lookup service is currently in backoff state due to previous errors. Logs whenever a hash-prefix real-time request is about to be attempted, which will not go through if the service is in backoff mode. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records whether all hash prefixes were found in the hash-prefix real-time lookups local cache. It indicates that as a result of the cache, there was no need to send a request to Safe Browsing servers. This is logged each time a lookup occurs, when the cache is searched. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records whether Safe Browsing can get the reputation of a URL when a hash-prefix real-time check is needed. Logged when URL is loading and hash-prefix real-time check is enabled. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logged when a SafeBrowsing hash-prefix real-time lookup request results in a net error ERR_FAILED. Specifies whether or not the error was caused by the OHTTP client destructing before it completed. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records whether the response from the hash-prefix real-time lookup contained any full hashes that did not match the requested hash prefixes. This is logged after the network request for the lookup returns. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs the latency between the start of getting a result from the cache and when the cached item is actually obtained for hash-prefix real-time lookups. This is an indicator of the efficiency of retrieving from the cache. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the threat type when the hash-prefix real-time lookup falls back to hash-prefix local database lookup. This happens when {TriggerType}. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs whether hash realtime service can obtain a non empty key from OHTTP key service. The lookup will fail if there is no key. Logged each time a top frame URL navigation happens for users who have hash-prefix real-time lookups enabled. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs whether hash-prefix real-time lookups are ineligible due to {IneligibleReason}. Logged when a browser URL loader throttle is created. Additionally, logged when creating a SafeBrowsing URL checker on iOS. There may be multiple reasons why the lookups are ineligible, but this reason is one of them. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs whether the hash-prefix real-time lookup service is found when a hash- prefix real-time check is needed. The lookup service is available if it is not nullptr. Logged when the hash-prefix real-time check is enabled and the URL doesn't match the allowlist. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs the result of checking the URL against the local Safe Browsing high confidence allowlist. Logged each time a top frame URL navigation happens for users who have hash-prefix real-time lookups enabled. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Response or error codes from SafeBrowsing hash-prefix real-time lookups. Logged when the resource check's lookup request results in entering backoff mode. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs the roundtrip time it took to perform a Safe Browsing hash-prefix real-time lookup. Logged on each resource check for which a lookup request is sent to the server. Note that this {Suffix}. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Response or error codes from SafeBrowsing hash-prefix real-time lookups that are obtained from {ResponseSource}. Logged on each resource check for which a lookup request is sent to the server. Not logged if the response is not from {ResponseSource}. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs if the OHTTP key service is currently in backoff state due to previous errors. Logs whenever a key fetch request is about to be attempted (either triggered by hash prefix lookup, asynchronous workflow or server hint), which will not go through if the service is in backoff mode. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs how the key fetch is triggered. Logs whenever a key fetch request is about to be attempted (either triggered by hash prefix lookup, asynchronous workflow or server hint), which will not go through if the service is in backoff mode. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com HTTP response code from the first SafeBrowsing hash-prefix real-time lookup using the current ohttp key. Logged only for the first response after a new ohttp key is fetched. This histogram helps us understand how often a new key fails to work. Not logged if this is the first request using the key that is retrieved from disk. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs whether OHTTP key service has a valid key cached in memory. Logged each time a key is requested through the get OHTTP key API. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Response or error codes from OHTTP key hosting endpoint. Logged on each key fetch request that is sent to the server. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the roundtrip time it took to fetch a new OHTTP key. Logged on each key fetch request that {Suffix}. {Version} xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the number of keys in the OHTTP key fetch response. Logged on each successful key fetch response that is received from the server. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the outcome of the OHTTP key fetch. Logged on each key fetch response that is received from the server. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the size of the OHTTP key fetch response. Logged on each key fetch response that is received from the server and valid at the network level {Suffix}. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the return status for hash-prefix real-time lookups. This is logged when the service is returning a response, which can be: if the result is found in the local cache, if the lookup doesn't run because the service is in backoff mode, if the lookup doesn't run because the OHTTP key can't be fetched, or after the lookup network request returns. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the operation outcome for hash-prefix real-time lookups when entering backoff mode. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The number of prefixes included in a hash-prefix real-time lookup request sent to the Google Safe Browsing servers. This excludes any prefixes found in the local cache. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs the number of unsafe threat type verdicts received in the check response (including cached results) that are relevant to hash-prefix real-time checks. Logged each time a lookup request completes without errors or when the request does not need to be sent because all the results are in the local cache. danieltwhite@google.com joemerramos@chromium.org chrome-counter-abuse-alerts@google.com Logs whether the Safe Browsing check is completed when a navigation response has arrived. If not, the navigation will be deferred until the Safe Browsing check is completed. Logs on each navigation response policy callback. danieltwhite@google.com joemerramos@chromium.org chrome-counter-abuse-alerts@google.com Logs whether a subsequent Safe Browsing navigation response without a matching call to ShouldAllowRequest was called. Logs on each subsequent navigation response policy callback. danieltwhite@google.com joemerramos@chromium.org chrome-counter-abuse-alerts@google.com Logs the latency between when a navigation response policy decision was deferred by Safe Browsing check and when the check is completed. Logs each time that a navigation was deferred by Safe Browsing check and the Safe Browsing check doesn't block the URL. danieltwhite@google.com joemerramos@chromium.org chrome-counter-abuse-alerts@google.com Logs the latency between when a navigation response policy decision was deferred by a Safe Browsing check and when the check is completed, for a {UserCategory} URL check request. This metric is different from SafeBrowsing.IOS.TotalDelay as it logs for each request, including those not deferred and those that are blocked, recording zero delay when the request is not deferred. domfc@chromium.org nancylanxiao@google.com chrome-counter-abuse-alerts@google.com This records whether local DLP scanning succeeded or not. It is logged once for each binary upload with DLP scanning enabled (file download or upload with the appropriate enterprise policies enabled). domfc@chromium.org nancylanxiao@google.com chrome-counter-abuse-alerts@google.com This records the duration of each binary upload request. It is logged once for each binary upload (file download or upload with the appropriate enterprise policies enabled). domfc@chromium.org nancylanxiao@google.com chrome-counter-abuse-alerts@google.com This records whether DLP scanning succeeded or not. It is logged once for each binary upload with DLP scanning enabled (file download or upload with the appropriate enterprise policies enabled). drubery@chromium.org nancylanxiao@google.com chrome-counter-abuse-alerts@google.com The net error or HTTP response code returned when a multipart uploader response is received for {UploaderConsumer}. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs whether the navigation id of the current navigation matches the one that is stored in unsafe resources. A warning will likely be shown if the value is true. Logged when PopUnsafeResourceForNavigation is called and the URL already matches. This histogram will help us understand how many warnings are skipped because the navigation id doesn't match. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records whether the URL being navigated to is the same as the URL flagged by Safe Browsing. They can be different if a server redirect is encountered. Logged each time a pre-commit Safe Browsing error page is about to show. If the URL is not the same, the URL displayed in the URL bar will be incorrect. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Records the latency of performing an allowlist check that happens before (possibly) performing inference on the notification content detection model. Logged when there is a request to display a persisitent notification. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Records 2 events for displaying a persistent notification for the feature that shows warnings for suspicious notifications. The first event is logged when a request is made to check the model, where the notification would otherwise be displayed immediately. The second event is logged when the notification content detection code actually displays the notification. This histogram is temporary for validating the correctness of the suspicious notification warning feature and the two event counts should match. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Records the suspicious label's score (or probability) from the notification content detection LiteRT model for some notification contents. Logged each time model inference is performed on the notification content model (for non-allowlisted sites only). skrakowi@google.com chrome-counter-abuse-alerts@google.com Records the reason an unwanted notification revocation occurred. Logged when the notification permission is revoked. skrakowi@google.com chrome-counter-abuse-alerts@google.com Records whether an origin is on the notifications global cache list. Logged when checking if an origin is on the notifications global cache list, only when the list has more than 0 entries. skrakowi@google.com chrome-counter-abuse-alerts@google.com Records the number of entries in the notifications global cache list of top legitimate notification senders. Logged when checking if an origin is on the notifications global cache list. nwokedi@chromium.org chrome-counter-abuse-alerts@google.com Records the size of a ClientSafeBrowsingReportRequest (CSBRR) in bytes. It is logged when the the NotificationTelemetryService's timer's interval has elapsed for an ESB user and the database of ServiceWorkerBehaviors is non-empty. anunoy@chromium.org chrome-counter-abuse-alerts@google.com Records whether the service worker's scope URL is present in the SafeBrowsing High Confidence Allowlist. Logged each time a service service worker's registration parameters are persisted to storage. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the reason that page load tokens are cleared. Logged each time tokens are cleared. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the duration between a token is created and a token is retrieved. Logged each time GetPageLoadToken is called and the token is found in the token map. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records whether a page load token has expired when it is retrieved. Logged each time GetPageLoadToken is called and the token is found in the token map. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records whether a page load token is found before password protection request is sent. Logged only when real time URL check is enabled. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the number of page load tokens stored in verdict cache manager. Logged each time after a periodic clean up on expired tokens is performed. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Records the number of times a user {UserEvent} a site that was flagged as phishy by safe browsing. Logged after 5 minutes of inactivity or when the user leaves the page. Note: This histogram was expired from 2026-03-29 to 2026-05-08. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Whether the Safe Browsing extended reporting service is currently enabled. Recorded for all non-Incognito profiles every 24 hours and at startup, if the last recording was more than 24 hours ago. awado@google.com chrome-counter-abuse-alerts@google.com Records the current state of the password leak toggle under standard protection on the chrome://settings/security page. Recorded for all non-Incognito profiles every 24 hours and at startup, if the last recording was more than 24 hours ago. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Whether the Safe Browsing mode is managed by the user's admin. Recorded for all non-Incognito profiles every 24 hours and at startup if the last recording was more than 24 hours ago. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com The current Safe Browsing state of the profile. Recorded for all non-Incognito profiles every 24 hours and at startup, if the last recording was more than 24 hours ago. drubery@chromium.org chrome-counter-abuse-alerts@google.com Whether the Safe Browsing enhanced protection service is currently enabled. Recorded for all non-Incognito profiles on profile startup. This metric is used to populate a dashboard on go/crsb-site. zackhan@chromium.org chrome-counter-abuse-alerts@google.com Whether the Safe Browsing enhanced protection service is currently enabled. Recorded for non-Incognito user profiles on profile startup. vakh@chromium.org chrome-counter-abuse-alerts@google.com Whether the Safe Browsing extended reporting service is currently enabled. Recorded for all non-Incognito profiles on profile startup. This metric is used to populate a dashboard on go/crsb-site. {SafeBrowsingScoutOptInLocations} vakh@chromium.org chrome-counter-abuse-alerts@google.com Whether the Safe Browsing service is currently enabled. Recorded for all non-Incognito profiles on profile startup. This metric is used to populate a dashboard on go/crsb-site. tiffanysong@google.com jacastro@chromium.org chrome-counter-abuse-alerts@google.com The current value of the JavascriptOptimizerSetting of the profile. Recorded for regular user profiles on profile startup. jeffcyr@google.com drubery@chromium.org chrome-counter-abuse-alerts@google.com The current Safe Browsing state of the main profile. Recorded for all uma log at upload time by the SafeBrowsingMetricsProvider for the main profile only. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com The result of referrer attribution, including different types of success or failure. This is incremented each time a safe browsing ping or download ping is generated. {ReferrerAttribution} xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com The length of referrer URL chain we get from referrer attribution. This is logged each time a safe browsing ping or download ping is generated. {ReferrerAttribution} xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs whether the Safe Browsing check is completed when the renderer URL loader starts to process a response. If not, the renderer URL loader will be deferred until the Safe Browsing check is completed. Logs each time the renderer URL loader dispatches WillProcessResponse() and the Safe Browsing check doesn't block the URL. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the request destination of the URL that is checked by the renderer URL loader throttle, and whether the URL check was requested. Logged each time WillStartRequest is called. nwokedi@chromium.org chrome-counter-abuse-alerts@google.com Recorded when the report-unsafe-site dialog is closed. Records the reason that the dialog was closed. nwokedi@chromium.org chrome-counter-abuse-alerts@google.com Logs whether the tab is split when the Report-Unsafe-Site dialog is shown. When a tab is split and the Report-Unsafe-Site dialog is triggered from the app menu, it is possible that the dialog is shown for a different tab than the user expected. drubery@chromium.org nancylanxiao@google.com chrome-counter-abuse-alerts@google.com The net error or HTTP response code returned when a resumable uploader response is received. This only applies to enterprise uploads. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs whether the size of the high confidence allowlist is too small. It can happen if it is misconfigured on the server-side, or the local file is corrupted on the disk. If too small, the allowlist is considered as unavailable. Logged each time a top frame URL navigation happens for users who have the real time URL lookups enabled. In M125 and M126, this contained logs from the full-screen use case of the allowlist as well. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs whether the local Safe Browsing stores are available. If not, all URLs are marked as safe during real time URL lookup. Logged each time a top frame URL navigation happens for users who have the real time URL lookups enabled. In M125 and M126, this contained logs from the full-screen use case of the allowlist as well. vakh@chromium.org chrome-counter-abuse-alerts@google.com Logs if the real time URL lookup service is currently in backoff state due to previous errors. Logs whenever a real time URL request is about to be attempted, which will not go through if the service is in backoff mode. {UserCategory} thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records whether a cleanup task trying to remove origin-keyed expired real-time URL verdict cache entries per reached the maximum number of origins that can be removed per cleanup task. Logged each time a cleanup task is run. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the time it takes to run a cleanup task in cache manager. Logged each time a cleanup task is run. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the number of real time URL verdicts stored for this profile. Logged each time a cleanup task is run. It counts both the expired and unexpired entries. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs whether Safe Browsing database can be checked in Safe Browsing URL checker. Logged each time a URL is checked by Safe Browsing URL checker. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the reason why a consumer version is preferred over the enterprise version for the RealTime URL Lookup service. Logged on all platforms with RealTime URL Lookup service, and logged whenever a URL is checked by Safe Browsing URL checker. May even be logged multiple times per URL check, depending on how many times the function is called. bcl@google.com chrome-counter-abuse-alerts@google.com Records whether a DNS resolution was attempted for the main frame URL during a real-time Safe Browsing lookup. bcl@google.com chrome-counter-abuse-alerts@google.com Records the result of the DNS resolution for the main frame URL during a real-time Safe Browsing lookup. bcl@google.com chrome-counter-abuse-alerts@google.com Records the time taken to resolve the DNS for the main frame URL during a real-time Safe Browsing lookup. thefrog@chromium.org chrome-counter-abuse-alerts@google.com When the EnterpriseRealTimeUrlCheckMode policy is enabled, logs whether a DM token is available. If the token is unavailable, the enterprise real time URL check will not be performed. This histogram reflects how often an admin has enabled the policy, but Chrome fails to apply it due to lack of DM token. Logged if the policy is enabled when a browser URL loader throttle is created. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the threat type of cached verdicts. If the threat type is not safe, it means the cache is a false positive. False positive verdicts are safe verdicts in cache manager but turns out to be dangerous in the Safe Browsing database. Logged each time a URL is checked by real time URL lookup and the response is safe from the cache manager. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the latency between the start of getting a result from the cache and when the cache is actually obtained. The time includes bouncing between IO and UI threads. This is an indicator of the efficiency of loading the cache. {UserCategory} xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the result of real time URL cache lookup. If the result is VERDICT_TYPE_UNSPECIFIED, that means cache miss and a ping will be sent afterwards. Otherwise, ping won't be sent. This is an indicator of cache hit rate. {UserCategory} xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the latency between the start of a token request and when the token is actually obtained. Logged each time a user performs a real-time Safe Browsing URL check with token. {UserCategory} xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs whether a token received from the token fetcher is nonempty. Logged each time a response is received from the token fetcher. It shows the validity of the tokens received from the token fetcher. {UserCategory} xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the threat type when the URL real-time lookup falls back to hash-prefix local database lookup. This happens when {TriggerType}. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs whether a token is attached when a URL lookup request is sent. Logged each time a URL lookup request is sent. It shows the percentage of URL lookup requests that are attached with tokens. {UserCategory} xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs whether the real time URL lookup service is found when a real time URL check is needed. The real time URL lookup service is available if it is not nullptr. Logged when real time URL check is enabled and the URL doesn't match the allowlist. zackhan@chromium.org chrome-counter-abuse-alerts@google.com Logs whether the response of the real time URL lookup is successful when the report type is {ReportType}. Logged on each resource check for which a lookup request is sent to the server. A failure can be either a network error or a parsing error. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs whether the response of the real time URL lookup is successful. Logged on each resource check for which a lookup request is sent to the server. A failure can be either a network error or a parsing error. {UserCategory} thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs the result of checking the URL against the local Safe Browsing high confidence allowlist for real time URL check request. Logged each time a top frame URL navigation happens for users who have the real time URL lookups enabled. {UserCategory} Until M117, this was being logged twice each time for iOS. Bucket ratios were still correct, just not total counts. zackhan@chromium.org chrome-counter-abuse-alerts@google.com Response or error codes from SafeBrowsing real time URL lookups when the report type is {ReportType}. Logged on each resource check for which a lookup request is sent to the server. Warning: this histogram was expired from 2024-11-17 to 2025-02-19; data may be missing. vakh@chromium.org chrome-counter-abuse-alerts@google.com Response or error codes from SafeBrowsing real time URL lookups. Logged on each resource check for which a lookup request is sent to the server. Starting M92, the ERR_HTTP_RESPONSE_CODE_FAILURE net error is matched to the actual HTTP response code. {UserCategory} vakh@chromium.org chrome-counter-abuse-alerts@google.com Logs the roundtrip time it took to perform a Safe Browsing real time URL lookup. Logged on each resource check for which a lookup request is sent to the server. {UserCategory} thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs whether a real-time lookup service request is concurrent with an existing request for the same sanitized URL. Concurrent requests are batched together so that only one network request is made to the backend lookup service. {UserCategory} xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the length of the referrer chain in a real time URL check request. Logged on each resource check for which a lookup request is sent to the server. {UserCategory} bcl@google.com chrome-counter-abuse-alerts@google.com Records the number of IP addresses contained in a referrer chain entry in the real-time lookup request. Logged for each referrer chain entry. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com The size of a real time URL check request in bytes. Logged on each resource check for which a lookup request is sent to the server. {UserCategory} xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the user population that was checked by Safe Browsing real time URL lookup. Logged on each resource check for which a lookup request is sent to the server. {UserCategory} zackhan@chromium.org chrome-counter-abuse-alerts@google.com Logs the verdict type of the response from real time URL check from an {UserPopulation} user. This histogram tells us whether EnhancedProtection users are more likely to get dangerous verdicts as well as the average number of Protego pings for EnhancedProtection users and non-EnhancedProtection users. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the verdict type of the response from real time URL check. Logged each time a response is received and the threat info size is greater than 0. {UserCategory} zackhan@chromium.org chrome-counter-abuse-alerts@google.com Logs the type of the real time URL check requests. It could be a sampled report request that only happens 1% of the time when URLs match the Protego allowlist, or a full report request otherwise when an real time URL request is sent. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the number of verdicts received in the real time URL check response. Logged on each resource check for which a lookup request is sent to the server. {UserCategory} thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records whether a Safe Browsing store has valid data, when it is queried. This is logged once for every 256 times a store is checked. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Track whether parsing results of reading the SafeBrowsing store file from disk succeeded. Recorded every time a store is read from disk. vakh@chromium.org jacastro@chromium.org chrome-counter-abuse-alerts@google.com Records the security settings bundle state right before Chrome attempts to show a toast for users migrated into the enhanced security settings bundle. The toast is only shown if the bundle state is 'enhanced'. We expect this to be 'enhanced' in most cases, as otherwise the user would've migrated into the enhanced bundle then quickly switched out of it before the toast could be shown. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the user action performed on the Safe Browsing settings page. Depending on the enum value, logged when the page is showned to the user or when the user performs an action on the page. jacastro@chromium.org tiffanysong@google.com chrome-counter-abuse-alerts@google.com Recorded during process selection when a navigation is deferred to compute site familiarity. Records the time elapsed between when the navigation is deferred and when the site familiarity verdict is reached and the navigation proceeds. jacastro@chromium.org chrome-counter-abuse-alerts@google.com Logged when the site familiarity verdict is finalized for {FrameType} navigation. Records the site familiarity verdict (Familiar or Unfamiliar). Only logged for non-incognito profiles when the V8 blocking feature is active. Familiarity is determined by the standard site familiarity heuristic (see SiteFamiliarityFetcher in the codebase). jacastro@chromium.org chrome-counter-abuse-alerts@google.com Logged after each non-incognito page navigation. Logs the matching user-familiarity heuristics for the site. If the site satisifies multiple heuristics the metric will be logged multiple times. NO_HEURISTIC_MATCH is logged if no user-familiarity heuristics match for the site. jacastro@chromium.org chrome-counter-abuse-alerts@google.com Logged after each non-off-the-record page navigation. Logs whether the site matches a heuristic which requires - The page to be on the safe browsing high confidence allowlist OR - The page to have been visited more than 24 hours ago OR - The page to have a site engagement score of > 15 jacastro@chromium.org chrome-counter-abuse-alerts@google.com Logged after each off-the-record page navigation. Logs the matching user-familiarity heuristics for the site. If the site satisifies multiple heuristics the metric will be logged multiple times. NO_HEURISTIC_MATCH is logged if no user-familiarity heuristics match for the site. pkotwicz@chromium.org chrome-counter-abuse-alerts@google.com Logged when SiteProtectionMetricsObserver has finished asynchronously fetching data from local databases in order to compute the user-familiarity for a given website. The computation occurs after each non-off-the-record page navigation. Logs the duration of fetching the data and doing the computation. pkotwicz@chromium.org chrome-counter-abuse-alerts@google.com Logged when SiteProtectionMetricsObserver has finished asynchronously fetching data from local databases in order to compute the user-familiarity for a given website. The computation occurs after each off-the-record page navigation. Logs the duration of fetching the data and doing the computation. jacastro@chromium.org chrome-counter-abuse-alerts@google.com Logged as a result of a page navigation when SiteProtectionMetricsObserver starts fetching data. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Records user interactions with the warning shown for suspicious notifications. Logged when a warning is shown and when a user performs a notification action. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Records the number of suspicious notifications, displayed on a warning notification, which have been suspended until the user taps to show the original suspicious notifications. Logged when the user taps the "Show notification(s)" button. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Records the number of suspicious notifications that were suspended behind a warning notification and despite the user tapping to show the original suspicious notifications, were unexpectedly dropped. If the expected notification count matches the actual count of notifications displayed, 0 is recorded. Logged when the user taps the "Show notification(s)" button. awado@google.com richche@google.com chrome-counter-abuse-alerts@google.com Records specific user interactions with the suspicious site warning dialog (e.g., Mark as safe, Back to safety, Dismissed, Manual Navigation, or Close tab). Logged when the warning dialog is shown, or when the user interacts with or dismisses it. awado@google.com richche@google.com chrome-counter-abuse-alerts@google.com Records whether a suspicious site warning threat type was received as a verdict during a real-time URL lookup. Logged even if the warning itself is disabled. awado@google.com richche@google.com chrome-counter-abuse-alerts@google.com Records whether the user adhered to the suspicious site warning or bypassed it. Logged when the suspicious site dialog is closed by the user interaction or navigating back. zackhan@chromium.org chrome-counter-abuse-alerts@google.com Records the outcome of the dialog when the ESB setting is synced. This dialog appears on Android when the ESB setting is synced, and it presents either an OK button to accept or a Turn On button to re-enable ESB. For this histogram, it's a dialog with a Turn On button because the ESB is synced to off. zackhan@chromium.org chrome-counter-abuse-alerts@google.com Records the dismiss reason of the message for ESB as a synced setting flow. This dialog appears on Android when the ESB setting is synced, and it presents either an OK button to accept or a Turn On button to re-enable ESB. zackhan@chromium.org chrome-counter-abuse-alerts@google.com Records the outcome of the dialog when the ESB setting is synced. This dialog appears on Android when the ESB setting is synced, and it presents either an OK button to accept or a Turn On button to re-enable ESB. For this histogram, it's a dialog with an OK button to accept the change because the ESB is synced to on. jacastro@chromium.org chrome-counter-abuse-alerts@google.com Records the result of displaying the Chrome enhanced protection opt-in/disabled dialog to sync users. It is logged once each time Chrome is informed that the account level enhanced protection bit has been disabled. jacastro@chromium.org chrome-counter-abuse-alerts@google.com Records the result of displaying the Chrome enhanced protection opt-in/enabled dialog to sync users. It is logged once each time Chrome is informed that the account level enhanced protection bit has been enabled. awado@chromium.org chrome-counter-abuse-alerts@google.com Records whether the observer-based retry mechanism for the ChromeTailoredSecurityService has been triggered or not which is logged on every update to the synced account ESB timestamp. jacastro@chromium.org chrome-counter-abuse-alerts@google.com Records the outcome of running the tailored security retry logic. It is logged once each time Chrome starts for syncing users in the cases where the retry attempt could occur. Warning: this histogram was expired from 2026-02-01 to 2026-03-05; data may be missing. jacastro@chromium.org chrome-counter-abuse-alerts@google.com Records the result of trying to show the Chrome enhanced protection opt-in/enabled notification to sync users. It is logged once each time Chrome is informed that the account level enhanced protection bit has been enabled. jacastro@chromium.org chrome-counter-abuse-alerts@google.com Logs the outcome of displaying the {PromptType} when a signed-in, syncing user changes their account tailored security setting to {Status}. Notification prompts were removed in M113 along with the corresponding UX. jacastro@chromium.org chrome-counter-abuse-alerts@google.com Safe Browsing needs a token in order to make a request to get the tailored security service bit. This histogram tracks whether getting a token is successful or not. Warning: this histogram was expired from 2025-09-29 to 2026-03-05; data may be missing. jacastro@chromium.org chrome-counter-abuse-alerts@google.com Safe Browsing needs a token in order to make a request to get the tailored security service bit. This histogram tracks the HTTP code when getting a token is not successful. jacastro@chromium.org chrome-counter-abuse-alerts@google.com The net error or HTTP response code returned when trying to fetch the OAuth token for a tailored security service query. jacastro@chromium.org chrome-counter-abuse-alerts@google.com Logs the outcome of displaying a modal dialog on Desktop when a signed-in, non-syncing user changes their account tailored security setting in the flow of consenting. Warning: this histogram was expired from 2025-12-24 to 2026-03-05; data may be missing. jacastro@chromium.org chrome-counter-abuse-alerts@google.com Logs the outcome of displaying a notification on desktop when a signed-in, non-syncing user changes their account tailored security setting not in the flow of consenting. jacastro@chromium.org chrome-counter-abuse-alerts@google.com Logs the outcome of displaying the message on Android when a signed-in, non-syncing user changes their account tailored security setting and is {Flow} of consenting. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Logs the error type from the token fetcher. Logs each time safe browsing gets a response from the token fetcher. When the error type is none, it means the token is obtained successfully. vakh@chromium.org chrome-counter-abuse-alerts@google.com Tracks the actions taken by the Ad Sampling trigger whenever it is executed. Warning: this histogram was expired from 2021-07-01 to 2021-10-25; data may be missing. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Tracks the state of the Suspicious Site trigger when its report delay timer fires. Warning: this histogram was expired from 2021-07-01 to 2023-11-28; data may be missing. vakh@chromium.org chrome-counter-abuse-alerts@google.com Tracks the events occurring in the Suspicious Site trigger whenever it is executed. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Tracks the reasons that a report requested by the Suspicious Site trigger is rejected by the Trigger Manager. Warning: this histogram was expired from 2021-11-07 to 2023-11-28; data may be missing. zackhan@chromium.org chrome-counter-abuse-alerts@google.com Tracks the the URL lookup verdicts from URL real-time lookups and the background HPRT lookups. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The size of {ThreatTypeKB} SafeBrowsing database or file on disk in 100 KB, after reading it from disk on startup and after a database update has occurred. Linear version of V4Database.Size histogram. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The size of {ThreatType} SafeBrowsing database or file on disk in megabytes, after reading it from disk on startup and after a database update has occurred. Linear version of V4Database.Size histogram. vakh@chromium.org chrome-counter-abuse-alerts@google.com The size of the SafeBrowsing database or file on disk in kilobytes, after reading it from disk on startup and after a database update has occurred. {SafeBrowsing_SBStore_Metrics} thefrog@chromium.org chrome-counter-abuse-alerts@google.com The latency of updating the SafeBrowsing database. This measures the time difference between calls to update the SafeBrowsing V4 database. This gets logged after every call for an update to the database, except for the first one. Warning: this histogram was expired from 2024-03-04 to 2024-04-17, and from 2026-03-01 to 2026-07-17; data may be missing. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Track whether a V4 request was able to be skipped because all parts of it were found in the local cache. Logged after the V4 local cache is checked. vakh@chromium.org chrome-counter-abuse-alerts@google.com Track cache hits for V4 full hashes. vakh@chromium.org chrome-counter-abuse-alerts@google.com Track get hash response hits for V4 full hash requests. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The number of prefixes included in a full hash request sent to the Google Safe Browsing servers. This is recorded each time there's a match found in the local database and requires sending a full hash request. vakh@chromium.org kcarattini@chromium.org chrome-counter-abuse-alerts@google.com Track the parsing results of a status 200 GetV4Hash request. vakh@chromium.org chrome-counter-abuse-alerts@google.com Track return status from V4 GetHash attempts. The buckets of this histogram overlap, so the counts cannot be used as percentages. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the number of verdicts received in the full hash check. Logged each time a full hash check response is received. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the number of additions hashes in a SafeBrowsing list full update. This was added in M92 to accomodate a larger maximum size. {SafeBrowsing_SBStore_Metrics} vakh@chromium.org chrome-counter-abuse-alerts@google.com Track the result of applying a full update for a store received from PVer4 SafeBrowsing service. {SafeBrowsing_SBStore_Metrics} drubery@chromium.org chrome-counter-abuse-alerts@google.com Records how long it took to perform a full update of a V4 store. This is recorded in thread time, to avoid recording any disk operations. vakh@chromium.org chrome-counter-abuse-alerts@google.com Track the result of decoding the Rice-encoded list of additions of 4-byte hash prefixes. This is logged once per store, per update containing Rice-encoded additions. This histogram is specific to processing full updates received from the server. {SafeBrowsing_SBStore_Metrics} xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the number of removals hashes in a SafeBrowsing list full update. {SafeBrowsing_SBStore_Metrics} xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the number of additions hashes in a SafeBrowsing list partial update. {SafeBrowsing_SBStore_Metrics} vakh@chromium.org chrome-counter-abuse-alerts@google.com Track the result of applying a partial update for a store received from PVer4 SafeBrowsing service. {SafeBrowsing_SBStore_Metrics} drubery@chromium.org chrome-counter-abuse-alerts@google.com Records how long it took to perform a partial update of a V4 store. This is recorded in thread time, to avoid recording any disk operations. vakh@chromium.org chrome-counter-abuse-alerts@google.com Track the result of decoding the Rice-encoded list of additions of 4-byte hash prefixes. This is logged once per store, per update containing Rice-encoded additions. This histogram is specific to processing partial updates received from the server. {SafeBrowsing_SBStore_Metrics} vakh@chromium.org chrome-counter-abuse-alerts@google.com Track the result of decoding the Rice-encoded list of indexes of hash prefixes to remove since the last update. This is logged once per store, per update containing Rice-encoded removals. {SafeBrowsing_SBStore_Metrics} xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records the number of removals hashes in a SafeBrowsing list partial update. {SafeBrowsing_SBStore_Metrics} thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the type of V4 update being processed. Logged each time an update is attempted on a store. vakh@chromium.org chrome-counter-abuse-alerts@google.com Track the result of applying an ListUpdateResponse read from disk after parsing it successfully as a protobuf. {SafeBrowsing_SBStore_Metrics} vakh@chromium.org chrome-counter-abuse-alerts@google.com Track the result of decoding the Rice-encoded list of additions of 4-byte hash prefixes. This is logged once per store, per Chrome launch. It is specific to processing V4StoreFileFormat proto read from disk. {SafeBrowsing_SBStore_Metrics} thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the granular outcome of converting the extensions blocklist from v5 to v4 format. Logged immediately after the conversion attempt completes. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records whether a store has valid data, when it is queried. This is logged once for every 256 times (a heuristic applied starting M104 for making recording more efficient) a store is checked (a few times for each download, and once when a potentially dangerous subresource is loaded). {SafeBrowsing_SBStore_Metrics} thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records how long it took to perform the V5 to V4 migration for a store on disk. Recorded when migration is attempted. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the reason why reading the V5 store failed during migration to V4. Recorded when attempting to parse the v5 store from disk fails. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Track the result of migrating a SafeBrowsing store from v5 to v4 on disk. Recorded when a migration is attempted even if it does not occur. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records whether the expected checksum is empty when verifying the checksum of a V4 store. Logged when verifying checksum of a store with valid data. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Track the parsing results of reading the SafeBrowsing V4 store file from disk. Recorded every time a store is read from disk. vakh@chromium.org chrome-counter-abuse-alerts@google.com Track the results of writing the SafeBrowsing V4 store file to disk. Recorded every time a store is written to disk. vakh@chromium.org chrome-counter-abuse-alerts@google.com Track the parsing results of a status 200 GetV4Update request. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The total size of the SafeBrowsing database or files on disk in megabytes, after reading it from disk on startup and after a database update has occurred for V5. Linear version of V5Database.Size histogram. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The size of UrlSoceng SafeBrowsing database or file on disk in megabytes, after reading it from disk on startup and after a database update has occurred for V5. Linear version of V5Database.Size histogram. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The size of {ThreatTypeKB} SafeBrowsing database or file on disk in 100 KB, after reading it from disk on startup and after a database update has occurred for V5. Linear version of V5Database.Size histogram. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The size of the SafeBrowsing database or file on disk in kilobytes, after reading it from disk on startup and after a database update has occurred for V5. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The latency of updating the SafeBrowsing database for V5. This measures the time difference between calls to update the SafeBrowsing V5 database. This gets logged after every call for an update to the database, except for the first one. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs whether a V5 GetHash response contained any full hashes that did not match the requested prefixes. Logged after a successful V5 GetHash request is parsed. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the number of GetHash attempts skipped (due to being in backoff) within the same backoff time window. Logged when recovering from backoff if any requests were skipped. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The overall outcome of a V5 GetHash operation. Logged when the operation completes, which can be due to a full cache hit, a successful network response, a network/HTTP error, a parse failure, or because the request was blocked by backoff. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The specific reason why parsing or validating a V5 GetHash network response failed. Logged when the response parsing fails or when required fields (like cache duration) are missing or invalid in the response. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The number of full hash details that matched the query for V5 local database checks. Logged when determining the most severe threat. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Track the result of applying a V5StoreFileFormat read from disk after parsing it successfully as a protobuf for V5. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records how long it took to verify and compute the checksum when converting the extensions blocklist hash file from v4 to v5 format. Logged only when checksum verification is performed and the hash file conversion completes without error. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the granular outcome of converting the extensions blocklist from v4 to v5 format. Logged immediately after the conversion attempt completes. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records whether a v5 store has valid data, when it is queried. This is logged once for every 256 times a store is checked. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records how long it took to perform the V4 to V5 migration for a store on disk. Recorded when migration is attempted. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the reason why reading the V4 store failed during migration to V5. Recorded when attempting to parse the v4 store from disk fails. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Track the result of migrating a SafeBrowsing store from v4 to v5 on disk. Recorded when a migration is attempted even if it does not occur. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Track the parsing results of reading the SafeBrowsing V5 store file from disk. Recorded every time a store is read from disk. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Track the results of writing the SafeBrowsing V5 store file to disk. Recorded every time a store is written to disk. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the category of update received from the Safe Browsing v5 update service. Logged whenever an update is processed. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Track the parsing results of a status 200 V5Update request. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Track return status from V5Update attempts. This is logged when the update request has completed and the response has either been parsed successfully or has failed. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the Rice input validation result of a V5 HashList update. Logged during parsing of the update response list before decoding. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records whether the minimum wait duration received from the V5 update response was unexpected (missing or zero). Logged when parsing the update response. jacastro@chromium.org chrome-counter-abuse-alerts@google.com Recorded during NavigationRequest::OnResponseStarted(). Records whether the navigation was delayed due to computing whether to disable v8-optimizations due to computing site-familiarity. jacastro@chromium.org chrome-counter-abuse-alerts@google.com Recorded when a navigation finishes. Records the v8-optimizer state of the frame whose navigation just finished as well as the v8-optimizer state of the topmost frame. Only recorded for non-topmost frames where the frame whose navigation just finished and the topmost frame are same-site. The purpose of this metric is to help determine how frequently an <iframe> (ex chat.google.com) has v8-optimization disabled when the toplevel frame (ex mail.google.com) has v8-optimization enabled. jacastro@chromium.org chrome-counter-abuse-alerts@google.com Recorded when a navigation finishes. Records the v8-optimizer state of the frame whose navigation just finished as well as the v8-optimizer state of the topmost frame. Only recorded for non-topmost frames. ntfschr@chromium.org src/android_webview/OWNERS Records whether the application has explicitly opted in or out of Safe Browsing by manifest tag, or if they're relying on the default behavior. This is recorded once during startup. Warning: this histogram was expired from 2024-06-06 to 2024-07-16 and 2025-01-05 to 2025-07-30; data may be missing. colibie@google.com src/android_webview/OWNERS Records whether the result of the query for Safe Browsing user consent matches the value stored in the disk cache. A value of true means they match, and false means they do not. The default value of the disk cache is false. This histogram is recorded when the query, which is called once per WebView global process startup, completes successfully. Note: Prior to M151, timeouts and errors were recorded as a consent value of false. colibie@google.com src/android_webview/OWNERS Records the result of the call to query Safe Browsing user consent. It logs success, timeout, or unknown error. It does not record the actual user consent value due to privacy considerations. This histogram is recorded when the query, which is called once per WebView global process startup, completes successfully or errors out. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the number of full hashes in the local cache for {CacheTypeForCounts} for this profile. Logged each time cleanup of expired entries is performed on the cache, which happens every 30 minutes. The value represents the count before cleanup and includes expired entries. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the number of hash prefixes in the local cache for {CacheTypeForCounts} for this profile. Logged each time cleanup of expired entries is performed on the cache, which happens every 30 minutes. The value represents the count before cleanup and includes expired entries. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs the cache duration that an item will have for a {CacheType}. Logged when the item is added to the cache. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs the remaining cache duration that an item has for a {CacheType}. Logged when there is a cache hit for the item. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records whether there was a cache hit when a hash prefix was searched for in the local cache for {CacheType}. A cache hit means the prefix was found in the cache (whether or not it has associated full hashes), which allows for that prefix not to be re-requested. This histogram is false in the case of a cache miss for the hash prefix. This is logged for each hash prefix in a lookup when the cache is searched. domfc@chromium.org nancylanxiao@google.com webprotect-team@google.com This records the bytes/sec from the size of a {CloudOrLocal} {Connector} request divided by the duration of a successful deep scanning upload request. It is logged once for each successful binary upload. domfc@chromium.org drubery@chromium.org nancylanxiao@google.com sseckler@chromium.org webprotect-team@google.com This records the {CloudOrLocal} deep scanning duration of a user {Connector} request with {Result} result. It is logged once for each binary upload with that result. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Records the number of GetHash attempts skipped (due to being in backoff) within the same backoff time window. Logged if there are any backoff errors at the time of backoff window expiry. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the category of update received from the {SafeBrowsingV4OrSB} update service. Logged whenever an update is processed. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Track return status from {SafeBrowsingV4OrSB} update attempts. The buckets of this histogram overlap, so the counts cannot be used as percentages. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the duration of the {StepName} step in a Safe Browsing {SafeBrowsingV4OrV5OrSB} URL check. Logged when this step completes. thefrog@chromium.org chrome-counter-abuse-alerts@google.com How long it took to create the {SafeBrowsingV4OrV5OrSB} database. Logged on each startup, when the database is created. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs each unique threat type that matched a prefix in the {SafeBrowsingV4OrV5OrSB} local database and initiated a full-hash lookup attempt (before checking the local cache). thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs each unique threat type included in a {SafeBrowsingV4OrV5OrSB} GetHash network request. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Response or error codes from the {SafeBrowsingV4OrV5OrSB} GetHash service. Logged after a GetHash request finishes to capture the response code or error code for that call. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The time that it took to receive a response from the Google SafeBrowsing servers for a {SafeBrowsingV4OrV5OrSB} GetHash request. Logged when the network request completes (either successfully or with an error). danieltwhite@google.com joemerramos@chromium.org chrome-counter-abuse-alerts@google.com Records the time since the last network response was received for a request to update the Safe Browsing local database. This will be logged whenever the database is queried, but only if at least one such network response has been received since the browser was launched. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records how long it took to verify the checksum of a {SafeBrowsingV4OrV5OrSB} store. This is recorded in thread time, to avoid recording any disk operations. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Logs whether an individual store has valid data immediately after being constructed. This is logged once for each {SafeBrowsingV4OrV5OrSB} store on each startup. Failures here can indicate an inability to read data from disk. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the file error when a {SafeBrowsingV4OrV5OrSB} store hash prefix map fails to be opened on disk. This can be logged once per map per database sync (roughly every 30 minutes). thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the file error when we fail to write to a previously opened {SafeBrowsingV4OrV5OrSB} store hash prefix map file. This can be logged once per map per database sync (roughly every 30 minutes). thefrog@chromium.org chrome-counter-abuse-alerts@google.com This records a more specific error for every UNEXPECTED_WRITE_FAILURE in the corresponding SafeBrowsing.*StoreWrite.Result histogram. This is logged at most once per hash prefix map write (roughly every 30 minutes). thefrog@chromium.org chrome-counter-abuse-alerts@google.com Response or error codes when fetching updates from the {SafeBrowsingV4OrV5OrSB} update service. Starting M92, the ERR_HTTP_RESPONSE_CODE_FAILURE net error is matched to the actual HTTP response code. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The time that it took for the update request to Safe Browsing servers using the {SafeBrowsingV4OrV5OrSB} update protocol, or how long it took for it to time out. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records whether the network request timed out when fetching updates from the {SafeBrowsingV4OrV5OrSB} update service. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the next update interval for Safe Browsing updates using the {SafeBrowsingV4OrV5OrSB} update protocol. Logged when calculating the next update interval. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The size of the response sent by the {SafeBrowsingV4OrV5OrSB} update service, in KB. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Track whether a {SafeBrowsingV5OrSB} GetHash request was able to be skipped because all parts of it were found in the local cache. Logged after the the local cache is checked. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The number of prefixes requested in a single GetHash request ({SafeBrowsingV5OrSB}). Recorded when a network request is sent. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The result of applying a {V5ProcessUpdateType} received from the PVer5 SafeBrowsing service. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The time it takes to apply a {V5ProcessUpdateType} received from the SafeBrowsing service. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The result of decoding Rice-encoded {AdditionsOrRemovals} from {V5ProcessUpdateType}s received from the server. thefrog@chromium.org chrome-counter-abuse-alerts@google.com The number of {AdditionsOrRemovals} hashes successfully decoded from a {V5ProcessUpdateType}. domfc@chromium.org chrome-counter-abuse-alerts@google.com This records whether DLP scanning succeeded or not. It is logged once for each binary upload with DLP scanning enabled (file download or upload with the appropriate enterprise policies enabled). drubery@chromium.org chrome-counter-abuse-alerts@google.com This records the duration of each binary upload request. It is logged once for each binary upload (file download or upload with the appropriate enterprise policies enabled). drubery@chromium.org chrome-counter-abuse-alerts@google.com This records whether the malware deep scanning succeeded or not. It is logged once for each binary upload with malware scanning enabled (file download or upload with the appropriate enterprise policies enabled). drubery@chromium.org chrome-counter-abuse-alerts@google.com This records the outcome of each binary upload request. It is logged once for each binary upload (file download or upload with the appropriate enterprise policies enabled).