baranerf@google.com jbroman@chromium.org adithyas@chromium.org Time taken from triggering the action to receiving the combined eligibility result (local + remote). Monitors performance of the eligibility check flow, which involves network calls for remote status. baranerf@google.com jbroman@chromium.org adithyas@chromium.org Measures how long the network request takes for the remote eligibility check. Monitors the performance of the network call. baranerf@google.com jbroman@chromium.org adithyas@chromium.org Records the decision returned by keyword heuristics. Helps track how often pages are identified as eligible for Indigo by the heuristics. baranerf@google.com jbroman@chromium.org adithyas@chromium.org Records the decision returned by the Optimization Guide for the current page. Helps track how often pages are identified as eligible for Indigo by the server-side hints. baranerf@google.com jbroman@chromium.org adithyas@chromium.org Records the total duration in milliseconds from starting the image transformation process until the image is ready to be displayed to the user. jbroman@chromium.org adithyas@chromium.org baranerf@google.com Records the entry point or presentation style of the Indigo page action when it is clicked by the user. jbroman@chromium.org adithyas@chromium.org baranerf@google.com Records the entry point or presentation style of the Indigo page action when it is shown to the user. jbroman@chromium.org adithyas@chromium.org baranerf@google.com Records the trigger source for the Indigo page action when it is shown. This helps determine if Indigo was forced, or which logic was used to decide to show it (e.g., optimization guide hint). jbroman@chromium.org adithyas@chromium.org baranerf@google.com Records whether an Indigo transformation was served from the in-memory page-scoped image cache (hit) or required a new generation RPC (miss). Recorded on successful image replacement. jbroman@chromium.org adithyas@chromium.org baranerf@google.com Records the result of Indigo action invocation. Failure reasons are recorded synchronously when the user attempts to invoke the action (e.g., if they are not signed in or the service is not supported). The 'Success' result is recorded asynchronously only after the image generation completes successfully. Note that failure reasons are rarely recorded because the entry point is typically hidden for users who are known to be ineligible; therefore, low counts in failure buckets should not be misinterpreted as indicating that most users are eligible. jbroman@chromium.org adithyas@chromium.org baranerf@google.com Records the trigger source of a transformation event. This tracks which UI surface or action initiated the transformation request.