See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/281448685

Web Analytics

Technical Report · July 2015

DOI: 10.13140/RG.2.1.4674.9926

CITATIONS READS
0 12,947

1 author:

Omar Shaya
Georg-August-Universität Göttingen
4 PUBLICATIONS 3 CITATIONS

SEE PROFILE

All content following this page was uploaded by Omar Shaya on 03 September 2015.

The user has requested enhancement of the downloaded file.

 19 July 2015
Georg-August-Universität Göttingen
Computer Science Institute

Web Analytics

By: Omar Shaya, omar.shaya@stud.uni-goettingen.de

1
TABLE OF CONTENTS
1 Introduction – 3
1.1 Definition and Scope – 4
1.2 Who Uses Web Analytics – 4
2 Data Collection – 5
2.1 Web Logs – 5
2.2 JavaScript Tagging – 6
2.3 Web Beacons – 8
2.4 Packet Sniffing – 8
2.5 Types of Data Collected in Web analytics – 9
3 Limitations – 10
3.1 Impact of Different Internet Technologies – 11
3.2 Impact of Web 2.0 Technologies – 11
4 Screenshots Demo - Google Analytics – 12
5 Ethics in Web Analytics – 12
5.1 Privacy enhancing technologies – 13
5.2 Non-tracking Web Analytics – 14
6 Potential Future Trends In Web Analytics – 14
7 Summary – 15
8 References – 15
Appendix – 16

2
1. INTRODUCTION
The internet has changed the way we live and conduct our different activities in so many ways.
And the World Wide Web is one of the most essential services that the internet provides.
According to [8], the definition of the World Wide Web is: “The Web is a global set of
documents, images and other resources, logically interrelated by hyperlinks and referenced with
Uniform Resource Identifiers (URIs). URIs symbolically identify services, servers, and other
databases, and the documents and resources that they can provide. Hypertext Transfer Protocol
(HTTP) is the main access protocol of the World Wide Web. Web services also use HTTP to allow
software systems to communicate in order to share and exchange business logic and data.”

In this report, we will cover the topic of Web Analytics. A huge number of businesses around the
world has a Web presence and some of them conduct all or the majority of their business
transactions online. That created the need to have tracking procedures in place to report and
measure the different activities that are happening on the web, like user behavior on a particular
website, the influence of new features on a website, the effect of a marketing campaign on
website traffic, and many more like monitoring the website traffic for any anomalies or attacks.

To create this report we used a literature review approach, searching for papers using Google
Scholar on keywords like Web Analytics and Web Tracking. We considered 36 papers based on
the titles, and after reading the abstract and conclusion for these papers and comparing the results
based on the relevance to the topic and the scope of the papers we selected 5 papers to be used
for this report and presentation. In addition, we were granted access from a software company
which choose to stay anonymous, to their Google Analytics account that is used for the purpose
of monitoring their website. And from that account we were able to provide some screenshots to
the Google Analytics software. In addition, we used Google to search the web for extra
clarification and definitions in some cases. Therefore this report is entirely based on these
references and doesn’t try to introduce any novel ideas. The last section that talks about future
trends in analytics is based on personal observations and opinions of industry trends and experts.

In this report we will start in section 1 with definition and scope of the report, then we talk about
who is using Web Analytics. In section 2 we talk about different methods for data collection in
web analytics. Section 3 is about limitations and deficiencies of Web Analytics. Section 4
provides information about Google Analytics and screenshots demo that can be found in the
Appendix. In section 5 we cover the issue of ethics and web analytics and explore methods to
enhance users’s privacy in the context of web analytics. In section 6 we share our observations
based on industry trends of the potential future trends in Web Analytics. And finally we
summarize the report in section 7. Section 8 contains the references, then followed by the
Appendix that contains the screenshots of of the Google Analytics account.

3
1.1 Definition and Scope
According to the Web Analytics Association, the official definition of Web Analytics is: “The
measurement, collection, analysis and reporting of Internet data for the purposes of
understanding and optimizing Web usage” [2]. In addition, it is important to notice that Web
Analytics is not a technology to produce reports; but rather it is a process that proposes a
virtuous cycle for website optimization [2]. As Figure 1 shows, the Web Analytics process starts
with defining goals for the Website, then there should be concrete KPIs (Key Performance
Indicators) that will help understand the different metrics used in the Web Analytics process.
After step 1 and 2 has been clearly defined, it is time to collect the data, and there are several
way to collect data in the context of Web Analytics that we will look at in detail in the Data
Collection Section. After collecting the data comes analyzing the data part, and finally
implementing the changes based on the analysis results which corresponds to the goals and KPIs
that were set in steps 1 and 2.

