Make Analytics Public

[Cleop]

@iteles to share details with @markwilliamfirth so he can check up on this.

[nelsonic]

Analytics are the lifeblood of the organisation ... @iteles please make them public.

[iteles]

So, after a little research, it looks like I can make some of our google analytics public using Google Analytics Super Proxy which I'm still looking into.

@Cleop @harrygfox @markwilliamfirth What kind of metrics do you think would be most useful to be public , seeing as we have to start somewhere? Have any of you done any research on analytics?
I've given you all access to our GA.

[harrygfox]

@iteles The stuff I find the most useful is seeing the point at which users leave the site: the sanky diagram showing users entering on this page then going to this page then leaving. why did they leave? are there patterns we can identify?
Ahh all of it is really interesting, especially devices and countries people are accessing from!

[Cleop]

It will be hard for us to track people's journeys if they're not clicking on things. Some significant parts of the site don't require any clicking to access them. However our clickable elements are:

• The dwyl tick (> Meet the Team) - I don't think this is very intuitive/ obvious and so I'm not sure what this data could reveal
• In the navbar: Offering, Process, Contact (can also be viewed by scrolling)
• Navbar: Values
• Navbar: Team
• Submit (on the contact form)
• Values: 'quality of our code', 'global network of expert contributors'
• Team: every team member's face (> their github)

We could also analyse the traffic source (not just by country) but something like:
and

and duration of stay

E.g. Do people who visit the site from an email link stay longer than others? What do they click on?

[harrygfox]

An interesting article on USING metrics from NNGroup:

Translating UX Goals into Analytics Measurement Plans

[Cleop]

As #286 states, since May 9th there has been no gathering of GA data.

[ghost]

@Cleop next step in this issue:

• Make the analytics public

[Cleop]

@markwilliamfirth - the way making analytics public works is that you have to write individual queries for the parts that you want to make public. Before I can simply 'make the analytics public', I need to know what queries to write. According to the number of queries this will impact how much time this takes. Please can you confirm which queries you'd like written?

[ghost]

@Cleop as an MVP let's go with:

• Number of page views for each page
• What countries people are coming from + source (email etc)
• Average length of time spent on each page

If these aren't achievable please swap them out for similar stats - we can start with these for now and augment later

[Cleop]

• Get app from github
• download and install Python 2.7
• Download and install the App Engine SDK for Python
• Need to get credentials for API but not sure how to fill this section in, keep choosing options that don't provide any credentials or getting 'not secure' for the combinations I'm trying
• Create an APIs Console Project (think this is done...)
• 13.16 'Create an actual application on app engine' / Create an app engine instance with url @appspot.com
• Configure the project with your details
• Deploy to app engine
• Create queries

[nelsonic]

@Cleop could you please add a comment with your conclusion on this quest so that we know where/how to pick up and complete it. thanks! 👍