sophey@chromium.org chrome-sherlock@google.com

Whether the webpage is a long-form article or not. This is logged when the user navigates away from the current page (via loading a different webpage or native page). It is only logged if the distillability of the page had been determined.

sophey@chromium.org chrome-sherlock@google.com

What the Open Graph Protocol classification of the page is. This is logged when the user navigates to the current page. It is only logged if there is an 'og:type' property in the HTML of the page.

fjacky@chromium.org dullweber@chromium.org src/components/permissions/PERMISSIONS_OWNERS

Logs the number of active expiries per provider type at content setting granularity. Events are recorded at expiry time.

cduvall@chromium.org jam@chromium.org

Measures how long a sync call to ContentSettingsManager::AllowStorageAccess takes. Logged each time a sync call is made that is not cached.

fsenra@chromium.org dullweber@chromium.org

Logs actions within the StorageAccess bubble.

engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS

Count of how often a specific content setting is set for an embedded URL by an extension. Only counts settings when the secondary pattern is different to the primary pattern. Exactly one of this or ContentSettings.ExtensionNonEmbeddedSettingSet will be emitted per call to contentSettings.set(), if the arguments to the call are valid.

engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS

Count of how often a specific content setting is set when only a single pattern is specified. Exactly one of this or ContentSettings.ExtensionEmbeddedSettingSet will be emitted per call to contentSettings.set(), if the arguments to the call are valid.

Removed in Nov 2022. alancutter@chromium.org src/chrome/browser/ui/page_action/OWNERS

Counts which content setting buttons are pressed by the user.

engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS

The number of user defined hostname patterns for content settings at browser start. Warning: this histogram was expired from 2022-08-28 to 2022-09-21; data may be missing.

engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS

Number of times a given permission was requested by a website and the user has the permission set to prompt (i.e. not blocked or allowed). Note this is probably not the metric you want - it does not correspond to the total number of times websites request a permission. Also, because specific permissions have code that can automatically block or grant permissions based on things like incognito, installed extensions etc., this does also not correspond to the number of times users are prompted to allow permissions. For a better metric to track how often users are prompted, either use ContentSettings.PermissionsActions*, or Permissions.Prompt.*. See https://crbug.com/638076 for more details. Warning: this histogram was expired from 2022-06-19 to 2022-09-21; data may be missing.

charleszhao@chromium.org lazzzis@google.com src/components/blocked_content/OWNERS

Tracks whether the popup content blocked puzzle piece was shown in the Omnibox, and how the user interacted with it.

csharrison@chromium.org lazzzis@google.com src/components/blocked_content/OWNERS

Counts of various events related to the popup blocker. Including blocked popups and overridden (clicked through) popups. This is similar to the ContentSettings.Popups but is at the per-popup layer rather than at the UI layer.

csharrison@chromium.org

Counts of various events related to the strong popup blocker (aka abusive experience enforcement), that is triggered via safe browsing.

ryankalla@google.com src/components/permissions/PERMISSIONS_OWNERS

The default Auto-verify setting at profile open. This histogram is only recorded for regular profiles.

tungnh@chromium.org src/components/permissions/PERMISSIONS_OWNERS

The default permission setting for Background Sync at profile open. This histogram is only recorded for regular profiles.

dullweber@chromium.org src/components/permissions/PERMISSIONS_OWNERS

The default storage access setting at profile open. This histogram is only recorded for regular profiles.

wenyufu@chromium.org src/components/permissions/PERMISSIONS_OWNERS

The default auto dark web content setting at profile open. Recorded for Android only. This histogram is only recorded {RegularProfileFiltered}.

Deprecated in M109. Used to include data from both regular and irregular profiles, such as incognito profiles. Consult the new histograms with the RegularProfile tag instead. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS

The default autoplay setting at profile open. This histogram is only recorded {RegularProfileFiltered}.

The default cookies setting at profile open. This histogram is only recorded {RegularProfileFiltered}.

The default permission setting for idle detection at profile open. This histogram is only recorded {RegularProfileFiltered}. This histogram was allowed to expire between 2022-10-23 and 2023-08-03.

