The Event Transactions view in Adobe Experience Platform Assurance allows you to validate and debug your Edge Network client implementation, and see the upstream validation results in near real time.
After setting up Assurance, ensure that you have implemented the latest versions of the Assurance and Edge Network extensions in your app.
To view your events, from the left side menu select Event Transactions under the Adobe Experience Platform Edge section.
If you do not see this option, select Configure in the bottom left of the window, add the Event Transactions view, and select Save.
In this section, get familiar with the Event Transaction view and learn how to use it efficiently for end to end validation on Edge Network workflows.
The Event Transactions view displays three columns in the order of the event processing flow:
Edge.sendEvent
, and the response event handles received by the client from the Edge Network server, if any. Examples of client-side events:
The events displayed in the Event Transactions view provide information about the format and content of the data being processed at each state, as well as insightful details about any warnings or errors encountered when the data is processed upstream. The view helps narrowing down the debugging information at the event/request level and identifying errors early on in the development cycle.
To inspect an event, select the desired one from the view. This action expands the Event Details view on the right side of the screen.
Nested data is displayed in a tree format. You can inspect nested key-values by selecting the + (plus) button to the left of the key name.
Each event name is prefixed with an icon which indicates the high-level status of the processing for that event:
You can check the currently used datastream identifier by selecting the info tooltip next to the Edge Network column header.
When multiple clients connect to the same Assurance session and different datastream IDs are used, you will see all of them displayed here. However, this doesn’t mean that your current implementation is using multiple datastreams. Only the current datastream ID set in the tag (mobile property) used by the app is used for processing new events from that client. When testing more complicated use-cases with different configuration settings and multiple clients connected, it may be helpful to use separate Assurance sessions to simplify the validation process.