Mapwize SDK and Mapwize UI do not have analytics trackers built in. This means that Mapwize does not know how maps are used in your applications, which we believe is a good thing for privacy. This also means that Mapwize is not able to provide you with analytics metrics and that, if you want any, you will have to instrument your code with your own analytics tracker.
If you are using the Mapwize iOS or Android apps from the App Stores, or maps.mapwize.io, please refer to the dedicated FAQ.
Events and callbacks from Mapwize SDK and Mapwize UI can be used to detect changes in the interface and trigger tracking events. We believe using the following events would make sense:
- venueEnter (Mapwize SDK & Mapwize UI)
- venueExit (Mapwize SDK & Mapwize UI)
- floorChange (Mapwize SDK & Mapwize UI)
- universeChange (Mapwize SDK & Mapwize UI)
- languageChange (Mapwize SDK & Mapwize UI)
- directionstart (Mapwize SDK & Mapwize UI)
- onSelectedChange (Mapwize UI only)
The onSelectedChange is a Mapwize UI specific event triggered when the selected place or placeList changes. Those changes can come from multiple user actions, like clicking on the map or using the search engine. The event comes with dedicated analytics parameters allowing you to know how the user selected the place or placelist and for example what search query was typed before a result was selected.
Please refer to the documentation of the specific SDK regarding detailed implementation.