Figure 1: The Web Analytics Process. Source: [2]

The focus of this report will be on the Data Collection process, and that comes for 3 main
reasons. First, we can conclude from the Web Analytics Process that there are several stake
holders involved. We can argue that steps 1 and 2 (defining goals and building KPIs) are tightly
related to business functions and therefore not really in the scope of our expertise as computer
scientists. Second, step 4 (data analysis) is a big field on its own, therefore we will not go into
the methods of data analysis. And lastly, step 5 (implementing changes) will always be case
specific, thus also will not be covered in this report. That leaves the data collection step where
we will go into detail to know more about the different methods of data collection in the context
of Web Analytics.

1.2 Who Uses Web Analytics

Web Analytics can help several stake holders do their jobs. We can categorize the stake holders
of Web Analytics into 3 main categories. First, server administrators. Second, web designers,
product managers, and software architects. And third, marketers [1].

Server administrators use Web Analytics mainly to monitor the availability of the Website and
making sure it is online at all times. In addition, by observing traffic patterns, server
administrators can predict and plan for growth in the need of server resources at certain times of

4
the year. In addition, they can monitor for any unusual and possibly malicious activity like
receiving unusually large numbers of requests from a single IP address [1].

Web designers, product managers, and software architects - depending on their assigned
responsibilities - use Web Analytics to assess user experience and site usability by looking at
patterns in user behavior and check for events like where users spend most of their time on the
site, or where do users mostly leave the site [1]. In addition, they can design web pages that cater
to different user environments by checking which types of devices the users used to browse the
site like a desktop computer or a mobile device. Also, they can check the screen resolution of the
users’ devices and modify the site resolution accordingly. They can also check the click train or
click stream which is the sequence of links the user clicked on until reaching some goods or
purchasing these goods, and based on that they can understand what features are working and
what features are not. Thus, improve current features, add new features, and delete unused
features [1].

Marketers benefit from Web Analytics by using it to track the effectiveness of different
advertising activities [1]. In online advertising, such as banner ads and other links, marketers can
use Web Analytics to understand which ads generate the most clicks and most purchases.
Marketers can also track the performance of off-line ads by giving special URLs in the offline
ads and when users visit the site by entering these special URLs, marketers know they are
coming as a result of an off-line ad [1]. In addition, Marketers can use Web Analytics to
understand the effectiveness of search engine keywords that lead the users to visit the site. To
give an example, a popcorn chain in New Jersey thought that users will search “gourmet
popcorn” to reach their site. However, using Web Analytics they figured out that users mostly are
searching for “chocolate popcorn” and “caramel popcorn” when they are looking for popcorn
[1].

2 DATA COLLECTION
In this section, we will look at the main ways of capturing behavioral data from Websites to be
used in Web Analytics. As mentioned earlier, the focus of this report will be on the data
collection process in Web Analytics because it is the most related to us as computer scientists. In
addition, other parts of the process in Figure 1 can be studied as separate topics on their own like
data analysis. According to [2] there are 4 main ways of capturing data for the purpose of Web
Analytics. They are: Web Logs data, JavaScript Tagging, Web Beacons, and Packet Sniffing. We
will see what are the advantages of each approach and how each of them works.

2.1 Web Logs

In Web Logs method of collecting website data, the server that hosts the website registers user
requests in a log file [2]. There are several file formats for log files, one example is the Extended
Log File Format. It is considered the commonest file format for Web Logs by [2]. Extend Log
File Format records several info for each request like the IP of the computer that requested the

5
information, date or time at which the transaction was completed by the user, the time taken for
the completion of the transaction, the amount of bytes transferred, the records whether a cache
hit occurred and the referrer to the page which is usually possible to obtain as part of the HTTP
protocol [2].

There are several advantages to using the Web Logs method to collect Website data. First, the
website owner owns the data as opposed to some other methods, like JavaScript tagging, where
the data is owned by a 3rd party [2]. Second, Web Logs are available backwards, which enables
the website owner to analyze history data and past campaigns. Third, Web Logs save web
crawler behavior to better understand how search engines work and rank the site, web crawlers
are used by search engines to index websites and show them as search results later [2].

Figure 2: Log File Data Collection Visualization. Source: [2]

Web Logs are collected when a customer enters a URL in a browser, the request comes to one of
the Web Servers on which the site is hosted, the web server then creates an entry in the log file
and then the requested page goes back to the customer, this process is shown in figure 2.

