Returns a customized report of realtime event data for your property. Events appear in realtime reports seconds after they have been sent to the Google Analytics. Realtime reports show events and usage data for the periods of time ranging from the present moment to 30 minutes ago (up to 60 minutes for Google Analytics 360 properties). For a guide to constructing realtime requests & understanding responses, see Creating a Realtime Report.

Scopes

You will need authorization for at least one of the following scopes to make a valid call:

https://www.googleapis.com/auth/analytics
https://www.googleapis.com/auth/analytics.readonly

If unset, the scope for this method defaults to https://www.googleapis.com/auth/analytics. You can set the scope for this method like this: analyticsdata1-beta --scope <scope> properties run-realtime-report ...

Required Scalar Argument

<property> (string)
- A Google Analytics GA4 property identifier whose events are tracked. Specified in the URL path and not the body. To learn more, see where to find your Property ID. Example: properties/1234

Required Request Value

The request value is a data-structure with various fields. Each field may be a simple scalar or another data-structure. In the latter case it is advised to set the field-cursor to the data-structure's field to specify values more concisely.

For example, a structure like this:

RunRealtimeReportRequest:
  dimension-filter:
    filter:
      between-filter:
        from-value:
          double-value: number
          int64-value: string
        to-value:
          double-value: number
          int64-value: string
      field-name: string
      in-list-filter:
        case-sensitive: boolean
        values: [string]
      numeric-filter:
        operation: string
        value:
          double-value: number
          int64-value: string
      string-filter:
        case-sensitive: boolean
        match-type: string
        value: string
  limit: string
  metric-aggregations: [string]
  metric-filter:
    filter:
      between-filter:
        from-value:
          double-value: number
          int64-value: string
        to-value:
          double-value: number
          int64-value: string
      field-name: string
      in-list-filter:
        case-sensitive: boolean
        values: [string]
      numeric-filter:
        operation: string
        value:
          double-value: number
          int64-value: string
      string-filter:
        case-sensitive: boolean
        match-type: string
        value: string
  return-property-quota: boolean

can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.

-r .dimension-filter.filter.between-filter.from-value double-value=0.8484298131719972
- Double value
int64-value=et
- Integer value
..to-value double-value=0.611403219211556
- Double value
int64-value=voluptua.
- Integer value
... field-name=dolore
- The dimension name or metric name. In most methods, dimensions & metrics can be used for the first time in this field. However in a RunPivotReportRequest, this field must be additionally specified by name in the RunPivotReportRequest's dimensions or metrics.
in-list-filter case-sensitive=false
- If true, the string value is case sensitive.
values=amet.
- The list of string values. Must be non-empty.
- Each invocation of this argument appends the given value to the array.
..numeric-filter operation=ea
- The operation type for this filter.
value double-value=0.05043422241780038
- Double value
int64-value=invidunt
- Integer value
...string-filter case-sensitive=true
- If true, the string value is case sensitive.
match-type=sit
- The match type for this filter.
value=et
- The string value used for the matching.
.... limit=tempor
- The number of rows to return. If unspecified, 10,000 rows are returned. The API returns a maximum of 250,000 rows per request, no matter how many you ask for. limit must be positive. The API can also return fewer rows than the requested limit, if there aren't as many dimension values as the limit. For instance, there are fewer than 300 possible values for the dimension country, so when reporting on only country, you can't get more than 300 rows, even if you set limit to a higher value.
metric-aggregations=aliquyam
- Aggregation of metrics. Aggregated metric values will be shown in rows where the dimension_values are set to "RESERVED_(MetricAggregation)".
- Each invocation of this argument appends the given value to the array.
metric-filter.filter.between-filter.from-value double-value=0.7521809909805838
- Double value
int64-value=sanctus
- Integer value
..to-value double-value=0.9329847794220517
- Double value
int64-value=est
- Integer value
... field-name=sed
- The dimension name or metric name. In most methods, dimensions & metrics can be used for the first time in this field. However in a RunPivotReportRequest, this field must be additionally specified by name in the RunPivotReportRequest's dimensions or metrics.
in-list-filter case-sensitive=true
- If true, the string value is case sensitive.
values=et
- The list of string values. Must be non-empty.
- Each invocation of this argument appends the given value to the array.
..numeric-filter operation=sed
- The operation type for this filter.
value double-value=0.7087562540955133
- Double value
int64-value=elitr
- Integer value
...string-filter case-sensitive=false
- If true, the string value is case sensitive.
match-type=no
- The match type for this filter.
value=nonumy
- The string value used for the matching.
.... return-property-quota=false
- Toggles whether to return the current state of this Analytics Property's Realtime quota. Quota is returned in PropertyQuota.

About Cursors

The cursor position is key to comfortably set complex nested structures. The following rules apply:

The cursor position is always set relative to the current one, unless the field name starts with the . character. Fields can be nested such as in -r f.s.o .
The cursor position is set relative to the top-level structure if it starts with ., e.g. -r .s.s
You can also set nested fields without setting the cursor explicitly. For example, to set a value relative to the current cursor position, you would specify -r struct.sub_struct=bar.
You can move the cursor one level up by using ... Each additional . moves it up one additional level. E.g. ... would go three levels up.

Optional Output Flags

The method's return value a JSON encoded structure, which will be written to standard output by default.

-o out
- out specifies the destination to which to write the server's result to. It will be a JSON-encoded structure. The destination may be - to indicate standard output, or a filepath that is to contain the received bytes. If unset, it defaults to standard output.

Optional General Properties

The following properties can configure any call, and are not specific to this method.

-p $-xgafv=string
- V1 error format.
-p access-token=string
- OAuth access token.
-p alt=string
- Data format for response.
-p callback=string
- JSONP
-p fields=string
- Selector specifying which fields to include in a partial response.
-p key=string
- API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.
-p oauth-token=string
- OAuth 2.0 token for the current user.
-p pretty-print=boolean
- Returns response with indentations and line breaks.
-p quota-user=string
- Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.
-p upload-type=string
- Legacy upload protocol for media (e.g. "media", "multipart").
-p upload-protocol=string
- Upload protocol for media (e.g. "raw", "multipart").