Copyright | (c) 2013-2021 Brendan Hay |
---|---|
License | Mozilla Public License, v. 2.0. |
Maintainer | Brendan Hay <brendan.g.hay+amazonka@gmail.com> |
Stability | auto-generated |
Portability | non-portable (GHC extensions) |
Safe Haskell | None |
Synopsis
- data Event = Event' {}
- newEvent :: Text -> UTCTime -> Event
- event_recommendationId :: Lens' Event (Maybe Text)
- event_eventValue :: Lens' Event (Maybe Double)
- event_itemId :: Lens' Event (Maybe Text)
- event_impression :: Lens' Event (Maybe (NonEmpty Text))
- event_eventId :: Lens' Event (Maybe Text)
- event_properties :: Lens' Event (Maybe Text)
- event_eventType :: Lens' Event Text
- event_sentAt :: Lens' Event UTCTime
Documentation
Represents user interaction event information sent using the PutEvents
API.
See: newEvent
smart constructor.
Event' | |
|
Instances
Create a value of Event
with all optional fields omitted.
Use generic-lens or optics to modify other optional fields.
The following record fields are available, with the corresponding lenses provided for backwards compatibility:
$sel:recommendationId:Event'
, event_recommendationId
- The ID of the recommendation.
$sel:eventValue:Event'
, event_eventValue
- The event value that corresponds to the EVENT_VALUE
field of the
Interactions schema.
$sel:itemId:Event'
, event_itemId
- The item ID key that corresponds to the ITEM_ID
field of the
Interactions schema.
$sel:impression:Event'
, event_impression
- A list of item IDs that represents the sequence of items you have shown
the user. For example, ["itemId1", "itemId2", "itemId3"]
.
$sel:eventId:Event'
, event_eventId
- An ID associated with the event. If an event ID is not provided, Amazon
Personalize generates a unique ID for the event. An event ID is not used
as an input to the model. Amazon Personalize uses the event ID to
distinquish unique events. Any subsequent events after the first with
the same event ID are not used in model training.
$sel:properties:Event'
, event_properties
- 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
(itemId
) and rating (eventValue
) , you might also send the number of
movie ratings made by the user.
Each item in the map consists of a key-value pair. For example,
{"numberOfRatings": "12"}
The keys use camel case names that match the fields in the Interactions
schema. In the above example, the numberOfRatings
would match the
'NUMBER_OF_RATINGS' field defined in the Interactions schema.
$sel:eventType:Event'
, event_eventType
- The type of event, such as click or download. This property corresponds
to the EVENT_TYPE
field of your Interactions schema and depends on the
types of events you are tracking.
$sel:sentAt:Event'
, event_sentAt
- The timestamp (in Unix time) on the client side when the event occurred.
event_eventValue :: Lens' Event (Maybe Double) Source #
The event value that corresponds to the EVENT_VALUE
field of the
Interactions schema.
event_itemId :: Lens' Event (Maybe Text) Source #
The item ID key that corresponds to the ITEM_ID
field of the
Interactions schema.
event_impression :: Lens' Event (Maybe (NonEmpty Text)) Source #
A list of item IDs that represents the sequence of items you have shown
the user. For example, ["itemId1", "itemId2", "itemId3"]
.
event_eventId :: Lens' Event (Maybe Text) Source #
An ID associated with the event. If an event ID is not provided, Amazon Personalize generates a unique ID for the event. An event ID is not used as an input to the model. Amazon Personalize uses the event ID to distinquish unique events. Any subsequent events after the first with the same event ID are not used in model training.
event_properties :: Lens' Event (Maybe Text) Source #
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
(itemId
) and rating (eventValue
) , you might also send the number of
movie ratings made by the user.
Each item in the map consists of a key-value pair. For example,
{"numberOfRatings": "12"}
The keys use camel case names that match the fields in the Interactions
schema. In the above example, the numberOfRatings
would match the
'NUMBER_OF_RATINGS' field defined in the Interactions schema.