@claycrenshaw commented on Mon Sep 17 2018
Install the Hotjar tracking code into the HEAD tag on every page of the "internal" Carbon site, so that we can gather feedback, track usage, etc. (http://design-system.stage1.mybluemix.net/)
The internal site will serve as the test site for Hotjar functionality, and once we have things working correctly, we can move to install on the primary site.
CODE:
<script>
(function(h,o,t,j,a,r){
h.hj=h.hj||function(){(h.hj.q=h.hj.q||[]).push(arguments)};
h._hjSettings={hjid:1017535,hjsv:6};
a=o.getElementsByTagName('head')[0];
r=o.createElement('script');r.async=1;
r.src=t+h._hjSettings.hjid+j+h._hjSettings.hjsv;
a.appendChild(r);
})(window,document,'https://static.hotjar.com/c/hotjar-','.js?sv=');
</script>
@joshblack commented on Tue Sep 18 2018
What kind of insights are we hoping to get from the tool? Definitely hesitant to do more data collection since we'd have to go through GDPR regulations (https://www.hotjar.com/legal/compliance/gdpr-commitment)
@claycrenshaw commented on Tue Sep 18 2018
This is being used as a user feedback collector. Completely opt-in.
@claycrenshaw commented on Tue Sep 18 2018
We can table any analytics gathering until we can dig in to the GDPR regs.
@shinytoyrobots commented on Tue Sep 18 2018
I think tabling makes sense, to dig into those.
Do we have any data about internal site usage at all? My gut is that internal site usage is minimal compared to the open source site, so I'm not sure of the value of focusing on internal only analysis.
@claycrenshaw commented on Tue Sep 18 2018
To clarify, I'm saying we table any ANALYTICS gathering which might touch on GDPR. But the feedback-gathering function is something I need right away. It's all the same code snippet.
@claycrenshaw commented on Tue Sep 18 2018
In case the need is confusing . . .
I (Clay) need a way to gather feedback on individual pages from internal users, so I can adjust the content based on that feedback.
This tool enables me to do that.
@shinytoyrobots commented on Tue Sep 18 2018
Sure, but why does that need to be specific to the internal site? What internal only content are we talking about?
@claycrenshaw commented on Tue Sep 18 2018
I want to test this new tool on the internal site before we take it to the main site. It's not for internal-only content, but for an internal-only audience for now.