Get desktop application:
View/edit binary Protocol Buffers messages
* A message that contains details about an analyzed verification attempt and is destined for a GCP Pub/Sub queue with a BigQuery subscription. For additional details, please see https://cloud.google.com/pubsub/docs/bigquery.
* The unique identifier for the session in which this attempt took place.
* The ordinal identifier for this attempt within a session.
* The name of the `VerificationCodeSender` used in this attempt.
* The message transport via which this attempt took place.
* The type of client that initiated this attempt.
* The ISO 3166-1 identifier for the region of the phone number associated with this attempt.
* The instant at which this attempt took place, formatted as a string that BigQuery will accept as a timestamp (see https://cloud.google.com/bigquery/docs/reference/standard-sql/data-types#timestamp_type).
* Indicates whether an account already exists with the given e164 (i.e. this is a "re-registration" attempt).
* Indicates whether this attempt to verify a phone number ultimately succeeded.
* The price to send the message associated with this attempt as reported by the sender. Prices are reported in "micros," or one millionth of the base unit of their currency. For example, a value of 100,000 with a currency of "USD" would represent a quantity of $0.10.
* The currency in which the price was reported by the sender.
* The MCC of the receiving device for this attempt as reported by the sender.
* The MNC of the receiving device for this attempt as reported by the sender.
* The estimated price to send the message associated with this attempt. Prices are reported in "micros," or one millionth of the base unit of their currency. For example, a value of 100,000 with a currency of "USD" would represent a quantity of $0.10.
* The currency for the estimated price.
* The MCC for the phone number associated with this attempt as reported by a lookup service.
* The MNC for the phone number associated with this attempt as reported by a lookup service.
* A message that contains details about a verification attempt. This message is published as soon as the outcome of the attempt is known.
* The unique identifier for the session in which this attempt took place.
* The ordinal identifier for this attempt within a session.
* The name of the `VerificationCodeSender` used in this attempt.
* The message transport via which this attempt took place.
* The type of client that initiated this attempt.
* The ISO 3166-1 identifier for the region of the phone number associated with this attempt.
* The instant at which this attempt took place, formatted as a string that BigQuery will accept as a timestamp (see https://cloud.google.com/bigquery/docs/reference/standard-sql/data-types#timestamp_type).
* Indicates whether an account already exists with the given e164 (i.e. this is a "re-registration" attempt).
* Indicates whether this attempt to verify a phone number ultimately succeeded.
* Indicates the reason we selected particular sender. (e.g. 'adaptive', 'configured', 'lang_support', 'random')
* A message that contains details about a verification attempt that was rejected by the provider due to fraud. This message is published as soon as the outcome of the attempt is known.
* The unique identifier for the session in which this attempt took place.
* The name of the `VerificationCodeSender` used in this attempt.
* The message transport via which this attempt took place.
* The type of client that initiated this attempt.
* The ISO 3166-1 identifier for the region of the phone number associated with this attempt.
* The instant at which this attempt took place, formatted as a string that BigQuery will accept as a timestamp (see https://cloud.google.com/bigquery/docs/reference/standard-sql/data-types#timestamp_type).
* Indicates whether an account already exists with the given e164 (i.e. this is a "re-registration" attempt).
* Indicates the reason we selected particular sender. (e.g. 'adaptive', 'configured', 'lang_support', 'random')