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.

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-pivot-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. Within a batch request, this property should either be unspecified or consistent with the batch-level property. 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:

RunPivotReportRequest:
  cohort-spec:
    cohort-report-settings:
      accumulate: boolean
    cohorts-range:
      end-offset: integer
      granularity: string
      start-offset: integer
  currency-code: string
  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
  keep-empty-rows: boolean
  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
  property: 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 .cohort-spec.cohort-report-settings accumulate=true

    • If true, accumulates the result from first touch day to the end day. Not supported in RunReportRequest.

  • ..cohorts-range end-offset=77

    • 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.
  • granularity=et
    • Required. The granularity used to interpret the startOffset and endOffset for the extended reporting date range for a cohort report.

  • start-offset=25

    • 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.

  • ... currency-code=erat

    • A currency code in ISO4217 format, such as "AED", "USD", "JPY". If the field is empty, the report uses the property's default currency.
  • dimension-filter.filter.between-filter.from-value double-value=0.06730027227364666
    • Double value

  • int64-value=dolore

    • Integer value

  • ..to-value double-value=0.9694857568940014

    • Double value

  • int64-value=voluptua.

    • Integer value

  • ... field-name=amet.

    • 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=diam

    • The list of string values. Must be non-empty.
    • Each invocation of this argument appends the given value to the array.

  • ..numeric-filter operation=dolor

    • The operation type for this filter.
  • value double-value=0.9625057030686941
    • Double value

  • int64-value=et

    • Integer value

  • ...string-filter case-sensitive=false

    • If true, the string value is case sensitive.
  • match-type=stet
    • The match type for this filter.

  • value=dolor

    • The string value used for the matching.

  • .... keep-empty-rows=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. Regardless of this keep_empty_rows setting, only data recorded by the Google Analytics (GA4) property can be displayed in a report. For example if a property never logs a purchase event, then a query for the eventName dimension and eventCount metric will not have a row eventName: "purchase" and eventCount: 0.
  • metric-filter.filter.between-filter.from-value double-value=0.1970220513983837
    • Double value

  • int64-value=stet

    • Integer value

  • ..to-value double-value=0.19657477328425788

    • Double value

  • int64-value=lorem

    • Integer value

  • ... field-name=diam

    • 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=ipsum

    • The list of string values. Must be non-empty.
    • Each invocation of this argument appends the given value to the array.

  • ..numeric-filter operation=accusam

    • The operation type for this filter.
  • value double-value=0.333591971041029
    • Double value

  • int64-value=voluptua.

    • Integer value

  • ...string-filter case-sensitive=false

    • If true, the string value is case sensitive.
  • match-type=erat
    • The match type for this filter.

  • value=consetetur

    • The string value used for the matching.

  • .... property=amet.

    • 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. Within a batch request, this property should either be unspecified or consistent with the batch-level property. Example: properties/1234
  • return-property-quota=true
    • Toggles whether to return the current state of this Analytics Property's 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").