2.2 JavaScript Tagging

Another method of data collection in web Analytics is using JavaScript Tagging. And that works
by inserting a small JavaScript code, Figure 3, in every page of a website. Then every time a
visitor opens a page, this JavaScript code is activated and the visitor information and actions are
saved in a separate file [2].

6
 Figure 3: Google Analytics Tracking Code. Source: [3]

The advantages of this methods are that it counts every visit to a website, unless the user closes
the page before the script is loaded, while log files can be affected by cached pages by the proxy.
Also, the JavaScript code is not read by the search engine crawlers, which generates high
amounts of traffic and are not representative of customers’s behavior, while in Log Files search
engine crawlers can be mistaken for actual users of the site [2]. Additionally, usually the analysis
resources of JavaScript Tagging data are outside the company which owns the website [2]. That
can be a good thing when companies don’t want to invest in infrastructure for data collection and
analysis, and they are fine with having their data hosted on a 3rd party servers.

Figure 4: JavaScript Tagging Data Collection Visualization. Source: [2]

The sequence in which JavaScript Tagging works, as in Figure 4, starts when the customer types
a URL in a browser, then this request comes to one of the Web Servers where the website is
hosted. The Web Server then sends back the requested page to the user along with a snippet of
JavaScript code appended. As the page loads, it executes the JavaScript code which captures
details about the visitor session and cookies, and sends it back to the data collection server [2].

7
And in some cases upon receipt of the first set of data, the server sends back additional code to
the browser to set additional cookies or collect more data [2].

2.3 Web Beacons

The third method of data collection in Web Analytics is by using Web Beacons. In this method, a
“tracking pixel” is used to measure banner impressions and click throughs [2]. So this method is
mainly used with online advertising, specially when using banner ads. As banner ads are usually
images, one pixel of the banner image is utilized to be the tracking pixel.

Figure 5: Web Beacon Data Collection Visualization, notice tracking across 2 different websites. Source: [2]

The benefit and common usage of Web Beacons is in tracking customer behavior across different
websites. Because the same server is collecting the data, reading the cookies and doing the
tracking, it is possible to track the same visitor across multiple sites or different visitors to the
same site. And therefore it is mainly used to know how are banner ads performing across
multiple websites [2].

As Figure 5 shows, the sequence in which Web Beacons work is first when a user types a URL in
a browser, the request comes to one of the web servers. Then the web server sends back the page
along with a GET request for a 1x1 pixel image from a 3rd party server. As the page loads, it
executes the call for the 1x1 pixel image and thus sending data about the page view back to the
third-party server. Then the third-party server sends the image back to the browser along with a
code that can read cookies and capture anonymous visitor data [2].

2.4 Packet Sniffing

The last method of data collection in Web Analytics that we discuss in this report is Packet
Sniffing. In this method, packets go through a packet sniffer that collects the packet’s attributes

8
[2]. A packet sniffer is a software or hardware that resides between the user’s device and the Web
Server. And used to read the packets that are passing between the two [5]. The advantage of
packet sniffing is that there is no need to tag pages like the case with some of the previous
methods, because all the information pass through the packet sniffer [2]. Packet sniffing s often
used with multivariate testing [2].

Figure 6: Packet Sniffing Data Collection Visualization. Source: [2]

When a user types a URL in browser, the request is routed to a the web server but it passes
through a software or hardware based packet sniffer that collects the attributes of the request.
The packet sniffer then sends the request to the web server where the request is sent back to the
customer but it also passes through the packet sniffer. The packet sniffer captures information
about the page going back to the user, it store that data and sends the page to the user’s browser
[2]. Some packet sniffers append a JavaScript tag that can send more data about the visitor back
to the packet sniffer [2]. The previous steps are shown in Figure 6.

2.5 Types of Data Collected in Web analytics

Taken from [1], Table 1 shows examples of the data types collected in Web Analytics. It is worth
noticing though that this table is not exhaustive, and other types of data might be collected in
Web Analytics, some that were mentioned in the previous data collection methods, or other data
types that are made possible to collect with the advancement of Web Analytics data collection
techniques. For example, in Web Logs files, data like Hits, Unique visitors, Page views, IP
Address, Browser Type, Search Engine keywords that led to the page, user’s connection speed,
and is possible to collect [1].

9
 Data Type Description
