This is one of several requests that demonstrates how Rovi can generate personalized entertainment recommendations for your customers. To understand this feature, we suggest working with these calls in this order:
|This Request . . .||Demonstrates . . .|
How an item taste profile gets added to a user taste profile.
What an item taste profile looks like.
What a user taste profile looks like.
How personalized recommendations are generated from a user taste profile.
ProfileVector returns the taste profile of a user as derived from past user events. A taste profile consists of normalized scores of Rovi entertainment categories, listed in order of highest to lowest score. The categories come from the taste profiles of items the user has acted on, and the scores depend on what action was taken. A user taste profile contains the basis for personalized recommendations, as shown in the ForYou request.
Note: You won't see the results of this call in an actual implementation of our personalized recommendations. This call and ItemVector give you an inside look at how our personalization engine works.
|apikey||Yes||Access code that authorizes your request for data from Rovi.|
|endpoint||Yes|| One of the following databases:
Note: The same results are available for each endpoint.
|sig||Yes|| A calculated authorization code. To perform the calculation, execute the MD5 function on the concatenation of the following three strings:
Perform the calculation at the time of each request to be sure it's within a five-minute window of the server time. If you're testing the call in a browser, use our online signature generator to perform the calculation.
|userid||Yes||ID of the user.|
|size||No||Number of categories to return. Default is 20.|
|controlSet||ControlSet||The HTTP response status.|
|id||string||Server transaction ID for the response.|
|results||result [ ]||Taste profile of the user requested.|