The Ascendon Listener enables real-time ingestion of billing and event data from Ascendon (a CSG platform) into an xponent graph. It leverages Ascendon’s existing event notification feed to support event-driven workflows based on user activity and billing updates.
Once configured, the listener automatically collects data from the associated Kinesis stream and routes it to the selected output destination in JSON format. Configuration involves:
Creating the Listener and generating stream credentials in Xponent
Setting up event notifications in Ascendon Invision and providing the Xponent stream details to establish the connection
This integration empowers businesses to:
Enable seamless cross-product integration within CSG without the need for middleware or custom infrastructure improving overall customer experience.
Fetch and process customer event data from Ascendon using kinesis in a seamless and automated way.
Orchestrate personlized experiences based on realtime feed/customer activities (like campaigns or service actions) based on customer activity. For Example - payments, plan changes, or account updates.
Streamline cross-product integration within the CSG, which improve customer experience.
Accelerate time to market with the native Ascendon Listener in Xponent.
Prerequisites
Ascendon Listener configuration involves setup in both Xponent and Ascendon Invision. Use Xponent to create the listener and generate the required credentials and stream, and use Invision to create and configure the customer event notifications.
Before you begin, ensure the following prerequisites are met to successfully configure and use the Ascendon Listener:
1️⃣ Create Graph
Identify the customer notification events required for your orchestration in Xponent. Each graph should handle a single notification type from Ascendon. For Example: create one graph for Payment events, another for Subscriber updates. Add the corresponding listener to the graph based on the event type.
2️⃣ Create Stream
Create streams using the guided flow as part of Listener configuration, Stream details are required to be provided in Ascendon to establish the link
3️⃣ Raise Service Request (SR)
You need to raise a one-time Service Request to set up Ascendon in non-prod, and for any changes in the production environment, a Service Request is always required.
4️⃣ AWS Credentials in Ascendon
Use the stream details and create new value for AWS credentials in Ascendon.
5️⃣ Create Event Notification Kinesis
Configure event notification kinesis in Ascendon to push data to the listener stream.
6️⃣ Deploy Graph with Ascendon Listener to Production
Once deployed, the graph with Ascendon listener details can be tracked from the Integrations tab.
Ascendon Listener Configuration
To create an Ascendon Listener on any graph:
Open your desired graph in the Graph Editor.
Click on the Graph Options menu located at the top-left corner of the Graph Editor interface.
Select Add Listener from the dropdown list.
This opens the Listener Editor window.
From the Listener Type dropdown, choose Ascendon.
Select the appropriate Environment from the Environment dropdown. For Example - Dev, QA, Prod.
Click Create Stream to initiate automatic setup. Behind the scenes, the system performs the following actions:
Provisions a Kinesis data stream under your selected environment.
Associates necessary IAM permissions for secure access.
Kinesis stream details are available to view, which are required for configuration in Ascendon.
Once the stream is created, the following stream-specific configuration details are displayed in the UI:
IAM Role (ARN) - The Amazon Resource Name of the IAM role created for stream access. This must be used in the Ascendon setup.
Region - The AWS region where the stream was created. For Example - us-east-1
Stream Name - The unique name of the created Kinesis stream.
Select the Output Destination for the listener. All messages received from Ascendon will be delivered to the Records node of the selected destination in JSON format.
Click Create Listener to complete the setup, and then proceed to configure the AWS credentials and Kinesis event notifications mapping in Ascendon.
Listener Lifecycle
Once the removed Ascendon Listener is added again, the system automatically reuses the existing stream you don’t need to recreate the stream again.
Streams generated by Xponent are linked to a specific graph and cannot be reused across multiple graphs.
If a listener is deleted, ensure the associated stream is not deleted. You can verify stream details in the Integrations tab.
The Kinesis stream, which powers Ascendon, retains data for 24 hours by default.
How Ascendon Configuration Connects to the Listener
To receive events from Ascendon, the billing system must be configured to push data to the newly created Kinesis stream. This is done inside the Ascendon application interface using the details generated during Listener creation. The setup involves:
Configuring AWS credentials inside Ascendon
Creating an Event notification kinesis to map events to your stream
Ascendon requires different levels of access and support depending on the environment:
For non-production environments, a Service Request (SR) must be raised for initial setup only.
For production environments, an Service Request is required for every change, including credential setup, stream mapping, or event configuration.
Ascendon notification events are triggered by customer activity. There may be a delay in data flow after configuration, as events are generated externally.
.png?sv=2026-02-06&spr=https&st=2026-07-22T10%3A20%3A39Z&se=2026-07-22T10%3A34%3A39Z&sr=c&sp=r&sig=6Jr4D8iSxJpfm%2B%2FWypSCP%2B2U26vNfpfN40qkVc%2Fb%2FFI%3D)
When an Order event is triggered (For Example: A new service is purchased or modified), the listener captures the event and displays its payload in JSON format. The payload typically includes metadata and detailed order attributes, such as:
It may take some time to start receiving events after configuration, as Ascendon events are triggered by real customer activity.