Enhance DataHub analytics to better understand our users

[jwhaney]

Research & Development: we need to learn more about better ways to use Google Analytics in the DataHub

• Track tool drawer button clicks?
  • which filters are being used the most?
  • how often is the geofilter being used? timeslider? etc
• Track Download Map clicks or maybe quad vs county downloads, etc?
• How often do ppl click/visit the Order tab of a collection?
• How often do ppl click/visit the Images tab of a collection?

There are probably many other questions that Analytics could address and assist with to better understand our users. Right now we have Google Analytics implemented in the most basic way.

i am happy to assist, but know very little about the google analytics. I do recall James saying it may not be the best way to track downloaded data, but that was on the old site.

So far this year we have had 580 Orders in the ticketing system, all via DataHub.
Advanced Search Tickets - 20200914.xlsx

[jwhaney]

thanks for the feedback @mitchellryant . you are correct, implementing google analytics better within the datahub would not necessarily be to assist with better tracking of downloads, or any for that matter. this is more from a perspective of better understanding users interaction with the site/application which will help drive future enhancements/work to the app.

i just included you in case you wanted to be notified of progress towards this effort. i can remove you as an assignee if you'd like.

Like i said im happy to help any way possible. @JasonKleinert briefly discussed exporting the Users for the ticketing system to get a better idea on customers asking questions. We could define users by sector type the work in, but this would only give us info on customers that ask questions.

Here is an interaction where the user does not know how to proceed, once an item has been placed in the cart.

[JasonKleinert]

Off topic from enhancing the analytics, but based on the two example tickets provided I agree that the location of the shopping cart can be confusing for users not familiar with the system and who only ever visit a single collection, add it to the cart, and then want to head straight to ordering.

some background on how we got here:
The app design started with the collection views being contained in a modal which allowed for higher visibility of the cart and better awareness for the user, but was changed per request. We then had issues with keeping the header up there all the time because the collection search bar confused users once they were in the collection card, so the view was adjusted to what we have now. No header in collection views.

Maybe we need to bring the header back across all views? Maybe just add a link to "checkout" in the feedback when you add an item to the cart? Just a couple ideas. Either way this feature could use some reworking.