Package-level declarations
Types
An intended audience of the Product for whom it's sold.
The color information of a Product.
Query terms that we want to match on.
Metadata that is used to define a condition that triggers an action. A valid condition must specify at least one of 'query_terms' or 'products_filter'. If multiple fields are specified, the condition is met if all the fields are satisfied e.g. if a set of query terms and product_filter are set, then only items matching the product_filter for requests with a query matching the query terms wil get boosted.
Used for time-dependent conditions. Example: Want to have rule applied for week long sale.
Fulfillment information, such as the store IDs for in-store pickup or region IDs for different shipping methods.
Product image. Recommendations AI and Retail Search do not use product images to improve prediction and search results. However, product images can be returned in results, and are shown in prediction or search previews in the console.
A floating point interval.
The inventory information at a place (e.g. a store) identified by a place ID.
Additional configs for the frequently-bought-together model type.
Additional model features config.
A candidate to consider for a given panel. Currently only ServingConfig are valid candidates.
An individual panel with a list of ServingConfigs to consider for it.
The PageOptimizationConfig for model training. This determines how many panels to optimize for, and which serving configs to consider for each panel. The purpose of this model is to optimize which ServingConfig to show on which panels in way that optimizes the visitors shopping journey.
Represents an ordered combination of valid serving configs, which can be used for PAGE_OPTIMIZATION
recommendations.
The price range of all variant Product having the same Product.primary_product_id.
The price information of a Product.
Product captures all metadata information of items to be recommended or searched.
Promotion specification.
The rating of a Product.
A boost action to apply to results matching condition specified above.
Prevents a term in the query from being used in search. Example: Don't search for "shoddy".
Maps a set of terms to a set of synonyms. Set of synonyms will be treated as synonyms of each query term only. query_terms
will not be treated as synonyms of each other. Example: "sneakers" will use a synonym of "shoes". "shoes" will not use a synonym of "sneakers".
Redirects a shopper to a specific page. * Rule Condition: - Must specify Condition.query_terms. * Action Input: Request Query * Action Result: Redirects shopper to provided uri.
Replaces a term in the query. Multiple replacement candidates can be specified. All query_terms
will be replaced with the replacement term. Example: Replace "gShoe" with "google shoe".
A rule is a condition-action pair * A condition defines when a rule is to be triggered. * An action specifies what occurs on that trigger. Currently rules only work for controls with SOLUTION_TYPE_SEARCH.
Creates a set of terms that will be treated as synonyms of each other. Example: synonyms of "sneakers" and "shoes": * "sneakers" will use a synonym of "shoes". * "shoes" will use a synonym of "sneakers".
The specifications of dynamically generated facets.
Specifies how a facet is computed.
A facet specification to perform faceted search.
The specification for personalization.