Blame - docs/dyn/analyticsdata_v1alpha.v1alpha.html - platform/external/python/google-api-python-client

2021-01-15 07:10:04 -0800

[diff] [blame]

102

"entity": { # The unique identifier of the property whose events are tracked. # A property whose events are tracked. This entity must be specified for the batch. The entity within RunPivotReportRequest may either be unspecified or consistent with this entity.

103

"propertyId": "A String", # A Google Analytics GA4 property id. To learn more, see [where to find your Property ID](https://developers.google.com/analytics/devguides/reporting/data/v1/property-id).

104

},

105

"requests": [ # Individual requests. Each request has a separate pivot report response. Each batch request is allowed up to 5 requests.

106

{ # The request to generate a pivot report.

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

107

"cohortSpec": { # The specification of cohorts for a cohort report. Cohort reports create a time series of user retention for the cohort. For example, you could select the cohort of users that were acquired in the first week of September and follow that cohort for the next six weeks. Selecting the users acquired in the first week of September cohort is specified in the `cohort` object. Following that cohort for the next six weeks is specified in the `cohortsRange` object. For examples, see [Cohort Report Examples](https://developers.google.com/analytics/devguides/reporting/data/v1/advanced#cohort_report_examples). The report response could show a weekly time series where say your app has retained 60% of this cohort after three weeks and 25% of this cohort after six weeks. These two percentages can be calculated by the metric `cohortActiveUsers/cohortTotalUsers` and will be separate rows in the report. # Cohort group associated with this request. If there is a cohort group in the request the 'cohort' dimension must be present.

108

"cohortReportSettings": { # Optional settings of a cohort report. # Optional settings for a cohort report.

109

"accumulate": True or False, # If true, accumulates the result from first touch day to the end day. Not supported in `RunReportRequest`.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

110

},

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

111

"cohorts": [ # Defines the selection criteria to group users into cohorts. Most cohort reports define only a single cohort. If multiple cohorts are specified, each cohort can be recognized in the report by their name.

112

{ # Defines a cohort selection criteria. A cohort is a group of users who share a common characteristic. For example, users with the same `firstSessionDate` belong to the same cohort.

113

"dateRange": { # A contiguous set of days: startDate, startDate + 1, ..., endDate. Requests are allowed up to 4 date ranges. # The cohort selects users whose first touch date is between start date and end date defined in the `dateRange`. This `dateRange` does not specify the full date range of event data that is present in a cohort report. In a cohort report, this `dateRange` is extended by the granularity and offset present in the `cohortsRange`; event data for the extended reporting date range is present in a cohort report. In a cohort request, this `dateRange` is required and the `dateRanges` in the `RunReportRequest` or `RunPivotReportRequest` must be unspecified. This `dateRange` should generally be aligned with the cohort's granularity. If `CohortsRange` uses daily granularity, this `dateRange` can be a single day. If `CohortsRange` uses weekly granularity, this `dateRange` can be aligned to a week boundary, starting at Sunday and ending Saturday. If `CohortsRange` uses monthly granularity, this `dateRange` can be aligned to a month, starting at the first and ending on the last day of the month.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

114

"endDate": "A String", # The inclusive end date for the query in the format `YYYY-MM-DD`. Cannot be before `start_date`. The format `NdaysAgo`, `yesterday`, or `today` is also accepted, and in that case, the date is inferred based on the property's reporting time zone.

115

"name": "A String", # Assigns a name to this date range. The dimension `dateRange` is valued to this name in a report response. If set, cannot begin with `date_range_` or `RESERVED_`. If not set, date ranges are named by their zero based index in the request: `date_range_0`, `date_range_1`, etc.

116

"startDate": "A String", # 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 accepted, and in that case, the date is inferred based on the property's reporting time zone.

117

},

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

118

"dimension": "A String", # Dimension used by the cohort. Required and only supports `firstSessionDate`.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

119

"name": "A String", # Assigns a name to this cohort. The dimension `cohort` is valued to this name in a report response. If set, cannot begin with `cohort_` or `RESERVED_`. If not set, cohorts are named by their zero based index `cohort_0`, `cohort_1`, etc.

Yoshi Automation Bot

2020-11-26 17:16:03 -0800

[diff] [blame]

120

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

121

],

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

122

"cohortsRange": { # Configures the extended reporting date range for a cohort report. Specifies an offset duration to follow the cohorts over. # Cohort reports follow cohorts over an extended reporting date range. This range specifies an offset duration to follow the cohorts over.

123

"endOffset": 42, # Required. `endOffset` specifies the end date of the extended reporting date range for a cohort report. `endOffset` can be any positive integer but is commonly set to 5 to 10 so that reports contain data on the cohort for the next several granularity time periods. If `granularity` is `DAILY`, the `endDate` of the extended reporting date range is `endDate` of the cohort plus `endOffset` days. If `granularity` is `WEEKLY`, the `endDate` of the extended reporting date range is `endDate` of the cohort plus `endOffset * 7` days. If `granularity` is `MONTHLY`, the `endDate` of the extended reporting date range is `endDate` of the cohort plus `endOffset * 30` days.

124

"granularity": "A String", # Required. The granularity used to interpret the `startOffset` and `endOffset` for the extended reporting date range for a cohort report.

125

"startOffset": 42, # `startOffset` specifies the start date of the extended reporting date range for a cohort report. `startOffset` is commonly set to 0 so that reports contain data from the acquisition of the cohort forward. If `granularity` is `DAILY`, the `startDate` of the extended reporting date range is `startDate` of the cohort plus `startOffset` days. If `granularity` is `WEEKLY`, the `startDate` of the extended reporting date range is `startDate` of the cohort plus `startOffset * 7` days. If `granularity` is `MONTHLY`, the `startDate` of the extended reporting date range is `startDate` of the cohort plus `startOffset * 30` days.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

126

},

127

},

128

"currencyCode": "A String", # A currency code in ISO4217 format, such as "AED", "USD", "JPY". If the field is empty, the report uses the entity's default currency.

129

"dateRanges": [ # The date range to retrieve event data for the report. If multiple date ranges are specified, event data from each date range is used in the report. A special dimension with field name "dateRange" can be included in a Pivot's field names; if included, the report compares between date ranges. In a cohort request, this `dateRanges` must be unspecified.

130

{ # A contiguous set of days: startDate, startDate + 1, ..., endDate. Requests are allowed up to 4 date ranges.

131

"endDate": "A String", # The inclusive end date for the query in the format `YYYY-MM-DD`. Cannot be before `start_date`. The format `NdaysAgo`, `yesterday`, or `today` is also accepted, and in that case, the date is inferred based on the property's reporting time zone.

132

"name": "A String", # Assigns a name to this date range. The dimension `dateRange` is valued to this name in a report response. If set, cannot begin with `date_range_` or `RESERVED_`. If not set, date ranges are named by their zero based index in the request: `date_range_0`, `date_range_1`, etc.

133

"startDate": "A String", # 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 accepted, and in that case, the date is inferred based on the property's reporting time zone.

134

},

135

],

136

"dimensionFilter": { # To express dimension or metric filters. The fields in the same FilterExpression need to be either all dimensions or all metrics. # The filter clause of dimensions. Dimensions must be requested to be used in this filter. Metrics cannot be used in this filter.

137

"andGroup": { # A list of filter expressions. # The FilterExpressions in and_group have an AND relationship.

138

"expressions": [ # A list of filter expressions.

139

# Object with schema name: FilterExpression

140

],

141

},

142

"filter": { # An expression to filter dimension or metric values. # A primitive filter. All fields in filter in same FilterExpression needs to be either all dimensions or metrics.

143

"betweenFilter": { # To express that the result needs to be between two numbers (inclusive). # A filter for two values.

144

"fromValue": { # To represent a number. # Begins with this number.

145

"doubleValue": 3.14, # Double value

146

"int64Value": "A String", # Integer value

147

},

148

"toValue": { # To represent a number. # Ends with this number.

149

"doubleValue": 3.14, # Double value

150

"int64Value": "A String", # Integer value

151

},

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

152

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

153

"fieldName": "A String", # The dimension name or metric name. Must be a name defined in dimensions or metrics.

154

"inListFilter": { # The result needs to be in a list of string values. # A filter for in list values.

155

"caseSensitive": True or False, # If true, the string value is case sensitive.

156

"values": [ # The list of string values. Must be non-empty.

157

"A String",

158

],

159

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

160

"numericFilter": { # Filters for numeric or date values. # A filter for numeric or date values.

161

"operation": "A String", # The operation type for this filter.

162

"value": { # To represent a number. # A numeric value or a date value.

163

"doubleValue": 3.14, # Double value

164

"int64Value": "A String", # Integer value

165

},

166

},

167

"stringFilter": { # The filter for string # Strings related filter.

168

"caseSensitive": True or False, # If true, the string value is case sensitive.

169

"matchType": "A String", # The match type for this filter.

170

"value": "A String", # The string value used for the matching.

171

},

172

},

173

"notExpression": # Object with schema name: FilterExpression # The FilterExpression is NOT of not_expression.

174

"orGroup": { # A list of filter expressions. # The FilterExpressions in or_group have an OR relationship.

175

"expressions": [ # A list of filter expressions.

176

# Object with schema name: FilterExpression

],

},

},

"dimensions": [ # The dimensions requested. All defined dimensions must be used by one of the following: dimension_expression, dimension_filter, pivots, order_bys.

181

{ # Dimensions are attributes of your data. For example, the dimension city indicates the city from which an event originates. Dimension values in report responses are strings; for example, city could be "Paris" or "New York". Requests are allowed up to 8 dimensions.

182

"dimensionExpression": { # Used to express a dimension which is the result of a formula of multiple dimensions. Example usages: 1) lower_case(dimension) 2) concatenate(dimension1, symbol, dimension2). # One dimension can be the result of an expression of multiple dimensions. For example, dimension "country, city": concatenate(country, ", ", city).

183

"concatenate": { # Used to combine dimension values to a single dimension. # Used to combine dimension values to a single dimension. For example, dimension "country, city": concatenate(country, ", ", city).

184

"delimiter": "A String", # The delimiter placed between dimension names. Delimiters are often single characters such as "|" or "," but can be longer strings. If a dimension value contains the delimiter, both will be present in response with no distinction. For example if dimension 1 value = "US,FR", dimension 2 value = "JP", and delimiter = ",", then the response will contain "US,FR,JP".

185

"dimensionNames": [ # Names of dimensions. The names must refer back to names in the dimensions field of the request.

"A String",

],

},

"lowerCase": { # Used to convert a dimension value to a single case. # Used to convert a dimension value to lower case.

190

"dimensionName": "A String", # Name of a dimension. The name must refer back to a name in dimensions field of the request.

191

},

192

"upperCase": { # Used to convert a dimension value to a single case. # Used to convert a dimension value to upper case.

193

"dimensionName": "A String", # Name of a dimension. The name must refer back to a name in dimensions field of the request.

194

},

195

},

196

"name": "A String", # The name of the dimension. See the [API Dimensions](https://developers.google.com/analytics/devguides/reporting/data/v1/api-schema#dimensions) for the list of dimension names. If `dimensionExpression` is specified, `name` can be any string that you would like. For example if a `dimensionExpression` concatenates `country` and `city`, you could call that dimension `countryAndCity`. Dimensions are referenced by `name` in `dimensionFilter`, `orderBys`, `dimensionExpression`, and `pivots`.

197

},

198

],

199

"entity": { # The unique identifier of the property whose events are tracked. # A property whose events are tracked. Within a batch request, this entity should either be unspecified or consistent with the batch-level entity.

200

"propertyId": "A String", # A Google Analytics GA4 property id. To learn more, see [where to find your Property ID](https://developers.google.com/analytics/devguides/reporting/data/v1/property-id).

201

},

202

"keepEmptyRows": True or False, # 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.

203

"metricFilter": { # To express dimension or metric filters. The fields in the same FilterExpression need to be either all dimensions or all metrics. # The filter clause of metrics. Applied at post aggregation phase, similar to SQL having-clause. Metrics must be requested to be used in this filter. Dimensions cannot be used in this filter.

204

"andGroup": { # A list of filter expressions. # The FilterExpressions in and_group have an AND relationship.

205

"expressions": [ # A list of filter expressions.

206

# Object with schema name: FilterExpression

207

],

208

},

209

"filter": { # An expression to filter dimension or metric values. # A primitive filter. All fields in filter in same FilterExpression needs to be either all dimensions or metrics.

210

"betweenFilter": { # To express that the result needs to be between two numbers (inclusive). # A filter for two values.

211

"fromValue": { # To represent a number. # Begins with this number.

212

"doubleValue": 3.14, # Double value

213

"int64Value": "A String", # Integer value

214

},

215

"toValue": { # To represent a number. # Ends with this number.

216

"doubleValue": 3.14, # Double value

217

"int64Value": "A String", # Integer value

218

},

219

},

220

"fieldName": "A String", # The dimension name or metric name. Must be a name defined in dimensions or metrics.

221

"inListFilter": { # The result needs to be in a list of string values. # A filter for in list values.

222

"caseSensitive": True or False, # If true, the string value is case sensitive.

223

"values": [ # The list of string values. Must be non-empty.

224

"A String",

225

],

226

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

227

"numericFilter": { # Filters for numeric or date values. # A filter for numeric or date values.

228

"operation": "A String", # The operation type for this filter.

229

"value": { # To represent a number. # A numeric value or a date value.

230

"doubleValue": 3.14, # Double value

231

"int64Value": "A String", # Integer value

232

},

233

},

234

"stringFilter": { # The filter for string # Strings related filter.

235

"caseSensitive": True or False, # If true, the string value is case sensitive.

236

"matchType": "A String", # The match type for this filter.

237

"value": "A String", # The string value used for the matching.

238

},

239

},

240

"notExpression": # Object with schema name: FilterExpression # The FilterExpression is NOT of not_expression.

241

"orGroup": { # A list of filter expressions. # The FilterExpressions in or_group have an OR relationship.

242

"expressions": [ # A list of filter expressions.

243

# Object with schema name: FilterExpression

],

},

},

"metrics": [ # The metrics requested, at least one metric needs to be specified. All defined metrics must be used by one of the following: metric_expression, metric_filter, order_bys.

248

{ # The quantitative measurements of a report. For example, the metric `eventCount` is the total number of events. Requests are allowed up to 10 metrics.

249

"expression": "A String", # A mathematical expression for derived metrics. For example, the metric Event count per user is `eventCount/totalUsers`.

250

"invisible": True or False, # Indicates if a metric is invisible in the report response. If a metric is invisible, the metric will not produce a column in the response, but can be used in `metricFilter`, `orderBys`, or a metric `expression`.

251

"name": "A String", # The name of the metric. See the [API Metrics](https://developers.google.com/analytics/devguides/reporting/data/v1/api-schema#metrics) for the list of metric names. If `expression` is specified, `name` can be any string that you would like. For example if `expression` is `screenPageViews/sessions`, you could call that metric's name = `viewsPerSession`. Metrics are referenced by `name` in `metricFilter`, `orderBys`, and metric `expression`.

252

},

253

],

254

"pivots": [ # Describes the visual format of the report's dimensions in columns or rows. The union of the fieldNames (dimension names) in all pivots must be a subset of dimension names defined in Dimensions. No two pivots can share a dimension. A dimension is only visible if it appears in a pivot.

255

{ # Describes the visible dimension columns and rows in the report response.

256

"fieldNames": [ # Dimension names for visible columns in the report response. Including "dateRange" produces a date range column; for each row in the response, dimension values in the date range column will indicate the corresponding date range from the request.

257

"A String",

258

],

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

259

"limit": "A String", # The number of rows to return in this pivot. If the `limit` parameter is unspecified, up to 10,000 rows are returned. The product of the `limit` for each `pivot` in a `RunPivotReportRequest` must not exceed 100,000. For example, a two pivot request with `limit: 1000` in each pivot will fail because the product is `1,000,000`.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

260

"metricAggregations": [ # Aggregate the metrics by dimensions in this pivot using the specified metric_aggregations.

261

"A String",

262

],

263

"offset": "A String", # The row count of the start row. The first row is counted as row 0.

264

"orderBys": [ # Specifies how dimensions are ordered in the pivot. In the first Pivot, the OrderBys determine Row and PivotDimensionHeader ordering; in subsequent Pivots, the OrderBys determine only PivotDimensionHeader ordering. Dimensions specified in these OrderBys must be a subset of Pivot.field_names.

265

{ # The sort options.

266

"desc": True or False, # If true, sorts by descending order.

267

"dimension": { # Sorts by dimension values. # Sorts results by a dimension's values.

268

"dimensionName": "A String", # A dimension name in the request to order by.

269

"orderType": "A String", # Controls the rule for dimension value ordering.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

270

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

271

"metric": { # Sorts by metric values. # Sorts results by a metric's values.

272

"metricName": "A String", # A metric name in the request to order by.

273

},

274

"pivot": { # Sorts by a pivot column group. # Sorts results by a metric's values within a pivot column group.

275

"metricName": "A String", # In the response to order by, order rows by this column. Must be a metric name from the request.

276

"pivotSelections": [ # Used to select a dimension name and value pivot. If multiple pivot selections are given, the sort occurs on rows where all pivot selection dimension name and value pairs match the row's dimension name and value pair.

277

{ # A pair of dimension names and values. Rows with this dimension pivot pair are ordered by the metric's value. For example if pivots = {{"browser", "Chrome"}} and metric_name = "Sessions", then the rows will be sorted based on Sessions in Chrome. ---------|----------|----------------|----------|---------------- | Chrome | Chrome | Safari | Safari ---------|----------|----------------|----------|---------------- Country | Sessions | Pages/Sessions | Sessions | Pages/Sessions ---------|----------|----------------|----------|---------------- US | 2 | 2 | 3 | 1 ---------|----------|----------------|----------|---------------- Canada | 3 | 1 | 4 | 1 ---------|----------|----------------|----------|----------------

278

"dimensionName": "A String", # Must be a dimension name from the request.

279

"dimensionValue": "A String", # Order by only when the named dimension is this value.

280

},

281

],

282

},

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

283

},

284

],

285

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

286

],

287

"returnPropertyQuota": True or False, # Toggles whether to return the current state of this Analytics Property's quota. Quota is returned in [PropertyQuota](#PropertyQuota).

Yoshi Automation Bot

2020-11-26 17:16:03 -0800

[diff] [blame]

288

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

289

],

290

}

Dmitry Frenkel

2020-10-06 16:46:05 -0700

[diff] [blame]

291

292

x__xgafv: string, V1 error format.

Allowed values

1 - v1 error format

2 - v2 error format

Returns:

An object of the form:

299

300

{ # The batch response containing multiple pivot reports.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

301

"pivotReports": [ # Individual responses. Each response has a separate pivot report request.

302

{ # The response pivot report table corresponding to a pivot request.

303

"aggregates": [ # Aggregation of metric values. Can be totals, minimums, or maximums. The returned aggregations are controlled by the metric_aggregations in the pivot. The type of aggregation returned in each row is shown by the dimension_values which are set to "RESERVED_".

304

{ # Report data for each row. For example if RunReportRequest contains: ```none "dimensions": [ { "name": "eventName" }, { "name": "countryId" } ], "metrics": [ { "name": "eventCount" } ] ``` One row with 'in_app_purchase' as the eventName, 'JP' as the countryId, and 15 as the eventCount, would be: ```none "dimensionValues": [ { "value": "in_app_purchase" }, { "value": "JP" } ], "metricValues": [ { "value": "15" } ] ```

305

"dimensionValues": [ # List of requested dimension values. In a PivotReport, dimension_values are only listed for dimensions included in a pivot.

306

{ # The value of a dimension.

307

"value": "A String", # Value as a string if the dimension type is a string.

308

},

309

],

310

"metricValues": [ # List of requested visible metric values.

311

{ # The value of a metric.

312

"value": "A String", # Measurement value. See MetricHeader for type.

313

},

314

],

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

315

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

316

],

317

"dimensionHeaders": [ # Describes dimension columns. The number of DimensionHeaders and ordering of DimensionHeaders matches the dimensions present in rows.

318

{ # Describes a dimension column in the report. Dimensions requested in a report produce column entries within rows and DimensionHeaders. However, dimensions used exclusively within filters or expressions do not produce columns in a report; correspondingly, those dimensions do not produce headers.

319

"name": "A String", # The dimension's name.

320

},

321

],

322

"metadata": { # Response's metadata carrying additional information about the report content. # Metadata for the report.

323

"dataLossFromOtherRow": True or False, # If true, indicates some buckets of dimension combinations are rolled into "(other)" row. This can happen for high cardinality reports.

324

},

325

"metricHeaders": [ # Describes metric columns. The number of MetricHeaders and ordering of MetricHeaders matches the metrics present in rows.

326

{ # Describes a metric column in the report. Visible metrics requested in a report produce column entries within rows and MetricHeaders. However, metrics used exclusively within filters or expressions do not produce columns in a report; correspondingly, those metrics do not produce headers.

327

"name": "A String", # The metric's name.

328

"type": "A String", # The metric's data type.

329

},

330

],

331

"pivotHeaders": [ # Summarizes the columns and rows created by a pivot. Each pivot in the request produces one header in the response. If we have a request like this: "pivots": [{ "fieldNames": ["country", "city"] }, { "fieldNames": "eventName" }] We will have the following `pivotHeaders` in the response: "pivotHeaders" : [{ "dimensionHeaders": [{ "dimensionValues": [ { "value": "United Kingdom" }, { "value": "London" } ] }, { "dimensionValues": [ { "value": "Japan" }, { "value": "Osaka" } ] }] }, { "dimensionHeaders": [{ "dimensionValues": [{ "value": "session_start" }] }, { "dimensionValues": [{ "value": "scroll" }] }] }]

332

{ # Dimensions' values in a single pivot.

333

"pivotDimensionHeaders": [ # The size is the same as the cardinality of the corresponding dimension combinations.

334

{ # Summarizes dimension values from a row for this pivot.

335

"dimensionValues": [ # Values of multiple dimensions in a pivot.

336

{ # The value of a dimension.

337

"value": "A String", # Value as a string if the dimension type is a string.

},

],

},

],

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

342

"rowCount": 42, # The cardinality of the pivot. The total number of rows for this pivot's fields regardless of how the parameters `offset` and `limit` are specified in the request.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

343

},

344

],

345

"propertyQuota": { # Current state of all quotas for this Analytics Property. If any quota for a property is exhausted, all requests to that property will return Resource Exhausted errors. # This Analytics Property's quota state including this request.

346

"concurrentRequests": { # Current state for a particular quota group. # Standard Analytics Properties can send up to 10 concurrent requests; Analytics 360 Properties can use up to 50 concurrent requests.

347

"consumed": 42, # Quota consumed by this request.

348

"remaining": 42, # Quota remaining after this request.

349

},

350

"serverErrorsPerProjectPerHour": { # Current state for a particular quota group. # Standard Analytics Properties and cloud project pairs can have up to 10 server errors per hour; Analytics 360 Properties and cloud project pairs can have up to 50 server errors per hour.

351

"consumed": 42, # Quota consumed by this request.

352

"remaining": 42, # Quota remaining after this request.

353

},

354

"tokensPerDay": { # Current state for a particular quota group. # Standard Analytics Properties can use up to 25,000 tokens per day; Analytics 360 Properties can use 250,000 tokens per day. Most requests consume fewer than 10 tokens.

355

"consumed": 42, # Quota consumed by this request.

356

"remaining": 42, # Quota remaining after this request.

357

},

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

358

"tokensPerHour": { # Current state for a particular quota group. # 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 consumes a single number of tokens, and that number is deducted from both the hourly and daily quotas.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

359

"consumed": 42, # Quota consumed by this request.

360

"remaining": 42, # Quota remaining after this request.

Yoshi Automation Bot

2020-11-26 17:16:03 -0800

[diff] [blame]

361

},

Dmitry Frenkel

2020-10-06 16:46:05 -0700

[diff] [blame]

362

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

363

"rows": [ # Rows of dimension value combinations and metric values in the report.

364

{ # Report data for each row. For example if RunReportRequest contains: ```none "dimensions": [ { "name": "eventName" }, { "name": "countryId" } ], "metrics": [ { "name": "eventCount" } ] ``` One row with 'in_app_purchase' as the eventName, 'JP' as the countryId, and 15 as the eventCount, would be: ```none "dimensionValues": [ { "value": "in_app_purchase" }, { "value": "JP" } ], "metricValues": [ { "value": "15" } ] ```

365

"dimensionValues": [ # List of requested dimension values. In a PivotReport, dimension_values are only listed for dimensions included in a pivot.

366

{ # The value of a dimension.

367

"value": "A String", # Value as a string if the dimension type is a string.

368

},

369

],

370

"metricValues": [ # List of requested visible metric values.

371

{ # The value of a metric.

372

"value": "A String", # Measurement value. See MetricHeader for type.

},

],

},

],

},

],

}</pre>

Dmitry Frenkel

2020-10-06 16:46:05 -0700

[diff] [blame]

</div>

<code class="details" id="batchRunReports">batchRunReports(body=None, x__xgafv=None)</code>

384

<pre>Returns multiple reports in a batch. All reports must be for the same Entity.

385

386

Args:

387

body: object, The request body.

388

The object takes the form of:

389

390

{ # The batch request containing multiple report requests.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

391

"entity": { # The unique identifier of the property whose events are tracked. # A property whose events are tracked. This entity must be specified for the batch. The entity within RunReportRequest may either be unspecified or consistent with this entity.

392

"propertyId": "A String", # A Google Analytics GA4 property id. To learn more, see [where to find your Property ID](https://developers.google.com/analytics/devguides/reporting/data/v1/property-id).

393

},

394

"requests": [ # Individual requests. Each request has a separate report response. Each batch request is allowed up to 5 requests.

395

{ # The request to generate a report.

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

396

"cohortSpec": { # The specification of cohorts for a cohort report. Cohort reports create a time series of user retention for the cohort. For example, you could select the cohort of users that were acquired in the first week of September and follow that cohort for the next six weeks. Selecting the users acquired in the first week of September cohort is specified in the `cohort` object. Following that cohort for the next six weeks is specified in the `cohortsRange` object. For examples, see [Cohort Report Examples](https://developers.google.com/analytics/devguides/reporting/data/v1/advanced#cohort_report_examples). The report response could show a weekly time series where say your app has retained 60% of this cohort after three weeks and 25% of this cohort after six weeks. These two percentages can be calculated by the metric `cohortActiveUsers/cohortTotalUsers` and will be separate rows in the report. # Cohort group associated with this request. If there is a cohort group in the request the 'cohort' dimension must be present.

397

"cohortReportSettings": { # Optional settings of a cohort report. # Optional settings for a cohort report.

398

"accumulate": True or False, # If true, accumulates the result from first touch day to the end day. Not supported in `RunReportRequest`.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

399

},

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

400

"cohorts": [ # Defines the selection criteria to group users into cohorts. Most cohort reports define only a single cohort. If multiple cohorts are specified, each cohort can be recognized in the report by their name.

401

{ # Defines a cohort selection criteria. A cohort is a group of users who share a common characteristic. For example, users with the same `firstSessionDate` belong to the same cohort.

402

"dateRange": { # A contiguous set of days: startDate, startDate + 1, ..., endDate. Requests are allowed up to 4 date ranges. # The cohort selects users whose first touch date is between start date and end date defined in the `dateRange`. This `dateRange` does not specify the full date range of event data that is present in a cohort report. In a cohort report, this `dateRange` is extended by the granularity and offset present in the `cohortsRange`; event data for the extended reporting date range is present in a cohort report. In a cohort request, this `dateRange` is required and the `dateRanges` in the `RunReportRequest` or `RunPivotReportRequest` must be unspecified. This `dateRange` should generally be aligned with the cohort's granularity. If `CohortsRange` uses daily granularity, this `dateRange` can be a single day. If `CohortsRange` uses weekly granularity, this `dateRange` can be aligned to a week boundary, starting at Sunday and ending Saturday. If `CohortsRange` uses monthly granularity, this `dateRange` can be aligned to a month, starting at the first and ending on the last day of the month.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

403

"endDate": "A String", # The inclusive end date for the query in the format `YYYY-MM-DD`. Cannot be before `start_date`. The format `NdaysAgo`, `yesterday`, or `today` is also accepted, and in that case, the date is inferred based on the property's reporting time zone.

404

"name": "A String", # Assigns a name to this date range. The dimension `dateRange` is valued to this name in a report response. If set, cannot begin with `date_range_` or `RESERVED_`. If not set, date ranges are named by their zero based index in the request: `date_range_0`, `date_range_1`, etc.

405

"startDate": "A String", # 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 accepted, and in that case, the date is inferred based on the property's reporting time zone.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

406

},

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

407

"dimension": "A String", # Dimension used by the cohort. Required and only supports `firstSessionDate`.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

408

"name": "A String", # Assigns a name to this cohort. The dimension `cohort` is valued to this name in a report response. If set, cannot begin with `cohort_` or `RESERVED_`. If not set, cohorts are named by their zero based index `cohort_0`, `cohort_1`, etc.

409

},

410

],

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

411

"cohortsRange": { # Configures the extended reporting date range for a cohort report. Specifies an offset duration to follow the cohorts over. # Cohort reports follow cohorts over an extended reporting date range. This range specifies an offset duration to follow the cohorts over.

412

"endOffset": 42, # Required. `endOffset` specifies the end date of the extended reporting date range for a cohort report. `endOffset` can be any positive integer but is commonly set to 5 to 10 so that reports contain data on the cohort for the next several granularity time periods. If `granularity` is `DAILY`, the `endDate` of the extended reporting date range is `endDate` of the cohort plus `endOffset` days. If `granularity` is `WEEKLY`, the `endDate` of the extended reporting date range is `endDate` of the cohort plus `endOffset * 7` days. If `granularity` is `MONTHLY`, the `endDate` of the extended reporting date range is `endDate` of the cohort plus `endOffset * 30` days.

413

"granularity": "A String", # Required. The granularity used to interpret the `startOffset` and `endOffset` for the extended reporting date range for a cohort report.

414

"startOffset": 42, # `startOffset` specifies the start date of the extended reporting date range for a cohort report. `startOffset` is commonly set to 0 so that reports contain data from the acquisition of the cohort forward. If `granularity` is `DAILY`, the `startDate` of the extended reporting date range is `startDate` of the cohort plus `startOffset` days. If `granularity` is `WEEKLY`, the `startDate` of the extended reporting date range is `startDate` of the cohort plus `startOffset * 7` days. If `granularity` is `MONTHLY`, the `startDate` of the extended reporting date range is `startDate` of the cohort plus `startOffset * 30` days.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

415

},

416

},

417

"currencyCode": "A String", # A currency code in ISO4217 format, such as "AED", "USD", "JPY". If the field is empty, the report uses the entity's default currency.

418

"dateRanges": [ # Date ranges of data to read. If multiple date ranges are requested, each response row will contain a zero based date range index. If two date ranges overlap, the event data for the overlapping days is included in the response rows for both date ranges. In a cohort request, this `dateRanges` must be unspecified.

419

{ # A contiguous set of days: startDate, startDate + 1, ..., endDate. Requests are allowed up to 4 date ranges.

420

"endDate": "A String", # The inclusive end date for the query in the format `YYYY-MM-DD`. Cannot be before `start_date`. The format `NdaysAgo`, `yesterday`, or `today` is also accepted, and in that case, the date is inferred based on the property's reporting time zone.

421

"name": "A String", # Assigns a name to this date range. The dimension `dateRange` is valued to this name in a report response. If set, cannot begin with `date_range_` or `RESERVED_`. If not set, date ranges are named by their zero based index in the request: `date_range_0`, `date_range_1`, etc.

422

"startDate": "A String", # 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 accepted, and in that case, the date is inferred based on the property's reporting time zone.

423

},

424

],

425

"dimensionFilter": { # To express dimension or metric filters. The fields in the same FilterExpression need to be either all dimensions or all metrics. # The filter clause of dimensions. Dimensions must be requested to be used in this filter. Metrics cannot be used in this filter.

426

"andGroup": { # A list of filter expressions. # The FilterExpressions in and_group have an AND relationship.

427

"expressions": [ # A list of filter expressions.

428

# Object with schema name: FilterExpression

429

],

430

},

431

"filter": { # An expression to filter dimension or metric values. # A primitive filter. All fields in filter in same FilterExpression needs to be either all dimensions or metrics.

432

"betweenFilter": { # To express that the result needs to be between two numbers (inclusive). # A filter for two values.

433

"fromValue": { # To represent a number. # Begins with this number.

434

"doubleValue": 3.14, # Double value

435

"int64Value": "A String", # Integer value

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

436

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

437

"toValue": { # To represent a number. # Ends with this number.

438

"doubleValue": 3.14, # Double value

439

"int64Value": "A String", # Integer value

440

},

441

},

442

"fieldName": "A String", # The dimension name or metric name. Must be a name defined in dimensions or metrics.

443

"inListFilter": { # The result needs to be in a list of string values. # A filter for in list values.

444

"caseSensitive": True or False, # If true, the string value is case sensitive.

445

"values": [ # The list of string values. Must be non-empty.

446

"A String",

447

],

448

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

449

"numericFilter": { # Filters for numeric or date values. # A filter for numeric or date values.

450

"operation": "A String", # The operation type for this filter.

451

"value": { # To represent a number. # A numeric value or a date value.

452

"doubleValue": 3.14, # Double value

453

"int64Value": "A String", # Integer value

454

},

455

},

456

"stringFilter": { # The filter for string # Strings related filter.

457

"caseSensitive": True or False, # If true, the string value is case sensitive.

458

"matchType": "A String", # The match type for this filter.

459

"value": "A String", # The string value used for the matching.

460

},

461

},

462

"notExpression": # Object with schema name: FilterExpression # The FilterExpression is NOT of not_expression.

463

"orGroup": { # A list of filter expressions. # The FilterExpressions in or_group have an OR relationship.

464

"expressions": [ # A list of filter expressions.

465

# Object with schema name: FilterExpression

],

},

},

"dimensions": [ # The dimensions requested and displayed.

470

{ # Dimensions are attributes of your data. For example, the dimension city indicates the city from which an event originates. Dimension values in report responses are strings; for example, city could be "Paris" or "New York". Requests are allowed up to 8 dimensions.

471

"dimensionExpression": { # Used to express a dimension which is the result of a formula of multiple dimensions. Example usages: 1) lower_case(dimension) 2) concatenate(dimension1, symbol, dimension2). # One dimension can be the result of an expression of multiple dimensions. For example, dimension "country, city": concatenate(country, ", ", city).

472

"concatenate": { # Used to combine dimension values to a single dimension. # Used to combine dimension values to a single dimension. For example, dimension "country, city": concatenate(country, ", ", city).

473

"delimiter": "A String", # The delimiter placed between dimension names. Delimiters are often single characters such as "|" or "," but can be longer strings. If a dimension value contains the delimiter, both will be present in response with no distinction. For example if dimension 1 value = "US,FR", dimension 2 value = "JP", and delimiter = ",", then the response will contain "US,FR,JP".

474

"dimensionNames": [ # Names of dimensions. The names must refer back to names in the dimensions field of the request.

"A String",

],

},

"lowerCase": { # Used to convert a dimension value to a single case. # Used to convert a dimension value to lower case.

479

"dimensionName": "A String", # Name of a dimension. The name must refer back to a name in dimensions field of the request.

480

},

481

"upperCase": { # Used to convert a dimension value to a single case. # Used to convert a dimension value to upper case.

482

"dimensionName": "A String", # Name of a dimension. The name must refer back to a name in dimensions field of the request.

483

},

484

},

485

"name": "A String", # The name of the dimension. See the [API Dimensions](https://developers.google.com/analytics/devguides/reporting/data/v1/api-schema#dimensions) for the list of dimension names. If `dimensionExpression` is specified, `name` can be any string that you would like. For example if a `dimensionExpression` concatenates `country` and `city`, you could call that dimension `countryAndCity`. Dimensions are referenced by `name` in `dimensionFilter`, `orderBys`, `dimensionExpression`, and `pivots`.

486

},

487

],

488

"entity": { # The unique identifier of the property whose events are tracked. # A property whose events are tracked. Within a batch request, this entity should either be unspecified or consistent with the batch-level entity.

489

"propertyId": "A String", # A Google Analytics GA4 property id. To learn more, see [where to find your Property ID](https://developers.google.com/analytics/devguides/reporting/data/v1/property-id).

490

},

491

"keepEmptyRows": True or False, # 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.

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

492

"limit": "A String", # The number of rows to return. If the `limit` parameter is unspecified, 10,000 rows are returned. The API returns a maximum of 100,000 rows per request, no matter how many you ask for.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

493

"metricAggregations": [ # Aggregation of metrics. Aggregated metric values will be shown in rows where the dimension_values are set to "RESERVED_(MetricAggregation)".

494

"A String",

495

],

496

"metricFilter": { # To express dimension or metric filters. The fields in the same FilterExpression need to be either all dimensions or all metrics. # The filter clause of metrics. Applied at post aggregation phase, similar to SQL having-clause. Metrics must be requested to be used in this filter. Dimensions cannot be used in this filter.

497

"andGroup": { # A list of filter expressions. # The FilterExpressions in and_group have an AND relationship.

498

"expressions": [ # A list of filter expressions.

499

# Object with schema name: FilterExpression

500

],

501

},

502

"filter": { # An expression to filter dimension or metric values. # A primitive filter. All fields in filter in same FilterExpression needs to be either all dimensions or metrics.

503

"betweenFilter": { # To express that the result needs to be between two numbers (inclusive). # A filter for two values.

504

"fromValue": { # To represent a number. # Begins with this number.

505

"doubleValue": 3.14, # Double value

506

"int64Value": "A String", # Integer value

507

},

508

"toValue": { # To represent a number. # Ends with this number.

509

"doubleValue": 3.14, # Double value

510

"int64Value": "A String", # Integer value

511

},

512

},

513

"fieldName": "A String", # The dimension name or metric name. Must be a name defined in dimensions or metrics.

514

"inListFilter": { # The result needs to be in a list of string values. # A filter for in list values.

515

"caseSensitive": True or False, # If true, the string value is case sensitive.

516

"values": [ # The list of string values. Must be non-empty.

517

"A String",

518

],

519

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

520

"numericFilter": { # Filters for numeric or date values. # A filter for numeric or date values.

521

"operation": "A String", # The operation type for this filter.

522

"value": { # To represent a number. # A numeric value or a date value.

523

"doubleValue": 3.14, # Double value

524

"int64Value": "A String", # Integer value

525

},

526

},

527

"stringFilter": { # The filter for string # Strings related filter.

528

"caseSensitive": True or False, # If true, the string value is case sensitive.

529

"matchType": "A String", # The match type for this filter.

530

"value": "A String", # The string value used for the matching.

531

},

532

},

533

"notExpression": # Object with schema name: FilterExpression # The FilterExpression is NOT of not_expression.

534

"orGroup": { # A list of filter expressions. # The FilterExpressions in or_group have an OR relationship.

535

"expressions": [ # A list of filter expressions.

536

# Object with schema name: FilterExpression

],

},

},

"metrics": [ # The metrics requested and displayed.

541

{ # The quantitative measurements of a report. For example, the metric `eventCount` is the total number of events. Requests are allowed up to 10 metrics.

542

"expression": "A String", # A mathematical expression for derived metrics. For example, the metric Event count per user is `eventCount/totalUsers`.

543

"invisible": True or False, # Indicates if a metric is invisible in the report response. If a metric is invisible, the metric will not produce a column in the response, but can be used in `metricFilter`, `orderBys`, or a metric `expression`.

544

"name": "A String", # The name of the metric. See the [API Metrics](https://developers.google.com/analytics/devguides/reporting/data/v1/api-schema#metrics) for the list of metric names. If `expression` is specified, `name` can be any string that you would like. For example if `expression` is `screenPageViews/sessions`, you could call that metric's name = `viewsPerSession`. Metrics are referenced by `name` in `metricFilter`, `orderBys`, and metric `expression`.

545

},

546

],

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

547

"offset": "A String", # The row count of the start row. The first row is counted as row 0.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

548

"orderBys": [ # Specifies how rows are ordered in the response.

549

{ # The sort options.

550

"desc": True or False, # If true, sorts by descending order.

551

"dimension": { # Sorts by dimension values. # Sorts results by a dimension's values.

552

"dimensionName": "A String", # A dimension name in the request to order by.

553

"orderType": "A String", # Controls the rule for dimension value ordering.

554

},

555

"metric": { # Sorts by metric values. # Sorts results by a metric's values.

556

"metricName": "A String", # A metric name in the request to order by.

557

},

558

"pivot": { # Sorts by a pivot column group. # Sorts results by a metric's values within a pivot column group.

559

"metricName": "A String", # In the response to order by, order rows by this column. Must be a metric name from the request.

560

"pivotSelections": [ # Used to select a dimension name and value pivot. If multiple pivot selections are given, the sort occurs on rows where all pivot selection dimension name and value pairs match the row's dimension name and value pair.

561

{ # A pair of dimension names and values. Rows with this dimension pivot pair are ordered by the metric's value. For example if pivots = {{"browser", "Chrome"}} and metric_name = "Sessions", then the rows will be sorted based on Sessions in Chrome. ---------|----------|----------------|----------|---------------- | Chrome | Chrome | Safari | Safari ---------|----------|----------------|----------|---------------- Country | Sessions | Pages/Sessions | Sessions | Pages/Sessions ---------|----------|----------------|----------|---------------- US | 2 | 2 | 3 | 1 ---------|----------|----------------|----------|---------------- Canada | 3 | 1 | 4 | 1 ---------|----------|----------------|----------|----------------

562

"dimensionName": "A String", # Must be a dimension name from the request.

563

"dimensionValue": "A String", # Order by only when the named dimension is this value.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

564

},

565

],

566

},

Yoshi Automation Bot

2020-11-25 07:50:41 -0800

[diff] [blame]

567

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

568

],

569

"returnPropertyQuota": True or False, # Toggles whether to return the current state of this Analytics Property's quota. Quota is returned in [PropertyQuota](#PropertyQuota).

570

},

571

],

572

}

Dmitry Frenkel

2020-10-06 16:46:05 -0700

[diff] [blame]

573

574

x__xgafv: string, V1 error format.

Allowed values

1 - v1 error format

2 - v2 error format

Returns:

An object of the form:

581

582

{ # The batch response containing multiple reports.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

583

"reports": [ # Individual responses. Each response has a separate report request.

584

{ # The response report table corresponding to a request.

585

"dimensionHeaders": [ # Describes dimension columns. The number of DimensionHeaders and ordering of DimensionHeaders matches the dimensions present in rows.

586

{ # Describes a dimension column in the report. Dimensions requested in a report produce column entries within rows and DimensionHeaders. However, dimensions used exclusively within filters or expressions do not produce columns in a report; correspondingly, those dimensions do not produce headers.

587

"name": "A String", # The dimension's name.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

588

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

589

],

590

"maximums": [ # If requested, the maximum values of metrics.

591

{ # Report data for each row. For example if RunReportRequest contains: ```none "dimensions": [ { "name": "eventName" }, { "name": "countryId" } ], "metrics": [ { "name": "eventCount" } ] ``` One row with 'in_app_purchase' as the eventName, 'JP' as the countryId, and 15 as the eventCount, would be: ```none "dimensionValues": [ { "value": "in_app_purchase" }, { "value": "JP" } ], "metricValues": [ { "value": "15" } ] ```

592

"dimensionValues": [ # List of requested dimension values. In a PivotReport, dimension_values are only listed for dimensions included in a pivot.

593

{ # The value of a dimension.

594

"value": "A String", # Value as a string if the dimension type is a string.

595

},

596

],

597

"metricValues": [ # List of requested visible metric values.

598

{ # The value of a metric.

599

"value": "A String", # Measurement value. See MetricHeader for type.

},

],

},

],

"metadata": { # Response's metadata carrying additional information about the report content. # Metadata for the report.

605

"dataLossFromOtherRow": True or False, # If true, indicates some buckets of dimension combinations are rolled into "(other)" row. This can happen for high cardinality reports.

606

},

607

"metricHeaders": [ # Describes metric columns. The number of MetricHeaders and ordering of MetricHeaders matches the metrics present in rows.

608

{ # Describes a metric column in the report. Visible metrics requested in a report produce column entries within rows and MetricHeaders. However, metrics used exclusively within filters or expressions do not produce columns in a report; correspondingly, those metrics do not produce headers.

609

"name": "A String", # The metric's name.

610

"type": "A String", # The metric's data type.

611

},

612

],

613

"minimums": [ # If requested, the minimum values of metrics.

614

{ # Report data for each row. For example if RunReportRequest contains: ```none "dimensions": [ { "name": "eventName" }, { "name": "countryId" } ], "metrics": [ { "name": "eventCount" } ] ``` One row with 'in_app_purchase' as the eventName, 'JP' as the countryId, and 15 as the eventCount, would be: ```none "dimensionValues": [ { "value": "in_app_purchase" }, { "value": "JP" } ], "metricValues": [ { "value": "15" } ] ```

615

"dimensionValues": [ # List of requested dimension values. In a PivotReport, dimension_values are only listed for dimensions included in a pivot.

616

{ # The value of a dimension.

617

"value": "A String", # Value as a string if the dimension type is a string.

618

},

619

],

620

"metricValues": [ # List of requested visible metric values.

621

{ # The value of a metric.

622

"value": "A String", # Measurement value. See MetricHeader for type.

},

],

},

],

"propertyQuota": { # Current state of all quotas for this Analytics Property. If any quota for a property is exhausted, all requests to that property will return Resource Exhausted errors. # This Analytics Property's quota state including this request.

628

"concurrentRequests": { # Current state for a particular quota group. # Standard Analytics Properties can send up to 10 concurrent requests; Analytics 360 Properties can use up to 50 concurrent requests.

629

"consumed": 42, # Quota consumed by this request.

630

"remaining": 42, # Quota remaining after this request.

631

},

632

"serverErrorsPerProjectPerHour": { # Current state for a particular quota group. # Standard Analytics Properties and cloud project pairs can have up to 10 server errors per hour; Analytics 360 Properties and cloud project pairs can have up to 50 server errors per hour.

633

"consumed": 42, # Quota consumed by this request.

634

"remaining": 42, # Quota remaining after this request.

635

},

636

"tokensPerDay": { # Current state for a particular quota group. # Standard Analytics Properties can use up to 25,000 tokens per day; Analytics 360 Properties can use 250,000 tokens per day. Most requests consume fewer than 10 tokens.

637

"consumed": 42, # Quota consumed by this request.

638

"remaining": 42, # Quota remaining after this request.

639

},

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

640

"tokensPerHour": { # Current state for a particular quota group. # 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 consumes a single number of tokens, and that number is deducted from both the hourly and daily quotas.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

641

"consumed": 42, # Quota consumed by this request.

642

"remaining": 42, # Quota remaining after this request.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

643

},

Dmitry Frenkel

2020-10-06 16:46:05 -0700

[diff] [blame]

644

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

645

"rowCount": 42, # The total number of rows in the query result, regardless of the number of rows returned in the response. For example if a query returns 175 rows and includes limit = 50 in the API request, the response will contain row_count = 175 but only 50 rows. To learn more about this pagination parameter, see [Pagination](https://developers.google.com/analytics/devguides/reporting/data/v1/basics#pagination).

646

"rows": [ # Rows of dimension value combinations and metric values in the report.

647

{ # Report data for each row. For example if RunReportRequest contains: ```none "dimensions": [ { "name": "eventName" }, { "name": "countryId" } ], "metrics": [ { "name": "eventCount" } ] ``` One row with 'in_app_purchase' as the eventName, 'JP' as the countryId, and 15 as the eventCount, would be: ```none "dimensionValues": [ { "value": "in_app_purchase" }, { "value": "JP" } ], "metricValues": [ { "value": "15" } ] ```

648

"dimensionValues": [ # List of requested dimension values. In a PivotReport, dimension_values are only listed for dimensions included in a pivot.

649

{ # The value of a dimension.

650

"value": "A String", # Value as a string if the dimension type is a string.

651

},

652

],

653

"metricValues": [ # List of requested visible metric values.

654

{ # The value of a metric.

655

"value": "A String", # Measurement value. See MetricHeader for type.

},

],

},

],

"totals": [ # If requested, the totaled values of metrics.

661

{ # Report data for each row. For example if RunReportRequest contains: ```none "dimensions": [ { "name": "eventName" }, { "name": "countryId" } ], "metrics": [ { "name": "eventCount" } ] ``` One row with 'in_app_purchase' as the eventName, 'JP' as the countryId, and 15 as the eventCount, would be: ```none "dimensionValues": [ { "value": "in_app_purchase" }, { "value": "JP" } ], "metricValues": [ { "value": "15" } ] ```

662

"dimensionValues": [ # List of requested dimension values. In a PivotReport, dimension_values are only listed for dimensions included in a pivot.

663

{ # The value of a dimension.

664

"value": "A String", # Value as a string if the dimension type is a string.

665

},

666

],

667

"metricValues": [ # List of requested visible metric values.

668

{ # The value of a metric.

669

"value": "A String", # Measurement value. See MetricHeader for type.

},

],

},

],

},

],

}</pre>

Dmitry Frenkel

2020-10-06 16:46:05 -0700

[diff] [blame]

</div>

<code class="details" id="close">close()</code>

681

<pre>Close httplib2 connections.</pre>

</div>

Dmitry Frenkel

2020-10-06 16:46:05 -0700

[diff] [blame]

685

<code class="details" id="runPivotReport">runPivotReport(body=None, x__xgafv=None)</code>

686

<pre>Returns a customized pivot report of your Google Analytics event data. Pivot reports are more advanced and expressive formats than regular reports. In a pivot report, dimensions are only visible if they are included in a pivot. Multiple pivots can be specified to further dissect your data.

687

688

Args:

689

body: object, The request body.

690

The object takes the form of:

691

692

{ # The request to generate a pivot report.

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

693

"cohortSpec": { # The specification of cohorts for a cohort report. Cohort reports create a time series of user retention for the cohort. For example, you could select the cohort of users that were acquired in the first week of September and follow that cohort for the next six weeks. Selecting the users acquired in the first week of September cohort is specified in the `cohort` object. Following that cohort for the next six weeks is specified in the `cohortsRange` object. For examples, see [Cohort Report Examples](https://developers.google.com/analytics/devguides/reporting/data/v1/advanced#cohort_report_examples). The report response could show a weekly time series where say your app has retained 60% of this cohort after three weeks and 25% of this cohort after six weeks. These two percentages can be calculated by the metric `cohortActiveUsers/cohortTotalUsers` and will be separate rows in the report. # Cohort group associated with this request. If there is a cohort group in the request the 'cohort' dimension must be present.

694

"cohortReportSettings": { # Optional settings of a cohort report. # Optional settings for a cohort report.

695

"accumulate": True or False, # If true, accumulates the result from first touch day to the end day. Not supported in `RunReportRequest`.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

696

},

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

697

"cohorts": [ # Defines the selection criteria to group users into cohorts. Most cohort reports define only a single cohort. If multiple cohorts are specified, each cohort can be recognized in the report by their name.

698

{ # Defines a cohort selection criteria. A cohort is a group of users who share a common characteristic. For example, users with the same `firstSessionDate` belong to the same cohort.

699

"dateRange": { # A contiguous set of days: startDate, startDate + 1, ..., endDate. Requests are allowed up to 4 date ranges. # The cohort selects users whose first touch date is between start date and end date defined in the `dateRange`. This `dateRange` does not specify the full date range of event data that is present in a cohort report. In a cohort report, this `dateRange` is extended by the granularity and offset present in the `cohortsRange`; event data for the extended reporting date range is present in a cohort report. In a cohort request, this `dateRange` is required and the `dateRanges` in the `RunReportRequest` or `RunPivotReportRequest` must be unspecified. This `dateRange` should generally be aligned with the cohort's granularity. If `CohortsRange` uses daily granularity, this `dateRange` can be a single day. If `CohortsRange` uses weekly granularity, this `dateRange` can be aligned to a week boundary, starting at Sunday and ending Saturday. If `CohortsRange` uses monthly granularity, this `dateRange` can be aligned to a month, starting at the first and ending on the last day of the month.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

700

"endDate": "A String", # The inclusive end date for the query in the format `YYYY-MM-DD`. Cannot be before `start_date`. The format `NdaysAgo`, `yesterday`, or `today` is also accepted, and in that case, the date is inferred based on the property's reporting time zone.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

701

"name": "A String", # Assigns a name to this date range. The dimension `dateRange` is valued to this name in a report response. If set, cannot begin with `date_range_` or `RESERVED_`. If not set, date ranges are named by their zero based index in the request: `date_range_0`, `date_range_1`, etc.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

702

"startDate": "A String", # 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 accepted, and in that case, the date is inferred based on the property's reporting time zone.

703

},

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

704

"dimension": "A String", # Dimension used by the cohort. Required and only supports `firstSessionDate`.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

705

"name": "A String", # Assigns a name to this cohort. The dimension `cohort` is valued to this name in a report response. If set, cannot begin with `cohort_` or `RESERVED_`. If not set, cohorts are named by their zero based index `cohort_0`, `cohort_1`, etc.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

706

},

707

],

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

708

"cohortsRange": { # Configures the extended reporting date range for a cohort report. Specifies an offset duration to follow the cohorts over. # Cohort reports follow cohorts over an extended reporting date range. This range specifies an offset duration to follow the cohorts over.

709

"endOffset": 42, # Required. `endOffset` specifies the end date of the extended reporting date range for a cohort report. `endOffset` can be any positive integer but is commonly set to 5 to 10 so that reports contain data on the cohort for the next several granularity time periods. If `granularity` is `DAILY`, the `endDate` of the extended reporting date range is `endDate` of the cohort plus `endOffset` days. If `granularity` is `WEEKLY`, the `endDate` of the extended reporting date range is `endDate` of the cohort plus `endOffset * 7` days. If `granularity` is `MONTHLY`, the `endDate` of the extended reporting date range is `endDate` of the cohort plus `endOffset * 30` days.

710

"granularity": "A String", # Required. The granularity used to interpret the `startOffset` and `endOffset` for the extended reporting date range for a cohort report.

711

"startOffset": 42, # `startOffset` specifies the start date of the extended reporting date range for a cohort report. `startOffset` is commonly set to 0 so that reports contain data from the acquisition of the cohort forward. If `granularity` is `DAILY`, the `startDate` of the extended reporting date range is `startDate` of the cohort plus `startOffset` days. If `granularity` is `WEEKLY`, the `startDate` of the extended reporting date range is `startDate` of the cohort plus `startOffset * 7` days. If `granularity` is `MONTHLY`, the `startDate` of the extended reporting date range is `startDate` of the cohort plus `startOffset * 30` days.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

712

},

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

713

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

714

"currencyCode": "A String", # A currency code in ISO4217 format, such as "AED", "USD", "JPY". If the field is empty, the report uses the entity's default currency.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

715

"dateRanges": [ # The date range to retrieve event data for the report. If multiple date ranges are specified, event data from each date range is used in the report. A special dimension with field name "dateRange" can be included in a Pivot's field names; if included, the report compares between date ranges. In a cohort request, this `dateRanges` must be unspecified.

716

{ # A contiguous set of days: startDate, startDate + 1, ..., endDate. Requests are allowed up to 4 date ranges.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

717

"endDate": "A String", # The inclusive end date for the query in the format `YYYY-MM-DD`. Cannot be before `start_date`. The format `NdaysAgo`, `yesterday`, or `today` is also accepted, and in that case, the date is inferred based on the property's reporting time zone.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

718

"name": "A String", # Assigns a name to this date range. The dimension `dateRange` is valued to this name in a report response. If set, cannot begin with `date_range_` or `RESERVED_`. If not set, date ranges are named by their zero based index in the request: `date_range_0`, `date_range_1`, etc.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

719

"startDate": "A String", # 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 accepted, and in that case, the date is inferred based on the property's reporting time zone.

720

},

721

],

722

"dimensionFilter": { # To express dimension or metric filters. The fields in the same FilterExpression need to be either all dimensions or all metrics. # The filter clause of dimensions. Dimensions must be requested to be used in this filter. Metrics cannot be used in this filter.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

723

"andGroup": { # A list of filter expressions. # The FilterExpressions in and_group have an AND relationship.

724

"expressions": [ # A list of filter expressions.

725

# Object with schema name: FilterExpression

726

],

727

},

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

728

"filter": { # An expression to filter dimension or metric values. # A primitive filter. All fields in filter in same FilterExpression needs to be either all dimensions or metrics.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

729

"betweenFilter": { # To express that the result needs to be between two numbers (inclusive). # A filter for two values.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

730

"fromValue": { # To represent a number. # Begins with this number.

731

"doubleValue": 3.14, # Double value

732

"int64Value": "A String", # Integer value

733

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

734

"toValue": { # To represent a number. # Ends with this number.

735

"doubleValue": 3.14, # Double value

736

"int64Value": "A String", # Integer value

737

},

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

738

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

739

"fieldName": "A String", # The dimension name or metric name. Must be a name defined in dimensions or metrics.

740

"inListFilter": { # The result needs to be in a list of string values. # A filter for in list values.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

741

"caseSensitive": True or False, # If true, the string value is case sensitive.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

742

"values": [ # The list of string values. Must be non-empty.

743

"A String",

744

],

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

745

},

746

"numericFilter": { # Filters for numeric or date values. # A filter for numeric or date values.

747

"operation": "A String", # The operation type for this filter.

748

"value": { # To represent a number. # A numeric value or a date value.

749

"doubleValue": 3.14, # Double value

750

"int64Value": "A String", # Integer value

751

},

752

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

753

"stringFilter": { # The filter for string # Strings related filter.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

754

"caseSensitive": True or False, # If true, the string value is case sensitive.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

755

"matchType": "A String", # The match type for this filter.

756

"value": "A String", # The string value used for the matching.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

757

},

758

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

759

"notExpression": # Object with schema name: FilterExpression # The FilterExpression is NOT of not_expression.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

760

"orGroup": { # A list of filter expressions. # The FilterExpressions in or_group have an OR relationship.

761

"expressions": [ # A list of filter expressions.

762

# Object with schema name: FilterExpression

763

],

764

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

765

},

766

"dimensions": [ # The dimensions requested. All defined dimensions must be used by one of the following: dimension_expression, dimension_filter, pivots, order_bys.

767

{ # Dimensions are attributes of your data. For example, the dimension city indicates the city from which an event originates. Dimension values in report responses are strings; for example, city could be "Paris" or "New York". Requests are allowed up to 8 dimensions.

768

"dimensionExpression": { # Used to express a dimension which is the result of a formula of multiple dimensions. Example usages: 1) lower_case(dimension) 2) concatenate(dimension1, symbol, dimension2). # One dimension can be the result of an expression of multiple dimensions. For example, dimension "country, city": concatenate(country, ", ", city).

769

"concatenate": { # Used to combine dimension values to a single dimension. # Used to combine dimension values to a single dimension. For example, dimension "country, city": concatenate(country, ", ", city).

770

"delimiter": "A String", # The delimiter placed between dimension names. Delimiters are often single characters such as "|" or "," but can be longer strings. If a dimension value contains the delimiter, both will be present in response with no distinction. For example if dimension 1 value = "US,FR", dimension 2 value = "JP", and delimiter = ",", then the response will contain "US,FR,JP".

771

"dimensionNames": [ # Names of dimensions. The names must refer back to names in the dimensions field of the request.

"A String",

],

},

"lowerCase": { # Used to convert a dimension value to a single case. # Used to convert a dimension value to lower case.

776

"dimensionName": "A String", # Name of a dimension. The name must refer back to a name in dimensions field of the request.

777

},

778

"upperCase": { # Used to convert a dimension value to a single case. # Used to convert a dimension value to upper case.

779

"dimensionName": "A String", # Name of a dimension. The name must refer back to a name in dimensions field of the request.

780

},

781

},

782

"name": "A String", # The name of the dimension. See the [API Dimensions](https://developers.google.com/analytics/devguides/reporting/data/v1/api-schema#dimensions) for the list of dimension names. If `dimensionExpression` is specified, `name` can be any string that you would like. For example if a `dimensionExpression` concatenates `country` and `city`, you could call that dimension `countryAndCity`. Dimensions are referenced by `name` in `dimensionFilter`, `orderBys`, `dimensionExpression`, and `pivots`.

783

},

784

],

785

"entity": { # The unique identifier of the property whose events are tracked. # A property whose events are tracked. Within a batch request, this entity should either be unspecified or consistent with the batch-level entity.

786

"propertyId": "A String", # A Google Analytics GA4 property id. To learn more, see [where to find your Property ID](https://developers.google.com/analytics/devguides/reporting/data/v1/property-id).

787

},

788

"keepEmptyRows": True or False, # 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.

789

"metricFilter": { # To express dimension or metric filters. The fields in the same FilterExpression need to be either all dimensions or all metrics. # The filter clause of metrics. Applied at post aggregation phase, similar to SQL having-clause. Metrics must be requested to be used in this filter. Dimensions cannot be used in this filter.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

790

"andGroup": { # A list of filter expressions. # The FilterExpressions in and_group have an AND relationship.

791

"expressions": [ # A list of filter expressions.

792

# Object with schema name: FilterExpression

793

],

794

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

795

"filter": { # An expression to filter dimension or metric values. # A primitive filter. All fields in filter in same FilterExpression needs to be either all dimensions or metrics.

796

"betweenFilter": { # To express that the result needs to be between two numbers (inclusive). # A filter for two values.

797

"fromValue": { # To represent a number. # Begins with this number.

798

"doubleValue": 3.14, # Double value

799

"int64Value": "A String", # Integer value

800

},

801

"toValue": { # To represent a number. # Ends with this number.

802

"doubleValue": 3.14, # Double value

803

"int64Value": "A String", # Integer value

804

},

805

},

806

"fieldName": "A String", # The dimension name or metric name. Must be a name defined in dimensions or metrics.

807

"inListFilter": { # The result needs to be in a list of string values. # A filter for in list values.

808

"caseSensitive": True or False, # If true, the string value is case sensitive.

809

"values": [ # The list of string values. Must be non-empty.

810

"A String",

811

],

812

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

813

"numericFilter": { # Filters for numeric or date values. # A filter for numeric or date values.

814

"operation": "A String", # The operation type for this filter.

815

"value": { # To represent a number. # A numeric value or a date value.

816

"doubleValue": 3.14, # Double value

817

"int64Value": "A String", # Integer value

818

},

819

},

820

"stringFilter": { # The filter for string # Strings related filter.

821

"caseSensitive": True or False, # If true, the string value is case sensitive.

822

"matchType": "A String", # The match type for this filter.

823

"value": "A String", # The string value used for the matching.

824

},

825

},

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

826

"notExpression": # Object with schema name: FilterExpression # The FilterExpression is NOT of not_expression.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

827

"orGroup": { # A list of filter expressions. # The FilterExpressions in or_group have an OR relationship.

828

"expressions": [ # A list of filter expressions.

829

# Object with schema name: FilterExpression

830

],

831

},

Yoshi Automation Bot

2020-11-26 17:16:03 -0800

[diff] [blame]

832

},

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

833

"metrics": [ # The metrics requested, at least one metric needs to be specified. All defined metrics must be used by one of the following: metric_expression, metric_filter, order_bys.

834

{ # The quantitative measurements of a report. For example, the metric `eventCount` is the total number of events. Requests are allowed up to 10 metrics.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

835

"expression": "A String", # A mathematical expression for derived metrics. For example, the metric Event count per user is `eventCount/totalUsers`.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

836

"invisible": True or False, # Indicates if a metric is invisible in the report response. If a metric is invisible, the metric will not produce a column in the response, but can be used in `metricFilter`, `orderBys`, or a metric `expression`.

837

"name": "A String", # The name of the metric. See the [API Metrics](https://developers.google.com/analytics/devguides/reporting/data/v1/api-schema#metrics) for the list of metric names. If `expression` is specified, `name` can be any string that you would like. For example if `expression` is `screenPageViews/sessions`, you could call that metric's name = `viewsPerSession`. Metrics are referenced by `name` in `metricFilter`, `orderBys`, and metric `expression`.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

838

},

839

],

Yoshi Automation Bot

2020-11-25 07:50:41 -0800

[diff] [blame]

840

"pivots": [ # Describes the visual format of the report's dimensions in columns or rows. The union of the fieldNames (dimension names) in all pivots must be a subset of dimension names defined in Dimensions. No two pivots can share a dimension. A dimension is only visible if it appears in a pivot.

841

{ # Describes the visible dimension columns and rows in the report response.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

842

"fieldNames": [ # Dimension names for visible columns in the report response. Including "dateRange" produces a date range column; for each row in the response, dimension values in the date range column will indicate the corresponding date range from the request.

843

"A String",

844

],

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

845

"limit": "A String", # The number of rows to return in this pivot. If the `limit` parameter is unspecified, up to 10,000 rows are returned. The product of the `limit` for each `pivot` in a `RunPivotReportRequest` must not exceed 100,000. For example, a two pivot request with `limit: 1000` in each pivot will fail because the product is `1,000,000`.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

846

"metricAggregations": [ # Aggregate the metrics by dimensions in this pivot using the specified metric_aggregations.

Yoshi Automation Bot

2020-11-26 17:16:03 -0800

[diff] [blame]

847

"A String",

848

],

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

849

"offset": "A String", # The row count of the start row. The first row is counted as row 0.

Yoshi Automation Bot

2020-11-25 07:50:41 -0800

[diff] [blame]

850

"orderBys": [ # Specifies how dimensions are ordered in the pivot. In the first Pivot, the OrderBys determine Row and PivotDimensionHeader ordering; in subsequent Pivots, the OrderBys determine only PivotDimensionHeader ordering. Dimensions specified in these OrderBys must be a subset of Pivot.field_names.

851

{ # The sort options.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

852

"desc": True or False, # If true, sorts by descending order.

853

"dimension": { # Sorts by dimension values. # Sorts results by a dimension's values.

854

"dimensionName": "A String", # A dimension name in the request to order by.

855

"orderType": "A String", # Controls the rule for dimension value ordering.

856

},

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

857

"metric": { # Sorts by metric values. # Sorts results by a metric's values.

858

"metricName": "A String", # A metric name in the request to order by.

859

},

Yoshi Automation Bot

2020-11-25 07:50:41 -0800

[diff] [blame]

860

"pivot": { # Sorts by a pivot column group. # Sorts results by a metric's values within a pivot column group.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

861

"metricName": "A String", # In the response to order by, order rows by this column. Must be a metric name from the request.

Yoshi Automation Bot

2020-11-25 07:50:41 -0800

[diff] [blame]

862

"pivotSelections": [ # Used to select a dimension name and value pivot. If multiple pivot selections are given, the sort occurs on rows where all pivot selection dimension name and value pairs match the row's dimension name and value pair.

863

{ # A pair of dimension names and values. Rows with this dimension pivot pair are ordered by the metric's value. For example if pivots = {{"browser", "Chrome"}} and metric_name = "Sessions", then the rows will be sorted based on Sessions in Chrome. ---------|----------|----------------|----------|---------------- | Chrome | Chrome | Safari | Safari ---------|----------|----------------|----------|---------------- Country | Sessions | Pages/Sessions | Sessions | Pages/Sessions ---------|----------|----------------|----------|---------------- US | 2 | 2 | 3 | 1 ---------|----------|----------------|----------|---------------- Canada | 3 | 1 | 4 | 1 ---------|----------|----------------|----------|----------------

864

"dimensionName": "A String", # Must be a dimension name from the request.

865

"dimensionValue": "A String", # Order by only when the named dimension is this value.

866

},

867

],

Yoshi Automation Bot

2020-11-26 17:16:03 -0800

[diff] [blame]

868

},

Yoshi Automation Bot

2020-11-24 15:48:03 -0800

[diff] [blame]

869

},

870

],

Dmitry Frenkel

2020-10-06 16:46:05 -0700

[diff] [blame]

871

},

Yoshi Automation Bot

2020-11-25 07:50:41 -0800

[diff] [blame]

872

],

Yoshi Automation Bot

2020-11-26 17:16:03 -0800

[diff] [blame]

873

"returnPropertyQuota": True or False, # Toggles whether to return the current state of this Analytics Property's quota. Quota is returned in [PropertyQuota](#PropertyQuota).

Yoshi Automation Bot

2020-11-25 07:50:41 -0800

[diff] [blame]

874

}

Dmitry Frenkel

2020-10-06 16:46:05 -0700

[diff] [blame]

875

876

x__xgafv: string, V1 error format.

Allowed values

1 - v1 error format

2 - v2 error format

Returns:

An object of the form:

883

884

{ # The response pivot report table corresponding to a pivot request.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

885

"aggregates": [ # Aggregation of metric values. Can be totals, minimums, or maximums. The returned aggregations are controlled by the metric_aggregations in the pivot. The type of aggregation returned in each row is shown by the dimension_values which are set to "RESERVED_".

886

{ # Report data for each row. For example if RunReportRequest contains: ```none "dimensions": [ { "name": "eventName" }, { "name": "countryId" } ], "metrics": [ { "name": "eventCount" } ] ``` One row with 'in_app_purchase' as the eventName, 'JP' as the countryId, and 15 as the eventCount, would be: ```none "dimensionValues": [ { "value": "in_app_purchase" }, { "value": "JP" } ], "metricValues": [ { "value": "15" } ] ```

887

"dimensionValues": [ # List of requested dimension values. In a PivotReport, dimension_values are only listed for dimensions included in a pivot.

888

{ # The value of a dimension.

889

"value": "A String", # Value as a string if the dimension type is a string.

890

},

891

],

892

"metricValues": [ # List of requested visible metric values.

893

{ # The value of a metric.

894

"value": "A String", # Measurement value. See MetricHeader for type.

895

},

896

],

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

897

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

898

],

899

"dimensionHeaders": [ # Describes dimension columns. The number of DimensionHeaders and ordering of DimensionHeaders matches the dimensions present in rows.

900

{ # Describes a dimension column in the report. Dimensions requested in a report produce column entries within rows and DimensionHeaders. However, dimensions used exclusively within filters or expressions do not produce columns in a report; correspondingly, those dimensions do not produce headers.

901

"name": "A String", # The dimension's name.

Yoshi Automation Bot

2020-11-26 17:16:03 -0800

[diff] [blame]

902

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

903

],

904

"metadata": { # Response's metadata carrying additional information about the report content. # Metadata for the report.

905

"dataLossFromOtherRow": True or False, # If true, indicates some buckets of dimension combinations are rolled into "(other)" row. This can happen for high cardinality reports.

906

},

907

"metricHeaders": [ # Describes metric columns. The number of MetricHeaders and ordering of MetricHeaders matches the metrics present in rows.

908

{ # Describes a metric column in the report. Visible metrics requested in a report produce column entries within rows and MetricHeaders. However, metrics used exclusively within filters or expressions do not produce columns in a report; correspondingly, those metrics do not produce headers.

909

"name": "A String", # The metric's name.

910

"type": "A String", # The metric's data type.

911

},

912

],

913

"pivotHeaders": [ # Summarizes the columns and rows created by a pivot. Each pivot in the request produces one header in the response. If we have a request like this: "pivots": [{ "fieldNames": ["country", "city"] }, { "fieldNames": "eventName" }] We will have the following `pivotHeaders` in the response: "pivotHeaders" : [{ "dimensionHeaders": [{ "dimensionValues": [ { "value": "United Kingdom" }, { "value": "London" } ] }, { "dimensionValues": [ { "value": "Japan" }, { "value": "Osaka" } ] }] }, { "dimensionHeaders": [{ "dimensionValues": [{ "value": "session_start" }] }, { "dimensionValues": [{ "value": "scroll" }] }] }]

914

{ # Dimensions' values in a single pivot.

915

"pivotDimensionHeaders": [ # The size is the same as the cardinality of the corresponding dimension combinations.

916

{ # Summarizes dimension values from a row for this pivot.

917

"dimensionValues": [ # Values of multiple dimensions in a pivot.

918

{ # The value of a dimension.

919

"value": "A String", # Value as a string if the dimension type is a string.

},

],

},

],

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

924

"rowCount": 42, # The cardinality of the pivot. The total number of rows for this pivot's fields regardless of how the parameters `offset` and `limit` are specified in the request.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

925

},

926

],

927

"propertyQuota": { # Current state of all quotas for this Analytics Property. If any quota for a property is exhausted, all requests to that property will return Resource Exhausted errors. # This Analytics Property's quota state including this request.

928

"concurrentRequests": { # Current state for a particular quota group. # Standard Analytics Properties can send up to 10 concurrent requests; Analytics 360 Properties can use up to 50 concurrent requests.

929

"consumed": 42, # Quota consumed by this request.

930

"remaining": 42, # Quota remaining after this request.

931

},

932

"serverErrorsPerProjectPerHour": { # Current state for a particular quota group. # Standard Analytics Properties and cloud project pairs can have up to 10 server errors per hour; Analytics 360 Properties and cloud project pairs can have up to 50 server errors per hour.

933

"consumed": 42, # Quota consumed by this request.

934

"remaining": 42, # Quota remaining after this request.

935

},

936

"tokensPerDay": { # Current state for a particular quota group. # Standard Analytics Properties can use up to 25,000 tokens per day; Analytics 360 Properties can use 250,000 tokens per day. Most requests consume fewer than 10 tokens.

937

"consumed": 42, # Quota consumed by this request.

938

"remaining": 42, # Quota remaining after this request.

939

},

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

940

"tokensPerHour": { # Current state for a particular quota group. # 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 consumes a single number of tokens, and that number is deducted from both the hourly and daily quotas.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

941

"consumed": 42, # Quota consumed by this request.

942

"remaining": 42, # Quota remaining after this request.

943

},

944

},

945

"rows": [ # Rows of dimension value combinations and metric values in the report.

946

{ # Report data for each row. For example if RunReportRequest contains: ```none "dimensions": [ { "name": "eventName" }, { "name": "countryId" } ], "metrics": [ { "name": "eventCount" } ] ``` One row with 'in_app_purchase' as the eventName, 'JP' as the countryId, and 15 as the eventCount, would be: ```none "dimensionValues": [ { "value": "in_app_purchase" }, { "value": "JP" } ], "metricValues": [ { "value": "15" } ] ```

947

"dimensionValues": [ # List of requested dimension values. In a PivotReport, dimension_values are only listed for dimensions included in a pivot.

948

{ # The value of a dimension.

949

"value": "A String", # Value as a string if the dimension type is a string.

950

},

951

],

952

"metricValues": [ # List of requested visible metric values.

953

{ # The value of a metric.

954

"value": "A String", # Measurement value. See MetricHeader for type.

},

],

},

],

}</pre>

Dmitry Frenkel

2020-10-06 16:46:05 -0700

[diff] [blame]

</div>

<code class="details" id="runReport">runReport(body=None, x__xgafv=None)</code>

964

<pre>Returns a customized report of your Google Analytics event data. Reports contain statistics derived from data collected by the Google Analytics tracking code. The data returned from the API is as a table with columns for the requested dimensions and metrics. Metrics are individual measurements of user activity on your property, such as active users or event count. Dimensions break down metrics across some common criteria, such as country or event name.

965

966

Args:

967

body: object, The request body.

968

The object takes the form of:

969

970

{ # The request to generate a report.

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

971

"cohortSpec": { # The specification of cohorts for a cohort report. Cohort reports create a time series of user retention for the cohort. For example, you could select the cohort of users that were acquired in the first week of September and follow that cohort for the next six weeks. Selecting the users acquired in the first week of September cohort is specified in the `cohort` object. Following that cohort for the next six weeks is specified in the `cohortsRange` object. For examples, see [Cohort Report Examples](https://developers.google.com/analytics/devguides/reporting/data/v1/advanced#cohort_report_examples). The report response could show a weekly time series where say your app has retained 60% of this cohort after three weeks and 25% of this cohort after six weeks. These two percentages can be calculated by the metric `cohortActiveUsers/cohortTotalUsers` and will be separate rows in the report. # Cohort group associated with this request. If there is a cohort group in the request the 'cohort' dimension must be present.

972

"cohortReportSettings": { # Optional settings of a cohort report. # Optional settings for a cohort report.

973

"accumulate": True or False, # If true, accumulates the result from first touch day to the end day. Not supported in `RunReportRequest`.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

974

},

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

975

"cohorts": [ # Defines the selection criteria to group users into cohorts. Most cohort reports define only a single cohort. If multiple cohorts are specified, each cohort can be recognized in the report by their name.

976

{ # Defines a cohort selection criteria. A cohort is a group of users who share a common characteristic. For example, users with the same `firstSessionDate` belong to the same cohort.

977

"dateRange": { # A contiguous set of days: startDate, startDate + 1, ..., endDate. Requests are allowed up to 4 date ranges. # The cohort selects users whose first touch date is between start date and end date defined in the `dateRange`. This `dateRange` does not specify the full date range of event data that is present in a cohort report. In a cohort report, this `dateRange` is extended by the granularity and offset present in the `cohortsRange`; event data for the extended reporting date range is present in a cohort report. In a cohort request, this `dateRange` is required and the `dateRanges` in the `RunReportRequest` or `RunPivotReportRequest` must be unspecified. This `dateRange` should generally be aligned with the cohort's granularity. If `CohortsRange` uses daily granularity, this `dateRange` can be a single day. If `CohortsRange` uses weekly granularity, this `dateRange` can be aligned to a week boundary, starting at Sunday and ending Saturday. If `CohortsRange` uses monthly granularity, this `dateRange` can be aligned to a month, starting at the first and ending on the last day of the month.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

978

"endDate": "A String", # The inclusive end date for the query in the format `YYYY-MM-DD`. Cannot be before `start_date`. The format `NdaysAgo`, `yesterday`, or `today` is also accepted, and in that case, the date is inferred based on the property's reporting time zone.

979

"name": "A String", # Assigns a name to this date range. The dimension `dateRange` is valued to this name in a report response. If set, cannot begin with `date_range_` or `RESERVED_`. If not set, date ranges are named by their zero based index in the request: `date_range_0`, `date_range_1`, etc.

980

"startDate": "A String", # 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 accepted, and in that case, the date is inferred based on the property's reporting time zone.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

981

},

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

982

"dimension": "A String", # Dimension used by the cohort. Required and only supports `firstSessionDate`.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

983

"name": "A String", # Assigns a name to this cohort. The dimension `cohort` is valued to this name in a report response. If set, cannot begin with `cohort_` or `RESERVED_`. If not set, cohorts are named by their zero based index `cohort_0`, `cohort_1`, etc.

984

},

985

],

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

986

"cohortsRange": { # Configures the extended reporting date range for a cohort report. Specifies an offset duration to follow the cohorts over. # Cohort reports follow cohorts over an extended reporting date range. This range specifies an offset duration to follow the cohorts over.

987

"endOffset": 42, # Required. `endOffset` specifies the end date of the extended reporting date range for a cohort report. `endOffset` can be any positive integer but is commonly set to 5 to 10 so that reports contain data on the cohort for the next several granularity time periods. If `granularity` is `DAILY`, the `endDate` of the extended reporting date range is `endDate` of the cohort plus `endOffset` days. If `granularity` is `WEEKLY`, the `endDate` of the extended reporting date range is `endDate` of the cohort plus `endOffset * 7` days. If `granularity` is `MONTHLY`, the `endDate` of the extended reporting date range is `endDate` of the cohort plus `endOffset * 30` days.

988

"granularity": "A String", # Required. The granularity used to interpret the `startOffset` and `endOffset` for the extended reporting date range for a cohort report.

989

"startOffset": 42, # `startOffset` specifies the start date of the extended reporting date range for a cohort report. `startOffset` is commonly set to 0 so that reports contain data from the acquisition of the cohort forward. If `granularity` is `DAILY`, the `startDate` of the extended reporting date range is `startDate` of the cohort plus `startOffset` days. If `granularity` is `WEEKLY`, the `startDate` of the extended reporting date range is `startDate` of the cohort plus `startOffset * 7` days. If `granularity` is `MONTHLY`, the `startDate` of the extended reporting date range is `startDate` of the cohort plus `startOffset * 30` days.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

990

},

991

},

992

"currencyCode": "A String", # A currency code in ISO4217 format, such as "AED", "USD", "JPY". If the field is empty, the report uses the entity's default currency.

993

"dateRanges": [ # Date ranges of data to read. If multiple date ranges are requested, each response row will contain a zero based date range index. If two date ranges overlap, the event data for the overlapping days is included in the response rows for both date ranges. In a cohort request, this `dateRanges` must be unspecified.

994

{ # A contiguous set of days: startDate, startDate + 1, ..., endDate. Requests are allowed up to 4 date ranges.

995

"endDate": "A String", # The inclusive end date for the query in the format `YYYY-MM-DD`. Cannot be before `start_date`. The format `NdaysAgo`, `yesterday`, or `today` is also accepted, and in that case, the date is inferred based on the property's reporting time zone.

996

"name": "A String", # Assigns a name to this date range. The dimension `dateRange` is valued to this name in a report response. If set, cannot begin with `date_range_` or `RESERVED_`. If not set, date ranges are named by their zero based index in the request: `date_range_0`, `date_range_1`, etc.

997

"startDate": "A String", # 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 accepted, and in that case, the date is inferred based on the property's reporting time zone.

998

},

999

],

1000

"dimensionFilter": { # To express dimension or metric filters. The fields in the same FilterExpression need to be either all dimensions or all metrics. # The filter clause of dimensions. Dimensions must be requested to be used in this filter. Metrics cannot be used in this filter.

1001

"andGroup": { # A list of filter expressions. # The FilterExpressions in and_group have an AND relationship.

1002

"expressions": [ # A list of filter expressions.

1003

# Object with schema name: FilterExpression

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

1004

],

1005

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

1006

"filter": { # An expression to filter dimension or metric values. # A primitive filter. All fields in filter in same FilterExpression needs to be either all dimensions or metrics.

1007

"betweenFilter": { # To express that the result needs to be between two numbers (inclusive). # A filter for two values.

1008

"fromValue": { # To represent a number. # Begins with this number.

1009

"doubleValue": 3.14, # Double value

1010

"int64Value": "A String", # Integer value

1011

},

1012

"toValue": { # To represent a number. # Ends with this number.

1013

"doubleValue": 3.14, # Double value

1014

"int64Value": "A String", # Integer value

1015

},

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

1016

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

1017

"fieldName": "A String", # The dimension name or metric name. Must be a name defined in dimensions or metrics.

1018

"inListFilter": { # The result needs to be in a list of string values. # A filter for in list values.

1019

"caseSensitive": True or False, # If true, the string value is case sensitive.

1020

"values": [ # The list of string values. Must be non-empty.

1021

"A String",

1022

],

1023

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

1024

"numericFilter": { # Filters for numeric or date values. # A filter for numeric or date values.

1025

"operation": "A String", # The operation type for this filter.

1026

"value": { # To represent a number. # A numeric value or a date value.

1027

"doubleValue": 3.14, # Double value

1028

"int64Value": "A String", # Integer value

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

1029

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

1030

},

1031

"stringFilter": { # The filter for string # Strings related filter.

1032

"caseSensitive": True or False, # If true, the string value is case sensitive.

1033

"matchType": "A String", # The match type for this filter.

1034

"value": "A String", # The string value used for the matching.

1035

},

1036

},

1037

"notExpression": # Object with schema name: FilterExpression # The FilterExpression is NOT of not_expression.

1038

"orGroup": { # A list of filter expressions. # The FilterExpressions in or_group have an OR relationship.

1039

"expressions": [ # A list of filter expressions.

1040

# Object with schema name: FilterExpression

],

},

},

"dimensions": [ # The dimensions requested and displayed.

1045

{ # Dimensions are attributes of your data. For example, the dimension city indicates the city from which an event originates. Dimension values in report responses are strings; for example, city could be "Paris" or "New York". Requests are allowed up to 8 dimensions.

1046

"dimensionExpression": { # Used to express a dimension which is the result of a formula of multiple dimensions. Example usages: 1) lower_case(dimension) 2) concatenate(dimension1, symbol, dimension2). # One dimension can be the result of an expression of multiple dimensions. For example, dimension "country, city": concatenate(country, ", ", city).

1047

"concatenate": { # Used to combine dimension values to a single dimension. # Used to combine dimension values to a single dimension. For example, dimension "country, city": concatenate(country, ", ", city).

1048

"delimiter": "A String", # The delimiter placed between dimension names. Delimiters are often single characters such as "|" or "," but can be longer strings. If a dimension value contains the delimiter, both will be present in response with no distinction. For example if dimension 1 value = "US,FR", dimension 2 value = "JP", and delimiter = ",", then the response will contain "US,FR,JP".

1049

"dimensionNames": [ # Names of dimensions. The names must refer back to names in the dimensions field of the request.

Yoshi Automation Bot

2020-11-24 15:48:03 -0800

[diff] [blame]

1050

"A String",

1051

],

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

1052

},

1053

"lowerCase": { # Used to convert a dimension value to a single case. # Used to convert a dimension value to lower case.

1054

"dimensionName": "A String", # Name of a dimension. The name must refer back to a name in dimensions field of the request.

1055

},

1056

"upperCase": { # Used to convert a dimension value to a single case. # Used to convert a dimension value to upper case.

1057

"dimensionName": "A String", # Name of a dimension. The name must refer back to a name in dimensions field of the request.

Yoshi Automation Bot

2020-11-24 15:48:03 -0800

[diff] [blame]

1058

},

Yoshi Automation Bot

2020-11-26 17:16:03 -0800

[diff] [blame]

1059

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

1060

"name": "A String", # The name of the dimension. See the [API Dimensions](https://developers.google.com/analytics/devguides/reporting/data/v1/api-schema#dimensions) for the list of dimension names. If `dimensionExpression` is specified, `name` can be any string that you would like. For example if a `dimensionExpression` concatenates `country` and `city`, you could call that dimension `countryAndCity`. Dimensions are referenced by `name` in `dimensionFilter`, `orderBys`, `dimensionExpression`, and `pivots`.

Yoshi Automation Bot

2020-11-24 15:48:03 -0800

[diff] [blame]

1061

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

1062

],

1063

"entity": { # The unique identifier of the property whose events are tracked. # A property whose events are tracked. Within a batch request, this entity should either be unspecified or consistent with the batch-level entity.

1064

"propertyId": "A String", # A Google Analytics GA4 property id. To learn more, see [where to find your Property ID](https://developers.google.com/analytics/devguides/reporting/data/v1/property-id).

1065

},

1066

"keepEmptyRows": True or False, # 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.

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

1067

"limit": "A String", # The number of rows to return. If the `limit` parameter is unspecified, 10,000 rows are returned. The API returns a maximum of 100,000 rows per request, no matter how many you ask for.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

1068

"metricAggregations": [ # Aggregation of metrics. Aggregated metric values will be shown in rows where the dimension_values are set to "RESERVED_(MetricAggregation)".

1069

"A String",

1070

],

1071

"metricFilter": { # To express dimension or metric filters. The fields in the same FilterExpression need to be either all dimensions or all metrics. # The filter clause of metrics. Applied at post aggregation phase, similar to SQL having-clause. Metrics must be requested to be used in this filter. Dimensions cannot be used in this filter.

1072

"andGroup": { # A list of filter expressions. # The FilterExpressions in and_group have an AND relationship.

1073

"expressions": [ # A list of filter expressions.

1074

# Object with schema name: FilterExpression

1075

],

Yoshi Automation Bot

2020-11-26 17:16:03 -0800

[diff] [blame]

1076

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

1077

"filter": { # An expression to filter dimension or metric values. # A primitive filter. All fields in filter in same FilterExpression needs to be either all dimensions or metrics.

1078

"betweenFilter": { # To express that the result needs to be between two numbers (inclusive). # A filter for two values.

1079

"fromValue": { # To represent a number. # Begins with this number.

1080

"doubleValue": 3.14, # Double value

1081

"int64Value": "A String", # Integer value

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

1082

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

1083

"toValue": { # To represent a number. # Ends with this number.

1084

"doubleValue": 3.14, # Double value

1085

"int64Value": "A String", # Integer value

Yoshi Automation Bot

2020-11-26 17:16:03 -0800

[diff] [blame]

1086

},

Yoshi Automation Bot

2020-11-26 17:16:03 -0800

[diff] [blame]

1087

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

1088

"fieldName": "A String", # The dimension name or metric name. Must be a name defined in dimensions or metrics.

1089

"inListFilter": { # The result needs to be in a list of string values. # A filter for in list values.

1090

"caseSensitive": True or False, # If true, the string value is case sensitive.

1091

"values": [ # The list of string values. Must be non-empty.

1092

"A String",

Yoshi Automation Bot

2020-11-25 07:50:41 -0800

[diff] [blame]

1093

],

1094

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

1095

"numericFilter": { # Filters for numeric or date values. # A filter for numeric or date values.

1096

"operation": "A String", # The operation type for this filter.

1097

"value": { # To represent a number. # A numeric value or a date value.

1098

"doubleValue": 3.14, # Double value

1099

"int64Value": "A String", # Integer value

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

1100

},

1101

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

1102

"stringFilter": { # The filter for string # Strings related filter.

1103

"caseSensitive": True or False, # If true, the string value is case sensitive.

1104

"matchType": "A String", # The match type for this filter.

1105

"value": "A String", # The string value used for the matching.

1106

},

1107

},

1108

"notExpression": # Object with schema name: FilterExpression # The FilterExpression is NOT of not_expression.

1109

"orGroup": { # A list of filter expressions. # The FilterExpressions in or_group have an OR relationship.

1110

"expressions": [ # A list of filter expressions.

1111

# Object with schema name: FilterExpression

],

},

},

"metrics": [ # The metrics requested and displayed.

1116

{ # The quantitative measurements of a report. For example, the metric `eventCount` is the total number of events. Requests are allowed up to 10 metrics.

1117

"expression": "A String", # A mathematical expression for derived metrics. For example, the metric Event count per user is `eventCount/totalUsers`.

1118

"invisible": True or False, # Indicates if a metric is invisible in the report response. If a metric is invisible, the metric will not produce a column in the response, but can be used in `metricFilter`, `orderBys`, or a metric `expression`.

1119

"name": "A String", # The name of the metric. See the [API Metrics](https://developers.google.com/analytics/devguides/reporting/data/v1/api-schema#metrics) for the list of metric names. If `expression` is specified, `name` can be any string that you would like. For example if `expression` is `screenPageViews/sessions`, you could call that metric's name = `viewsPerSession`. Metrics are referenced by `name` in `metricFilter`, `orderBys`, and metric `expression`.

1120

},

1121

],

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

1122

"offset": "A String", # The row count of the start row. The first row is counted as row 0.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

1123

"orderBys": [ # Specifies how rows are ordered in the response.

1124

{ # The sort options.

1125

"desc": True or False, # If true, sorts by descending order.

1126

"dimension": { # Sorts by dimension values. # Sorts results by a dimension's values.

1127

"dimensionName": "A String", # A dimension name in the request to order by.

1128

"orderType": "A String", # Controls the rule for dimension value ordering.

1129

},

1130

"metric": { # Sorts by metric values. # Sorts results by a metric's values.

1131

"metricName": "A String", # A metric name in the request to order by.

1132

},

1133

"pivot": { # Sorts by a pivot column group. # Sorts results by a metric's values within a pivot column group.

1134

"metricName": "A String", # In the response to order by, order rows by this column. Must be a metric name from the request.

1135

"pivotSelections": [ # Used to select a dimension name and value pivot. If multiple pivot selections are given, the sort occurs on rows where all pivot selection dimension name and value pairs match the row's dimension name and value pair.

1136

{ # A pair of dimension names and values. Rows with this dimension pivot pair are ordered by the metric's value. For example if pivots = {{"browser", "Chrome"}} and metric_name = "Sessions", then the rows will be sorted based on Sessions in Chrome. ---------|----------|----------------|----------|---------------- | Chrome | Chrome | Safari | Safari ---------|----------|----------------|----------|---------------- Country | Sessions | Pages/Sessions | Sessions | Pages/Sessions ---------|----------|----------------|----------|---------------- US | 2 | 2 | 3 | 1 ---------|----------|----------------|----------|---------------- Canada | 3 | 1 | 4 | 1 ---------|----------|----------------|----------|----------------

1137

"dimensionName": "A String", # Must be a dimension name from the request.

1138

"dimensionValue": "A String", # Order by only when the named dimension is this value.

},

],

},

},

],

"returnPropertyQuota": True or False, # Toggles whether to return the current state of this Analytics Property's quota. Quota is returned in [PropertyQuota](#PropertyQuota).

1145

}

Dmitry Frenkel

2020-10-06 16:46:05 -0700

[diff] [blame]

1146

1147

x__xgafv: string, V1 error format.

Allowed values

1 - v1 error format

2 - v2 error format

Returns:

An object of the form:

1154

1155

{ # The response report table corresponding to a request.

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

1156

"dimensionHeaders": [ # Describes dimension columns. The number of DimensionHeaders and ordering of DimensionHeaders matches the dimensions present in rows.

1157

{ # Describes a dimension column in the report. Dimensions requested in a report produce column entries within rows and DimensionHeaders. However, dimensions used exclusively within filters or expressions do not produce columns in a report; correspondingly, those dimensions do not produce headers.

1158

"name": "A String", # The dimension's name.

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

1159

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

1160

],

1161

"maximums": [ # If requested, the maximum values of metrics.

1162

{ # Report data for each row. For example if RunReportRequest contains: ```none "dimensions": [ { "name": "eventName" }, { "name": "countryId" } ], "metrics": [ { "name": "eventCount" } ] ``` One row with 'in_app_purchase' as the eventName, 'JP' as the countryId, and 15 as the eventCount, would be: ```none "dimensionValues": [ { "value": "in_app_purchase" }, { "value": "JP" } ], "metricValues": [ { "value": "15" } ] ```

1163

"dimensionValues": [ # List of requested dimension values. In a PivotReport, dimension_values are only listed for dimensions included in a pivot.

1164

{ # The value of a dimension.

1165

"value": "A String", # Value as a string if the dimension type is a string.

1166

},

1167

],

1168

"metricValues": [ # List of requested visible metric values.

1169

{ # The value of a metric.

1170

"value": "A String", # Measurement value. See MetricHeader for type.

1171

},

1172

],

Yoshi Automation Bot

2020-12-09 08:56:03 -0800

[diff] [blame]

1173

},

Yoshi Automation Bot

2021-01-15 07:10:04 -0800

[diff] [blame]

1174

],

1175

"metadata": { # Response's metadata carrying additional information about the report content. # Metadata for the report.

1176

"dataLossFromOtherRow": True or False, # If true, indicates some buckets of dimension combinations are rolled into "(other)" row. This can happen for high cardinality reports.

1177

},

1178

"metricHeaders": [ # Describes metric columns. The number of MetricHeaders and ordering of MetricHeaders matches the metrics present in rows.

1179

{ # Describes a metric column in the report. Visible metrics requested in a report produce column entries within rows and MetricHeaders. However, metrics used exclusively within filters or expressions do not produce columns in a report; correspondingly, those metrics do not produce headers.

1180

"name": "A String", # The metric's name.

1181

"type": "A String", # The metric's data type.

1182

},

1183

],

1184

"minimums": [ # If requested, the minimum values of metrics.

1185

{ # Report data for each row. For example if RunReportRequest contains: ```none "dimensions": [ { "name": "eventName" }, { "name": "countryId" } ], "metrics": [ { "name": "eventCount" } ] ``` One row with 'in_app_purchase' as the eventName, 'JP' as the countryId, and 15 as the eventCount, would be: ```none "dimensionValues": [ { "value": "in_app_purchase" }, { "value": "JP" } ], "metricValues": [ { "value": "15" } ] ```

1186

"dimensionValues": [ # List of requested dimension values. In a PivotReport, dimension_values are only listed for dimensions included in a pivot.

1187

{ # The value of a dimension.

1188

"value": "A String", # Value as a string if the dimension type is a string.

1189

},

1190

],

1191

"metricValues": [ # List of requested visible metric values.

1192

{ # The value of a metric.

1193

"value": "A String", # Measurement value. See MetricHeader for type.

},

],

},

],

"propertyQuota": { # Current state of all quotas for this Analytics Property. If any quota for a property is exhausted, all requests to that property will return Resource Exhausted errors. # This Analytics Property's quota state including this request.

1199

"concurrentRequests": { # Current state for a particular quota group. # Standard Analytics Properties can send up to 10 concurrent requests; Analytics 360 Properties can use up to 50 concurrent requests.

1200

"consumed": 42, # Quota consumed by this request.

1201

"remaining": 42, # Quota remaining after this request.

1202

},

1203

"serverErrorsPerProjectPerHour": { # Current state for a particular quota group. # Standard Analytics Properties and cloud project pairs can have up to 10 server errors per hour; Analytics 360 Properties and cloud project pairs can have up to 50 server errors per hour.

1204

"consumed": 42, # Quota consumed by this request.

1205

"remaining": 42, # Quota remaining after this request.

1206

},

1207

"tokensPerDay": { # Current state for a particular quota group. # Standard Analytics Properties can use up to 25,000 tokens per day; Analytics 360 Properties can use 250,000 tokens per day. Most requests consume fewer than 10 tokens.

1208

"consumed": 42, # Quota consumed by this request.

1209

"remaining": 42, # Quota remaining after this request.

1210

},

yoshi-code-bot

2021-03-02 11:49:08 -0800

[diff] [blame]

1211

"tokensPerHour": { # Current state for a particular quota group. # 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 consumes a single number of tokens, and that number is deducted from both the hourly and daily quotas.

Yoshi Automation Bot