user_events
Creates, updates, deletes, gets or lists a user_events
resource.
Overview
Name | user_events |
Type | Resource |
Id | google.discoveryengine.user_events |
Fields
SELECT
not supported for this resource, use SHOW METHODS
to view available operations for the resource.
Methods
Name | Accessible by | Required Params | Description |
---|---|---|---|
projects_locations_collections_data_stores_user_events_collect | EXEC | collectionsId, dataStoresId, locationsId, projectsId | Writes a single user event from the browser. This uses a GET request to due to browser restriction of POST-ing to a third-party domain. This method is used only by the Discovery Engine API JavaScript pixel and Google Tag Manager. Users should not call this method directly. |
projects_locations_collections_data_stores_user_events_import | EXEC | collectionsId, dataStoresId, locationsId, projectsId | 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. |
projects_locations_collections_data_stores_user_events_purge | EXEC | collectionsId, dataStoresId, locationsId, projectsId | 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. |
projects_locations_collections_data_stores_user_events_write | EXEC | collectionsId, dataStoresId, locationsId, projectsId | Writes a single user event. |
projects_locations_data_stores_user_events_collect | EXEC | dataStoresId, locationsId, projectsId | Writes a single user event from the browser. This uses a GET request to due to browser restriction of POST-ing to a third-party domain. This method is used only by the Discovery Engine API JavaScript pixel and Google Tag Manager. Users should not call this method directly. |
projects_locations_data_stores_user_events_import | EXEC | dataStoresId, locationsId, projectsId | 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. |
projects_locations_data_stores_user_events_purge | EXEC | dataStoresId, locationsId, projectsId | 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. |
projects_locations_data_stores_user_events_write | EXEC | dataStoresId, locationsId, projectsId | Writes a single user event. |
projects_locations_user_events_collect | EXEC | locationsId, projectsId | Writes a single user event from the browser. This uses a GET request to due to browser restriction of POST-ing to a third-party domain. This method is used only by the Discovery Engine API JavaScript pixel and Google Tag Manager. Users should not call this method directly. |
projects_locations_user_events_write | EXEC | locationsId, projectsId | Writes a single user event. |