GooglePlayDeveloperReportingV1beta1TimelineSpec

import type { GooglePlayDeveloperReportingV1beta1TimelineSpec } from "https://googleapis.deno.dev/v1/playdeveloperreporting:v1beta1.ts";

Specification of the time-related aggregation parameters of a timeline. Timelines have an aggregation period (DAILY, HOURLY, etc) which defines how events are aggregated in metrics. The points in a timeline are defined by the starting DateTime of the aggregation period. The duration is implicit in the AggregationPeriod. Hourly aggregation periods, when supported by a metric set, are always specified in UTC to avoid ambiguities around daylight saving time transitions, where an hour is skipped when adopting DST, and repeated when abandoning DST. For example, the timestamp '2021-11-07 01:00:00 America/Los_Angeles' is ambiguous since it can correspond to '2021-11-07 08:00:00 UTC' or '2021-11-07 09:00:00 UTC'. Daily aggregation periods require specifying a timezone which will determine the precise instants of the start and the end of the day. Not all metric sets support all timezones, so make sure to check which timezones are supported by the metric set you want to query.

interface GooglePlayDeveloperReportingV1beta1TimelineSpec {

aggregationPeriod?:

| "AGGREGATION_PERIOD_UNSPECIFIED"

| "HOURLY"

| "DAILY"

| "FULL_RANGE";

endTime?: GoogleTypeDateTime;

startTime?: GoogleTypeDateTime;

}

§Properties

aggregationPeriod?: "AGGREGATION_PERIOD_UNSPECIFIED" | "HOURLY" | "DAILY" | "FULL_RANGE"

[src]

Type of the aggregation period of the datapoints in the timeline. Intervals are identified by the date and time at the start of the interval.

endTime?: GoogleTypeDateTime

[src]

Ending datapoint of the timeline (exclusive). See start_time for restrictions. The timezone of the end point must match the timezone of the start point.

startTime?: GoogleTypeDateTime

[src]

Starting datapoint of the timeline (inclusive). Must be aligned to the aggregation period as follows: * HOURLY: the 'minutes', 'seconds' and 'nanos' fields must be unset. The time_zone can be left unset (defaults to UTC) or set explicitly to "UTC". Setting any other utc_offset or timezone id will result in a validation error. * DAILY: the 'hours', 'minutes', 'seconds' and 'nanos' fields must be unset. Different metric sets support different timezones. It can be left unset to use the default timezone specified by the metric set. The timezone of the end point must match the timezone of the start point.