Currently route-change transactions are started everytime the currentAppId$ changes and are closed upon largestContentPaint. This diagram illustrates it - You can see that navigations within the app don't create an APM transaction at all.

We want to change the integration in such a way that a new transaction is started every time a page changes. This would require a way of letting apps communicate page changes. @Bamieh mentioned the TrackApplicationView component, but that one may open multiple view contexts one withing the other (for example a flyout within a page can use a TrackApplicationView).

The end result should look something like this (includes changing page-load behavior as described here:

Once we have this, we will proceed to track individual events within each transaction.