You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/dyn/retail_v2alpha.projects.locations.catalogs.placements.html
+8-1Lines changed: 8 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -167,7 +167,7 @@ <h3>Method Details</h3>
167
167
"followupQuestion": { # The conversational followup question generated for Intent refinement. # The conversational filtering question.
168
168
"followupQuestion": "A String", # The conversational followup question generated for Intent refinement.
169
169
"suggestedAnswers": [ # The answer options provided to client for the follow-up question.
170
-
{ # Suggested answers to the follow-up question.
170
+
{ # Suggested answers to the follow-up question. If it's numerical attribute, only ProductAttributeInterval will be set. If it's textual attribute, only productAttributeValue will be set.
171
171
"productAttributeValue": { # Product attribute which structured by an attribute name and value. This structure is used in conversational search filters and answers. For example, if we have `name=color` and `value=red`, this means that the color is `red`. # Product attribute value, including an attribute key and an attribute value. Other types can be added here in the future.
172
172
"name": "A String", # The attribute name.
173
173
"value": "A String", # The attribute value.
@@ -578,6 +578,13 @@ <h3>Method Details</h3>
578
578
],
579
579
"tileNavigationRequested": True or False, # This field specifies whether the customer would like to request tile navigation.
580
580
},
581
+
"userAttributes": { # Optional. The user attributes that could be used for personalization of search results. * Populate at most 100 key-value pairs per query. * Only supports string keys and repeated string values. * Duplcate keys are not allowed within a single query. Example: user_attributes: [ { key: "pets" value { values: "dog" values: "cat" } }, { key: "state" value { values: "CA" } } ]
582
+
"a_key": { # A list of string values.
583
+
"values": [ # String values.
584
+
"A String",
585
+
],
586
+
},
587
+
},
581
588
"userInfo": { # Information of an end user. # User information.
582
589
"directUserRequest": True or False, # True if the request is made directly from the end user, in which case the ip_address and user_agent can be populated from the HTTP request. This flag should be set only if the API request is made directly from the end user such as a mobile app (and not if a gateway or a server is processing and pushing the user events). This should not be set when using the JavaScript tag in UserEventService.CollectUserEvent.
583
590
"ipAddress": "A String", # The end user's IP address. This field is used to extract location information for personalization. This field must be either an IPv4 address (e.g. "104.133.9.80") or an IPv6 address (e.g. "2001:0db8:85a3:0000:0000:8a2e:0370:7334"). Otherwise, an INVALID_ARGUMENT error is returned. This should not be set when: * setting SearchRequest.user_info. * using the JavaScript tag in UserEventService.CollectUserEvent or if direct_user_request is set.
Copy file name to clipboardExpand all lines: docs/dyn/retail_v2alpha.projects.locations.catalogs.servingConfigs.html
+8-1Lines changed: 8 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -260,7 +260,7 @@ <h3>Method Details</h3>
260
260
"followupQuestion": { # The conversational followup question generated for Intent refinement. # The conversational filtering question.
261
261
"followupQuestion": "A String", # The conversational followup question generated for Intent refinement.
262
262
"suggestedAnswers": [ # The answer options provided to client for the follow-up question.
263
-
{ # Suggested answers to the follow-up question.
263
+
{ # Suggested answers to the follow-up question. If it's numerical attribute, only ProductAttributeInterval will be set. If it's textual attribute, only productAttributeValue will be set.
264
264
"productAttributeValue": { # Product attribute which structured by an attribute name and value. This structure is used in conversational search filters and answers. For example, if we have `name=color` and `value=red`, this means that the color is `red`. # Product attribute value, including an attribute key and an attribute value. Other types can be added here in the future.
265
265
"name": "A String", # The attribute name.
266
266
"value": "A String", # The attribute value.
@@ -1129,6 +1129,13 @@ <h3>Method Details</h3>
1129
1129
],
1130
1130
"tileNavigationRequested": True or False, # This field specifies whether the customer would like to request tile navigation.
1131
1131
},
1132
+
"userAttributes": { # Optional. The user attributes that could be used for personalization of search results. * Populate at most 100 key-value pairs per query. * Only supports string keys and repeated string values. * Duplcate keys are not allowed within a single query. Example: user_attributes: [ { key: "pets" value { values: "dog" values: "cat" } }, { key: "state" value { values: "CA" } } ]
1133
+
"a_key": { # A list of string values.
1134
+
"values": [ # String values.
1135
+
"A String",
1136
+
],
1137
+
},
1138
+
},
1132
1139
"userInfo": { # Information of an end user. # User information.
1133
1140
"directUserRequest": True or False, # True if the request is made directly from the end user, in which case the ip_address and user_agent can be populated from the HTTP request. This flag should be set only if the API request is made directly from the end user such as a mobile app (and not if a gateway or a server is processing and pushing the user events). This should not be set when using the JavaScript tag in UserEventService.CollectUserEvent.
1134
1141
"ipAddress": "A String", # The end user's IP address. This field is used to extract location information for personalization. This field must be either an IPv4 address (e.g. "104.133.9.80") or an IPv6 address (e.g. "2001:0db8:85a3:0000:0000:8a2e:0370:7334"). Otherwise, an INVALID_ARGUMENT error is returned. This should not be set when: * setting SearchRequest.user_info. * using the JavaScript tag in UserEventService.CollectUserEvent or if direct_user_request is set.
"description": "Suggested answers to the follow-up question.",
4746
+
"description": "Suggested answers to the follow-up question. If it's numerical attribute, only ProductAttributeInterval will be set. If it's textual attribute, only productAttributeValue will be set.",
"description": "Optional. This field specifies tile navigation related parameters."
7415
7415
},
7416
+
"userAttributes": {
7417
+
"additionalProperties": {
7418
+
"$ref": "GoogleCloudRetailV2alphaStringList"
7419
+
},
7420
+
"description": "Optional. The user attributes that could be used for personalization of search results. * Populate at most 100 key-value pairs per query. * Only supports string keys and repeated string values. * Duplcate keys are not allowed within a single query. Example: user_attributes: [ { key: \"pets\" value { values: \"dog\" values: \"cat\" } }, { key: \"state\" value { values: \"CA\" } } ]",
7421
+
"type": "object"
7422
+
},
7416
7423
"userInfo": {
7417
7424
"$ref": "GoogleCloudRetailV2alphaUserInfo",
7418
7425
"description": "User information."
@@ -8169,6 +8176,20 @@
8169
8176
"properties": {},
8170
8177
"type": "object"
8171
8178
},
8179
+
"GoogleCloudRetailV2alphaStringList": {
8180
+
"description": "A list of string values.",
8181
+
"id": "GoogleCloudRetailV2alphaStringList",
8182
+
"properties": {
8183
+
"values": {
8184
+
"description": "String values.",
8185
+
"items": {
8186
+
"type": "string"
8187
+
},
8188
+
"type": "array"
8189
+
}
8190
+
},
8191
+
"type": "object"
8192
+
},
8172
8193
"GoogleCloudRetailV2alphaTile": {
8173
8194
"description": "This field specifies the tile information including an attribute key, attribute value. More fields will be added in the future, eg: product id or product counts, etc.",
0 commit comments