|
22 | 22 | "errors":[
|
23 | 23 | {"shape":"InvalidInputException"}
|
24 | 24 | ],
|
25 |
| - "documentation":"<p>Records user interaction event data.</p>" |
| 25 | + "documentation":"<p>Records user interaction event data. For more information see <a>event-record-api</a>.</p>" |
26 | 26 | }
|
27 | 27 | },
|
28 | 28 | "shapes":{
|
|
32 | 32 | "type":"structure",
|
33 | 33 | "required":[
|
34 | 34 | "eventType",
|
35 |
| - "properties", |
36 | 35 | "sentAt"
|
37 | 36 | ],
|
38 | 37 | "members":{
|
|
44 | 43 | "shape":"StringType",
|
45 | 44 | "documentation":"<p>The type of event. This property corresponds to the <code>EVENT_TYPE</code> field of the Interactions schema.</p>"
|
46 | 45 | },
|
| 46 | + "eventValue":{ |
| 47 | + "shape":"FloatType", |
| 48 | + "documentation":"<p>The event value that corresponds to the <code>EVENT_VALUE</code> field of the Interactions schema.</p>" |
| 49 | + }, |
| 50 | + "itemId":{ |
| 51 | + "shape":"ItemId", |
| 52 | + "documentation":"<p>The item ID key that corresponds to the <code>ITEM_ID</code> field of the Interactions schema.</p>" |
| 53 | + }, |
47 | 54 | "properties":{
|
48 | 55 | "shape":"EventPropertiesJSON",
|
49 |
| - "documentation":"<p>A string map of event-specific data that you might choose to record. For example, if a user rates a movie on your site, you might send the movie ID and rating, and the number of movie ratings made by the user.</p> <p>Each item in the map consists of a key-value pair. For example,</p> <p> <code>{\"itemId\": \"movie1\"}</code> </p> <p> <code>{\"itemId\": \"movie2\", \"eventValue\": \"4.5\"}</code> </p> <p> <code>{\"itemId\": \"movie3\", \"eventValue\": \"3\", \"numberOfRatings\": \"12\"}</code> </p> <p>The keys use camel case names that match the fields in the Interactions schema. The <code>itemId</code> and <code>eventValue</code> keys correspond to the <code>ITEM_ID</code> and <code>EVENT_VALUE</code> fields. In the above example, the <code>eventType</code> might be 'MovieRating' with <code>eventValue</code> being the rating. The <code>numberOfRatings</code> would match the 'NUMBER_OF_RATINGS' field defined in the Interactions schema.</p>", |
| 56 | + "documentation":"<p>A string map of event-specific data that you might choose to record. For example, if a user rates a movie on your site, other than movie ID (<code>itemId</code>) and rating (<code>eventValue</code>) , you might also send the number of movie ratings made by the user.</p> <p>Each item in the map consists of a key-value pair. For example,</p> <p> <code>{\"numberOfRatings\": \"12\"}</code> </p> <p>The keys use camel case names that match the fields in the Interactions schema. In the above example, the <code>numberOfRatings</code> would match the 'NUMBER_OF_RATINGS' field defined in the Interactions schema.</p>", |
50 | 57 | "jsonvalue":true
|
51 | 58 | },
|
52 | 59 | "sentAt":{
|
53 | 60 | "shape":"Date",
|
54 |
| - "documentation":"<p>The timestamp on the client side when the event occurred.</p>" |
| 61 | + "documentation":"<p>The timestamp (in Unix time) on the client side when the event occurred.</p>" |
| 62 | + }, |
| 63 | + "recommendationId":{ |
| 64 | + "shape":"RecommendationId", |
| 65 | + "documentation":"<p>The ID of the recommendation.</p>" |
| 66 | + }, |
| 67 | + "impression":{ |
| 68 | + "shape":"Impression", |
| 69 | + "documentation":"<p>A list of item IDs that represents the sequence of items you have shown the user. For example, <code>[\"itemId1\", \"itemId2\", \"itemId3\"]</code>.</p>" |
55 | 70 | }
|
56 | 71 | },
|
57 | 72 | "documentation":"<p>Represents user interaction event information sent using the <code>PutEvents</code> API.</p>"
|
|
67 | 82 | "max":1024,
|
68 | 83 | "min":1
|
69 | 84 | },
|
| 85 | + "FloatType":{"type":"float"}, |
| 86 | + "Impression":{ |
| 87 | + "type":"list", |
| 88 | + "member":{"shape":"ItemId"}, |
| 89 | + "max":25, |
| 90 | + "min":1 |
| 91 | + }, |
70 | 92 | "InvalidInputException":{
|
71 | 93 | "type":"structure",
|
72 | 94 | "members":{
|
|
76 | 98 | "error":{"httpStatusCode":400},
|
77 | 99 | "exception":true
|
78 | 100 | },
|
| 101 | + "ItemId":{ |
| 102 | + "type":"string", |
| 103 | + "max":256, |
| 104 | + "min":1 |
| 105 | + }, |
79 | 106 | "PutEventsRequest":{
|
80 | 107 | "type":"structure",
|
81 | 108 | "required":[
|
|
94 | 121 | },
|
95 | 122 | "sessionId":{
|
96 | 123 | "shape":"StringType",
|
97 |
| - "documentation":"<p>The session ID associated with the user's visit.</p>" |
| 124 | + "documentation":"<p>The session ID associated with the user's visit. Your application generates the sessionId when a user first visits your website or uses your application. Amazon Personalize uses the sessionId to associate events with the user before they log in. For more information see <a>event-record-api</a>.</p>" |
98 | 125 | },
|
99 | 126 | "eventList":{
|
100 | 127 | "shape":"EventList",
|
101 | 128 | "documentation":"<p>A list of event data from the session.</p>"
|
102 | 129 | }
|
103 | 130 | }
|
104 | 131 | },
|
| 132 | + "RecommendationId":{ |
| 133 | + "type":"string", |
| 134 | + "max":40, |
| 135 | + "min":1 |
| 136 | + }, |
105 | 137 | "StringType":{
|
106 | 138 | "type":"string",
|
107 | 139 | "max":256,
|
|
113 | 145 | "min":1
|
114 | 146 | }
|
115 | 147 | },
|
116 |
| - "documentation":"<p/>" |
| 148 | + "documentation":"<p>Amazon Personalize can consume real-time user event data, such as <i>stream</i> or <i>click</i> data, and use it for model training either alone or combined with historical data. For more information see <a>recording-events</a>.</p>" |
117 | 149 | }
|
0 commit comments