Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master

Ensure that keywords are escaped within a spree_analytics call

Thanks to Michael Bianco from Ascension Press for bringing this to our
latest commit 079949fd0e
Chris Mar cmar authored
Failed to load latest commit information.
app Ensure that keywords are escaped within a spree_analytics call
lib removed dependency, additional tests
script first commit
spec Ensure that keywords are escaped within a spree_analytics call
.gitignore testing
Gemfile Migrating to Spree 1.0
Gemfile.lock Migrating to Spree 1.0
LICENSE first commit note about analytics being integrated into Spree core
Rakefile Migrating to Spree 1.0
Versionfile Migrating to Spree 1.0
spree_analytics.gemspec Migrating to Spree 1.0

Spree Analytics

Spree Analytics were integrated into Spree in v1.0, you only need this extension if you are using an older version of Spree

Spree Extension for robust analytics tailored for ecommerce merchants.

Provides a transparent view into your store performance so that you can make better-informed decisions to increase your revenues. Tracks metrics that are relevant and actionable for store managers, not web masters. Key information like trending products, revenue per customer, etc., can be easily compiled because of the deep integration with Spree


  1. add spree_analytics to your gemfile
gem 'spree_analytics', :git => ""
  1. create an initializer file in config/initializers/spree_analytics.rb
SpreeAnalytics.app_id = <APP_ID>
SpreeAnalytics.site_id = <SITE_ID>
SpreeAnalytics.token = "<TOKEN>"


Note: the spec/dummy/config/routes.rb file gets created with an incorrect engine name. It should be SpreeAnalytics::Engine.

Be sure to add the rspec-rails gem to your Gemfile and then create a dummy test app for the specs to run against.

$ bundle exec rake test_app
$ bundle exec rake spec

Copyright (c) 2011 Spree Commerce

Something went wrong with that request. Please try again.