Reversing Events
In some cases, the effects of an event can be reversed by another event.
For example, a client can define both an “add to the wishlist” event and a
“remove from the wishlist” event; and in this scenario, the "remove" event
reverses the "add" event. When defining an event in the CRMS, the client using
the CRMS to define an event specifies that another specific event is the
"Reversing Event.
Note: The identification of a reversing event is a one-time, one-way
process, and this means that the sequence is crucial. Because it is slightly
tricky, we describe it both here and in the CRMS online help, as follows:
- In the CRMS, the Reversing
Event should be defined first, so that it is available for selection when you
define the primary event.
- Then (using the example
mentioned above), when you define the primary event, "Add", in the CRMS, you
can select "Remove" as the reversing event.
Note: Be aware that reciprocation is not required and is NOT allowed. This
means that you would NOT define "Add" as the reversing vent when defining the
"Remove" event.
When defining Generic Events in the CRMS, if the client defines the
remove event as the reverse of the add event, this setting allows TIBCO Reward
to match the events sent in the Generic Events import file. This refinement
makes it possible to target customers more accurately, by adjusting the net
number of instances. For example, if customer A adds an item to her wishlist
and there is a current profile that includes all customers who have added at
least one item in the wishlist in an encompassing time frame, then customer A
is included in the profile. However, if customer A removes all items from the
wishlist, the same profile will no longer target this customer.
If you believe that customers commonly perform an action on the object
that has the effect of reversing the effect of another event, contact TIBCO Reward's Account Management department for assistance.