Track events & entities
In this section, you will add tracking to your own application, as well as learn how to create schemas that describe your custom events & entities, and how to track these from your application/s.
Step 1: Track out-of-the-box events from your own application
- Alternatively you can embed the Browser tracker directly into your application
- Please see our quick start guide for the Snowplow iOS and Android tracker
You can find our full list of our SDKs here (including our server side trackers, and 3rd party webhooks).
We recommend installing the Snowplow Inspector chrome extension developed by our partner Poplin Data which allows you to view & validate events that are being tracked from a web page and can be used for QA purposes.
Step 2: Track custom events & entities
Custom events & entities allow you to track & collect events that better reflect your business. In this step, you will define your custom event by creating a schema for it and uploading it to Iglu - your schema repository - and then start tracking it from your application.
Learn more why schemas are a powerful feature of Snowplow, and about the anatomy of a schema.
- First create the schema for the event
- The below is an example - you can create your own schema or edit this schema to better suit your needs
"description": "Schema for a button click event",
- You should then save this schema in the following folder structure, with a filename of
- Note: If you update the
vendorstring in the example, you should update the above path too.
- Upload your schema to your Iglu registry that you created when setting up your pipeline
- Download the latest igluctl if you haven't already
- To upload your schemas on localhost to the Iglu Server, use the following command:
igluctl static push --public <local path to schemas/> <Iglu server endpoint> <iglu_super_api_key>
- You can find more information on the Igluctl docs page
content: 'Purchase Now'
Once you've sent this event at least once, you can take a look at this event in Postgres. You'll find the core event properties in
atomic.events and the event specific properties in
You can join back to atomic.events using
root_id = event_id.
Next, learn how to further enrich your data and configure extra enrichments if necessary.
Once you are all set, check out our recipes to get tackling real-world use cases!