The default image setting at profile open. This histogram is only recorded {RegularProfileFiltered}. This histogram was allowed to expire between 2022-10-23 and 2023-08-03.

The default JavaScript setting at profile open. This histogram is only recorded {RegularProfileFiltered}.

The default location setting at profile open. This histogram is only recorded {RegularProfileFiltered}.

The default camera setting at profile open. This histogram is only recorded {RegularProfileFiltered}.

The default microphone setting at profile open. Warning: this histogram was expired from 2022-06-19 to 2022-09-21; data may be missing. This histogram is only recorded {RegularProfileFiltered}.

The default MIDI permission setting on sysex (system exclusive) messages at profile open. The default microphone setting at profile open. Warning: this histogram was expired from 2022-08-21 to 2022-09-21; data may be missing. This histogram is only recorded {RegularProfileFiltered}.

The default notification setting at profile open. This histogram is only recorded {RegularProfileFiltered}.

The default popups setting at profile open. Warning: this histogram was expired from 2022-08-21 to 2022-09-21; data may be missing. This histogram is only recorded {RegularProfileFiltered}.

Deprecated in M109. Used to include data from both regular and irregular profiles, such as incognito profiles. Consult the new histograms with the RegularProfile tag instead. shuyng@google.com twellington@chromium.org

The request desktop site content setting at profile open. Recorded for Android and iOS only. This histogram is only recorded {RegularProfileFiltered}.

The default sound setting at profile open. This histogram is only recorded {RegularProfileFiltered}.

The default subresource filter setting at profile open. Warning: this histogram was expired from 2022-06-19 to 2022-09-21; data may be missing. This histogram is only recorded {RegularProfileFiltered}.

The default permission setting for WebUSB at profile open. This histogram is only recorded {RegularProfileFiltered}.

The default permission setting for Web Bluetooth at profile open. Warning: this histogram was expired from 2022-08-21 to 2022-09-21; data may be missing. This histogram is only recorded {RegularProfileFiltered}.

Deprecated in M109. Used to include data from both regular and irregular profiles, such as incognito profiles. Consult the new histograms with the RegularProfile tag instead. lshang@chromium.org dullweber@chromium.org engedy@chromium.org

The number of user defined content setting exceptions at browser start. Suffixed with the name of content setting types. Histogram content setting type: {ContentSettingsType} This histogram is only recorded {RegularProfileFiltered}.

Deprecated in M109. Used to include data from both regular and irregular profiles, such as incognito profiles. Consult the new histograms with the RegularProfile tag instead. dewittj@chromium.org feed@chromium.org

Whether the feed was fetched with activity logging enabled. This is logged on every feed fetch.

adamta@google.com sczs@chromium.org feed@chromium.org

When the NTP view hierarchy is fixed upon NTP creation, this hisotgram logs which part was broken. Temporary log used to gather info for crbug.com/1262536.

harringtond@chromium.org thegreenfrog@chromium.org feed@chromium.org

Whether showing the Feed is permitted. The Feed can be shown if (A) profile policies allow this, (B) the FeedAblationEnabled feature is disabled, and (C) the user has not turned it off in Settings. Note that this does not denote (A) whether the Feed is visible at the time the metric is emitted or (B) whether the Feed was ever visible during the browser process lifetime. iOS only. Emitted when building a MetricsLog for the current session.

carlosk@chromium.org harringtond@chromium.org feed@chromium.org

Android: The time since locally stored content was fetched from the server. Reported when the feed surface is shown, and content is refreshed from the network. This typically only happens when content is stale, so this is a measurement of how stale content is before it's replaced by a blocking refresh. Feed v2 only.

carlosk@chromium.org harringtond@chromium.org feed@chromium.org

Android: The time since locally stored content was fetched from the server. Reported when the feed surface is shown, and the local persisted feed content is loaded instead of a direct network refresh. This provides a measure of how stale feed content is when the feed loads without a blocking network request. Feed v2 only.

Deprecated in 11/2022. Replaced by ContentDuplication2 metrics. jianli@chromium.org feed@chromium.org

Android: Reports whether the feed content at the specific position is duplicate. It is reported when the feed content is received from the server.

