Collecting data with Trackers and Webhooks

  1. Home
  2. Docs
  3. Collecting data with Trackers and Webhooks
  4. Trackers – collecting data from your own applications
  5. Python Tracker
  6. Intialization

Intialization

Assuming you have completed the Python Tracker Setup for your Python project, you are now ready to initialize the Python Tracker.

Importing the module

Require the Python Tracker’s module into your Python code like so:

from snowplow_tracker import Subject, Tracker, Emitter

That’s it – you are now ready to initialize a tracker instance.

Creating a tracker

The simplest tracker initialization only requires you to provide the URI of the collector to which the tracker will log events:

e = Emitter("d3rkrsqld9gmqf.cloudfront.net") t = Tracker(e)

There are other optional keyword arguments:

Argument NameDescriptionRequired?Default
emittersThe emitter to which events are sentYesNone
subjectThe user being trackedNosubject.Subject()
namespaceThe name of the tracker instanceNoNone
app_idThe application IDNoNone
encode_base64Whether to enable base 64 encodingNoTrue

A more complete example:

tracker = Tracker( Emitter("d3rkrsqld9gmqf.cloudfront.net") , namespace="cf", app_id="cf29ea", encode_base64=False)

emitters

This can be a single emitter or an array containing at least one emitter. The tracker will send events to these emitters, which will in turn send them to a collector.

subject

The user which the Tracker will track. This should be an instance of the Subject class. You don’t need to set this during Tracker construction; you can use the Tracker.set_subject method afterwards. In fact, you don’t need to create a subject at all. If you don’t, though, your events won’t contain user-specific data such as timezone and language.

namespace

If provided, the namespace argument will be attached to every event fired by the new tracker. This allows you to later identify which tracker fired which event if you have multiple trackers running.

app_id

The app_id argument lets you set the application ID to any string.

encode_base64

By default, unstructured events and custom contexts are encoded into Base64 to ensure that no data is lost or corrupted. You can turn encoding on or off using the Boolean encode_base64 argument.