How Events are Processed

When the Event Listener receives and processes an XML event record. The XML event records are in KCXML ( Connect XML), which is describe in more detail in a later chapter. When the Event Listener receives a new XML event record, it performs the following tasks:

• Parse and validate the XML.

• Save the event record into the EVENT_QUEUE tables in the database.

• Update customer data and attributes.

• Subscribe or unsubscribe customers to or from the campaign's conversation.

After the Event Listener updates the customer profile and saves the event record in the EVENT_QUEUE tables, it is finished with the event.

The next step is for the Conversation Manager to process the EVENT_QUEUE record and to generate and send a message. The Conversation Manager continually polls for new events in the EVENT_QUEUE table. When a new event is found, the Conversation Manager fetches all the information about the event and any customer attributes and preferences required to generate the event-triggered message. It then passes this information to a Mail Sender or SMPP Sender process so that the message can be generated and sent to the customer.

The following diagram illustrates the activities that take place when Connect receives and processes an event.