From Localytics' perspective, if you have a hybrid iOS app it basically means you have the ability to tag at two different "layers". You can tag at the native layer (e.g. within the native iOS codebase) or within the webview layer (e.g. within the HTML / CSS / Javascript code that is cued up by the native app, but presented in a webview). Ultimately, the goal for tagging a hybrid app is to make sure that no matter where the behavior occurs or where the tags are located in your code, the resulting data maps to a single "app key" so that it is all represented under a single app within the Localytics dashboard.
The way to accomplish this is to insert tags into the webviews and then "relay" these to the native app through a URL. The native container parses the URL and tags an event/screen appropriately. This way, all data will be tracked through the native app layer and appear under the same app in the Localytics dashboard. In other words, all behaviors will be represented under a single app within Localytics, despite the fact that they were tagged at two different technical "layers".
We have a blog post that describes how to tag hybrid apps on iOS. We also have published the codebase for a sample app with hybrid tags published on Github.