[ckan-dev] tracking users

David Read david.read at hackneyworkshop.com
Mon Aug 20 16:10:01 UTC 2012


Toby,

This is great, many thanks. The key to it all is in your last sentence
- about writing the internal tracking code, so that you can avoid
sending data to Google.

Here's my summary:

* Core CKAN can track page views and downloads into the tracking_raw table
* ckanext-googleanalytics can use Google Analytics instead to track
similar info, but in the resource_stats and package_stats tables
* You can periodically run paster commands that loads a summary of
either data into the tracking_summary tables, which is then read by
the templates to show number of downloads.

David

On 20 August 2012 12:30, Toby Dacre <toby.okfn at gmail.com> wrote:
> Toby
>
> On 20 August 2012 11:58, David Read <david.read at hackneyworkshop.com> wrote:
>>
>> I note that CKAN has some code that tracks user as, as well as some
>> new developments in the Google Analytics extension. I've not looked
>> too closely, but can someone explain why we have both and what
>> different things are tracked on each system?
>>
> Hi David,
>
> Essentially the differences are
>
> ckanext-googleanalytics
> -----------------------------------
> this uses ga to track visitors to the site by using ga code as supplied by
> google - the extension must be installed/configured
>
> for internal tracking use branch enhancement-2251-tracking
> stats updated via `paster loadanalytics internal` first time will be slow as
> it will ty to load ~ last 2 years tracking data by day
>
> * lots of stuff is tracked
>
> internal tracking
> -----------------------
>
> this is enabled by setting ckan.tracking_enabled = true in the .ini
> this will then make a request to ckan for each page visited with the url
> visited - it also track click of resource 'download' similar to ga
> these are logged in ckan
>
> stats are updated via `paster tracking -c xx.ini`
>
> * very limited tracking enough to roughly tell a vistor is unique - IP,
> user-agent, username if logged in  plus resource/url
>
> Both
> -------
>
> If internal tracking data is processed via the relevant paster command
> Note: a reindex is also needed `paster search-index rebuild -r`
> the package/resource dicts will now contain 'tracking_summary' of {'total':
> <num>, 'recent': <num>} which can be used on pages
>
>
>> We're upping what we track in DGU and will make all the usage stats
>> transparent, so we're just looking at the best way to do this.
>
>
>
> Depends what you want ga is much richer info but goggle have all your data
>
>
>>
>> David
>>
>> _______________________________________________
>> ckan-dev mailing list
>> ckan-dev at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/ckan-dev
>
>
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
>




More information about the ckan-dev mailing list