Deprecated in 11/2022. Replaced by ContentDuplication2 metrics. jianli@chromium.org feed@chromium.org

Android: Reports the percentage of the duplicate contents received for a range of cards. It is reported when the feed contents are received from the server.

jianli@chromium.org feed@chromium.org

Android: Reports whether the feed content at the specific position is duplicate to previous contents. The feed contents that are not viewed before are not counted towards the duplication even if they show up again. It is reported when the feed content is received from the server.

jianli@chromium.org feed@chromium.org

Android: Reports the percentage of the duplicate contents received for a range of cards. The feed contents that are not viewed before are not counted towards the duplication even if they show up again. It is reported when the feed contents are received from the server.

birnie@google.com feed@chromium.org

Android: The invalid age lifetime of content fetched from the server. Reported when new content is served to the feed from the server. This provides a measure of how stale feed content is from the client side.

birnie@google.com feed@chromium.org

Android: If the content lifetime of a feed response has a non zero invalid age when fetched from the server. Reported when new content is served to the feed from the server. This provides a measure of how stale feed content is from the client side.

birnie@google.com feed@chromium.org

Android: The stale age lifetime of content fetched from the server. Reported when new content is served to the feed from the server. This provides a measure of how stale feed content is from the client side.

birnie@google.com feed@chromium.org

Android: If the content lifetime of a feed response has a non zero stale age when fetched from the server. Reported when new content is served to the feed from the server. This provides a measure of how stale feed content is from the client side.

vincb@google.com feed@chromium.org src/components/feed/OWNERS

Actions related to the feed controls.

carlosk@chromium.org harringtond@chromium.org feed@chromium.org

Android: The display status of the content suggestions when users open NTPs. Whether content suggestions are disabled by policy (e.g. enterprise or supervised users), enabled but collapsed, or enabled and expanded when a new NTP is created.

harringtond@chromium.org feed@chromium.org

Number of docids sent when loading the Feed from the network. Reported when the Feed is loaded from the network, when docview sending is allowed. This histogram has a maximum count of 100.

harringtond@chromium.org feed@chromium.org

Number of docids sent when loading the Feed from the network. Reported when the Feed is loaded from the network, when docview sending is allowed. This histogram has a maximum count of 1000, see ContentSuggestions.Feed.DocumentViewSendCount100 for a more accurate representation of lower counts.

harringtond@chromium.org feed@chromium.org

If too many document IDs are stored within a short time period, they are dropped rather than recorded in ContentSuggestions.Feed.DocumentViewSendCount. This histogram is recorded when document IDs must be dropped in this way, and reports the number of IDs dropped.

sczs@chromium.org tinazwang@chromium.org feed@chromium.org

Recorded when a signed out user triggered a sign-in related UI from feed personalization control. iOS only.

sczs@chromium.org tinazwang@chromium.org feed@chromium.org

Recorded when a user interacts with a Sync Promo inside the Feed, e.g.: accepting the bottom sync promo, or closing the top Sync promos. iOS only.

harringtond@chromium.org feed@chromium.org

Android: Status of image fetches for the feed. Recorded for each image fetch. Fetches happen when loading the feed or scrolling the feed. Fetched images are cached, so subsequent loads may not fetch again. Feed v2 only.

harringtond@chromium.org feed@chromium.org

Latencies for individual steps taken to load the feed. This is reported at most once per Chrome execution, and only reported for a Feed load operation that ends with the Feed showing up on the UI. All steps added together tally to the total time taken. Feed v2 only.

harringtond@chromium.org carlosk@chromium.org feed@chromium.org

Status of loading additional Feed content onto the bottom of the stream. Feed v2 only.

jianli@chromium.org feed@chromium.org

The interval between current pull-to-refresh time and last time when the feed is refreshed (background refresh or pull-to-refresh), up to 1 day. This is reported when the pull-to-refresh occurs.

carlosk@chromium.org harringtond@chromium.org feed@chromium.org

Android: The wire size (potentially compressed) of a {NetworkRequestType} network response received by the Feed's networking host. Recorded when a successful response is received.

sczs@chromium.org harringtond@chromium.org feed@chromium.org

