Recombee API Client
Public Member Functions | Properties | List of all members
Recombee.ApiClient.ApiRequests.RecommendUsersToUser Class Reference

Recommend users to user More...

Inheritance diagram for Recombee.ApiClient.ApiRequests.RecommendUsersToUser:
Inheritance graph
[legend]
Collaboration diagram for Recombee.ApiClient.ApiRequests.RecommendUsersToUser:
Collaboration graph
[legend]

Public Member Functions

 RecommendUsersToUser (string userId, long count, string scenario=null, bool? cascadeCreate=null, bool? returnProperties=null, string[] includedProperties=null, string filter=null, string booster=null, Logic logic=null, double? diversity=null, string minRelevance=null, double? rotationRate=null, double? rotationTime=null, Dictionary< string, object > expertSettings=null, bool? returnAbGroup=null)
 Construct the request More...
 
override string Path ()
 
Returns
URI to the endpoint including path parameters
More...
 
override Dictionary< string, object > QueryParameters ()
 Get query parameters More...
 
override Dictionary< string, object > BodyParameters ()
 Get body parameters More...
 
- Public Member Functions inherited from Recombee.ApiClient.ApiRequests.Request
 Request (HttpMethod httpMethod, int timeoutMilliseconds, bool ensureHttps=false)
 Construct the request More...
 

Properties

string UserId [get]
 User to whom we find similar users More...
 
long Count [get]
 Number of users to be recommended (N for the top-N recommendation). More...
 
string Scenario [get]
 Scenario defines a particular application of recommendations. It can be for example "homepage", "cart" or "emailing". You can set various settings to the scenario in the Admin UI. You can also see performance of each scenario in the Admin UI separately, so you can check how well each application performs. The AI which optimizes models in order to get the best results may optimize different scenarios separately, or even use different models in each of the scenarios. More...
 
bool? CascadeCreate [get]
 If the user does not exist in the database, returns a list of non-personalized recommendations and creates the user in the database. This allows for example rotations in the following recommendations for that user, as the user will be already known to the system. More...
 
bool? ReturnProperties [get]
 With returnProperties=true, property values of the recommended users are returned along with their IDs in a JSON dictionary. The acquired property values can be used for easy displaying the recommended users. Example response: More...
 
string[] IncludedProperties [get]
 Allows to specify, which properties should be returned when returnProperties=true is set. The properties are given as a comma-separated list. Example response for includedProperties=country: More...
 
string Filter [get]
 Boolean-returning ReQL expression which allows you to filter recommended items based on the values of their attributes. Filters can be also assigned to a scenario in the Admin UI. More...
 
string Booster [get]
 Number-returning ReQL expression which allows you to boost recommendation rate of some items based on the values of their attributes. Boosters can be also assigned to a scenario in the Admin UI. More...
 
Logic Logic [get]
 Logic specifies particular behavior of the recommendation models. You can pick tailored logic for your domain and use case. See this section for list of available logics and other details. The difference between logic and scenario is that logic specifies mainly behavior, while scenario specifies the place where recommendations are shown to the users. Logic can be also set to a scenario in the Admin UI. More...
 
double? Diversity [get]
 **Expert option** Real number from [0.0, 1.0] which determines how much mutually dissimilar should the recommended users be. The default value is 0.0, i.e., no diversification. Value 1.0 means maximal diversification. More...
 
string MinRelevance [get]
 **Expert option** Specifies the threshold of how much relevant must the recommended users be. Possible values one of: "low", "medium", "high". More...
 
double? RotationRate [get]
 **Expert option** If your users browse the system in real-time, it may easily happen that you wish to offer them recommendations multiple times. Here comes the question: how much should the recommendations change? Should they remain the same, or should they rotate? Recombee API allows you to control this per-request in backward fashion. You may penalize an user for being recommended in the near past. For the specific user, rotationRate=1 means maximal rotation, rotationRate=0 means absolutely no rotation. You may also use, for example rotationRate=0.2 for only slight rotation of recommended users. More...
 
double? RotationTime [get]
 **Expert option** Taking rotationRate into account, specifies how long time it takes to an user to recover from the penalization. For example, rotationTime=7200.0 means that users recommended less than 2 hours ago are penalized. More...
 
Dictionary< string, object > ExpertSettings [get]
 Dictionary of custom options. More...
 
bool? ReturnAbGroup [get]
 If there is a custom AB-testing running, return name of group to which the request belongs. More...
 
- Properties inherited from Recombee.ApiClient.ApiRequests.Request
TimeSpan Timeout [get, set]
 Timeout for the request in milliseconds More...
 
bool EnsureHttps [get]
 If true, HTTPS must be chosen over HTTP for this request More...
 
HttpMethod RequestHttpMehod [get]
 Used HTTP method More...
 

Additional Inherited Members

- Protected Member Functions inherited from Recombee.ApiClient.ApiRequests.Request
double ConvertToUnixTimestamp (DateTime date)
 
Returns
Converts DateTime to UNIX timestamp (epoch)
More...
 

Detailed Description

Recommend users to user

