From a4305eb487eec6c9c6a42f846d083c944d25e99e Mon Sep 17 00:00:00 2001
From: "gcf-owl-bot[bot]" <78513119+gcf-owl-bot[bot]@users.noreply.github.com>
Date: Tue, 8 Aug 2023 18:54:14 +0530
Subject: [PATCH] docs: Minor formatting (#6537)
docs: Add clarifications
PiperOrigin-RevId: 553885123
Source-Link: https://github.com/googleapis/googleapis/commit/9458a5adb714906f10b9ffd7aba1f91497f5b82f
Source-Link: https://github.com/googleapis/googleapis-gen/commit/8b7876034fcfb521dbd9297709e073b61cd89351
Copy-Tag: eyJwIjoiQW5hbHl0aWNzRGF0YS8uT3dsQm90LnlhbWwiLCJoIjoiOGI3ODc2MDM0ZmNmYjUyMWRiZDkyOTc3MDllMDczYjYxY2Q4OTM1MSJ9
---
.../src/V1beta/CheckCompatibilityRequest.php | 12 ----
AnalyticsData/src/V1beta/DateRange.php | 4 +-
.../Gapic/BetaAnalyticsDataGapicClient.php | 24 +++++---
AnalyticsData/src/V1beta/MinuteRange.php | 4 +-
AnalyticsData/src/V1beta/Pivot.php | 8 +--
AnalyticsData/src/V1beta/PropertyQuota.php | 56 +++++++++----------
AnalyticsData/src/V1beta/ResponseMetaData.php | 36 ++++++++++++
.../src/V1beta/RunPivotReportRequest.php | 20 +++++++
.../src/V1beta/RunRealtimeReportRequest.php | 8 +--
AnalyticsData/src/V1beta/RunReportRequest.php | 36 +++++++++---
10 files changed, 141 insertions(+), 67 deletions(-)
diff --git a/AnalyticsData/src/V1beta/CheckCompatibilityRequest.php b/AnalyticsData/src/V1beta/CheckCompatibilityRequest.php
index efdee8cac98..85cc2221a1f 100644
--- a/AnalyticsData/src/V1beta/CheckCompatibilityRequest.php
+++ b/AnalyticsData/src/V1beta/CheckCompatibilityRequest.php
@@ -24,9 +24,6 @@ class CheckCompatibilityRequest extends \Google\Protobuf\Internal\Message
* ID](https://developers.google.com/analytics/devguides/reporting/data/v1/property-id).
* `property` should be the same value as in your `runReport` request.
* Example: properties/1234
- * Set the Property ID to 0 for compatibility checking on dimensions and
- * metrics common to all properties. In this special mode, this method will
- * not return custom dimensions and metrics.
*
* Generated from protobuf field string property = 1;
*/
@@ -80,9 +77,6 @@ class CheckCompatibilityRequest extends \Google\Protobuf\Internal\Message
* ID](https://developers.google.com/analytics/devguides/reporting/data/v1/property-id).
* `property` should be the same value as in your `runReport` request.
* Example: properties/1234
- * Set the Property ID to 0 for compatibility checking on dimensions and
- * metrics common to all properties. In this special mode, this method will
- * not return custom dimensions and metrics.
* @type array<\Google\Analytics\Data\V1beta\Dimension>|\Google\Protobuf\Internal\RepeatedField $dimensions
* The dimensions in this report. `dimensions` should be the same value as in
* your `runReport` request.
@@ -112,9 +106,6 @@ public function __construct($data = NULL) {
* ID](https://developers.google.com/analytics/devguides/reporting/data/v1/property-id).
* `property` should be the same value as in your `runReport` request.
* Example: properties/1234
- * Set the Property ID to 0 for compatibility checking on dimensions and
- * metrics common to all properties. In this special mode, this method will
- * not return custom dimensions and metrics.
*
* Generated from protobuf field string property = 1;
* @return string
@@ -130,9 +121,6 @@ public function getProperty()
* ID](https://developers.google.com/analytics/devguides/reporting/data/v1/property-id).
* `property` should be the same value as in your `runReport` request.
* Example: properties/1234
- * Set the Property ID to 0 for compatibility checking on dimensions and
- * metrics common to all properties. In this special mode, this method will
- * not return custom dimensions and metrics.
*
* Generated from protobuf field string property = 1;
* @param string $var
diff --git a/AnalyticsData/src/V1beta/DateRange.php b/AnalyticsData/src/V1beta/DateRange.php
index cd067eb52b9..7c8515fbe9d 100644
--- a/AnalyticsData/src/V1beta/DateRange.php
+++ b/AnalyticsData/src/V1beta/DateRange.php
@@ -9,8 +9,8 @@
use Google\Protobuf\Internal\GPBUtil;
/**
- * 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.
*
* Generated from protobuf message google.analytics.data.v1beta.DateRange
*/
diff --git a/AnalyticsData/src/V1beta/Gapic/BetaAnalyticsDataGapicClient.php b/AnalyticsData/src/V1beta/Gapic/BetaAnalyticsDataGapicClient.php
index dbe9787af5c..4fdeef7c0e5 100644
--- a/AnalyticsData/src/V1beta/Gapic/BetaAnalyticsDataGapicClient.php
+++ b/AnalyticsData/src/V1beta/Gapic/BetaAnalyticsDataGapicClient.php
@@ -457,10 +457,6 @@ public function batchRunReports(array $optionalArgs = [])
* `property` should be the same value as in your `runReport` request.
*
* Example: properties/1234
- *
- * Set the Property ID to 0 for compatibility checking on dimensions and
- * metrics common to all properties. In this special mode, this method will
- * not return custom dimensions and metrics.
* @type Dimension[] $dimensions
* The dimensions in this report. `dimensions` should be the same value as in
* your `runReport` request.
@@ -668,6 +664,13 @@ public function getMetadata($name, array $optionalArgs = [])
* If false or unspecified, each row with all metrics equal to 0 will not be
* returned. If true, these rows will be returned if they are not separately
* removed by a filter.
+ *
+ * Regardless of this `keep_empty_rows` setting, only data recorded by the
+ * Google Analytics (GA4) property can be displayed in a report.
+ *
+ * For example if a property never logs a `purchase` event, then a query for
+ * the `eventName` dimension and `eventCount` metric will not have a row
+ * eventName: "purchase" and eventCount: 0.
* @type bool $returnPropertyQuota
* Toggles whether to return the current state of this Analytics Property's
* quota. Quota is returned in [PropertyQuota](#PropertyQuota).
@@ -790,7 +793,7 @@ public function runPivotReport(array $optionalArgs = [])
* SQL having-clause. Dimensions cannot be used in this filter.
* @type int $limit
* The number of rows to return. If unspecified, 10,000 rows are returned. The
- * API returns a maximum of 100,000 rows per request, no matter how many you
+ * API returns a maximum of 250,000 rows per request, no matter how many you
* ask for. `limit` must be positive.
*
* The API can also return fewer rows than the requested `limit`, if there
@@ -934,7 +937,7 @@ public function runRealtimeReport(array $optionalArgs = [])
* response rows for both date ranges. In a cohort request, this `dateRanges`
* must be unspecified.
* @type FilterExpression $dimensionFilter
- * Dimension filters allow you to ask for only specific dimension values in
+ * Dimension filters let you ask for only specific dimension values in
* the report. To learn more, see [Fundamentals of Dimension
* Filters](https://developers.google.com/analytics/devguides/reporting/data/v1/basics#dimension_filters)
* for examples. Metrics cannot be used in this filter.
@@ -953,7 +956,7 @@ public function runRealtimeReport(array $optionalArgs = [])
* [Pagination](https://developers.google.com/analytics/devguides/reporting/data/v1/basics#pagination).
* @type int $limit
* The number of rows to return. If unspecified, 10,000 rows are returned. The
- * API returns a maximum of 100,000 rows per request, no matter how many you
+ * API returns a maximum of 250,000 rows per request, no matter how many you
* ask for. `limit` must be positive.
*
* The API can also return fewer rows than the requested `limit`, if there
@@ -980,6 +983,13 @@ public function runRealtimeReport(array $optionalArgs = [])
* If false or unspecified, each row with all metrics equal to 0 will not be
* returned. If true, these rows will be returned if they are not separately
* removed by a filter.
+ *
+ * Regardless of this `keep_empty_rows` setting, only data recorded by the
+ * Google Analytics (GA4) property can be displayed in a report.
+ *
+ * For example if a property never logs a `purchase` event, then a query for
+ * the `eventName` dimension and `eventCount` metric will not have a row
+ * eventName: "purchase" and eventCount: 0.
* @type bool $returnPropertyQuota
* Toggles whether to return the current state of this Analytics Property's
* quota. Quota is returned in [PropertyQuota](#PropertyQuota).
diff --git a/AnalyticsData/src/V1beta/MinuteRange.php b/AnalyticsData/src/V1beta/MinuteRange.php
index 5f4a576f6a3..cf5895b025c 100644
--- a/AnalyticsData/src/V1beta/MinuteRange.php
+++ b/AnalyticsData/src/V1beta/MinuteRange.php
@@ -9,8 +9,8 @@
use Google\Protobuf\Internal\GPBUtil;
/**
- * 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.
*
* Generated from protobuf message google.analytics.data.v1beta.MinuteRange
*/
diff --git a/AnalyticsData/src/V1beta/Pivot.php b/AnalyticsData/src/V1beta/Pivot.php
index 78ee6686bdb..ecbd81cb5b0 100644
--- a/AnalyticsData/src/V1beta/Pivot.php
+++ b/AnalyticsData/src/V1beta/Pivot.php
@@ -45,7 +45,7 @@ class Pivot extends \Google\Protobuf\Internal\Message
* pivot. The `limit` parameter is required. A `limit` of 10,000 is common for
* 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`.
*
* Generated from protobuf field int64 limit = 4;
@@ -83,7 +83,7 @@ class Pivot extends \Google\Protobuf\Internal\Message
* pivot. The `limit` parameter is required. A `limit` of 10,000 is common for
* 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`.
* @type array|\Google\Protobuf\Internal\RepeatedField $metric_aggregations
* Aggregate the metrics by dimensions in this pivot using the specified
@@ -192,7 +192,7 @@ public function setOffset($var)
* pivot. The `limit` parameter is required. A `limit` of 10,000 is common for
* 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`.
*
* Generated from protobuf field int64 limit = 4;
@@ -208,7 +208,7 @@ public function getLimit()
* pivot. The `limit` parameter is required. A `limit` of 10,000 is common for
* 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`.
*
* Generated from protobuf field int64 limit = 4;
diff --git a/AnalyticsData/src/V1beta/PropertyQuota.php b/AnalyticsData/src/V1beta/PropertyQuota.php
index f114976a8d5..068a2effcbc 100644
--- a/AnalyticsData/src/V1beta/PropertyQuota.php
+++ b/AnalyticsData/src/V1beta/PropertyQuota.php
@@ -18,16 +18,16 @@
class PropertyQuota extends \Google\Protobuf\Internal\Message
{
/**
- * 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.
*
* Generated from protobuf field .google.analytics.data.v1beta.QuotaStatus tokens_per_day = 1;
*/
private $tokens_per_day = null;
/**
- * 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.
*
@@ -59,9 +59,9 @@ class PropertyQuota extends \Google\Protobuf\Internal\Message
*/
private $potentially_thresholded_requests_per_hour = null;
/**
- * 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.
@@ -77,12 +77,12 @@ class PropertyQuota extends \Google\Protobuf\Internal\Message
* Optional. Data for populating the Message object.
*
* @type \Google\Analytics\Data\V1beta\QuotaStatus $tokens_per_day
- * 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.
* @type \Google\Analytics\Data\V1beta\QuotaStatus $tokens_per_hour
- * 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.
* @type \Google\Analytics\Data\V1beta\QuotaStatus $concurrent_requests
@@ -98,9 +98,9 @@ class PropertyQuota extends \Google\Protobuf\Internal\Message
* is individually counted for this quota if the request contains potentially
* thresholded dimensions.
* @type \Google\Analytics\Data\V1beta\QuotaStatus $tokens_per_project_per_hour
- * 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.
@@ -112,8 +112,8 @@ public function __construct($data = NULL) {
}
/**
- * 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.
*
* Generated from protobuf field .google.analytics.data.v1beta.QuotaStatus tokens_per_day = 1;
@@ -135,8 +135,8 @@ public function clearTokensPerDay()
}
/**
- * 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.
*
* Generated from protobuf field .google.analytics.data.v1beta.QuotaStatus tokens_per_day = 1;
@@ -152,8 +152,8 @@ public function setTokensPerDay($var)
}
/**
- * 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.
*
@@ -176,8 +176,8 @@ public function clearTokensPerHour()
}
/**
- * 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.
*
@@ -314,9 +314,9 @@ public function setPotentiallyThresholdedRequestsPerHour($var)
}
/**
- * 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.
@@ -340,9 +340,9 @@ public function clearTokensPerProjectPerHour()
}
/**
- * 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.
diff --git a/AnalyticsData/src/V1beta/ResponseMetaData.php b/AnalyticsData/src/V1beta/ResponseMetaData.php
index 35443c89e08..d8250e3636f 100644
--- a/AnalyticsData/src/V1beta/ResponseMetaData.php
+++ b/AnalyticsData/src/V1beta/ResponseMetaData.php
@@ -18,6 +18,15 @@ class ResponseMetaData extends \Google\Protobuf\Internal\Message
/**
* 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).
*
* Generated from protobuf field bool data_loss_from_other_row = 3;
*/
@@ -82,6 +91,15 @@ class ResponseMetaData extends \Google\Protobuf\Internal\Message
* @type bool $data_loss_from_other_row
* 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).
* @type \Google\Analytics\Data\V1beta\ResponseMetaData\SchemaRestrictionResponse $schema_restriction_response
* Describes the schema restrictions actively enforced in creating this
* report. To learn more, see [Access and data-restriction
@@ -122,6 +140,15 @@ public function __construct($data = NULL) {
/**
* 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).
*
* Generated from protobuf field bool data_loss_from_other_row = 3;
* @return bool
@@ -134,6 +161,15 @@ public function getDataLossFromOtherRow()
/**
* 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).
*
* Generated from protobuf field bool data_loss_from_other_row = 3;
* @param bool $var
diff --git a/AnalyticsData/src/V1beta/RunPivotReportRequest.php b/AnalyticsData/src/V1beta/RunPivotReportRequest.php
index 3cd375deaa9..dd2aaba68b2 100644
--- a/AnalyticsData/src/V1beta/RunPivotReportRequest.php
+++ b/AnalyticsData/src/V1beta/RunPivotReportRequest.php
@@ -94,6 +94,11 @@ class RunPivotReportRequest extends \Google\Protobuf\Internal\Message
* If false or unspecified, each row with all metrics equal to 0 will not be
* returned. If true, these rows will be returned if they are not separately
* removed by a filter.
+ * Regardless of this `keep_empty_rows` setting, only data recorded by the
+ * Google Analytics (GA4) property can be displayed in a report.
+ * For example if a property never logs a `purchase` event, then a query for
+ * the `eventName` dimension and `eventCount` metric will not have a row
+ * eventName: "purchase" and eventCount: 0.
*
* Generated from protobuf field bool keep_empty_rows = 10;
*/
@@ -155,6 +160,11 @@ class RunPivotReportRequest extends \Google\Protobuf\Internal\Message
* If false or unspecified, each row with all metrics equal to 0 will not be
* returned. If true, these rows will be returned if they are not separately
* removed by a filter.
+ * Regardless of this `keep_empty_rows` setting, only data recorded by the
+ * Google Analytics (GA4) property can be displayed in a report.
+ * For example if a property never logs a `purchase` event, then a query for
+ * the `eventName` dimension and `eventCount` metric will not have a row
+ * eventName: "purchase" and eventCount: 0.
* @type bool $return_property_quota
* Toggles whether to return the current state of this Analytics Property's
* quota. Quota is returned in [PropertyQuota](#PropertyQuota).
@@ -475,6 +485,11 @@ public function setCohortSpec($var)
* If false or unspecified, each row with all metrics equal to 0 will not be
* returned. If true, these rows will be returned if they are not separately
* removed by a filter.
+ * Regardless of this `keep_empty_rows` setting, only data recorded by the
+ * Google Analytics (GA4) property can be displayed in a report.
+ * For example if a property never logs a `purchase` event, then a query for
+ * the `eventName` dimension and `eventCount` metric will not have a row
+ * eventName: "purchase" and eventCount: 0.
*
* Generated from protobuf field bool keep_empty_rows = 10;
* @return bool
@@ -488,6 +503,11 @@ public function getKeepEmptyRows()
* If false or unspecified, each row with all metrics equal to 0 will not be
* returned. If true, these rows will be returned if they are not separately
* removed by a filter.
+ * Regardless of this `keep_empty_rows` setting, only data recorded by the
+ * Google Analytics (GA4) property can be displayed in a report.
+ * For example if a property never logs a `purchase` event, then a query for
+ * the `eventName` dimension and `eventCount` metric will not have a row
+ * eventName: "purchase" and eventCount: 0.
*
* Generated from protobuf field bool keep_empty_rows = 10;
* @param bool $var
diff --git a/AnalyticsData/src/V1beta/RunRealtimeReportRequest.php b/AnalyticsData/src/V1beta/RunRealtimeReportRequest.php
index 9251e337271..f27ef71b329 100644
--- a/AnalyticsData/src/V1beta/RunRealtimeReportRequest.php
+++ b/AnalyticsData/src/V1beta/RunRealtimeReportRequest.php
@@ -52,7 +52,7 @@ class RunRealtimeReportRequest extends \Google\Protobuf\Internal\Message
private $metric_filter = null;
/**
* The number of rows to return. If unspecified, 10,000 rows are returned. The
- * API returns a maximum of 100,000 rows per request, no matter how many you
+ * API returns a maximum of 250,000 rows per request, no matter how many you
* ask for. `limit` must be positive.
* The API can also return fewer rows than the requested `limit`, if there
* aren't as many dimension values as the `limit`. For instance, there are
@@ -117,7 +117,7 @@ class RunRealtimeReportRequest extends \Google\Protobuf\Internal\Message
* SQL having-clause. Dimensions cannot be used in this filter.
* @type int|string $limit
* The number of rows to return. If unspecified, 10,000 rows are returned. The
- * API returns a maximum of 100,000 rows per request, no matter how many you
+ * API returns a maximum of 250,000 rows per request, no matter how many you
* ask for. `limit` must be positive.
* The API can also return fewer rows than the requested `limit`, if there
* aren't as many dimension values as the `limit`. For instance, there are
@@ -307,7 +307,7 @@ public function setMetricFilter($var)
/**
* The number of rows to return. If unspecified, 10,000 rows are returned. The
- * API returns a maximum of 100,000 rows per request, no matter how many you
+ * API returns a maximum of 250,000 rows per request, no matter how many you
* ask for. `limit` must be positive.
* The API can also return fewer rows than the requested `limit`, if there
* aren't as many dimension values as the `limit`. For instance, there are
@@ -325,7 +325,7 @@ public function getLimit()
/**
* The number of rows to return. If unspecified, 10,000 rows are returned. The
- * API returns a maximum of 100,000 rows per request, no matter how many you
+ * API returns a maximum of 250,000 rows per request, no matter how many you
* ask for. `limit` must be positive.
* The API can also return fewer rows than the requested `limit`, if there
* aren't as many dimension values as the `limit`. For instance, there are
diff --git a/AnalyticsData/src/V1beta/RunReportRequest.php b/AnalyticsData/src/V1beta/RunReportRequest.php
index 0d1027ef544..15d16203c72 100644
--- a/AnalyticsData/src/V1beta/RunReportRequest.php
+++ b/AnalyticsData/src/V1beta/RunReportRequest.php
@@ -50,7 +50,7 @@ class RunReportRequest extends \Google\Protobuf\Internal\Message
*/
private $date_ranges;
/**
- * Dimension filters allow you to ask for only specific dimension values in
+ * Dimension filters let you ask for only specific dimension values in
* the report. To learn more, see [Fundamentals of Dimension
* Filters](https://developers.google.com/analytics/devguides/reporting/data/v1/basics#dimension_filters)
* for examples. Metrics cannot be used in this filter.
@@ -79,7 +79,7 @@ class RunReportRequest extends \Google\Protobuf\Internal\Message
private $offset = 0;
/**
* The number of rows to return. If unspecified, 10,000 rows are returned. The
- * API returns a maximum of 100,000 rows per request, no matter how many you
+ * API returns a maximum of 250,000 rows per request, no matter how many you
* ask for. `limit` must be positive.
* The API can also return fewer rows than the requested `limit`, if there
* aren't as many dimension values as the `limit`. For instance, there are
@@ -123,6 +123,11 @@ class RunReportRequest extends \Google\Protobuf\Internal\Message
* If false or unspecified, each row with all metrics equal to 0 will not be
* returned. If true, these rows will be returned if they are not separately
* removed by a filter.
+ * Regardless of this `keep_empty_rows` setting, only data recorded by the
+ * Google Analytics (GA4) property can be displayed in a report.
+ * For example if a property never logs a `purchase` event, then a query for
+ * the `eventName` dimension and `eventCount` metric will not have a row
+ * eventName: "purchase" and eventCount: 0.
*
* Generated from protobuf field bool keep_empty_rows = 13;
*/
@@ -160,7 +165,7 @@ class RunReportRequest extends \Google\Protobuf\Internal\Message
* response rows for both date ranges. In a cohort request, this `dateRanges`
* must be unspecified.
* @type \Google\Analytics\Data\V1beta\FilterExpression $dimension_filter
- * Dimension filters allow you to ask for only specific dimension values in
+ * Dimension filters let you ask for only specific dimension values in
* the report. To learn more, see [Fundamentals of Dimension
* Filters](https://developers.google.com/analytics/devguides/reporting/data/v1/basics#dimension_filters)
* for examples. Metrics cannot be used in this filter.
@@ -177,7 +182,7 @@ class RunReportRequest extends \Google\Protobuf\Internal\Message
* [Pagination](https://developers.google.com/analytics/devguides/reporting/data/v1/basics#pagination).
* @type int|string $limit
* The number of rows to return. If unspecified, 10,000 rows are returned. The
- * API returns a maximum of 100,000 rows per request, no matter how many you
+ * API returns a maximum of 250,000 rows per request, no matter how many you
* ask for. `limit` must be positive.
* The API can also return fewer rows than the requested `limit`, if there
* aren't as many dimension values as the `limit`. For instance, there are
@@ -201,6 +206,11 @@ class RunReportRequest extends \Google\Protobuf\Internal\Message
* If false or unspecified, each row with all metrics equal to 0 will not be
* returned. If true, these rows will be returned if they are not separately
* removed by a filter.
+ * Regardless of this `keep_empty_rows` setting, only data recorded by the
+ * Google Analytics (GA4) property can be displayed in a report.
+ * For example if a property never logs a `purchase` event, then a query for
+ * the `eventName` dimension and `eventCount` metric will not have a row
+ * eventName: "purchase" and eventCount: 0.
* @type bool $return_property_quota
* Toggles whether to return the current state of this Analytics Property's
* quota. Quota is returned in [PropertyQuota](#PropertyQuota).
@@ -336,7 +346,7 @@ public function setDateRanges($var)
}
/**
- * Dimension filters allow you to ask for only specific dimension values in
+ * Dimension filters let you ask for only specific dimension values in
* the report. To learn more, see [Fundamentals of Dimension
* Filters](https://developers.google.com/analytics/devguides/reporting/data/v1/basics#dimension_filters)
* for examples. Metrics cannot be used in this filter.
@@ -360,7 +370,7 @@ public function clearDimensionFilter()
}
/**
- * Dimension filters allow you to ask for only specific dimension values in
+ * Dimension filters let you ask for only specific dimension values in
* the report. To learn more, see [Fundamentals of Dimension
* Filters](https://developers.google.com/analytics/devguides/reporting/data/v1/basics#dimension_filters)
* for examples. Metrics cannot be used in this filter.
@@ -455,7 +465,7 @@ public function setOffset($var)
/**
* The number of rows to return. If unspecified, 10,000 rows are returned. The
- * API returns a maximum of 100,000 rows per request, no matter how many you
+ * API returns a maximum of 250,000 rows per request, no matter how many you
* ask for. `limit` must be positive.
* The API can also return fewer rows than the requested `limit`, if there
* aren't as many dimension values as the `limit`. For instance, there are
@@ -475,7 +485,7 @@ public function getLimit()
/**
* The number of rows to return. If unspecified, 10,000 rows are returned. The
- * API returns a maximum of 100,000 rows per request, no matter how many you
+ * API returns a maximum of 250,000 rows per request, no matter how many you
* ask for. `limit` must be positive.
* The API can also return fewer rows than the requested `limit`, if there
* aren't as many dimension values as the `limit`. For instance, there are
@@ -621,6 +631,11 @@ public function setCohortSpec($var)
* If false or unspecified, each row with all metrics equal to 0 will not be
* returned. If true, these rows will be returned if they are not separately
* removed by a filter.
+ * Regardless of this `keep_empty_rows` setting, only data recorded by the
+ * Google Analytics (GA4) property can be displayed in a report.
+ * For example if a property never logs a `purchase` event, then a query for
+ * the `eventName` dimension and `eventCount` metric will not have a row
+ * eventName: "purchase" and eventCount: 0.
*
* Generated from protobuf field bool keep_empty_rows = 13;
* @return bool
@@ -634,6 +649,11 @@ public function getKeepEmptyRows()
* If false or unspecified, each row with all metrics equal to 0 will not be
* returned. If true, these rows will be returned if they are not separately
* removed by a filter.
+ * Regardless of this `keep_empty_rows` setting, only data recorded by the
+ * Google Analytics (GA4) property can be displayed in a report.
+ * For example if a property never logs a `purchase` event, then a query for
+ * the `eventName` dimension and `eventCount` metric will not have a row
+ * eventName: "purchase" and eventCount: 0.
*
* Generated from protobuf field bool keep_empty_rows = 13;
* @param bool $var