The amount of time a {NetworkEvent} network event took.

harringtond@chromium.org feed@chromium.org

Android: the approximate size in bytes of the FeedQuery GET request. Recorded when a FeedQuery is sent.

carlosk@chromium.org harringtond@chromium.org feed@chromium.org

Android: the size in kb of gzip-compressed requests sent by the Feed's networking host. Recorded when a request is sent.

carlosk@chromium.org harringtond@chromium.org feed@chromium.org

Android: The integer status code of network requests made by the feed library's networking host. This code includes both protocol(1xx-5xx) and non-protocol(-xxx) errors. Recorded when a request completes.

carlosk@chromium.org harringtond@chromium.org feed@chromium.org

Android: the uncompressed size in KB of responses received by the Feed's networking host. Recorded when a successful response is received.

carlosk@chromium.org harringtond@chromium.org feed@chromium.org

The HTTP response status for a network request made by the Feed component.

carlosk@chromium.org harringtond@chromium.org feed@chromium.org

Android: failure reason when attempting to fetch an OAuth token for the feed. Recorded when a token fetch completes.

vincb@google.com feed@chromium.org

Android: Reports whether the notice card for feed action reporting has been fulfilled. Recorded when reading the response content of the feed query that is successful (includes both load stream and load more queries).

vincb@google.com feed@chromium.org

Android: Reports whether the notice card for feed action reporting has been fulfilled. Recorded when reading the response content of the load stream query that is successful.

edchin@google.com sczs@chromium.org feed@chromium.org

Tracks triggers that ask the Discover engine to refresh the feed. However, a network call may or may not occur based on configuration thresholds.

jianli@chromium.org feed@chromium.org

Android: Status of resource fetches for the feed. Recorded for each resource fetch. Fetches happen when the specific resource is needed to enhance the feed content while the feed is being displayed.

carlosk@chromium.org petewil@chromium.org feed@chromium.org

Number of each type of feedback sent about the feed.

edchin@google.com sczs@chromium.org feed@chromium.org

The amount of time a user spends in the feed in a single session. A session is measured only by user interactions or user scrolling events in the feed. Two events are considered as being within the same session if they are at most 5 minutes apart from each other. A series of events is likely to constitute a single session. A user opening the feed but having no interaction and not scrolling is not considered a session. A user tapping an article then quickly returning to the feed is considered within the same session. The time between sessions by definition will be longer than 5 minutes.

birnie@google.com feed@chromium.org

Android: If the user triggers a sign in action from somewhere in the Feed we track the status of the sign in as a boolean (successful=true, unsuccessful= false). This provides a measure of how many users are signing in via the Feed and features like Back of Card sign in promo vs other sign in avenues.

edchin@google.com sczs@chromium.org feed@chromium.org

The amount of time between user interactions or user scrolling in the feed.

edchin@google.com sczs@chromium.org feed@chromium.org

The amount of time between user feed sessions, as defined in |ContentSuggestions.Feed.SessionDuration|. This is by definition longer than 5 minutes.

carlosk@chromium.org harringtond@chromium.org feed@chromium.org

How long a user used the Feed in one day (local time midnight to midnight). Reported at most once per day. Usage reported is typically from the previous day, but could be from several days ago if the user is not active. Time is calculated starting with the first Feed interaction, until the Feed surface is closed, or the user is idle (no scrolling or other actions) for 30 seconds.

tbansal@chromium.org harringtond@chromium.org feed@chromium.org

Records count of entries in the pref store after the store is initialized (which happens during the feed service intiialization). The metric is recorded after the store is cleaned up and conpacted (as part of store initialization).

tbansal@chromium.org harringtond@chromium.org feed@chromium.org

Recorded everytime when the user clicks a feed link article and an entry is recorded to the user actions collector. The entry may not be recorded in certain cases (not a complete list): the URL of the clicked link was not valid, the MIDs was missing etc.

iwells@chromium.org harringtond@chromium.org feed@chromium.org

Result of attempting to upload a batch of one or more actions.

iwells@chromium.org harringtond@chromium.org feed@chromium.org

