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
POST https://discoveryengine.googleapis.com/v1alpha/{parent=projects/*/locations/*/collections/*/dataStores/*}/userEvents:import
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
parent |
Required. Parent DataStore resource name, of the form |
Request body
The request body contains data with the following structure:
JSON representation |
---|
{ "errorConfig": { object ( |
Fields | |
---|---|
error |
The desired location of errors incurred during the Import. Cannot be set for inline user event imports. |
Union field source . Required - The desired input source of the user event data. source can be only one of the following: |
|
inline |
The Inline source for the input content for UserEvents. |
gcs |
Cloud Storage location for the input content. |
bigquery |
BigQuery input source. |
Response body
If successful, the response body contains an instance of Operation
.
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/cloud-platform
For more information, see the Authentication Overview.
IAM Permissions
Requires the following IAM permission on the parent
resource:
discoveryengine.userEvents.import
For more information, see the IAM documentation.