No description
Find a file
2017-11-06 18:24:06 +01:00
lib added code to improve tracking for single site pages 2017-11-05 19:02:35 +01:00
test added code to improve tracking for single site pages 2017-11-05 19:02:35 +01:00
.gitignore updated .gitignore 2017-04-17 02:48:15 +03:00
.travis.yml unittests added 2017-04-21 03:07:42 +03:00
jekyll-analytics.gemspec Update jekyll-analytics.gemspec 2017-11-06 18:24:06 +01:00
LICENSE.txt Create LICENSE.txt 2017-04-17 04:16:49 +03:00
Rakefile unittests added 2017-04-21 03:07:42 +03:00
README.md Fix Piwik, so it matches documentation. Gems is deprecated in _config.yml. Replaced it with plugins. 2017-08-05 23:14:52 +02:00

Build Status

Jekyll::analytics

Webanalytics for Jekyll.

There are many tutorials online to add analytics to jekyll by extending the template. Jekyll-analytics is here to take care of this. Just install the plugin, configure it and you are done :)

Jekyll-analytics: Webanalytics made easy.

Supported:

Installation

Add this to your Gemfile:

gem 'jekyll-analytics'

Then execute

$ bundle

Or install it yourself

gem install jekyll-analytics

Configuration

Edit _config.yml to use the plugin:

plugins:
  - jekyll-analytics

Configure the plugin in _config.yml by adding:

jekyll_analytics: 
  GoogleAnalytics:          # Add, if you want to track with Google Analytics
    id: UA-123-456          # Required - replace with your tracking id
    anonymizeIp: false      # Optional - Default: false - set to true for anonymized tracking

  Piwik:                    # Add, if you want to track with Piwik
    url: piwik.example.com  # Required - url to piwik installation without trailing /
    siteId: "1234"          # Required - replace with your piwik site id (Write id as string)

  MPulse:                   # Add if you want to track performance with mPulse
    apikey: XXXXX-YYYYY-ZZZZZ-AAAAA-23456   # Required - replace with your mPulse API key

Usage

Tracking will be disabled in development mode. To enable production mode set enviroment variable JEKYLL_ENV=production. Github pages automatically sets JEKYLL_ENV to production. For testing use

$ JEKYLL_ENV=production jekyll serve

Contributing

  1. Fork it ( https://github.com/hendrikschneider/jekyll-analytics/fork )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request

How to add support for a new tracker:

  1. Create new tracker class in lib/analytics/YourTracker.rb
#initialize and render must be implemented!
class YourTracker
  def initialize(config)
    #validate config
  end

  def render
    return "Tracking code to insert into html > head"
  end
end
  1. Update README.md