Result of an UploadActionsTask run in which zero or more batches of user actions are uploaded. See ContentSuggestions.Feed.UploadActionsBatchStatus for the status of a particular batch upload.

freedjm@google.com feed@chromium.org

Android: Reports whether the visibility log was uploaded successfully.

freedjm@google.com feed@chromium.org

Android: Reports whether the {LogType} log was uploaded successfully.

harringtond@chromium.org carlosk@chromium.org feed@chromium.org

Counts of Feed user actions. e.g. (Open a Card, Hide the Feed, etc.). Recorded when the user takes an explicit action related to the Feed.

harringtond@chromium.org sczs@chromium.org feed@chromium.org

Recorded whenever an Elements commands has taken place which wasn't handled explicitly by ContentSuggestions.Feed.UserActions. e.g. A new command to added server side to "Report Content".(iOS only).

harringtond@chromium.org carlosk@chromium.org feed@chromium.org

Time between the UI requesting additional stream content and failure by either a 15 second timeout or a surface closure.

harringtond@chromium.org carlosk@chromium.org feed@chromium.org

Time between the UI requesting additional stream content and the content being provided within 15 seconds. Providing content entails showing either a cached or newly fetched Feed card.

harringtond@chromium.org carlosk@chromium.org feed@chromium.org

Reported when a user taps on a {Surface} card and the page is not loaded successfully within 20 seconds.

harringtond@chromium.org carlosk@chromium.org feed@chromium.org

The time between a user tapping on a {Surface} card and the page finishes loading successfully. Only reported when loading takes less than 20 seconds.

harringtond@chromium.org carlosk@chromium.org feed@chromium.org

The time between a {Surface} opening and either providing user content, or failing to provide content. Providing content entails showing either a cached or newly fetched Feed card within 15 seconds. Success is reported upon view of the card. Failure is reported when either the surface is closed or a timeout of 15 seconds expires.

carlosk@chromium.org harringtond@chromium.org feed@chromium.org

The state of some account settings that affect Feed users. Reported once at startup (to a single bucket), for all users. Note that this histogram uses data cached from the last time the Feed was fetched. Android only.

jianli@chromium.org feed@chromium.org

Tracks the number of cards viewed at the time of pull-to-refresh. This is reported when the pull-to-refresh occurs. This is computed as the number of cards that are viewed (2/3rds of card is in the viewport) since last time when the feed is refreshed (background refresh or pull-to-refresh).

jianli@chromium.org feed@chromium.org

Tracks the percentage of cards viewed at the time of pull-to-refresh. This is reported when the pull-to-refresh occurs. This is computed as the percentage of cards that are viewed (2/3rds of card is in the viewport) since last time when the feed is refreshed (background refresh or pull-to-refresh).

freedjm@google.com feed@chromium.org

Android: Reports whether visibility logging is enabled when logging is attempted.

harringtond@chromium.org freedjm@chromium.org feed@chromium.org

Android: Time spent reading the page linked by an opened suggestion card. This is a lower-bound time. Does not include time after Chrome is closed and re-opened. Does not include time after the visited tab no longer has focus, or after the tab is navigated. For the 'open in new tab' action, time starts when the user switches to the new tab. If the user returns by tapping the suggestion again, it will be recorded as another entry in this histogram. Feed v2 only.

harringtond@chromium.org feed@chromium.org

Android: The result of following a WebFeed when the Web Feed ID is known. Reported when the follow is attempted, once per request. Triggered by a user's request to follow a Web Feed.

harringtond@chromium.org feed@chromium.org

Replaced with the ContentSuggestions.{FeedType}.FollowCount.Engaged2 histogram pattern because this one had a misleading name. It will be effectively obsoleted in the future. Android: The number of web feeds the user is following. Reported at most once per feed visit, when the user engages (FeedEngagementType.Engaged) with either the For-You or Following Feeds.

harringtond@chromium.org feed@chromium.org

Android: The number of web feeds the user is following. Reported {Event}.

harringtond@chromium.org feed@chromium.org

Android: The result of following a WebFeed when the Web Feed ID is NOT known. Reported when the follow is attempted, once per request. Triggered by a user's request to follow a Web Feed.

carlosk@chromium.org harringtond@chromium.org feed@chromium.org

