.travisCommon: migrate Hadoop Event Recovery deployment to Release Manager (close #2983)Anton Parkhomenko4 months ago
1-trackersActionScript 3.0 Tracker: bump git submodule to 0.3.0 (closes #2727)Anton Parkhomenko8 months ago
2-collectorsScala Stream Collector: add Kafka sink (close #2937)Alex Dean5 months ago
3-enrichEmrEtlRunner: catch Elasticity ArgumentErrors while waiting for EMR (close #3027)Alex Dean2 months ago
4-storageRedshift: added manifest table (close #2265)Alex Dean2 months ago
5-data-modelingData modeling: add drill fields to web block (close #2956)Diogo Pacheco4 months ago
distCommon: added vagrant push scripting to publish Kinesis apps (closes #1288)Alex Dean2 years ago
integration-testsScala Hadoop Enrich: add test for SQL Query Enrichment (closes #2718)Anton Parkhomenko8 months ago
vagrantCommon: update script to sync eu-west-2 (London) Snowplow Hosted Assets bucket (close #3005)Alex Dean4 months ago
.gitignoreAdded dedicated Vagrant setup (closes #1266)Alex Dean2 years ago
.gitmodulesStorage: add Kinesis S3 git submodule (closes #2706)Josh7 months ago
.travis.ymlCommon: remove short-hostname addon from travis.yml (close #2674)Anton Parkhomenko4 months ago
CHANGELOGPrepared for releaseAlex Dean2 months ago
CONTRIBUTING.mdRemoved confusing reference to translationsAlexander Dean4 years ago
LICENSE-2.0.txtHack to make merge workAlex Dean2 years ago
README.mdPrepared for releaseAlex Dean2 months ago
VERSIONPrepared for releaseAlex Dean2 months ago
VagrantfileCommon: delete publish-kinesis-release.bash (closes #2711)Fred Blundun10 months ago


[ ![Build Status] travis-image ] travis [ ![Release] release-image ] releases [ License license-image ] license

Snowplow logo

Snowplow is an enterprise-strength marketing and product analytics platform. It does three things:

  1. Identifies your users, and tracks the way they engage with your website or application
  2. Stores your users' behavioural data in a scalable "event data warehouse" you control: in Amazon S3 and (optionally) Amazon Redshift or Postgres
  3. Lets you leverage the biggest range of tools to analyze that data, including big data tools (e.g. Spark) via EMR or more traditional tools e.g. Looker, Mode, Caravel, Re:dash to analyze that behavioural data

To find out more, please check out the [Snowplow website] website and the [Snowplow wiki] wiki.

Snowplow technology 101

The repository structure follows the conceptual architecture of Snowplow, which consists of six loosely-coupled sub-systems connected by five standardized data protocols/formats:

![architecture] architecture-image

To briefly explain these six sub-systems:

  • Trackers fire Snowplow events. Currently we have 12 trackers, covering web, mobile, desktop, server and IoT
  • Collectors receive Snowplow events from trackers. Currently we have three different event collectors, sinking events either to Amazon S3, Apache Kafka or Amazon Kinesis
  • Enrich cleans up the raw Snowplow events, enriches them and puts them into storage. Currently we have a Hadoop-based enrichment process, and a Kinesis- or Kafka-based process
  • Storage is where the Snowplow events live. Currently we store the Snowplow events in a flatfile structure on S3, and in the Redshift and Postgres databases
  • Data modeling is where event-level data is joined with other data sets and aggregated into smaller data sets, and business logic is applied. This produces a clean set of tables which make it easier to perform analysis on the data. We have data models for Redshift and Looker looker
  • Analytics are performed on the Snowplow events or on the aggregate tables.

For more information on the current Snowplow architecture, please see the [Technical architecture] architecture-doc.


Assuming git, [Vagrant] vagrant-install and [VirtualBox] virtualbox-install installed:

 host$ git clone https://github.com/snowplow/snowplow.git
 host$ cd snowplow
 host$ vagrant up && vagrant ssh
guest$ cd /vagrant/3-enrich/scala-common-enrich
guest$ sbt test

Find out more

| [Technical Docs] techdocs | [Setup Guide] setup | Roadmap roadmap | Contributing contributing | |-------------------------------------|-------------------------------|-----------------------------------|---------------------------------------------| | [![i1] techdocs-image] techdocs | [![i2] setup-image] setup | [![i3] roadmap-image] roadmap | [![i4] contributing-image] contributing |


We're committed to a loosely-coupled architecture for Snowplow and would love to get your contributions within each of the six sub-systems.

If you would like help implementing a new tracker, adding an additional enrichment or loading Snowplow events into an alternative database, check out our Contributing contributing page on the wiki!

Questions or need help?

Check out the [Talk to us] talk-to-us page on our wiki.

Copyright and license

Snowplow is copyright 2012-2013 Snowplow Analytics Ltd.

Licensed under the [Apache License, Version 2.0] license (the "License"); you may not use this software except in compliance with the License.

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

About FluentSend Feedback