The Target View Class, if not a generic name like UIButton or UIView, can be used to inform the event, and Target Text or an Accessibility Label can be used to more specifically define the interaction. In these situations, oftentimes a combination of other properties can be used to define the event. Sometimes Heap is not able to capture the Target View Name. The Target View Name is typically the most specific piece of information for a touch event, as this relates back to the name that the UIView has in the app code, and will generally uniquely identify the UI element. Depending on the structure of the app code, touch events may capture different pieces of data. In iOS apps, touch events occur on UI elements called UIViews. When a new screen loads in the app, Heap will autocapture an event that provides the name of the ViewController, though that event can be re-defined with a name that fits into your event taxonomy.Ĭommon properties for defining screenviews: In Heap, the iOS ‘View screen’ event is tied to a ViewController transition. Under the hood, iOS screens are almost always associated with a View Controller object. We recommend using Live View to define view events instead of the Event Visualizer. View events only appear in the list of event activity when using the Event Visualizer with Heap versions 7.3.0 and above. The best practices section of this guide aims to demystify details about the actual data, which is helpful in understanding which events to tag. The iOS Event Visualizer attempts to make this easier by providing screenshots and human-readable text descriptions of what is occurring. As a result, it can sometimes be tricky to interpret if you don’t understand the technical details of how web and mobile apps are built. Best Practices for Defining iOS EventsĪutocaptured data is, by its very nature, application-level information that is captured from a mobile or web app. If desired, the default gesture used for pairing can be disabled with. It is not strictly necessary, as the connection will be severed after a successful pairing and subsequent Heap web app-initiated disconnection. is a generally optional call that can be made if you want to have a way to explicitly disable pairing from the app. Once has been called, you will be able see the device or emulator in a list of possible pairings. The method should generally be activated via a button in a debug menu or by implementing a specialized gesture that will trigger the method call. To enable this, the iOS SDK will introduce two new methods to the client library: and. The iOS Event Visualizer utilizes a pairing flow to ensure that events are only captured from an intended iOS device or simulator. IOS Developers: Enabling Event Visualizer Pairing
0 kommentar(er)