Hit Each element of web page downloaded to web browser
Unique visitors Number of (unique) viewers
New/Return visitors Number of first time visitors vs. returning visitors
Page views Number of times each webpage has been viewed
Page views per visitor Number of page views divided by the number of visitors
IP Address A numeric identifier for a computer (country, computer
network)
Visitor location Geographic location of visitors
Visitor language Language settings on visitor’s computer
Referring pages/sites Indicate how visitor get to website (direct address, link)
(URLs)
Keywords If visitor coming from search engine, we know which
keywords they used
Browser type The type of browser software visitors use
Operating system version The specific OS of the visittor
Screen resolution Display setting for the visitor’s computer
Java or flash-enabled Whether visitor’s computer allows java or flash
Connection speed Whether visitors using slow or fast connection
Errors The number of errors identified by the server e.g. 404 (help
identify broken links)
Visit duration Length the visitor stays on the site before leaving
Visitor paths/navigation How visitors navigate the website (entry, exit, …)
Bounce rate The percentage of visitors who leave the site after the first page

Table 1: Types of Data in Log File Analysis. Source: [1]

3 LIMITATIONS
Despite being widely used, Web Analytics still face many deficiencies and limitations to date. In
this section, we will go over some of these deficiencies and limitations which will be categorized

10
according to [1] by limitations caused by the impact of different internet technologies and
limitations caused by the impact of Web 2.0 technologies.

3.1 Impact of Different Internet Technologies

Several internet technologies are very common today in for various reasons like security,
privacy or performance optimization. For security and privacy, technologies like Firewalls and
Proxies are usually used. In addition, to optimize performance of websites for the users and
optimize traffic, technologies like caching and proxy servers are used. We will see how these
technologies affect Web Analytics.

Proxy servers are network servers that act as intermediary between the user’s computer and the
actual server on which the website resides [1]. Proxy servers can cause an under reporting of
unique visitors because if a page was requested before through the proxy, then for the next user
that requests the same page, the proxy will fetch the same page that was fetched for the previous
user and stored in the proxy’s memory. Although that will bring the page faster to the user, but
the pages delivered by the proxy will not be logged in the log file on the Web Server [1]. All user
requests that go through the proxy will seem to the web server as if they are coming from the
same IP address. And in a another scenario users can be assigned a new IP address by the proxy
overtime and this results in inflating the number of unique visitors [1].

Another internet technology that affects the accuracy of Web Analytics is Firewalls. Firewalls are
devices like a server or a proxy, or they are software based that is used to protect internal users
from outside threats on the internet [1]. And like the case with proxies, Firewalls hide the actual
IP address of the user and present a single IP to all of the users behind the Firewall [1], which
causes under reporting of unique visitors when using Web Logs.

Furthermore, another reason for limitations of Web Analytics is web browser caching. Which
means that the web browser keeps a copy of a web page in its memory and rather than requesting
the page again from the server, the browser displays a copy of the page rather than another new
request to the Web Server [1]. That caching will result in under reporting the actual visit count
because the Web Log files will not report these cached page views [1].

3.2 Impact of Web 2.0 Technologies

Web 2.0 is defined by [1] as the “uses of the Internet [that] are based on user-generated content
and a more user-driven experience; they include, for example, blogging (or posting entries to a
Website in the form of a diary or journal, also known as a ‘web log’—not to be confused with
Web log files), tagging, RSS feeds, wikis, interacting on social networking sites (such as
MySpace, Facebook, or LinkedIn) and sharing rich-media content such as videos (e.g.,
YouTube). [All] Known collectively as Web 2.0.” And although many Web Analytics techniques
still work in the context of Web 2.0 technologies, there are some limitations that should be

11
addressed in order to get accurate Web Analytics on Web 2.0 based sites. We will cover two Web
2.0 related technologies: AJAX and RSS.

AJAX stands for Asynchronous JavaScript and XML and it is “a A programming technique that
allows the Website to exchange small amounts of data with the server behind the scenes (rather
than reloading the entire Web page each time the user requests an update)” [1]. Therefore in
some cases, a whole website can be designed in a way to be a single page only. Thus, with
traditional Web Analytics tools the page view will be recorded only once regardless of how much
the user stays and interacts with the page [1]. However, some techniques can provide some
capability for tracking refreshed page views through a tagging and “call back” to the server [1].

Another Web 2.0 technology that could have an effect on Web Analytics is RSS which stands for
Real Simple Syndication, and according to [1], RSS “allows people to sign up to have news
articles, blog posts, or audio interviews/podcasts from Websites sent directly to their computers
essentially, the syndication of Web content”. In order to get accurate Web Analytics when using
RSS, There is a need for a solution to track content that is no longer contained in a single
Website, but rather is distributed to other sites and feed readers across the web [1].

