RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://docs.aws.amazon.com/sdkforruby/api/Aws/PersonalizeEvents/Types/Event.html below:

Event — AWS SDK for Ruby V2

You are viewing documentation for version 2 of the AWS SDK for Ruby. Version 3 documentation can be found here.

Class: Aws::PersonalizeEvents::Types::Event

Inherits:

Struct

Object
Struct
Aws::PersonalizeEvents::Types::Event

show all

Defined in:: (unknown)

Overview Note:

When passing Event as input to an Aws::Client method, you can use a vanilla Hash:

{
  event_id: "StringType",
  event_type: "StringType",   event_value: 1.0,
  item_id: "ItemId",
  properties: "EventPropertiesJSON",
  sent_at: Time.now,   recommendation_id: "RecommendationId",
  impression: ["ItemId"],
}

Represents user interaction event information sent using the PutEvents API.

Instance Attribute Summary collapse

#event_id ⇒ String An ID associated with the event.
#event_type ⇒ String The type of event, such as click or download.
#event_value ⇒ Float The event value that corresponds to the EVENT_VALUE field of the Interactions schema.
#impression ⇒ Array<String> A list of item IDs that represents the sequence of items you have shown the user.
#item_id ⇒ String The item ID key that corresponds to the ITEM_ID field of the Interactions schema.
#properties ⇒ String A string map of event-specific data that you might choose to record.
#recommendation_id ⇒ String The ID of the recommendation.
#sent_at ⇒ Time The timestamp (in Unix time) on the client side when the event occurred.

Instance Attribute Details #event_id ⇒ String

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_type ⇒ String

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.

#event_value ⇒ Float

The event value that corresponds to the EVENT_VALUE field of the Interactions schema.

#impression ⇒ Array<String>

A list of item IDs that represents the sequence of items you have shown the user. For example, ["itemId1", "itemId2", "itemId3"].

#item_id ⇒ String

The item ID key that corresponds to the ITEM_ID field of the Interactions schema.

#properties ⇒ String

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.

#recommendation_id ⇒ String

The ID of the recommendation.

#sent_at ⇒ Time

The timestamp (in Unix time) on the client side when the event occurred.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4