Skip to content

Commit 89c5147

Browse files
author
AWS
committed
Amazon Personalize Events Update: Adds support implicit and explicit impression input
1 parent 8f9c2a2 commit 89c5147

File tree

2 files changed

+43
-6
lines changed

2 files changed

+43
-6
lines changed
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
{
2+
"type": "feature",
3+
"category": "Amazon Personalize Events",
4+
"description": "Adds support implicit and explicit impression input"
5+
}

services/personalizeevents/src/main/resources/codegen-resources/service-2.json

Lines changed: 38 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@
2222
"errors":[
2323
{"shape":"InvalidInputException"}
2424
],
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>"
2626
}
2727
},
2828
"shapes":{
@@ -32,7 +32,6 @@
3232
"type":"structure",
3333
"required":[
3434
"eventType",
35-
"properties",
3635
"sentAt"
3736
],
3837
"members":{
@@ -44,14 +43,30 @@
4443
"shape":"StringType",
4544
"documentation":"<p>The type of event. This property corresponds to the <code>EVENT_TYPE</code> field of the Interactions schema.</p>"
4645
},
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+
},
4754
"properties":{
4855
"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>",
5057
"jsonvalue":true
5158
},
5259
"sentAt":{
5360
"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>"
5570
}
5671
},
5772
"documentation":"<p>Represents user interaction event information sent using the <code>PutEvents</code> API.</p>"
@@ -67,6 +82,13 @@
6782
"max":1024,
6883
"min":1
6984
},
85+
"FloatType":{"type":"float"},
86+
"Impression":{
87+
"type":"list",
88+
"member":{"shape":"ItemId"},
89+
"max":25,
90+
"min":1
91+
},
7092
"InvalidInputException":{
7193
"type":"structure",
7294
"members":{
@@ -76,6 +98,11 @@
7698
"error":{"httpStatusCode":400},
7799
"exception":true
78100
},
101+
"ItemId":{
102+
"type":"string",
103+
"max":256,
104+
"min":1
105+
},
79106
"PutEventsRequest":{
80107
"type":"structure",
81108
"required":[
@@ -94,14 +121,19 @@
94121
},
95122
"sessionId":{
96123
"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>"
98125
},
99126
"eventList":{
100127
"shape":"EventList",
101128
"documentation":"<p>A list of event data from the session.</p>"
102129
}
103130
}
104131
},
132+
"RecommendationId":{
133+
"type":"string",
134+
"max":40,
135+
"min":1
136+
},
105137
"StringType":{
106138
"type":"string",
107139
"max":256,
@@ -113,5 +145,5 @@
113145
"min":1
114146
}
115147
},
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>"
117149
}

0 commit comments

Comments
 (0)