4 SCREENSHOTS DEMO - GOOGLE ANALYTICS

Google Analytics is “a ‘client-side’ data collection system that uses page-tagging techniques in
which a line of JavaScript code is embedded into the footer of each page of the website”[9]. It is
one of the most widely used Web Analytics tools. According to [9] “Because of its [Google
Analytics] strong abilities to provide statistics in great abundance, both researchers and
practitioners have used Google Analytics to track users’ interactions on websites.” The
Appendix part in this report contains screenshots taken form a Google Analytics account that
was set to report on the official website of a software company.

One example of how this company used Google Analytics is that they looked at patterns, trends
and spikes in the Google Analytics repots of their website. And they noticed that at certain days
of the month they see a significant increase in traffic coming to the website and then traffic
comes back to average on the next day. After analyzing the spikes and their relations to any
special events on these days, it led the company to understand that the traffic spikes were
happening because of two main reasons. One is when this company publishes a new press release
on the Web to make a new announcement. And the second reason for the spikes was that when
the company posts a new job opening on the Website, the traffic to the Website increases
significantly on that day. That shows us how Web Analytics helps understand what is happening
with user behavior on websites.

5 ETHICS IN WEB ANALYTICS

Web Analytics is based on user’s data and the way they use the web, therefore there is an ethical
aspect to Web Analytics specially that the users’ data is sometimes stored on 3rd party servers

12
that don’t belong to the website that the user is actually visiting, and sometimes this data is
stored without users’ knowledge or the data is used or sold for advertising purposes therefore
there was a lot of concern over the ethical aspects of Web Analytics, and in their paper [6]
present the minimum duties of organizations that collect data for the purpose of Web Analytics as
following:
• The customer is the owner of information about them
• The customer should be informed on the information the organization is collecting and for
what purpose the information is being collected
• The customer should have the option not to participate (opt-out)
• The customer's information should be protected from third-party access
• Appropriate governance on management and destruction of customer data is established

5.1 Privacy enhancing technologies

According to [7], certain countermeasures exist that help individuals to protect themselves from
being identified and tracked on the Internet. However these measures are not a guarantee that
they are not being tracked in some way.

One of the countermeasures is hiding IP addresses in order not to let other parties know a user’s
IP address, for that a proxy server is used that acts as an intermediary that forwards requests on
behalf of clients. All data, including responses from the destination, flow through the proxy, such
that the IP address of the client computer is only revealed to the proxy. The destination server
only sees the address of the proxy and not the user [7]. Another option is to use an onion routing
mechanism, where encrypted connections between multiple chained relays are established.
Applications do not contact the destination server directly, but instead send data through a Tor
proxy, which serves as the first node in the chain [7].

Another privacy enhancing mechanism is using End-to-end Encryption. For example, the
HTTPS protocol, a combination of HTTP and TLS, is commonly used to protect web traffic [7].
HTTPS uses the public key of the Web Server, published in its certificate, to negotiate a
symmetric encryption key, which is then used to secure all further communication [7].

In addition, there exists browser-based blocking and plugins to to prevent users from being
tracked such extensions are Tracking Protection Lists, Torbutton, Adblock Plus, NoScript, and
RequestPolicy [7].

Other ways to prevent tracking are Private Browsing Modes where there is no browser history,
no caching, and disabled cookies. Also Opt-out cookies which are special cookies that get
recognized and honored by tracking companies not to track that user [7]. And HTTP Do not track
header which is set by the browser, and signalizes to the server that the user doesn’t want to be
tracked [7].

13
5.2 Non-tracking Web Analytics
In addition to having privacy enhancing techniques on the users’s side, there is some research
from both academia and the industry to create non-tracking Web Analytics systems for the
purpose of getting the important web analytics from users while maintaining users’ privacy and
ownership of their data. An example of such research can be found in [4] where they present in
the paper a system for non-tracking Web Analytics.

Figure 7a: Operation of today’s tracking web analytics

systems. Source: [4]

Figure 7b: Query workflow of [4]’s system. Source: [4]

In [4]’s system, the data resides in a database at the client’s side and publishers, who want to
conduct the web analytics, query the clients’ database using SQL. Then the client sends the data
to data aggregators (third parties) via the publisher (as a proxy) and the data is encrypted with
public key at the aggregator for protection, in addition, and for more security and privacy, noise
is added to the information at the publisher and at the aggregator so that none of them can see the
actual data. [4] assumes the publisher and the aggregator are trustworthy. Figure 7a shows how
traditional Web Analytics with 3rd party server currently work and Figure 7b shows the system
presented in [4].

