On this page:

Related pages:

Your Rating:
19 rates

You can correlate mobile network requests with business transactions. In actuality, the correlation is made between instances of network requests (network request snapshots) and instances of business transactions (transaction snapshots).

The correlation enables you to map network requests made by your mobile application with an underlying backend application. Business transaction correlation is disabled by default.


To correlate business transactions, you are required to do the following:

  • purchase licenses for Application Performance Monitoring (APM) and End-User Monitoring (EUM)
  • instrument an application with an app agent
  • instrument a mobile application with a mobile agent
  • enable business transaction correlation in the Controller UI

App Server Agents Supporting Business Transaction Correlation

To correlate business transactions, your business application must have one of the following App Server Agents installed:

Benefits of Correlating Business Transactions

By correlating business transactions with network request snapshots, you can identify potential issues with the backend application that are causing bad user experiences. For example, you might find that a server error or a database query is causing a slow or very slow user experience.

How It Works

  When an end user takes an action with your mobile application that requires a network request:

  1.   The app agent does the following:
    • sends HTTP headers identifying the business transaction to the end user's mobile device.
    • aggregates backend metrics and sends them along with the business transaction identifiers to the Controller. This serves as the content for the transaction snapshot.
  2. The Mobile Agent sends metrics and the business transaction identifiers (from the HTTP header) to the EUM Server. This serves as the content for the network request snapshot.
  3. The Controller fetches the metrics and business transaction identifiers from the EUM Server and then uses the business transaction identifiers to correlate the network request snapshot with the transaction snapshots.

Enable Business Transaction Correlation

You need to configure the Controller to correlate business transactions. The Controller will map the business transactions with the network request snapshots based on the process described above in How It Works.

To enable business transaction correlation:

  1. From the Application Dashboard, click Configuration.
  2. Click User Experience App Integration >.
  3. From the Business Transaction Correlation tab, check the Enable Business Transaction Correlation check box.

Specify Business Transactions to Include Correlation Headers

You can also specify which business transactions will include or exclude correlation headers. If you do not add request match rules or request exclude rules, correlation headers will be added to all requests.

To add a request rule:

  1. Click the plus icon to open the Create HTTP Request Match Rule dialog.
  2. From the Create HTTP Request Match Rule dialog:
    1. Check the Method checkbox and select an HTTP method that you want to match. If you do not select an HTTP method, the rule will be applied to all HTTP requests.
    2. Check the URI checkbox and enter your criteria.
    3. Click Save to save the match rule.
  3. From the Business Transaction Correlation tab, click Save.

View Business Transaction Correlation

There are several ways to navigate from a browser snapshot to its correlated business transaction. The following steps show you one possible way.

  1. From the Mobile App Dashboard, click Network Requests.
  2. Click Snapshots.
  3. You should now see network transaction snapshots as shown below:

  4. Double-click one of the browser snapshots to open the Network Request Snapshot Details dialog. If a correlated transaction snapshot exists, you will see a link in the Business Transactions section as shown here:
  5. You can then click links in the transaction snapshot or transaction snapshot itself to view corresponding pages in APM.
  • No labels