Introduction to Customer Event APIs
MXO 's Event APIs enable your organization to track customer activity and events that occur outside the MXO framework. Using our APIs, you can send information to MXO about customer activity related to real-time events.
MXO provides a numbers of APIs that enable you manage customer events in real-time.
Customer API
The Customer API enables you to send information to MXO about customer activity without the need to define the context (Interaction) in MXO . You need only provide a Touchpoint, Proposition Code and Activity Type Code for MXO to register activity for a specific customer. The API requires OAuth2 authentication.
The API enables your existing applications and back-end systems to send information to MXO about customer activity in real-time. You can send in data about customer activity relating either to existing Propositions you have set up in MXO or to Dynamic Propositions that MXO has no prior knowledge of.
Dynamic Propositions provide you with the ability to send information to MXO about customer activity relating, for example, to transient products and services, such as special offers or time-bound campaigns or to numerous physical locations, such as Bank ATMs. Dynamic Propositions remove the requirement to set up large numbers of Propositions in MXO for products and services that change frequently or have a limited lifespan.
For more information, see the Deleting Customer Data held in MXO Datastores documentation.
Lightweight Event Listening API
The Lightweight Event Listening API enables you to send information about customer events to MXO , without triggering any optimizations or tracking and capture points. There are no authentication requirements.
The API enables your existing applications and back-end systems to send information to MXO about customer activity in both real-time and as a result of batch processing.
For more information, see the Expected Response Body documentation.
Interaction API
The Interaction API is similar to the Lightweight Event Listening API, with the exception that it requires OAuth2 authentication and is able to trigger decisioning and the subsequent execution of optimizations.
This API is ideal for situations where you want not only to send information to MXO about customer events, but also to trigger the results of decisioning and, for example, to send back personalized content to display to a customer based on their current interaction.
For more information, see the Expected Response Body documentation.
