Xponent Journey Hub January 2026 (25.3.3) Release Notes

Overview

The 25.3.3 release introduces the JDA Insights Conversational Assistant. It lets users ask natural‑language questions and explore journey analytics through simple follow‑ups. This makes insights easier to access and complements existing JDA visualizations. This release also includes enhanced support for Ascendon’s updated payload handling. Xponent can now process larger event data more reliably, ensuring smoother end‑to‑end ingestion without exposing internal implementation details

• JDA Insights Conversational Assistant

  The JDA Insights Conversational Assistant introduces a natural language interface that allows users to ask complex journey analytics questions. It also complements existing JDA capabilities by enabling deeper exploration of journey data through follow-up questions, alongside Journey Insights cards and visualizations like Sankey for initial analysis. Users can ask queries like:

  • What is the average number of steps taken by all customers in the last 3 months, that made it to the Journey End step in the Payment Reminder journey?

  • How is the new Send Reminder Email step performing?

  • Which customer segments most often reach the Journey End step in the Renewal journey?

  • Which channels had the highest engagement in the Renewal journey?

  This feature works alongside existing JDA visualizations to deliver a richer analytics experience. It makes insights accessible to both technical and non-technical stakeholders. It helps uncover trends and anomalies. It simplifies optimization and accelerates data-driven decisions without technical barriers.

Continuous Improvements

• Ascendon Listener - Support for compressed payloads.

  Ascendon Listener adds support for Ascendon’s new automatic compression for payloads larger than 1 MB, addressing size limits in the integration with Xponent. This enhancement ensures that large payloads are no longer dropped due to Kinesis size constraints.

  With this update, the Listener can process both compressed and non‑compressed messages. This improves reliability, prevents data gaps, and stabilizes the event flow between Ascendon and Xponent when handling mixed payload types.