I would love this to be added too... but you should know that we created
a "proxy" activity map in our own implementation to avoid all the extra
server calls. Since we already had to use processing rules to populate
the value of the Activity Map items (page, link, region) into some
"replication" eVars so that they would actually be included in our Raw
Data Feeds... I actually had our app developers maintain equivalent
values for app navigation, and pass them on the next trackState... I
then map ...