Attlib - an open source library for extracting search marketing attribution data from referrer URLs
Update 17-Dec-12: We have renamed Attlib to referer-parser, to make it clearer what Attlib does: parse referer URLs. The repository has been updated accordingly. Some of the example code below is out-of-date now: we recommend checking out the repository for more information.
Last night we published Attlib, an open source Ruby library for extracting search marketing attribution data from referer (sic) URLs. In this post we talk through:
- What Attlib does, and how to use it
- Installing Attlib
- The search_engine.yml file
- Attlib as part of the Snowplow stack
- Attlib in other languages
- Making components of Snowplow available as standalone open source projects
What Attlib does, and how to use it
Attlib is straightforward Ruby library for extracting seach marketing attribution data from referrer URLs. You give it a referer URL to parse: it then lets you now whether the URL is from a search engine. If it is, it will tell you which search engine it is, and what keywords were typed. (If those keywords are included in the query string - this is no longer the case for users logged in to Google, as documented here.)
Attlib is available via a Ruby Gem. To install, simply run the following at the command line:
sudo gem install attlib
The sourcecode is available on Github
The search_engines.yml file
Extracting search engine names and keywords from a referer URL is pretty straightforward. What is more complicated is keeping track of the myriad search engines that are out there, operating in different countries, the myriad domains they operate on, and the different query parameters that each of them uses to store the keywords.
Because the space is constantly evolving, none of this information (about search engines, parameters and domains) has been hard coded into Attlib. All of it is available in the search_engines.yml file, in the data in the repo.
The structure of the YAML file should be straightforward to understand. Each search engine is a top level item. For each search engine, two lists are given: one is a list of parameters used in that search engine’s query string to identify the keywords entered. The other is the list of domains on which that search engine operates. An extract is shown below:
Keeping this file up to date is a big job: one of our hopes releasing Attlib as an open source, standalone library, is that the community contributes to the file. We are enormously grateful to our friends at Piwik as our initial version of the file is based on the Piwik equivalent SearchEngines.php, for the hard work they put into this version.
Attlib as part of the Snowplow stack
Our intention is to port Attlib into Scala and integrate it into the Snowplow stack: specifically the ETL phase. Both Ruby and Scala versions of Attlib will run based on the same search_engines.yml file.
Attlib in other languages
As well as contributing to the search search_engines.yml file, we also hope that community members will develop versions of Attlib in other languages e.g. Python.
Making components of Snowplow available as standalone open source projects
Attlib is the first component in the Snowplow stack that we have released as a standalone library. There are many more in the pipeline. (More on this in future blog posts :-) ). For us, this is a key part of the Snowplow strategy:
- Keeping the Snowplow architecture as loosely coupled as possible. We believe this makes Snowplow robust, scalable and extendable
- Grow the userbase of people using and contributing to each component. Processing web analytics data is a big job: there are many individual components involved, and each of them needs to evolve with the changing marketplace. Attlib is concerned today with extracting useful data from search engine referrers: but it is likely that as time goes on, we’ll want to extend it to capture data from other types of referrers e.g. social networks or affiliate sites. The bigger the community of people on top of those developments, the better for everyone in the web analytics community. Releasing each component as a standalone open source library should help grow that community.
Any questions about Attlib, or anything else in this post? Then get in touch with the Snowplow team.