Get similar users as some given user, based on the user's past interactions (purchases, ratings, etc.) and values of properties. It is also possible to use POST HTTP method (for example in case of very long ReQL filter) - query parameters then become body parameters. The returned users are sorted by similarity (first user being the most similar).

Constructor & Destructor Documentation

◆ RecommendUsersToUser()

Recombee.ApiClient.ApiRequests.RecommendUsersToUser.RecommendUsersToUser ( string  userId,
long  count,
string  scenario = null,
bool?  cascadeCreate = null,
bool?  returnProperties = null,
string[]  includedProperties = null,
string  filter = null,
string  booster = null,
Logic  logic = null,
double?  diversity = null,
string  minRelevance = null,
double?  rotationRate = null,
double?  rotationTime = null,
Dictionary< string, object >  expertSettings = null,
bool?  returnAbGroup = null 
)
inline

Construct the request

Parameters
userIdUser to whom we find similar users
countNumber of users to be recommended (N for the top-N recommendation).
scenarioScenario defines a particular application of recommendations. It can be for example "homepage", "cart" or "emailing". You can set various settings to the scenario in the Admin UI. You can also see performance of each scenario in the Admin UI separately, so you can check how well each application performs. The AI which optimizes models in order to get the best results may optimize different scenarios separately, or even use different models in each of the scenarios.
cascadeCreateIf the user does not exist in the database, returns a list of non-personalized recommendations and creates the user in the database. This allows for example rotations in the following recommendations for that user, as the user will be already known to the system.
returnPropertiesWith returnProperties=true, property values of the recommended users are returned along with their IDs in a JSON dictionary. The acquired property values can be used for easy displaying the recommended users. Example response:
{
"recommId": "9cb9c55d-50ba-4478-84fd-ab456136156e",
"recomms":
[
{
"id": "user-17",
"values": {
"country": "US",
"sex": "F"
}
},
{
"id": "user-2",
"values": {
"country": "CAN",
"sex": "M"
}
}
],
"numberNextRecommsCalls": 0
}
Parameters
includedPropertiesAllows to specify, which properties should be returned when returnProperties=true is set. The properties are given as a comma-separated list. Example response for includedProperties=country:
{
"recommId": "b326d82d-5d57-4b45-b362-c9d6f0895855",
"recomms":
[
{
"id": "user-17",
"values": {
"country": "US"
}
},
{
"id": "user-2",
"values": {
"country": "CAN"
}
}
],
"numberNextRecommsCalls": 0
}
Parameters
filterBoolean-returning ReQL expression which allows you to filter recommended items based on the values of their attributes. Filters can be also assigned to a scenario in the Admin UI.
boosterNumber-returning ReQL expression which allows you to boost recommendation rate of some items based on the values of their attributes. Boosters can be also assigned to a scenario in the Admin UI.
logicLogic specifies particular behavior of the recommendation models. You can pick tailored logic for your domain and use case. See this section for list of available logics and other details. The difference between logic and scenario is that logic specifies mainly behavior, while scenario specifies the place where recommendations are shown to the users. Logic can be also set to a scenario in the Admin UI.
diversity**Expert option** Real number from [0.0, 1.0] which determines how much mutually dissimilar should the recommended users be. The default value is 0.0, i.e., no diversification. Value 1.0 means maximal diversification.
minRelevance**Expert option** Specifies the threshold of how much relevant must the recommended users be. Possible values one of: "low", "medium", "high".
rotationRate**Expert option** If your users browse the system in real-time, it may easily happen that you wish to offer them recommendations multiple times. Here comes the question: how much should the recommendations change? Should they remain the same, or should they rotate? Recombee API allows you to control this per-request in backward fashion. You may penalize an user for being recommended in the near past. For the specific user, rotationRate=1 means maximal rotation, rotationRate=0 means absolutely no rotation. You may also use, for example rotationRate=0.2 for only slight rotation of recommended users.
rotationTime**Expert option** Taking rotationRate into account, specifies how long time it takes to an user to recover from the penalization. For example, rotationTime=7200.0 means that users recommended less than 2 hours ago are penalized.
expertSettingsDictionary of custom options.
returnAbGroupIf there is a custom AB-testing running, return name of group to which the request belongs.

Member Function Documentation

◆ BodyParameters()

override Dictionary<string, object> Recombee.ApiClient.ApiRequests.RecommendUsersToUser.BodyParameters ( )
inlinevirtual

Get body parameters

Returns
Dictionary containing values of body parameters (name of parameter: value of the parameter)

Implements Recombee.ApiClient.ApiRequests.Request.

◆ Path()

override string Recombee.ApiClient.ApiRequests.RecommendUsersToUser.Path ( )
inlinevirtual

Returns
URI to the endpoint including path parameters

Implements Recombee.ApiClient.ApiRequests.Request.

◆ QueryParameters()

override Dictionary<string, object> Recombee.ApiClient.ApiRequests.RecommendUsersToUser.QueryParameters ( )
inlinevirtual

Get query parameters

Returns
Dictionary containing values of query parameters (name of parameter: value of the parameter)

