Javascript Tracker

HOME > [SNOWPLOW TECHNICAL DOCUMENTATION](Snowplow technical documentation) > Trackers > Javascript Tracker

Contents

• 1. Overview
• 2. General parameters
  • 2.1 Setting the endpoint
    • 2.1.1 setCollectorCf
    • 2.1.2 setCollectorUrl
  • 2.2 Setting the application ID
    • 2.2.1 setAppId
  • 2.3 Setting the cookie domain
    • 2.3.1 setCookieDomain
  • 2.4 Setting the user ID
    • 2.4.1 setUserId
• 3. Tracking specific events
  • 3.1 Pageviews
    • 3.1.1 trackPageView
  • 3.2 Pagepings
    • 3.2.1 enableActivityTracking
  • 3.3 Ecommerce transaction tracking
    • 3.3.1 addTrans
    • 3.3.2 addItem
    • 3.3.3 trackTrans
    • 3.3.4 Pulling it all together: an example
  • 3.4 Social tracking
    • 3.4.1 trackSocial
  • 3.5 Campaign tracking
    • 3.5.1 Identifying paid sources
    • 3.5.2 Anatomy of the query parameter
  • 3.6 Ad impression tracking
    • 3.6.1 trackImpression
  • 3.7 Tracking custom structured events
    • 3.7.1 trackStructEvent
  • 3.8 Tracking custom unstructured events
    • 3.8.1 trackUnstructEvent
  • 3.9 Link click tracking
    • 3.9.1 enableLinkTracking

## 1. Overview

The Snowplow Javascript tracker works in much the same way as Javascript trackers for other major web analytics solutions including Google Analytics and Omniture. We have tried, as far as possible, to keep the API very close to that used by Google Analytics, so that users who have implemented Google Analytics Javascript tags have no difficulty also implementing the Snowplow Javascript tags.

Tracking is done by inserting Javascript tags onto pages. These tags run functions defined in snowplow.js, that trigger GET requests of the Snowplow pixel. The Javascript functions append data points to be passed into Snowplow onto the query string for the GET requests. These then get logged by the Snowplow collector. For a full list of data points that can be passed into Snowplow in this way, please refer to the Snowplow tracker protocol documentation.

The Javascript tracker supports both syncronous and asyncronous tags. We recommend the asyncronous tags in nearly all instances, as these do not slow down page load times.

Back to top
2. General parameters
3. Tracking specific events