---
title: "POST /v2/{+catalog}:exportAnalyticsMetrics"
method: POST
path: "/v2/{+catalog}:exportAnalyticsMetrics"
tags: ["projects"]
---

# POST /v2/{+catalog}:exportAnalyticsMetrics

`POST /v2/{+catalog}:exportAnalyticsMetrics`

Exports analytics metrics. `Operation.response` is of type `ExportAnalyticsMetricsResponse`. `Operation.metadata` is of type `ExportMetadata`.

## Path parameters

- `catalog` string, required

## Request body

- GoogleCloudRetailV2ExportAnalyticsMetricsRequest — Request message for the `ExportAnalyticsMetrics` method.
  - `outputConfig` GoogleCloudRetailV2OutputConfig — The output configuration setting.
    - `bigqueryDestination` GoogleCloudRetailV2OutputConfigBigQueryDestination — The BigQuery output destination configuration.
      - `datasetId` string — Required. The ID of a BigQuery Dataset.
      - `tableType` string — Required. Describes the table type. The following values are supported: * `table`: A BigQuery native table. * `view`: A virtual table defined by a SQL query.
      - `tableIdPrefix` string — Required. The prefix of exported BigQuery tables.
    - `gcsDestination` GoogleCloudRetailV2OutputConfigGcsDestination — The Google Cloud Storage output destination configuration.
      - `outputUriPrefix` string — Required. The output uri prefix for saving output data to json files. Some mapping examples are as follows: output_uri_prefix sample output(assuming the object is foo.json) ======================== ============================================= gs://bucket/ gs://bucket/foo.json gs://bucket/folder/ gs://bucket/folder/foo.json gs://bucket/folder/item_ gs://bucket/folder/item_foo.json
  - `filter` string — A filtering expression to specify restrictions on returned metrics. The expression is a sequence of terms. Each term applies a restriction to the returned metrics. Use this expression to restrict results to a specific time range. Currently we expect only one types of fields: * `timestamp`: This can be specified twice, once with a less than operator and once with a greater than operator. The `timestamp` restriction should result in one, contiguous, valid, `timestamp` range. Some examples of valid filters expressions: * Example 1: `timestamp > "2012-04-23T18:25:43.511Z" timestamp < "2012-04-23T18:30:43.511Z"` * Example 2: `timestamp > "2012-04-23T18:25:43.511Z"`

## Response `200`

Successful response

---

[API](https://skmtc.net/google/apis/retail.md) · [All operations](https://skmtc.net/google/apis/retail/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/google/retail/versions/146c67e59640/schema)