6 POTENTIAL FUTURE TRENDS IN WEB ANALYTICS

As we’ve seen before that some new technologies bring some limitations to Web Analytics like
Web 2.0. There are more trends in technology, particularly in the way we use the internet and the
Web that will naturally create the need for new research and tools in Web Analytics beyond the

14
simple Web browser on a desktop computer. Since the raise of the smartphone, users’ internet
usage behavior has been shifting more and more to mobile based apps instead of the browser
which eventually means that there will be a need for mobile app analytics to meet the consumer
shift and enable organizations to track and understand user behavior on mobile apps. In addition,
many expert forecasts predict that the introduction of new internet connected devices like
smartwatches, smart glasses, connected cars (where cars will be more integrated into the
internet), and generally the internet of things, where every electronic device will be connected to
the internet, will eventually lead to the need for new ways of tracking and understanding user
behavior and thus new analytics tools to keep up with the new trends.

7 SUMMARY
In this report, we talked about Web Analytics, and we mainly focused on the data collection
techniques that are employed in Web Analytics like Web Logs, JavaScript tagging and others. In
addition, we looked at the limitations of Web Analytics which are mainly a result of some
internet technologies and Web 2.0 technologies. We also looked at the ethical duties of
organizations that collect data to conduct Web Analytics, and explored some privacy enhancing
techniques that could protect users from being tracked on the web. And in addition to the client’s
side, we looked at some research that suggests a non-tracking Web Analytics system to provide
better security and privacy to the clients. Lastly we suggested potential future trends in Web
Analytics as a response to the needs created by new technologies and new ways that the users are
using the web.

8 REFERENCES
[1] Anthony Ferrini (Acquiremarketing.com, USA), Jakki J. Mohr (University of Montana,
USA). Uses, Limitations, and Trends in Web Analytics. In Handbook of Research on Web Log
Analysis, Chapter VII, pages 122 - 140, 2009
[2] Daniel Waisberg and Avinash Kaushik. Web Analytics 2.0: Empowering Customer Centricity.
In SEMJ.org, volume2, issue 1, 2009.
[3] Google Analytics. http://www.google.com/analytics/. June 23, 2015
[4] Istemi Ekin Akkus, Ruichuan Chen, Paul Francis (all from MPI-SWS), Michaela Hardt
(Twitter Inc.), and Johannes Gehrke (Cornell University). Non-tracking Web Analytics. In CCS
'12 Proceedings of the 2012 ACM conference on Computer and communications security,
pages 687-698, 2012
[5] Ivo Rehberger, interview. Packet Sniffing for Web Analytics. In http://metaanalytics.org/web-
analytics/packet-sniffing-for-web-analytics-amazing-interview-to-ivo-rehberger-from-nextwell/,
June 23, 2015
[6] Kenny, Rebecca, Pierce, Justin and Pye, Graeme 2012. Ethical considerations and guidelines
in web analytics and digital marketing : a retail case study. In AiCE 2012 : Proceedings of the 6th
Australian Institute of Computer Ethics conference, Australian Institute of Computer Ethics,
Melbourne, Vic., pages 5-12, 2012

15
[7] Niklas Schmücker, Berlin University of Technology. Web Tracking. In SNET2 Seminar Paper
- Summer Term, 2011
[8] World Wide Web. https://en.wikipedia.org/wiki/Internet#World_Wide_Web. July 18, 2015
[9] Xing, Guo, Fitzgerald, and Xu. Google Analytics based Temporal-Geospatial Analysis for
Web Management: A Case Study of a K-12 Online Resource Website. In International Journal of
Information Science and Management, Vol. 13, No. 1, pages 87-106, 2015

APPENDIX

Screenshot 1: Audience Overview 1/2. Source: [3]

Screenshot 2: Audience Overview 2/2. Source: [3]

16
 Screenshot 3: User Type. Source: [3]

Screenshot 4: Web Browser. Source: [3]

17
Screenshot 5: Mobile Device. Source: [3]

Screenshot 6: Service Provider. Source: [3]

18
 Screenshot 7: Country. Source: [3]

Screenshot 8: Demographics - Age. Source: [3]

19
 Screenshot 9: Demographics - Gender. Source: [3]

Screenshot 10: Demographics - Interest Category. Source: [3]

20

View publication stats