SNOGmetrics is a bridge between Rails and KISSmetrics' JavaScript API.
Yes, but it's not as good as the JavaScript one, they even say so themselves:
One thing to note about the Ruby API is that it is not as full featured as the JavaScript client. Therefore, in most cases we recommend using the JavaScript client. However, some things are easier to track server-side, therefore we have provided a basic Ruby client.
It's true, but why settle for either or?
SNOGmetrics works similarly to flash messages. Events are recorded and saved to the session, and are then sent when the next page is rendered. This way you get all of the benefits of the JavaScript API, but you can record events in your controllers. All you have to do is install this gem, configure it, and add a snipplet of code to your layout.
gem install snogmetrics
- Edit
config/environment.rb
and addconfig.gem 'snogmetrics'
- Edit your layout(s) and add
<%= km.js! %>
where you keep your JavaScript includes. - Replace all your
KM.record(...)
andKM.identify(...)
calls in JavaScript with calls tokm.record(...)
andkm.identify(...)
Have a look at the included example application to see it in action.
Yes it does.
Just do it. You need to make sure that the _kmq
array exists, though. SNOGmetrics will define it where you place <%= km.js! %>
, but that is usually at the bottom of the page (with the async API you could probably put it at the top if you wanted to), so if you want to add things to _kmq
before that you need to define it yourself. Just add var _kmq = _kmq || []
and you're set.
SNOGmetrics implements #set, which is equivalent to _kmq.push(["set", ...])
, the preferred way of recording which version a user saw in an A/B test. SNOGmetrics does not support the KM.ab
function, because that's something you want to do in JavaScript only.
Yes, SNOGmetrics will not output the KISSmetrics API code unless RAILS_ENV
is production
. Instead it will output code that logs all calls to the console (if console
is defined).
In a future version this behaviour might be overrideable.
- Fork the project.
- Make your feature addition or bug fix.
- Add tests for it. This is important so I don't break it in a future version unintentionally.
- Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)
- Send me a pull request. Bonus points for topic branches.
Copyright (c) 2010 Theo Hultberg / Burt. See LICENSE for details.