Select to view content in your preferred language

Provide ability to track ArcGIS Experience Builder interactions with Google Analytics

19355
56
10-19-2020 10:20 AM
Status: Implemented
PeterKnoop
MVP Regular Contributor

Add support for Google Analytics to Experience Builder. Keep it simple, as was done in StoryMaps and Hub, where you have a setting or property for each Experience into which you can paste your Google Analytics Tracking ID.

[Original GeoNet thread: Google Analytics with Experience Builder?]

56 Comments
NavaSheer

Please!!! This is really needed for our projects!  Even more than story maps which has this option.

LiamHarrington-Missin

Agreed more and more it is important to gather insights from the content we share rather than just throw it out there and know nothing about how it is performing.

fpolia21

YES.  Every project we work on is demanding Google Analytics' tracking. 
( If there is a way to track Experience Builder with ArcGIS Monitor , it would be OK too )

Thank you 

Kara_Shindle

This would be quite useful - especially as we are getting more requests for that sort of information to be collected in situations where we would have used Experience Builder but have to choose a different format due to the lack of tracking information needed for legislative reporting requirements.

BrittanyBurson

Every new app our org deploys now has a requirement for some form of usage analytics, specifically Google Analytics. Upvote from me.

MichaelOKonski1

In the same boat as most commenters here. Every app needs Google Analytics plugged in: Dashboards especially. Not sure why, that after so many years, is this basic functionality is still only available on Storymaps and Hub? Consider this an enthusiastic upvote.  

PedroCasimiro

Yes, please this is critical!

RafaelaNeves

O Google Analytics para todas as aplicações seria o ideal para acompanhar a utilização dos projetos.

DavidHood_USFS

Yes please, this is important functionality.

From our Web Manager on why this important: What analytics tells us is who is accessing our products with what platforms, how they find it, and how long they stay and how much they interact with the products. While this  isn’t directly tied to accessibility (it won’t tell us they are using a screen reader, for instance), it will give us a better idea on what our app designs should be first and foremost designed around.

FredericPoliart_EsriAU

Just create an <embed> widget and paste this in the content | code : 


<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src=https://www.googletagmanager.com/gtag/js?id=G-DH7R6Wxxxx></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag() { dataLayer.push(arguments); }
gtag('js', new Date());
gtag('config', 'G-DH7R6Wxxxxx');
gtag('event', 'aaa', {
'event_category' : 'bbb',
'event_label' : 'ccc'
});
</script>