DPS Hybrid App Tracking - Best Practices?



Does anyone have experience or can share analytics best practices for a hybrid DPS app?

I have a DPS-built tablet app which contains a home screen, and uses several HTML pages (processed through the compiler) for the rest of the app experience. When the app was first created, DPS automatically created a new report suite with it's custom app conversion variables (Article reports, Collections, Publications...). These will only track the native DPS-built screens which is "home" in this case, but not the HTML content.

My plan is to use Adobe Analytics via DTM for the HTML content using the same report suite, and then map "page names" to "article names". The weakness behind this method is DTM will not fire the tracking of the HTML pages if the tablet is offline.

I'm open to any suggestions or recommendations on how to better track this type of app.

Accepted Solutions (1)

Accepted Solutions (1)



One thing to keep in mind is making sure the visitor maintains one visitor ID. If the visitor ID changes when the user crosses from the app to the web portion, the visit would break and an inflated visitor count would be reported in Analytics. There is documentation available at the links below that details how to pass the visitor ID from the app to the mobile web. 

Android - https://marketing.adobe.com/resources/help/en_US/mobile/android/hybrid_app.html

iOS - https://marketing.adobe.com/resources/help/en_US/mobile/ios/hybrid_app.html

Answers (0)