Describes whether Android Autofill was available. If not, it splits the reasons why. Only one reason is recorded (e.g. the pref isn't checked if a policy makes it impossible to set the pref).

Describes the state of a prefill request for a given, cacheable, form.

Records when a user opts in or out of the address autofill feature.

A bitmask indicating which data sources provided an accepted AtMemory suggestion.

The different types of bubbles that can be shown by the Autofill bubble manager.

A bitmask indicating which credit card field types were autofilled.

The user selected a masked server card that triggered an unmask attempt. The user selected a masked server card that triggered an unmask attempt at least once.

Describes which method of Android Autofill's AutofillManager was called. Ordered alphabetically.

Describes the surface used by the user for adding a new address.

The HTTP method used to fetch a URL. Logged as a boolean corresponding to the first two enumeration values found in ::net::URLFetcher::RequestType. See: net/url_request/url_fetcher.h

Closed with successful unmask on the first attempt. Closed with successful unmask after failed attempts.

Defines possible outcomes of handling a form submission message on iOS.

Represents the various reasons why form data extraction might fail on iOS.

The type of data a query or piece of information is related to.

The verdict of a PhishGuard check before offering to autofill one-time tokens. Recorded every time a PhishGuard check is completed.

Represents the various reasons why a form submission might be blocked or ignored by Autofill on iOS.