Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

Pivot

import type { Pivot } from "https://googleapis.deno.dev/v1/analyticsdata:v1beta.ts";

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

interface Pivot {
fieldNames?: string[];
limit?: bigint;
metricAggregations?:
| "METRIC_AGGREGATION_UNSPECIFIED"
| "TOTAL"
| "MINIMUM"
| "MAXIMUM"
| "COUNT"[];
offset?: bigint;
orderBys?: OrderBy[];
}

§Properties

§
fieldNames?: string[]
[src]

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.

§
limit?: bigint
[src]

The number of unique combinations of dimension values to return in this pivot. The limit parameter is required. A limit of 10,000 is common for single pivot requests. The product of the limit for each pivot in a RunPivotReportRequest must not exceed 250,000. For example, a two pivot request with limit: 1000 in each pivot will fail because the product is 1,000,000.

§
metricAggregations?: "METRIC_AGGREGATION_UNSPECIFIED" | "TOTAL" | "MINIMUM" | "MAXIMUM" | "COUNT"[]
[src]

Aggregate the metrics by dimensions in this pivot using the specified metric_aggregations.

§
offset?: bigint
[src]

The row count of the start row. The first row is counted as row 0.

§
orderBys?: OrderBy[]
[src]

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.