#[non_exhaustive]pub struct UserEvent {Show 21 fields
pub event_type: String,
pub visitor_id: String,
pub session_id: String,
pub event_time: Option<Timestamp>,
pub experiment_ids: Vec<String>,
pub attribution_token: String,
pub product_details: Vec<ProductDetail>,
pub completion_detail: Option<CompletionDetail>,
pub attributes: HashMap<String, CustomAttribute>,
pub cart_id: String,
pub purchase_transaction: Option<PurchaseTransaction>,
pub search_query: String,
pub filter: String,
pub order_by: String,
pub offset: i32,
pub page_categories: Vec<String>,
pub user_info: Option<UserInfo>,
pub uri: String,
pub referrer_uri: String,
pub page_view_id: String,
pub entity: String,
/* private fields */
}Expand description
UserEvent captures all metadata information Retail API needs to know about how end users interact with customers’ website.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.event_type: StringRequired. User event type. Allowed values are:
add-to-cart: Products being added to cart.remove-from-cart: Products being removed from cart.category-page-view: Special pages such as sale or promotion pages viewed.detail-page-view: Products detail page viewed.home-page-view: Homepage viewed.purchase-complete: User finishing a purchase.search: Product search.shopping-cart-page-view: User viewing a shopping cart.
visitor_id: StringRequired. A unique identifier for tracking visitors.
For example, this could be implemented with an HTTP cookie, which should be able to uniquely identify a visitor on a single device. This unique identifier should not change if the visitor log in/out of the website.
Don’t set the field to the same fixed ID for different users. This mixes the event history of those users together, which results in degraded model quality.
The field must be a UTF-8 encoded string with a length limit of 128 characters. Otherwise, an INVALID_ARGUMENT error is returned.
The field should not contain PII or user-data. We recommend to use Google Analytics Client ID for this field.
session_id: StringA unique identifier for tracking a visitor session with a length limit of 128 bytes. A session is an aggregation of an end user behavior in a time span.
A general guideline to populate the session_id:
- If user has no activity for 30 min, a new session_id should be assigned.
- The session_id should be unique across users, suggest use uuid or add visitor_id as prefix.
event_time: Option<Timestamp>Only required for UserEventService.ImportUserEvents method. Timestamp of when the user event happened.
experiment_ids: Vec<String>A list of identifiers for the independent experiment groups this user event belongs to. This is used to distinguish between user events associated with different experiment setups (e.g. using Retail API, using different recommendation models).
attribution_token: StringHighly recommended for user events that are the result of PredictionService.Predict. This field enables accurate attribution of recommendation model performance.
The value must be a valid PredictResponse.attribution_token for user events that are the result of PredictionService.Predict. The value must be a valid SearchResponse.attribution_token for user events that are the result of SearchService.Search.
This token enables us to accurately attribute page view or purchase back to the event and the particular predict response containing this clicked/purchased product. If user clicks on product K in the recommendation results, pass PredictResponse.attribution_token as a URL parameter to product K’s page. When recording events on product K’s page, log the PredictResponse.attribution_token to this field.
product_details: Vec<ProductDetail>The main product details related to the event.
This field is optional except for the following event types:
add-to-cartdetail-page-viewpurchase-complete
In a search event, this field represents the products returned to the end
user on the current page (the end user may have not finished browsing the
whole page yet). When a new page is returned to the end user, after
pagination/filtering/ordering even for the same query, a new search event
with different
product_details is
desired. The end user may have not finished browsing the whole page yet.
completion_detail: Option<CompletionDetail>The main auto-completion details related to the event.
This field should be set for search event when autocomplete function is
enabled and the user clicks a suggestion for search.
attributes: HashMap<String, CustomAttribute>Extra user event features to include in the recommendation model.
If you provide custom attributes for ingested user events, also include them in the user events that you associate with prediction requests. Custom attribute formatting must be consistent between imported events and events provided with prediction requests. This lets the Retail API use those custom attributes when training models and serving predictions, which helps improve recommendation quality.
This field needs to pass all below criteria, otherwise an INVALID_ARGUMENT error is returned:
- The key must be a UTF-8 encoded string with a length limit of 5,000 characters.
- For text attributes, at most 400 values are allowed. Empty values are not allowed. Each value must be a UTF-8 encoded string with a length limit of 256 characters.
- For number attributes, at most 400 values are allowed.
For product recommendations, an example of extra user information is traffic_channel, which is how a user arrives at the site. Users can arrive at the site by coming to the site directly, coming through Google search, or in other ways.
cart_id: StringThe ID or name of the associated shopping cart. This ID is used to associate multiple items added or present in the cart before purchase.
This can only be set for add-to-cart, purchase-complete, or
shopping-cart-page-view events.
purchase_transaction: Option<PurchaseTransaction>A transaction represents the entire purchase transaction.
Required for purchase-complete events. Other event types should not set
this field. Otherwise, an INVALID_ARGUMENT error is returned.
search_query: StringThe user’s search query.
See SearchRequest.query for definition.
The value must be a UTF-8 encoded string with a length limit of 5,000 characters. Otherwise, an INVALID_ARGUMENT error is returned.
At least one of
search_query or
page_categories is
required for search events. Other event types should not set this field.
Otherwise, an INVALID_ARGUMENT error is returned.
filter: StringThe filter syntax consists of an expression language for constructing a predicate from one or more fields of the products being filtered.
See SearchRequest.filter for definition and syntax.
The value must be a UTF-8 encoded string with a length limit of 1,000 characters. Otherwise, an INVALID_ARGUMENT error is returned.
order_by: StringThe order in which products are returned.
See SearchRequest.order_by for definition and syntax.
The value must be a UTF-8 encoded string with a length limit of 1,000 characters. Otherwise, an INVALID_ARGUMENT error is returned.
This can only be set for search events. Other event types should not set
this field. Otherwise, an INVALID_ARGUMENT error is returned.
offset: i32An integer that specifies the current offset for pagination (the 0-indexed starting location, amongst the products deemed by the API as relevant).
See SearchRequest.offset for definition.
If this field is negative, an INVALID_ARGUMENT is returned.
This can only be set for search events. Other event types should not set
this field. Otherwise, an INVALID_ARGUMENT error is returned.
page_categories: Vec<String>The categories associated with a category page.
To represent full path of category, use ‘>’ sign to separate different hierarchies. If ‘>’ is part of the category name, replace it with other character(s).
Category pages include special pages such as sales or promotions. For instance, a special sale page may have the category hierarchy: “pageCategories” : [“Sales > 2017 Black Friday Deals”].
Required for category-page-view events. At least one of
search_query or
page_categories is
required for search events. Other event types should not set this field.
Otherwise, an INVALID_ARGUMENT error is returned.
user_info: Option<UserInfo>User information.
uri: StringComplete URL (window.location.href) of the user’s current page.
When using the client side event reporting with JavaScript pixel and Google Tag Manager, this value is filled in automatically. Maximum length 5,000 characters.
referrer_uri: StringThe referrer URL of the current page.
When using the client side event reporting with JavaScript pixel and Google Tag Manager, this value is filled in automatically.
page_view_id: StringA unique ID of a web page view.
This should be kept the same for all user events triggered from the same
pageview. For example, an item detail page view could trigger multiple
events as the user is browsing the page. The pageViewId property should
be kept the same for all these events so that they can be grouped together
properly.
When using the client side event reporting with JavaScript pixel and Google Tag Manager, this value is filled in automatically.
entity: StringThe entity for customers that may run multiple different entities, domains,
sites or regions, for example, Google US, Google Ads, Waymo,
google.com, youtube.com, etc.
We recommend that you set this field to get better per-entity search,
completion, and prediction results.
Implementations§
Source§impl UserEvent
impl UserEvent
pub fn new() -> Self
Sourcepub fn set_event_type<T: Into<String>>(self, v: T) -> Self
pub fn set_event_type<T: Into<String>>(self, v: T) -> Self
Sourcepub fn set_visitor_id<T: Into<String>>(self, v: T) -> Self
pub fn set_visitor_id<T: Into<String>>(self, v: T) -> Self
Sourcepub fn set_session_id<T: Into<String>>(self, v: T) -> Self
pub fn set_session_id<T: Into<String>>(self, v: T) -> Self
Sourcepub fn set_event_time<T>(self, v: T) -> Self
pub fn set_event_time<T>(self, v: T) -> Self
Sets the value of event_time.
§Example
use wkt::Timestamp;
let x = UserEvent::new().set_event_time(Timestamp::default()/* use setters */);Sourcepub fn set_or_clear_event_time<T>(self, v: Option<T>) -> Self
pub fn set_or_clear_event_time<T>(self, v: Option<T>) -> Self
Sets or clears the value of event_time.
§Example
use wkt::Timestamp;
let x = UserEvent::new().set_or_clear_event_time(Some(Timestamp::default()/* use setters */));
let x = UserEvent::new().set_or_clear_event_time(None::<Timestamp>);Sourcepub fn set_experiment_ids<T, V>(self, v: T) -> Self
pub fn set_experiment_ids<T, V>(self, v: T) -> Self
Sets the value of experiment_ids.
§Example
let x = UserEvent::new().set_experiment_ids(["a", "b", "c"]);Sourcepub fn set_attribution_token<T: Into<String>>(self, v: T) -> Self
pub fn set_attribution_token<T: Into<String>>(self, v: T) -> Self
Sets the value of attribution_token.
§Example
let x = UserEvent::new().set_attribution_token("example");Sourcepub fn set_product_details<T, V>(self, v: T) -> Self
pub fn set_product_details<T, V>(self, v: T) -> Self
Sets the value of product_details.
§Example
use google_cloud_retail_v2::model::ProductDetail;
let x = UserEvent::new()
.set_product_details([
ProductDetail::default()/* use setters */,
ProductDetail::default()/* use (different) setters */,
]);Sourcepub fn set_completion_detail<T>(self, v: T) -> Selfwhere
T: Into<CompletionDetail>,
pub fn set_completion_detail<T>(self, v: T) -> Selfwhere
T: Into<CompletionDetail>,
Sets the value of completion_detail.
§Example
use google_cloud_retail_v2::model::CompletionDetail;
let x = UserEvent::new().set_completion_detail(CompletionDetail::default()/* use setters */);Sourcepub fn set_or_clear_completion_detail<T>(self, v: Option<T>) -> Selfwhere
T: Into<CompletionDetail>,
pub fn set_or_clear_completion_detail<T>(self, v: Option<T>) -> Selfwhere
T: Into<CompletionDetail>,
Sets or clears the value of completion_detail.
§Example
use google_cloud_retail_v2::model::CompletionDetail;
let x = UserEvent::new().set_or_clear_completion_detail(Some(CompletionDetail::default()/* use setters */));
let x = UserEvent::new().set_or_clear_completion_detail(None::<CompletionDetail>);Sourcepub fn set_attributes<T, K, V>(self, v: T) -> Self
pub fn set_attributes<T, K, V>(self, v: T) -> Self
Sets the value of attributes.
§Example
use google_cloud_retail_v2::model::CustomAttribute;
let x = UserEvent::new().set_attributes([
("key0", CustomAttribute::default()/* use setters */),
("key1", CustomAttribute::default()/* use (different) setters */),
]);Sourcepub fn set_cart_id<T: Into<String>>(self, v: T) -> Self
pub fn set_cart_id<T: Into<String>>(self, v: T) -> Self
Sourcepub fn set_purchase_transaction<T>(self, v: T) -> Selfwhere
T: Into<PurchaseTransaction>,
pub fn set_purchase_transaction<T>(self, v: T) -> Selfwhere
T: Into<PurchaseTransaction>,
Sets the value of purchase_transaction.
§Example
use google_cloud_retail_v2::model::PurchaseTransaction;
let x = UserEvent::new().set_purchase_transaction(PurchaseTransaction::default()/* use setters */);Sourcepub fn set_or_clear_purchase_transaction<T>(self, v: Option<T>) -> Selfwhere
T: Into<PurchaseTransaction>,
pub fn set_or_clear_purchase_transaction<T>(self, v: Option<T>) -> Selfwhere
T: Into<PurchaseTransaction>,
Sets or clears the value of purchase_transaction.
§Example
use google_cloud_retail_v2::model::PurchaseTransaction;
let x = UserEvent::new().set_or_clear_purchase_transaction(Some(PurchaseTransaction::default()/* use setters */));
let x = UserEvent::new().set_or_clear_purchase_transaction(None::<PurchaseTransaction>);Sourcepub fn set_search_query<T: Into<String>>(self, v: T) -> Self
pub fn set_search_query<T: Into<String>>(self, v: T) -> Self
Sourcepub fn set_filter<T: Into<String>>(self, v: T) -> Self
pub fn set_filter<T: Into<String>>(self, v: T) -> Self
Sourcepub fn set_order_by<T: Into<String>>(self, v: T) -> Self
pub fn set_order_by<T: Into<String>>(self, v: T) -> Self
Sourcepub fn set_offset<T: Into<i32>>(self, v: T) -> Self
pub fn set_offset<T: Into<i32>>(self, v: T) -> Self
Sourcepub fn set_page_categories<T, V>(self, v: T) -> Self
pub fn set_page_categories<T, V>(self, v: T) -> Self
Sets the value of page_categories.
§Example
let x = UserEvent::new().set_page_categories(["a", "b", "c"]);