WebViews serve web pages through mobile apps. Heap autocapture for WebViews is achieved by installing our web SDK on the underlying website.
Note that since the structure of web apps and mobile apps are fundamentally different, the types of events and sets of properties that are autocaptured also differ between platforms.
Additionally, sessions (ie, period of activity) are defined differently in Heap for web vs. mobile. A web session ends after 30 minutes of inactivity, while a mobile session ends after 5 minutes of inactivity. This will limit your ability to do “within-a-session” analysis for interactions within your mobile app and WebViews, though you can use time restrictions (e.g. “within-an-hour”) as a proxy.
How do WebViews impact session behavior?
A session involving webviews will use a mix of our web SDK and our mobile SDK. As a result, for any given session, two session IDs will be created (one for the web portion and one for the native portion).
Webviews can be distinguished from true website visits by looking at the Browser property of a session. For example, webviews on iOS will have a browser value such as Mobile Safari UIWebView.