- HTTP request
- Request body
- Response body
- Authorization Scopes
- ReportRequest
- Sampling
- Dimension
- DimensionFilterClause
- FilterLogicalOperator
- DimensionFilter
- Operator
- Metric
- MetricType
- MetricFilterClause
- MetricFilter
- Operator
- OrderBy
- OrderType
- SortOrder
- Segment
- DynamicSegment
- SegmentDefinition
- SegmentFilter
- SimpleSegment
- OrFiltersForSegment
- SegmentFilterClause
- SegmentDimensionFilter
- Operator
- SegmentMetricFilter
- Scope
- Operator
- SequenceSegment
- SegmentSequenceStep
- MatchType
- Pivot
- CohortGroup
- Cohort
- Type
- Report
- ColumnHeader
- MetricHeader
- MetricHeaderEntry
- PivotHeader
- PivotHeaderEntry
- ReportData
- ReportRow
- DateRangeValues
- PivotValueRegion
- ResourceQuotasRemaining
- Try it!
Returns the Analytics data.
HTTP request
POST https://analyticsreporting.googleapis.com/v4/reports:batchGet
The URL uses gRPC Transcoding syntax.
Request body
The request body contains data with the following structure:
JSON representation | |
---|---|
{
"reportRequests": [
{
object( |
Fields | |
---|---|
reportRequests[] |
Requests, each request will have a separate response. There can be a maximum of 5 requests. All requests should have the same |
useResourceQuotas |
Enables resource based quotas, (defaults to |
Response body
If successful, the response body contains data with the following structure:
The main response class which holds the reports from the Reporting API batchGet
call.
JSON representation | |
---|---|
{ "reports": [ { object( |
Fields | |
---|---|
reports[] |
Responses corresponding to each of the request. |
queryCost |
The amount of resource quota tokens deducted to execute the query. Includes all responses. |
resourceQuotasRemaining |
The amount of resource quota remaining for the property. |
Authorization Scopes
Requires one of the following OAuth scopes:
https://www.googleapis.com/auth/analytics.readonly
https://www.googleapis.com/auth/analytics
ReportRequest
The main request class which specifies the Reporting API request.
JSON representation | |
---|---|
{ "viewId": string, "dateRanges": [ { object( |
Fields | |
---|---|
viewId |
The Analytics view ID from which to retrieve data. Every ReportRequest within a |
dateRanges[] |
Date ranges in the request. The request can have a maximum of 2 date ranges. The response will contain a set of metric values for each combination of the dimensions for each date range in the request. So, if there are two date ranges, there will be two set of metric values, one for the original date range and one for the second date range. The |
samplingLevel |
The desired report sample size. If the the |
dimensions[] |
The dimensions requested. Requests can have a total of 9 dimensions. |
dimensionFilterClauses[] |
The dimension filter clauses for filtering Dimension Values. They are logically combined with the |
metrics[] |
The metrics requested. Requests must specify at least one metric. Requests can have a total of 10 metrics. |
metricFilterClauses[] |
The metric filter clauses. They are logically combined with the |
filtersExpression |
Dimension or metric filters that restrict the data returned for your request. To use the |
orderBys[] |
Sort order on output rows. To compare two rows, the elements of the following are applied in order until a difference is found. All date ranges in the output get the same row order. |
segments[] |
Segment the data returned for the request. A segment definition helps look at a subset of the segment request. A request can contain up to four segments. Every ReportRequest within a |
pivots[] |
The pivot definitions. Requests can have a maximum of 2 pivots. |
cohortGroup |
Cohort group associated with this request. If there is a cohort group in the request the |
pageToken |
A continuation token to get the next page of the results. Adding this to the request will return the rows after the pageToken. The pageToken should be the value returned in the nextPageToken parameter in the response to the reports.batchGet request. |
pageSize |
Page size is for paging and specifies the maximum number of returned rows. Page size should be >= 0. A query returns the default of 1,000 rows. The Analytics Core Reporting API returns a maximum of 100,000 rows per request, no matter how many you ask for. It can also return fewer rows than requested, if there aren't as many dimension segments as you expect. For instance, there are fewer than 300 possible values for |
includeEmptyRows |
If set to false, the response does not include rows if all the retrieved metrics are equal to zero. The default is false which will exclude these rows. |
hideTotals |
If set to true, hides the total of all metrics for all the matching rows, for every date range. The default false and will return the totals. |
hideValueRanges |
If set to true, hides the minimum and maximum across all matching rows. The default is false and the value ranges are returned. |
Sampling
Values for the sampling level.
Enums | |
---|---|
SAMPLING_UNSPECIFIED |
If the samplingLevel field is unspecified the DEFAULT sampling level is used. |
DEFAULT |
Returns response with a sample size that balances speed and accuracy. |
SMALL |
It returns a fast response with a smaller sampling size. |
LARGE |
Returns a more accurate response using a large sampling size. But this may result in response being slower. |
Dimension
Dimensions are attributes of your data. For example, the dimension ga:city
indicates the city, for example, "Paris" or "New York", from which a session originates.
JSON representation | |
---|---|
{ "name": string, "histogramBuckets": [ string ] } |
Fields | |
---|---|
name |
Name of the dimension to fetch, for example |
histogramBuckets[] |
If non-empty, we place dimension values into buckets after string to int64. Dimension values that are not the string representation of an integral value will be converted to zero. The bucket values have to be in increasing order. Each bucket is closed on the lower end, and open on the upper end. The "first" bucket includes all values less than the first boundary, the "last" bucket includes all values up to infinity. Dimension values that fall in a bucket get transformed to a new dimension value. For example, if one gives a list of "0, 1, 3, 4, 7", then we return the following buckets:
NOTE: If you are applying histogram mutation on any dimension, and using that dimension in sort, you will want to use the sort type "<50", "1001+", "121-1000", "50-120" And the ascending "<50", "50-120", "121-1000", "1001+" The client has to explicitly request |
DimensionFilterClause
A group of dimension filters. Set the operator value to specify how the filters are logically combined.
JSON representation | |
---|---|
{ "operator": enum( |
Fields | |
---|---|
operator |
The operator for combining multiple dimension filters. If unspecified, it is treated as an |
filters[] |
The repeated set of filters. They are logically combined based on the operator specified. |
FilterLogicalOperator
How the filters are logically combined.
Enums | |
---|---|
OPERATOR_UNSPECIFIED |
Unspecified operator. It is treated as an OR . |
OR |
The logical OR operator. |
AND |
The logical AND operator. |
DimensionFilter
Dimension filter specifies the filtering options on a dimension.
JSON representation | |
---|---|
{
"dimensionName": string,
"not": boolean,
"operator": enum( |
Fields | |
---|---|
dimensionName |
The dimension to filter on. A DimensionFilter must contain a dimension. |
not |
Logical |
operator |
How to match the dimension to the expression. The default is REGEXP. |
expressions[] |
Strings or regular expression to match against. Only the first value of the list is used for comparison unless the operator is |
caseSensitive |
Should the match be case sensitive? Default is false. |
Operator
Different match types supported.
Enums | |
---|---|
OPERATOR_UNSPECIFIED |
If the match type is unspecified, it is treated as a REGEXP . |
REGEXP |
The match expression is treated as a regular expression. All match types are not treated as regular expressions. |
BEGINS_WITH |
Matches the value which begin with the match expression provided. |
ENDS_WITH |
Matches the values which end with the match expression provided. |
PARTIAL |
Substring match. |
EXACT |
The value should match the match expression entirely. |
NUMERIC_EQUAL |
Integer comparison filters. case sensitivity is ignored for these and the expression is assumed to be a string representing an integer. Failure conditions:
|
NUMERIC_GREATER_THAN |
Checks if the dimension is numerically greater than the match expression. Read the description for NUMERIC_EQUALS for restrictions. |
NUMERIC_LESS_THAN |
Checks if the dimension is numerically less than the match expression. Read the description for NUMERIC_EQUALS for restrictions. |
IN_LIST |
This option is used to specify a dimension filter whose expression can take any value from a selected list of values. This helps avoiding evaluating multiple exact match dimension filters which are OR'ed for every single response row. For example:
Any response row whose dimension has it is value as A, B or C, matches this DimensionFilter. |
Metric
Metrics are the quantitative measurements. For example, the metric ga:users
indicates the total number of users for the requested time period.
JSON representation | |
---|---|
{
"expression": string,
"alias": string,
"formattingType": enum( |
Fields | |
---|---|
expression |
A metric expression in the request. An expression is constructed from one or more metrics and numbers. Accepted operators include: Plus (+), Minus (-), Negation (Unary -), Divided by (/), Multiplied by (*), Parenthesis, Positive cardinal numbers (0-9), can include decimals and is limited to 1024 characters. Example |
alias |
An alias for the metric expression is an alternate name for the expression. The alias can be used for filtering and sorting. This field is optional and is useful if the expression is not a single metric but a complex expression which cannot be used in filtering and sorting. The alias is also used in the response column header. |
formattingType |
Specifies how the metric expression should be formatted, for example |
MetricType
The types of metrics.
Enums | |
---|---|
METRIC_TYPE_UNSPECIFIED |
Metric type is unspecified. |
INTEGER |
Integer metric. |
FLOAT |
Float metric. |
CURRENCY |
Currency metric. |
PERCENT |
Percentage metric. |
TIME |
Time metric in HH:MM:SS format. |
MetricFilterClause
Represents a group of metric filters. Set the operator value to specify how the filters are logically combined.
JSON representation | |
---|---|
{ "operator": enum( |
Fields | |
---|---|
operator |
The operator for combining multiple metric filters. If unspecified, it is treated as an |
filters[] |
The repeated set of filters. They are logically combined based on the operator specified. |
MetricFilter
MetricFilter specifies the filter on a metric.
JSON representation | |
---|---|
{
"metricName": string,
"not": boolean,
"operator": enum( |
Fields | |
---|---|
metricName |
The metric that will be filtered on. A metricFilter must contain a metric name. A metric name can be an alias earlier defined as a metric or it can also be a metric expression. |
not |
Logical |
operator |
Is the metric |
comparisonValue |
The value to compare against. |
Operator
Different comparison type options.
Enums | |
---|---|
OPERATOR_UNSPECIFIED |
If the operator is not specified, it is treated as EQUAL . |
EQUAL |
Should the value of the metric be exactly equal to the comparison value. |
LESS_THAN |
Should the value of the metric be less than to the comparison value. |
GREATER_THAN |
Should the value of the metric be greater than to the comparison value. |
IS_MISSING |
Validates if the metric is missing. Doesn't take comparisonValue into account. |
OrderBy
Specifies the sorting options.
JSON representation | |
---|---|
{ "fieldName": string, "orderType": enum( |
Fields | |
---|---|
fieldName |
The field which to sort by. The default sort order is ascending. Example: |
orderType |
The order type. The default orderType is |
sortOrder |
The sorting order for the field. |
OrderType
OrderType controls how the sort order is being determined.
Enums | |
---|---|
ORDER_TYPE_UNSPECIFIED |
Unspecified order type will be treated as sort based on value. |
VALUE |
The sort order is based on the value of the chosen column; looks only at the first date range. |
DELTA |
The sort order is based on the difference of the values of the chosen column between the first two date ranges. Usable only if there are exactly two date ranges. |
SMART |
The sort order is based on weighted value of the chosen column. If column has n/d format, then weighted value of this ratio will be (n + totals.n)/(d + totals.d) Usable only for metrics that represent ratios. |
HISTOGRAM_BUCKET |
Histogram order type is applicable only to dimension columns with non-empty histogram-buckets. |
DIMENSION_AS_INTEGER |
If the dimensions are fixed length numbers, ordinary sort would just work fine. DIMENSION_AS_INTEGER can be used if the dimensions are variable length numbers. |
SortOrder
The Sorting order of the sort.
Enums | |
---|---|
SORT_ORDER_UNSPECIFIED |
If the sort order is unspecified, the default is ascending. |
ASCENDING |
Ascending sort. The field will be sorted in an ascending manner. |
DESCENDING |
Descending sort. The field will be sorted in a descending manner. |
Segment
The segment definition, if the report needs to be segmented. A Segment is a subset of the Analytics data. For example, of the entire set of users, one Segment might be users from a particular country or city.
JSON representation | |
---|---|
{ // Union field |
Fields | ||
---|---|---|
Union field dynamicOrById . The segment can be defined dynamically using DynamicSegment or by using an ID of a built-in or custom segment. dynamicOrById can be only one of the following: |
||
dynamicSegment |
A dynamic segment definition in the request. |
|
segmentId |
The segment ID of a built-in or custom segment, for example |
DynamicSegment
Dynamic segment definition for defining the segment within the request. A segment can select users, sessions or both.
JSON representation | |
---|---|
{ "name": string, "userSegment": { object( |
Fields | |
---|---|
name |
The name of the dynamic segment. |
userSegment |
User Segment to select users to include in the segment. |
sessionSegment |
Session Segment to select sessions to include in the segment. |
SegmentDefinition
SegmentDefinition defines the segment to be a set of SegmentFilters which are combined together with a logical AND
operation.
JSON representation | |
---|---|
{
"segmentFilters": [
{
object( |
Fields | |
---|---|
segmentFilters[] |
A segment is defined by a set of segment filters which are combined together with a logical |
SegmentFilter
SegmentFilter defines the segment to be either a simple or a sequence segment. A simple segment condition contains dimension and metric conditions to select the sessions or users. A sequence segment condition can be used to select users or sessions based on sequential conditions.
JSON representation | |
---|---|
{ "not": boolean, // Union field |
Fields | ||
---|---|---|
not |
If true, match the complement of simple or sequence segment. For example, to match all visits not from "New York", we can define the segment as follows:
|
|
Union field simpleOrSequence . Is it a simple segment or a sequence segment definition. simpleOrSequence can be only one of the following: |
||
simpleSegment |
A Simple segment conditions consist of one or more dimension/metric conditions that can be combined |
|
sequenceSegment |
Sequence conditions consist of one or more steps, where each step is defined by one or more dimension/metric conditions. Multiple steps can be combined with special sequence operators. |
SimpleSegment
A Simple segment conditions consist of one or more dimension/metric conditions that can be combined.
JSON representation | |
---|---|
{
"orFiltersForSegment": [
{
object( |
Fields | |
---|---|
orFiltersForSegment[] |
A list of segment filters groups which are combined with logical |
OrFiltersForSegment
A list of segment filters in the OR
group are combined with the logical OR operator.
JSON representation | |
---|---|
{
"segmentFilterClauses": [
{
object( |
Fields | |
---|---|
segmentFilterClauses[] |
List of segment filters to be combined with a |
SegmentFilterClause
Filter Clause to be used in a segment definition, can be wither a metric or a dimension filter.
JSON representation | |
---|---|
{ "not": boolean, // Union field |
Fields | ||
---|---|---|
not |
Matches the complement ( |
|
Union field dimensionOrMetricFilter . Dimension or a metric filter. dimensionOrMetricFilter can be only one of the following: |
||
dimensionFilter |
Dimension Filter for the segment definition. |
|
metricFilter |
Metric Filter for the segment definition. |
SegmentDimensionFilter
Dimension filter specifies the filtering options on a dimension.
JSON representation | |
---|---|
{
"dimensionName": string,
"operator": enum( |
Fields | |
---|---|
dimensionName |
Name of the dimension for which the filter is being applied. |
operator |
The operator to use to match the dimension with the expressions. |
caseSensitive |
Should the match be case sensitive, ignored for |
expressions[] |
The list of expressions, only the first element is used for all operators |
minComparisonValue |
Minimum comparison values for |
maxComparisonValue |
Maximum comparison values for |
Operator
Different match types supported.
Enums | |
---|---|
OPERATOR_UNSPECIFIED |
If the match type is unspecified, it is treated as a REGEXP. |
REGEXP |
The match expression is treated as a regular expression. All other match types are not treated as regular expressions. |
BEGINS_WITH |
Matches the values which begin with the match expression provided. |
ENDS_WITH |
Matches the values which end with the match expression provided. |
PARTIAL |
Substring match. |
EXACT |
The value should match the match expression entirely. |
IN_LIST |
This option is used to specify a dimension filter whose expression can take any value from a selected list of values. This helps avoiding evaluating multiple exact match dimension filters which are OR'ed for every single response row. For example:
Any response row whose dimension has it is value as A, B or C, matches this DimensionFilter. |
NUMERIC_LESS_THAN |
Integer comparison filters. case sensitivity is ignored for these and the expression is assumed to be a string representing an integer. Failure conditions:
Checks if the dimension is numerically less than the match expression. |
NUMERIC_GREATER_THAN |
Checks if the dimension is numerically greater than the match expression. |
NUMERIC_BETWEEN |
Checks if the dimension is numerically between the minimum and maximum of the match expression, boundaries excluded. |
SegmentMetricFilter
Metric filter to be used in a segment filter clause.
JSON representation | |
---|---|
{ "scope": enum( |
Fields | |
---|---|
scope |
Scope for a metric defines the level at which that metric is defined. The specified metric scope must be equal to or greater than its primary scope as defined in the data model. The primary scope is defined by if the segment is selecting users or sessions. |
metricName |
The metric that will be filtered on. A |
operator |
Specifies is the operation to perform to compare the metric. The default is |
comparisonValue |
The value to compare against. If the operator is |
maxComparisonValue |
Max comparison value is only used for |
Scope
A scope for a metric defines the level at which that metric is defined - PRODUCT
, HIT
, SESSION
, or USER
. Metric values can also be reported at scopes greater than its primary scope. E.g., ga:pageviews
and ga:transactions
can be reported at SESSION
and USER
level by just adding them up for each hit that occurs in those sessions or for those users.
Enums | |
---|---|
UNSPECIFIED_SCOPE |
If the scope is unspecified, it defaults to the condition scope, USER or SESSION depending on if the segment is trying to choose users or sessions. |
PRODUCT |
Product scope. |
HIT |
Hit scope. |
SESSION |
Session scope. |
USER |
User scope. |
Operator
Different comparison type options.
Enums | |
---|---|
UNSPECIFIED_OPERATOR |
Unspecified operator is treated as LESS_THAN operator. |
LESS_THAN |
Checks if the metric value is less than comparison value. |
GREATER_THAN |
Checks if the metric value is greater than comparison value. |
EQUAL |
Equals operator. |
BETWEEN |
For between operator, both the minimum and maximum are exclusive. We will use LT and GT for comparison. |
SequenceSegment
Sequence conditions consist of one or more steps, where each step is defined by one or more dimension/metric conditions. Multiple steps can be combined with special sequence operators.
JSON representation | |
---|---|
{
"segmentSequenceSteps": [
{
object( |
Fields | |
---|---|
segmentSequenceSteps[] |
The list of steps in the sequence. |
firstStepShouldMatchFirstHit |
If set, first step condition must match the first hit of the visitor (in the date range). |
SegmentSequenceStep
A segment sequence definition.
JSON representation | |
---|---|
{ "orFiltersForSegment": [ { object( |
Fields | |
---|---|
orFiltersForSegment[] |
A sequence is specified with a list of Or grouped filters which are combined with |
matchType |
Specifies if the step immediately precedes or can be any time before the next step. |
MatchType
The match type for the sequence.
Enums | |
---|---|
UNSPECIFIED_MATCH_TYPE |
Unspecified match type is treated as precedes. |
PRECEDES |
Operator indicates that the previous step precedes the next step. |
IMMEDIATELY_PRECEDES |
Operator indicates that the previous step immediately precedes the next step. |
Pivot
The Pivot describes the pivot section in the request. The Pivot helps rearrange the information in the table for certain reports by pivoting your data on a second dimension.
JSON representation | |
---|---|
{ "dimensions": [ { object( |
Fields | |
---|---|
dimensions[] |
A list of dimensions to show as pivot columns. A Pivot can have a maximum of 4 dimensions. Pivot dimensions are part of the restriction on the total number of dimensions allowed in the request. |
dimensionFilterClauses[] |
DimensionFilterClauses are logically combined with an |
metrics[] |
The pivot metrics. Pivot metrics are part of the restriction on total number of metrics allowed in the request. |
startGroup |
If k metrics were requested, then the response will contain some data-dependent multiple of k columns in the report. E.g., if you pivoted on the dimension The following let you choose which of the groups of k columns are included in the response. |
maxGroupCount |
Specifies the maximum number of groups to return. The default value is 10, also the maximum value is 1,000. |
CohortGroup
Defines a cohort group. For example:
"cohortGroup": {
"cohorts": [{
"name": "cohort 1",
"type": "FIRST_VISIT_DATE",
"dateRange": { "startDate": "2015-08-01", "endDate": "2015-08-01" }
},{
"name": "cohort 2"
"type": "FIRST_VISIT_DATE"
"dateRange": { "startDate": "2015-07-01", "endDate": "2015-07-01" }
}]
}
JSON representation | |
---|---|
{
"cohorts": [
{
object( |
Fields | |
---|---|
cohorts[] |
The definition for the cohort. |
lifetimeValue |
Enable Life Time Value (LTV). LTV measures lifetime value for users acquired through different channels. Please see: Cohort Analysis and Lifetime Value If the value of lifetimeValue is false:
When the lifetimeValue is true:
|
Cohort
Defines a cohort. A cohort is a group of users who share a common characteristic. For example, all users with the same acquisition date belong to the same cohort.
JSON representation | |
---|---|
{ "name": string, "type": enum( |
Fields | |
---|---|
name |
A unique name for the cohort. If not defined name will be auto-generated with values cohort_[1234...]. |
type |
Type of the cohort. The only supported type as of now is |
dateRange |
This is used for |
Type
The cohort type.
Enums | |
---|---|
UNSPECIFIED_COHORT_TYPE |
If unspecified it's treated as FIRST_VISIT_DATE . |
FIRST_VISIT_DATE |
Cohorts that are selected based on first visit date. |
Report
The data response corresponding to the request.
JSON representation | |
---|---|
{ "columnHeader": { object( |
Fields | |
---|---|
columnHeader |
The column headers. |
data |
Response data. |
nextPageToken |
Page token to retrieve the next page of results in the list. |
ColumnHeader
Column headers.
JSON representation | |
---|---|
{
"dimensions": [
string
],
"metricHeader": {
object( |
Fields | |
---|---|
dimensions[] |
The dimension names in the response. |
metricHeader |
Metric headers for the metrics in the response. |
MetricHeader
The headers for the metrics.
JSON representation | |
---|---|
{ "metricHeaderEntries": [ { object( |
Fields | |
---|---|
metricHeaderEntries[] |
Headers for the metrics in the response. |
pivotHeaders[] |
Headers for the pivots in the response. |
MetricHeaderEntry
Header for the metrics.
JSON representation | |
---|---|
{
"name": string,
"type": enum( |
Fields | |
---|---|
name |
The name of the header. |
type |
The type of the metric, for example |
PivotHeader
The headers for each of the pivot sections defined in the request.
JSON representation | |
---|---|
{
"pivotHeaderEntries": [
{
object( |
Fields | |
---|---|
pivotHeaderEntries[] |
A single pivot section header. |
totalPivotGroupsCount |
The total number of groups for this pivot. |
PivotHeaderEntry
The headers for the each of the metric column corresponding to the metrics requested in the pivots section of the response.
JSON representation | |
---|---|
{
"dimensionNames": [
string
],
"dimensionValues": [
string
],
"metric": {
object( |
Fields | |
---|---|
dimensionNames[] |
The name of the dimensions in the pivot response. |
dimensionValues[] |
The values for the dimensions in the pivot. |
metric |
The metric header for the metric in the pivot. |
ReportData
The data part of the report.
JSON representation | |
---|---|
{ "rows": [ { object( |
Fields | |
---|---|
rows[] |
There's one ReportRow for every unique combination of dimensions. |
totals[] |
For each requested date range, for the set of all rows that match the query, every requested value format gets a total. The total for a value format is computed by first totaling the metrics mentioned in the value format and then evaluating the value format as a scalar expression. E.g., The "totals" for |
rowCount |
Total number of matching rows for this query. |
minimums[] |
Minimum and maximum values seen over all matching rows. These are both empty when |
maximums[] |
Minimum and maximum values seen over all matching rows. These are both empty when |
samplesReadCounts[] |
If the results are sampled, this returns the total number of samples read, one entry per date range. If the results are not sampled this field will not be defined. See developer guide for details. |
samplingSpaceSizes[] |
If the results are sampled, this returns the total number of samples present, one entry per date range. If the results are not sampled this field will not be defined. See developer guide for details. |
isDataGolden |
Indicates if response to this request is golden or not. Data is golden when the exact same request will not produce any new results if asked at a later point in time. |
dataLastRefreshed |
The last time the data in the report was refreshed. All the hits received before this timestamp are included in the calculation of the report. A timestamp in RFC3339 UTC "Zulu" format, accurate to nanoseconds. Example: |
ReportRow
A row in the report.
JSON representation | |
---|---|
{
"dimensions": [
string
],
"metrics": [
{
object( |
Fields | |
---|---|
dimensions[] |
List of requested dimensions. |
metrics[] |
List of metrics for each requested DateRange. |
DateRangeValues
Used to return a list of metrics for a single DateRange / dimension combination
JSON representation | |
---|---|
{
"values": [
string
],
"pivotValueRegions": [
{
object( |
Fields | |
---|---|
values[] |
Each value corresponds to each Metric in the request. |
pivotValueRegions[] |
The values of each pivot region. |
PivotValueRegion
The metric values in the pivot region.
JSON representation | |
---|---|
{ "values": [ string ] } |
Fields | |
---|---|
values[] |
The values of the metrics in each of the pivot regions. |
ResourceQuotasRemaining
The resource quota tokens remaining for the property after the request is completed.
JSON representation | |
---|---|
{ "dailyQuotaTokensRemaining": number, "hourlyQuotaTokensRemaining": number } |
Fields | |
---|---|
dailyQuotaTokensRemaining |
Daily resource quota remaining remaining. |
hourlyQuotaTokensRemaining |
Hourly resource quota tokens remaining. |