One other item of note.  If you are trying to identify 'the last page of the visit' for time purposes, the brilliant ursulab50161321​ shared that method here: Make it possible to segment on the hit of the exit page and entry page If you then attempt to break down pages by time, with page views as yo...

Two things to take into considerationExit pages have a visit breakdown scope, meaning they persist across all hits for a visit. When you use that dimension it is not considering just the last time the page value was set.Second, from the documentation:"In the case of props, time spent is counted acro...

As an example; a user could interact with a value of a dimension within a visit , but the order might not be attributed to that dimension.  This would explain a difference.

What breakdown are you using?  It could be an issue with how you are combining with that dimension?=.

In this scenario wouldn't you the component migration tool?

Natalie, I would expect that (Page Views - Exits) would be closer to the sum of the individuals rows of the time spent dimensions.Time calculations within Adobe Analytics are (time of most recent event - [minus] time of prior event).  If a user loads a page and then exits the site there isn't a seco...

If your website is public facing you could also share it here.  This would make it easier for the community to trouble shoot your issue.

This is a key difference between the Adobe and Google platforms, within GA the presence of a new UTM parameter instantiates a new visit- which is not true in Adobe.

You can use the out of the box dimension of 'Operating System Type' to create your segments.

This is a relatively simple custom metric to create.  Depending on what you need represented the segment could be at the visitor level instead of visit level as shown above.