Generic Events
You can use Reward's Generic Events framework to capture non-transaction data about customer actions and behavior. Typical examples of generic events include customer actions such as writing a product review, abandoning a product in an online shopping cart, or adding a reward item to a wishlist. Reward can collect these events through generic event batch files or real-time generic event API processing.
For example, you might define customers addition to their wishlist as an event. Referring to this event, the basic definition is: Customer X (subject) AddsToWishlist (action) Product Y (object) on date (time). If you define a customer reviewing a product as an event, the event based definition is: Customer X (subject) Reviews (action) Product Y (object) on date (time).
What do you do with Event Data?
The data collected from these generic events can be used in CRMS profiles to target email or offers to customers.
In addition to collecting data that indicates a type of event has occurred, you can use the generic events options to define events according to whether very specific numbers occurred. Using this you can target customers based on the occurrence of crucial pieces of numeric data associated with the event. These are called "Event Values." You can create more specific targeting rules based on these specific event values.