Google analytics report
From CIRCA
| VTracker |
|---|
| Content deleted. (2 Occurances) |
| Content stucture deleted. (2 Occurances) |
| Content inserted. (6 Occurances) |
| Content structure inserted. (12 Occurances) |
| Content structure deleted. (2 Occurances) |
| Content changed. (5 Occurances) |
| Content style of a font changed. (3 Occurances) |
Google analytics report ofGWrit
To have a better understanding of the usage of GWrit, we use google analytics to analyze some basic information of users, including audience overview, user behaviors, and the relationship between events flow and due date.
The most commonly used language is American English, followed byCanada English, Chinese, Great Britain English and korean. Thelanguage usage is judged by users??? browser setting, and not bythe nationality of user. So, we can see the most of the users areEnglish speakers.
The most commonly used operating system is windows system, followed by Macintosh, iOS, Android, Linux and Chrome OS. The usage of mobile development is opposite from the PC operating system. The iOS is the most commonly used system, and then it comes Windows and Android. We can also see the browser usage from google analytics. Users using Chrome browser accounts for 44.68%, ranks first, and the second one is Safari, accounting for 30.83%.From the service provider section, we can see the most of users (48.68%) visit GWrit through the university service.
We draw two different trajectories of user behavior in differenttime according to the data from google analytics. The first one isthe behavior when there is no task due. The second one is in taskdue date.The first trajectory is: User login and selects coursefrom the courses list. Then he select a project of this course. Inthe project page, he clicks ???View Other Submissions??? for aspecific task. In the task submissions page, he selects anotheruser???s work to view.The second trajectory is:User login andselects course from the courses list. Then he select a task, andviews the completed task or comments on this task. After make somemodification, he saves the completed task.
This is a figure shows the relationship between pageview andtask due date. Sep.18, Oct.9 and Oct.16 are three due date duringthe selected time. From the statistic, we can see that in thebeginning of the term, users visit GWrit frequently. As time goesby, the pageview changes according the the task due date. Pageviewof GWrit achieves to peak point when there is a task deadline.
This is a picture shows the relationship between due date anduser???s actions. The time points in X array are three task duedates: Sep.18, Oct.9 and Oct.16. Y array stands for the accounts ofactions.We can see the trend line of set, triggerreward, save andlogin reach to peak point on the due date. While the trend line ofprofile, submit_comment and word_cloud seems have littlerelationship with due date.The account of the word_cloud events isquite small compared to other events, especially the save event.So, it seems that using word_cloud is not a necessary action beforewriting submission. Since the current word-cloud analysis tool isonly used to show the word frequency, so we plan to make it morefunctional for future version, making it more interactive. The lineof submit_comment shows that there is not a clear relationshipbetween commenting and task due date. And the the account ofcommenting action is not very big compared with other actions. Fromthe small-scale of commenting action, the only way of socialcommunication among GWrit users, we can see that the socialfunction is not an outstanding part of the current version ofGWrit. Besides, comments from others plays a less important role tohelp improve online writing than we hypothesised.
