v1

latestOpenAPI 3.0.0Creative Commons Attribution 3.02026-07-13175378.4 KB
projects

Deletes permanently all user events specified by the filter provided. Depending on the number of events specified by the filter, this operation could take hours or days to complete. To test a filter, use the list command first.

post/v1beta1/{+parent}/userEvents:purge

Path parameters

parentstring required

Required. The resource name of the event_store under which the events are created. The format is projects/${projectId}/locations/global/catalogs/${catalogId}/eventStores/${eventStoreId}

Request body

forceboolean

Optional. The default value is false. Override this flag to true to actually perform the purge. If the field is not set to true, a sampling of events to be deleted will be returned.

filterstring

Required. The filter string to specify the events to be deleted. Empty string filter is not allowed. The eligible fields for filtering are: * eventType: UserEvent.eventType field of type string. * eventTime: in ISO 8601 "zulu" format. * visitorId: field of type string. Specifying this will delete all events associated with a visitor. * userId: field of type string. Specifying this will delete all events associated with a user. Examples: * Deleting all events in a time range: eventTime > "2012-04-23T18:25:43.511Z" eventTime < "2012-04-23T18:30:43.511Z" * Deleting specific eventType in time range: eventTime > "2012-04-23T18:25:43.511Z" eventType = "detail-page-view" * Deleting all events for a specific visitor: visitorId = "visitor1024" The filtering fields are assumed to have an implicit AND.

Response

Successful response