ckanext-googleanalytics_v2..../README.rst

173 lines
6.0 KiB
ReStructuredText
Raw Normal View History

CKAN Google Analytics Extension
===============================
**Status:** Production
**CKAN Version:** 1.5.*
Overview
--------
A CKAN extension for doing things with Google Analytics:
2011-04-05 16:15:46 +02:00
* It puts the relevant tracking code in your templates for you
(including tracking code for external resource download links)
* It provides a page showing top packages and resources
* It inserts download stats onto individual package pages
Installation
------------
2011-04-06 12:05:00 +02:00
1. Install the extension as usual, e.g. (from an activated virtualenv):
2011-04-06 11:07:58 +02:00
::
2012-05-10 14:43:36 +02:00
$ pip install -e git+https://github.com/okfn/ckanext-googleanalytics.git#egg=ckanext-googleanalytics
2012-05-10 14:43:36 +02:00
2. Edit your development.ini (or similar) to provide these necessary parameters:
::
googleanalytics.id = UA-1010101-1
googleanalytics.account = Account name (i.e. data.gov.uk, see top level item at https://www.google.com/analytics)
2012-05-10 14:43:36 +02:00
googleanalytics.username = googleaccount@gmail.com
googleanalytics.password = googlepassword
Note that your password will probably be readable by other people;
so you may want to set up a new gmail account specifically for
accessing your gmail profile.
3. Run the following command from ``src/ckanext-googleanalytics`` to
2011-04-07 11:41:27 +02:00
set up the required database tables (of course, altering the
``--config`` option to point to your site config file)::
paster initdb --config=../ckan/development.ini
2012-05-10 14:43:36 +02:00
4. Edit again your configuration ini file to activate the extension
2011-04-07 11:37:47 +02:00
with:
::
ckan.plugins = googleanalytics
(If there are other plugins activated, add this to the list. Each
plugin should be separated with a space)
2011-04-06 11:34:52 +02:00
2011-04-07 11:37:47 +02:00
Finally, there are some optional configuration settings (shown here
with their default settings)::
2011-04-06 11:34:52 +02:00
googleanalytics.resource_prefix = /downloads/
googleanalytics.domain = auto
googleanalytics.show_downloads = true
googleanalytics.track_events = false
2011-04-06 11:34:52 +02:00
``resource_prefix`` is an arbitrary identifier so that we can query
for downloads in Google Analytics. It can theoretically be any
string, but should ideally resemble a URL path segment, to make
filtering for all resources easier in the Google Analytics web
interface.
2012-05-10 14:43:36 +02:00
``domain`` allows you to specify a domain against which Analytics
will track users. You will usually want to leave this as ``auto``;
if you are tracking users from multiple subdomains, you might want
to specify something like ``.mydomain.com``.
See `Google's documentation
<http://code.google.com/apis/analytics/docs/gaJS/gaJSApiDomainDirectory.html#_gat.GA_Tracker_._setDomainName>`_
for more info.
If ``show_downloads`` is set, a download count for resources will
be displayed on individual package pages.
If ``track_events`` is set, Google Analytics event tracking will be
enabled.
Follow the steps described in the Authorization section below.
2012-05-10 14:43:36 +02:00
5. Restart CKAN (e.g. by restarting Apache)
2012-05-10 14:43:36 +02:00
6. Wait a while for some stats to be recorded in Google
2012-05-10 14:43:36 +02:00
7. Import Google stats by running the following command from
2011-04-04 18:44:39 +02:00
``src/ckanext-googleanalytics``::
paster loadanalytics token.dat 2012-10-10 --config=../ckan/development.ini
2011-04-04 18:44:39 +02:00
(Of course, pointing config at your specific site config and token.dat at the
oauth file generated from the authorization step)
2011-04-04 18:44:39 +02:00
2012-05-10 14:43:36 +02:00
8. Look at some stats within CKAN
2011-04-06 11:07:58 +02:00
Once your GA account has gathered some data, you can see some basic
information about the most popular packages at:
http://mydomain.com/analytics/dataset/top
2011-04-06 11:07:58 +02:00
By default the only data that is injected into the public-facing
website is on the package page, where number of downloads are
displayed next to each resource.
2011-04-04 18:44:39 +02:00
2012-05-10 14:43:36 +02:00
9. Consider running the import command reguarly as a cron job, or
remember to run it by hand, or your statistics won't get updated.
2011-04-04 18:44:39 +02:00
Authorization
--------------
Before you can access the data, you need to set up the OAUTH details which you can do by following the `instructions <https://developers.google.com/analytics/resources/tutorials/hello-analytics-api>`_ the outcome of which will be a file called credentials.json which should look like credentials.json.template with the relevant fields completed. These steps are below for convenience:
1. Visit the `Google APIs Console <https://code.google.com/apis/console>`_
2. Sign-in and create a project or use an existing project.
3. In the `Services pane <https://code.google.com/apis/console#:services>`_ , activate Analytics API for your project. If prompted, read and accept the terms of service.
4. Go to the `API Access pane <https://code.google.com/apis/console/#:access>`_
5. Click Create an OAuth 2.0 client ID....
6. Fill out the Branding Information fields and click Next.
7. In Client ID Settings, set Application type to Installed application.
8. Click Create client ID
9. The details you need below are Client ID, Client secret, and Redirect URIs
Once you have set up your credentials.json file you can generate an oauth token file by using the
following command, which will store your oauth token in a file called token.dat once you have finished
giving permission in the browser::
$ paster getauthtoken --config=../ckan/development.ini
Testing
-------
There are some very high-level functional tests that you can run using::
(pyenv)~/pyenv/src/ckan$ nosetests --ckan ../ckanext-googleanalytics/tests/
(note -- that's run from the CKAN software root, not the extension root)
Future
------
This is a bare-bones, first release of the software. There are
several directions it could take in the future.
Because we use Google Analytics for recording statistics, we can hook
into any of its features. For example, as a measure of popularity, we
could record bounce rate, or new visits only; we could also display
which datasets are popular where, or highlight packages that have been
linked to from other locations.
2011-04-06 11:34:52 +02:00
We could also embed extra metadata information in tracking links, to
enable reports on particular types of data (e.g. most popular data
format by country of origin, or most downloaded resource by license)