Google Analytics and Hub -- Which metrics?

[KansasDASC]

We're trying to setup GA to track item downloads in our Hub site and so far, the only useful metric is number of downloads by item type (shapefile, KML, CSV, etc). We'd like to actually see what those items are. For instance, the item name, owner, and such. Yes, you can grab that info from ArcGIS API for Python, but now the number of downloads. GA also seems to report on birds-eye system info rather than details about the application/site content.

Even at a minimum, it'd be nice to return (in GA) what item ID it is so that we can relate it back to ArcGIS. Any idea if this is possible?

[ThomasHervey1]

Hi and thanks for asking about GA telemetry in ArcGIS Hub.

Eventually we're aiming to release a guide on telemetry events logged and how to interact with events in your Google Analytics account. In the meantime, ArcGIS Hub logs custom dimensions for certain interactions.

For downloads in particular, you can look for the custom dimension titled "id". This is the ID for the item, and in some cases a layer ID representing the service layer number backing that item. For example, you might see a value like "<itemID>_1". My recommendation is to experiment charting this custom dimension in Google Data Studio to get a feel for your results.

[KansasDASC]

Hi Thomas, thanks, but can you be a little more specific. Looking for 'ID' in the dimensions list brings back many results and none show me what we're looking for. They're either blank or they're Google IDs that have little to do with Esri content. All we need is something that can be used to relate to the actual Hub item/AGO item that was downloaded. The item name, the AGO item ID, anything would help.

[AJ_devaccount · Accepted solution]

If you go to Behaviour > Events > Top Events > Interaction > Downloads, you'll be able to see the downloads by file type. If you click on any of the file types, and choose Page Title as a Secondary dimension, you'll be able to see which datasets were downloaded

[KansasDASC]

Thanks! This should help to actually link back to specific AGOL items for our metrics reporting.