You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In both the iOS and Android app, my ideal tracking would be:
Location Search (do not care about capturing the location they searched for, just the count of location searches)
Filter Searches (if possible what filters they used: species vs diameter vs height vs missing stuff)
"Add Tree" clicks
"Save" on Add Tree workflow
Add a Picture clicks (Add a Tree vs Edit Tree Details breakdown would be awesome)
Tree Detail "Edit" clicks
Tree Detail "Save" clicks
My guess is that the mobile apps will show more editing and adding Trees, so we need this information the most. People are almost certainly not going to add photos inside at their desk, so it would be good to understand if and how people are taking photos in the field. Lastly, the filter function is closely related to work order management (filter by trees assigned to me, or by trees that need trimming, etc), so it would be good to add in that code now.
EDIT: This all assumes we are attaching the info above to the user ID so we can pass it back to Google Analytics and get a whole picture of how people are interacting with OTM across all platforms.
The text was updated successfully, but these errors were encountered:
Once we decide exactly what we want to track we'll need a parallel issue in
otm-android
.@kjustice writes:
In both the iOS and Android app, my ideal tracking would be:
My guess is that the mobile apps will show more editing and adding Trees, so we need this information the most. People are almost certainly not going to add photos inside at their desk, so it would be good to understand if and how people are taking photos in the field. Lastly, the filter function is closely related to work order management (filter by trees assigned to me, or by trees that need trimming, etc), so it would be good to add in that code now.
EDIT: This all assumes we are attaching the info above to the user ID so we can pass it back to Google Analytics and get a whole picture of how people are interacting with OTM across all platforms.
The text was updated successfully, but these errors were encountered: