Method: projects.locations.catalogs.eventStores.userEvents.import

Bulk import of User events. Request processing might be synchronous. Events that already exist are skipped. Use this method for backfilling historical user events.

Operation.response is of type ImportResponse. Note that it is possible for a subset of the items to be successfully inserted. Operation.metadata is of type ImportMetadata.

HTTP request


The URL uses gRPC Transcoding syntax.

Path parameters



Required. projects/1234/locations/global/catalogs/default_catalog/eventStores/default_event_store

Authorization requires the following IAM permission on the specified resource parent:


Request body

The request body contains data with the following structure:

JSON representation
  "requestId": string,
  "inputConfig": {
    object (InputConfig)
  "errorsConfig": {
    object (ImportErrorsConfig)


Optional. Unique identifier provided by client, within the ancestor dataset scope. Ensures idempotency for expensive long running operations. Server-generated if unspecified. Up to 128 characters long. This is returned as in the response. Note that this field must not be set if the desired input config is catalogInlineSource.


object (InputConfig)

Required. The desired input location of the data.


object (ImportErrorsConfig)

Optional. The desired location of errors incurred during the Import.

Response body

If successful, the response body contains an instance of Operation.

Authorization Scopes

Requires the following OAuth scope:


For more information, see the Authentication Overview.