Android: The time spent by the renderer main thread to collect and send back to the browser process a list of RSS/Atom links embedded in a web page. This is recorded every time the renderer fulfills a request for these links, currently only requested by the web feeds system. This histogram is only logged in platforms with high-resolution clocks.

harringtond@chromium.org feed@chromium.org

Android: Reports the total number of {ContentOrder} cards in the Following feed when data is successfully loaded to be presented to the user. Reported after an initial load. Only one of 'Grouped' or 'ReverseChron' is reported for each stream load.

harringtond@chromium.org feed@chromium.org

Change reason for the follow. Reported upon successfully following a web feed. Reported as 'true' if the web feed was recommended, even if the user did not see or interact with recommendation UI.

harringtond@chromium.org feed@chromium.org

Whether the followed web feed was recommended by the server. Reported upon successfully following a web feed.

carlosk@chromium.org harringtond@chromium.org feed@chromium.org

Records the reason why the web feeds system is requesting information from the renderer process about a loaded web page.

harringtond@chromium.org feed@chromium.org

Android: Reports which presentation of the post-follow dialog is shown. Reported when the post-follow dialog is displayed, after the user follows a Web Feed.

jeffreycohen@chromium.org feed@chromium.org

Android: Reports the result of a user's request to query a Web Feed. Reported after the query attempt has completed, once per request.

harringtond@chromium.org feed@chromium.org

The content order requested when refreshing content on the Following feed. Reported before sending a refresh request to the server. Not reported for NextPage requests.

harringtond@chromium.org feed@chromium.org

Android: Reports the status of attempting to refresh the list of recommended Web Feeds from the server. The refresh occurrs periodically when the information is stale.

harringtond@chromium.org feed@chromium.org

Android: Reports the status of attempting to refresh the list of subscribed Web Feeds from the server. {Kind}

adamta@google.com sczs@chromium.org feed@chromium.org

The sort type that was selected from the feed's sort menu.

adamta@google.com sczs@chromium.org feed@chromium.org

The currently selected sort type when the user has engaged with the Following feed.

harringtond@chromium.org feed@chromium.org

Android: The result of attempting to unfollow a WebFeed. Reported when the unfollow is attempted, once per request. Triggered by a user's request to unfollow a Web Feed.

jianli@chromium.org feed@chromium.org

Android: records errors occurred during the video player initialization. The embedded video player needs to be initialized before it can be used to play a video in {PlayType} mode. In autoplay muted mode, the initialization may kick off even before the video view is scrolled to become visible. In normal unmuted mode, this happens when the user taps the video to launch the video in fullscreen playing mode.

jianli@chromium.org feed@chromium.org

Android: records errors occurred during the video playing, in {PlayType} mode. Upon the successful initialization of the embedded player, the video starts to play and any error occurs since then is reported here.

jianli@chromium.org feed@chromium.org

Android: records events triggered during the video playing, in {PlayType} mode.

jeffreyochen@chromium.org creator@chromium.org

Android: reports the entry point used to launch the single web feed view.

guiperez@google.com feed@chromium.org

Tracks user activity buckets with {FeedType}. Each bucket composed of the user's activity level. Logs the for the first time 1 day after the metric is active (only on first time use), then logs an activity bucket after at least 24hrs from the last log have elapsed. When the "Engaged" metric is triggered we log one more day of activity during the past 28 days.

guiperez@google.com feed@chromium.org

Tracks user activity buckets for the filter. Reported every time a metric is reported through the MetricsProvider to allow filtering. The histogram used for analysis is ContentSuggestions.{FeedType}.Activity, whilst this one will only be used for the filter. Any changes to ContentSuggestions.{FeedType}.Activity will also change how this metric is reported.

adamta@google.com feed@chromium.org

iOS: Before switching to a new feed type, logs the index of the last visible card.

petewil@chromium.org harringtond@chromium.org feed@chromium.org

