@google-analytics/data 3.2.2 → 4.0.0

package/build/protos/google/analytics/data/v1beta/data.proto

@@ -1,4 +1,4 @@
-// Copyright 2022 Google LLC
+// Copyright 2023 Google LLC
 //
 // Licensed under the Apache License, Version 2.0 (the "License");
 // you may not use this file except in compliance with the License.
@@ -21,8 +21,8 @@ option java_multiple_files = true;
 option java_outer_classname = "ReportingApiProto";
 option java_package = "com.google.analytics.data.v1beta";
 
-// A contiguous set of days: startDate, startDate + 1, ..., endDate. Requests
-// are allowed up to 4 date ranges.
+// A contiguous set of days: `startDate`, `startDate + 1`, ..., `endDate`.
+// Requests are allowed up to 4 date ranges.
 message DateRange {
   // The inclusive start date for the query in the format `YYYY-MM-DD`. Cannot
   // be after `end_date`. The format `NdaysAgo`, `yesterday`, or `today` is also
@@ -43,8 +43,8 @@ message DateRange {
   string name = 3;
 }
 
-// A contiguous set of minutes: startMinutesAgo, startMinutesAgo + 1, ...,
-// endMinutesAgo. Requests are allowed up to 2 minute ranges.
+// A contiguous set of minutes: `startMinutesAgo`, `startMinutesAgo + 1`, ...,
+// `endMinutesAgo`. Requests are allowed up to 2 minute ranges.
 message MinuteRange {
   // The inclusive start minute for the query as a number of minutes before now.
   // For example, `"startMinutesAgo": 29` specifies the report should include
@@ -420,7 +420,7 @@ message Pivot {
   // single pivot requests.
   //
   // The product of the `limit` for each `pivot` in a `RunPivotReportRequest`
-  // must not exceed 100,000. For example, a two pivot request with `limit:
+  // must not exceed 250,000. For example, a two pivot request with `limit:
   // 1000` in each pivot will fail because the product is `1,000,000`.
   int64 limit = 4;
 
@@ -581,6 +581,18 @@ message ResponseMetaData {
 
   // If true, indicates some buckets of dimension combinations are rolled into
   // "(other)" row. This can happen for high cardinality reports.
+  //
+  // The metadata parameter dataLossFromOtherRow is populated based on the
+  // aggregated data table used in the report. The parameter will be accurately
+  // populated regardless of the filters and limits in the report.
+  //
+  // For example, the (other) row could be dropped from the report because the
+  // request contains a filter on sessionSource = google. This parameter will
+  // still be populated if data loss from other row was present in the input
+  // aggregate data used to generate this report.
+  //
+  // To learn more, see [About the (other) row and data
+  // sampling](https://support.google.com/analytics/answer/13208658#reports).
   bool data_loss_from_other_row = 3;
 
   // Describes the schema restrictions actively enforced in creating this
@@ -739,13 +751,13 @@ message NumericValue {
 // property is exhausted, all requests to that property will return Resource
 // Exhausted errors.
 message PropertyQuota {
-  // Standard Analytics Properties can use up to 25,000 tokens per day;
-  // Analytics 360 Properties can use 250,000 tokens per day. Most requests
+  // Standard Analytics Properties can use up to 200,000 tokens per day;
+  // Analytics 360 Properties can use 2,000,000 tokens per day. Most requests
   // consume fewer than 10 tokens.
   QuotaStatus tokens_per_day = 1;
 
-  // Standard Analytics Properties can use up to 5,000 tokens per hour;
-  // Analytics 360 Properties can use 50,000 tokens per hour. An API request
+  // Standard Analytics Properties can use up to 40,000 tokens per hour;
+  // Analytics 360 Properties can use 400,000 tokens per hour. An API request
   // consumes a single number of tokens, and that number is deducted from all of
   // the hourly, daily, and per project hourly quotas.
   QuotaStatus tokens_per_hour = 2;
@@ -765,9 +777,9 @@ message PropertyQuota {
   // thresholded dimensions.
   QuotaStatus potentially_thresholded_requests_per_hour = 5;
 
-  // Analytics Properties can use up to 25% of their tokens per project per
-  // hour. This amounts to standard Analytics Properties can use up to 1,250
-  // tokens per project per hour, and Analytics 360 Properties can use 12,500
+  // Analytics Properties can use up to 35% of their tokens per project per
+  // hour. This amounts to standard Analytics Properties can use up to 14,000
+  // tokens per project per hour, and Analytics 360 Properties can use 140,000
   // tokens per project per hour. An API request consumes a single number of
   // tokens, and that number is deducted from all of the hourly, daily, and per
   // project hourly quotas.