Implements Recombee.ApiClient.ApiRequests.Request.

Property Documentation

◆ Booster

string Recombee.ApiClient.ApiRequests.RecommendUsersToUser.Booster
get

Number-returning ReQL expression which allows you to boost recommendation rate of some items based on the values of their attributes. Boosters can be also assigned to a scenario in the Admin UI.

◆ CascadeCreate

bool? Recombee.ApiClient.ApiRequests.RecommendUsersToUser.CascadeCreate
get

If the user does not exist in the database, returns a list of non-personalized recommendations and creates the user in the database. This allows for example rotations in the following recommendations for that user, as the user will be already known to the system.

◆ Count

long Recombee.ApiClient.ApiRequests.RecommendUsersToUser.Count
get

Number of users to be recommended (N for the top-N recommendation).

◆ Diversity

double? Recombee.ApiClient.ApiRequests.RecommendUsersToUser.Diversity
get

**Expert option** Real number from [0.0, 1.0] which determines how much mutually dissimilar should the recommended users be. The default value is 0.0, i.e., no diversification. Value 1.0 means maximal diversification.

◆ ExpertSettings

Dictionary<string, object> Recombee.ApiClient.ApiRequests.RecommendUsersToUser.ExpertSettings
get

Dictionary of custom options.

◆ Filter

string Recombee.ApiClient.ApiRequests.RecommendUsersToUser.Filter
get

Boolean-returning ReQL expression which allows you to filter recommended items based on the values of their attributes. Filters can be also assigned to a scenario in the Admin UI.

◆ IncludedProperties

string [] Recombee.ApiClient.ApiRequests.RecommendUsersToUser.IncludedProperties
get

Allows to specify, which properties should be returned when returnProperties=true is set. The properties are given as a comma-separated list. Example response for includedProperties=country:

{
"recommId": "b326d82d-5d57-4b45-b362-c9d6f0895855",
"recomms":
[
{
"id": "user-17",
"values": {
"country": "US"
}
},
{
"id": "user-2",
"values": {
"country": "CAN"
}
}
],
"numberNextRecommsCalls": 0
}

◆ Logic

Logic Recombee.ApiClient.ApiRequests.RecommendUsersToUser.Logic
get

Logic specifies particular behavior of the recommendation models. You can pick tailored logic for your domain and use case. See this section for list of available logics and other details. The difference between logic and scenario is that logic specifies mainly behavior, while scenario specifies the place where recommendations are shown to the users. Logic can be also set to a scenario in the Admin UI.

◆ MinRelevance

string Recombee.ApiClient.ApiRequests.RecommendUsersToUser.MinRelevance
get

**Expert option** Specifies the threshold of how much relevant must the recommended users be. Possible values one of: "low", "medium", "high".

◆ ReturnAbGroup

bool? Recombee.ApiClient.ApiRequests.RecommendUsersToUser.ReturnAbGroup
get

If there is a custom AB-testing running, return name of group to which the request belongs.

◆ ReturnProperties

bool? Recombee.ApiClient.ApiRequests.RecommendUsersToUser.ReturnProperties
get

With returnProperties=true, property values of the recommended users are returned along with their IDs in a JSON dictionary. The acquired property values can be used for easy displaying the recommended users. Example response:

{
"recommId": "9cb9c55d-50ba-4478-84fd-ab456136156e",
"recomms":
[
{
"id": "user-17",
"values": {
"country": "US",
"sex": "F"
}
},
{
"id": "user-2",
"values": {
"country": "CAN",
"sex": "M"
}
}
],
"numberNextRecommsCalls": 0
}

◆ RotationRate

double? Recombee.ApiClient.ApiRequests.RecommendUsersToUser.RotationRate
get

**Expert option** If your users browse the system in real-time, it may easily happen that you wish to offer them recommendations multiple times. Here comes the question: how much should the recommendations change? Should they remain the same, or should they rotate? Recombee API allows you to control this per-request in backward fashion. You may penalize an user for being recommended in the near past. For the specific user, rotationRate=1 means maximal rotation, rotationRate=0 means absolutely no rotation. You may also use, for example rotationRate=0.2 for only slight rotation of recommended users.

◆ RotationTime

double? Recombee.ApiClient.ApiRequests.RecommendUsersToUser.RotationTime
get

**Expert option** Taking rotationRate into account, specifies how long time it takes to an user to recover from the penalization. For example, rotationTime=7200.0 means that users recommended less than 2 hours ago are penalized.

◆ Scenario

string Recombee.ApiClient.ApiRequests.RecommendUsersToUser.Scenario
get

Scenario defines a particular application of recommendations. It can be for example "homepage", "cart" or "emailing". You can set various settings to the scenario in the Admin UI. You can also see performance of each scenario in the Admin UI separately, so you can check how well each application performs. The AI which optimizes models in order to get the best results may optimize different scenarios separately, or even use different models in each of the scenarios.

◆ UserId

string Recombee.ApiClient.ApiRequests.RecommendUsersToUser.UserId
get

User to whom we find similar users


The documentation for this class was generated from the following file: