Purpose and Usage
TIBCO Reward encourages clients to provide the Event file in the standard, supported .xml file format. However, if the client cannot support .xml files, then the necessary file transforms will be established during the on-boarding process.
Clients can provide one file for each event or a common event file that includes data for multiple events. Common examples include a daily update file that includes web analytics data (product browsing and cart abandonment data, for example) and a separate daily file for product reviews. A generic event file includes one record for each event occurrence (that is, for each instance of an event). The same file can include records that refer to instances of different events, and there is no required order for the instance records within a file.
The EventReferenceTag is used to identify the Events in the file and in the CRMS. The reference tag text for an event in the file must exactly match the reference tag text specified when the event was defined in CRMS.
An event subject must be a customer, and an object can be a customer, product, or reward product. In a Generic Event import file, the Subject is identified by using the retailer-provided identifier for the event’s subject (the customer). Similarly, the Object corresponds to the retailer-provided identifier for the event’s object. If the subject does not already exist in the system, the event record will be ignored during the import process. A valid object Id is required to process the file correctly. If the object Id does not already exist in the system, TIBCO Reward imports the record, but the ObjectId is nulled, that is, the object ID is ignored.
Supported subject identifiers are:
Only one of the above subject identifiers can be used, and the same identifier must be used across all events. This identifier must be setup during the initial configuration of the client -- retailer (during the on-boarding process). The customer email address is the default identifier.
Regarding Object Ids: Products and reward products are matched based on SKU.