Tracks user behavior with {FeedType}. Each bucket is one of two types of metric. Per-visit metrics sample once per "visit", which is a cluster of user activities separated by less than 5 minutes of inactivity. Per-visit metrics record a sample at the moment that the visit's criteria are first met. Per-interaction metrics are not clustered and report samples immediately. In the UI, Bucket Proportion and Total Count are not meaningful as these metrics are not independent. All buckets of this metric can be moved by changes in the Discover service as well as by client changes. go/discover-oncall describes how to get in touch with Discover oncall engineers.

harringtond@chromium.org feed@chromium.org

Android: The number of web feeds the user is following. Reported at most once per feed visit, when the user engages (FeedEngagementType.Engaged, non-Simple) with {FeedType}.

jianli@chromium.org harringtond@chromium.org feed@chromium.org

Android: Reports when {Action} has occurred for an info card. The type of the info card was reported.

Deprecated in 05/2022 since we removed feed notice card related codes. jianli@chromium.org feed@chromium.org

Android: Reports when an invalid notice key is received from the server.

harringtond@chromium.org feed@chromium.org

Android: Reports the total number of cards when the {FeedType} data is successfully loaded to be presented to the user. Reported after an initial load. Not reported after a NextPage request. When loading data from local storage, previously fetched NextPage cards are counted though.

dewittj@chromium.org feed@chromium.org

The number of cards not yet scrolled into visibility at the moment the Feed decides to load more content.

dewittj@chromium.org feed@chromium.org

The total number of cards in the feed stream at the moment the Feed decides to load more content.

harringtond@chromium.org carlosk@chromium.org feed@chromium.org

Android: Status of loading new {FeedType} data in the background. Reported any time Chrome attempts to fetch fresh Feed content in the background. This is either due to a background fetch schedule, or when fetching the Web-Feed while the For-You feed is active.

harringtond@chromium.org carlosk@chromium.org feed@chromium.org

Android: Status of loading the initial {FeedType} stream, which happens when the {FeedType} surface is shown. Feed v2 only.

harringtond@chromium.org carlosk@chromium.org feed@chromium.org

Android: The status of loading the Feed from the local store. Reported when loading the Feed for display. Recorded at the same time as ContentSuggestions.{FeedType}.LoadStreamStatus.Initial to differentiate between store errors and network fetch results.

jianli@chromium.org feed@chromium.org

Android: status of pulling-to-refresh the {FeedType} stream per the user request. Reported when the refresh completes.

Deprecated in 05/2022 since we removed feed notice card related codes. jianli@chromium.org feed@chromium.org

Android: Reports how the notice acknowledgement is reached. Reported when an action, i.e. viewing, tapping or dismissing the notice, results in the notice being acknowledged.

Deprecated in 05/2022 since we removed feed notice card related codes. jianli@chromium.org feed@chromium.org

Android: Reports whether an {Action} for an notice is performed.

freedjm@chromium.org feed@chromium.org

Android: The position of the {FeedType} card on it's surface, that is clicked through to the host website of the content. We track the position the card had in the list when it was first seen by the user. This tracked position can be different from the position observed by the user, e.g. when the user dismissed some suggestions from the list or requested more that got inserted in the middle of the feed.

harringtond@chromium.org feed@chromium.org

Android: Reports the number of cards in the {FeedType}. Reported when the last card of the {FeedType} is shown. Note that this is reported even if the Feed is attempting to load additional content (LoadMore), as long as the last card is 2/3rds shown before additional content loads. In this case, this histogram can be reported multiple times without leaving the Feed surface.

harringtond@chromium.org feed@chromium.org

Android: Reports the total size in KB of the shared state for the {FeedType}. Reported once when loading {FeedType} content for display, and once each time additional pages of content are added.

freedjm@chromium.org feed@chromium.org

Android: The position of a {FeedType} card that was shown on it's surface. A card is considered shown when at least 2/3 of its height is visible on the screen. For each card, at most one impression is recorded per instance. We track the position the card had in the list when it was first seen by the user. This tracked position can be different from the position observed by the user, e.g. when the user dismissed some suggestions from the list or requested more that got inserted in the middle of the feed.

harringtond@chromium.org feed@chromium.org

Android: Reports the total size in KB of all of the {FeedType} content (not including shared state, or dynamically fetched media). Reported once when loading {FeedType} content for display, and once each time additional pages of content are added.