RTE - Real-Time Server

Real-time Session State

The RTE component provides the foundation for the real-time subsystems.

RTE takes events from the Collection Server (part of CCS) and runs the real-time Analytical Models on these, creating an in-memory Session State for each active session. This Session State is constantly updated providing an up-to-the-second view of every session on the site. The Session State is utilized by the other real-time components (RTT and RTP) and surfaced by RTE via open APIs.

Real-time Customer State

If ABI is deployed as part of the Customer Insight Platform cluster than RTE will also query ABI for customer data relating to each session, extending the Session State dataset for each visitor with a Customer State dataset providing historical data on the customer.

Automated Back-office Integration

As ABI is provided with an open schema back office systems can add additional information to a customer’s profile (e.g. product recommendations) and because this information will be included in RTE’s Customer State record for each session, this provides a mechanism to link back office modeling and analytics with real-time online applications and web sites.

Open APIs save Development Time

RTE provides an industry-standard SOAP and high-performance HTTP-based API, these interfaces allow the application developer (or web site programmer) to access both the real-time Session State and historic Customer State data maintained by RTE.
This means that developers do not need to implement “stateful” applications, relying instead on Celebrus to do the “heavy lifting” of maintain real-time and historic customer information.