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?]
Yes, totally agree with this idea. We need Google Analytics tracking on as much of AGOL as possible in order to gather insight into how people are using our content.
Yes, this would be great!
Yes please! We need this to be able to analyse our Experience page usage along with all our other web content.
Yes please this is critical!
I totally agree. Also, knowing how to include SEO parameters, so anyone who looks for the webpage on Google can find it, rather than typing the URL o having the link.
This is very important! The lack of Google Analytics capability in Experience Builder is one of the central reasons some organizations (in my case, in academia) are hesitant to embrace EB.
Also our group would like this very much!
Yes, this would be very helpful. I'm certain it's easy enough to do in the Developer edition, much like with the Web App Builder but it would still be very helpful in the Online version.
Yes please!
This would be really helpful. Google Analytics is basic requirement for apps our organization deploys.
Please!!! This is really needed for our projects! Even more than story maps which has this option.
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.
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
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.
Every new app our org deploys now has a requirement for some form of usage analytics, specifically Google Analytics. Upvote from me.
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.
Yes, please this is critical!
O Google Analytics para todas as aplicações seria o ideal para acompanhar a utilização dos projetos.
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.
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>
please provide it. its much necessary to us
@FredericPoliart_EsriAU ,
In order for your solution to work, do you have to activate the EUEI agreement for all users to your portal/AGOL site?
In the embed that is created, does it need anything on the URL side, or just the code you entered, and the changes to my specific Google Analytics Tag?
@FredericPoliart_EsriAU
I tried using the embed widget and also tried using both the G4 tag and the universal tag with no success. Is their anything else we need to do to get it to work?
@FredericPoliart_EsriAU I tried your suggested workaround using an Embed widget however, it did not work for me. Does it matter where the Embed widget is placed on the page, relative to other content? Did you actually get this solution to work at some point, or was it just an idea to try?
Do we know if this has been added to the Road Map? Any idea when it may be released?
@PeterKnoop yes it works on my page. We've gone live (soft open) https://fam.brisbane.qld.gov.au
@FredericPoliart_EsriAU Nice app! Do you mind sharing how you got the "Techincal FloodWise Property Report" to generate? I'm interested in doing something similar.
@FredericPoliart_EsriAU when I look at your app's source, I see that the Google Analytics script is in the <head> of the HTML page, not as part of a Experience Builder Embed widget, which would put it in an <iframe> in the <body>. Did I misunderstand your original suggestion, which I read as using the out-of-the-box Embed widget in Experience Builder?
The suggested Idea here was also meant for the regular Experience Builder environment, not the developer edition. It looks like your site was built using the developer edition, which means it is easy to insert the Google Analytics script in the <head>. I don't believe you can do that in the regular edition, or is there something I am missing here?
Thanks!
Thanks @Kara_Shindle . The FloodWise Property report is generated like this:1. We create another separate ExB app that has just one huge custom widget (imagine a widget that is the width of a piece of paper and tall like 6 pieces of paper)
2. Inside that widget we nest a standard Map Widget (to show the map and zoom-to property)
3. Inside that widget we have an area of bar-graph showing the property's highest and lowest level, together with other metrics values. It is basically a JavaScript canvas that draws the bar chart; The axis are dynamically calculated based on the height of the bars in the bargraph. The ExB also consumes a web map table, called "metrics" - we query that table to render the bar graph in JavaScript. 4. Once the html is rendered, we use a lambda process (hosted on AWS) to convert it to PDF and return it to the client.
This one's nice too 🙂 https://franklincountypa.maps.arcgis.com/apps/webappviewer/index.html?id=22d612cb86914276aa9c47e1bff6a9a7
@PeterKnoop correct, we pre-load google analytics on startup in the <head> but then we also have hidden <embed> tags throughout the experience builder app. On Google Analytics we get a bit more information on specific sub-pages .
Melden Sie sich an, um zu posten, Inhalte zu folgen und mehr. Neu hier? Kostenlos registrieren.
