npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

jquery-track

v2.0.0

Published

Bind google analytics events to DOM elements easily using HTML data attributes.

Downloads

30

Readme

jquery-track

Bind google analytics events to DOM elements easily using HTML data attributes.

Build Status Code Climate npm

Installation

Usage

Basic example using data- attributes:

<a href="/"
    data-event-category="Site Navigation"
    data-event-action="click"
    data-event-label="Home">Home</a>
// initialize the plugin
$('a').track();

Data attributes

The following data attributes are available, most of which map directly to GA event fields.

  • data-event-category maps to the eventCategory GA field. Required.
  • data-event-action maps to the eventAction GA field. Required.
  • data-event-label maps to the eventLabel GA field. Optional, defaults to null.
  • data-event-value maps to the eventValue GA field. Optional, defaults to null.
  • data-non-interation maps to the nonInteraction GA field. Optional, defaults to false.
  • data-transport maps to the transport GA field. Optional, defaults to null.
  • data-event-type is the event types you want to trigger the event on. Optional, defaults to click. Can be any DOM event type that is supported by jQuery, as well as custom events.
  • data-hit-type maps to the hitType GA field. Optional, defaults to event. Can only be event or social.

Further details about the meaning of these fields can be found in the Google Analytics documentation.

Plugin options

debug {Boolean} Default: false

Set to true to turn on debug mode. Events will get logged to the browser console, instead of being sent to GA.

$('a').track({ debug: true });

social {Boolean} Default: false

Set to true if you're tracking a social event.

<a href="#"
    data-event-category="Twitter"
    data-event-action="tweet"
    data-event-label="http://codfish.io">Tweet</a>
$('a').track({ social: true });

Alternatively, you can use the data-hit-type attribute if you don't want to use the option, or you have a mixture of non-social & social elements you're tracking.

<a href="#"
    data-hit-type="social"
    data-event-category="Twitter"
    data-event-action="tweet"
    data-event-label="http://codfish.io">Tweet</a>

prefix {String} Default: ''

Use this option to tell the plugin to grab field values from data attributes with this prefix, i.e. data-{prefix}event-category. This can help in the rare instance that you may have a naming conflict with a data attribute.

<a href="/"
    data-ga-event-category="Site Navigation"
    data-ga-event-action="click"
    data-ga-event-label="Home">Home</a>
$('a').track({ prefix: 'ga-' });

Todo

  • [x] Add options
  • [x] Add umd during build process
  • [x] Add individual data attributes
  • [x] Add transport: 'beacon' support. https://developers.google.com/analytics/devguides/collection/analyticsjs/sending-hits#specifying_different_transport_mechanisms
  • [ ] Store each instance of the plugin as a dataset item, to help prevent re-initializing items.
  • [ ] Handle multiple event types, i.e. data-event-type="load click"
  • [ ] Possibly refactor to handle all hit types, i.e. page/app tracking (pageview, screenview), ecommerce tracking (transaction or item)