kandi background

autotrack | enhanced Google Analytics tracking for common user interactions | Analytics library

Download this library from

kandi X-RAY | autotrack Summary

autotrack is a JavaScript library typically used in Analytics, React, Nodejs, Selenium applications. autotrack has no bugs, it has no vulnerabilities and it has medium support. However autotrack has a Non-SPDX License. You can install using 'npm i autotrack' or download it from GitHub, npm.
The default JavaScript tracking snippet for Google Analytics runs when a web page is first loaded and sends a pageview hit to Google Analytics. If you want to know about more than just pageviews (e.g. where the user clicked, how far they scroll, did they see certain elements, etc.), you have to write code to capture that information yourself. Since most website owners care about a lot of the same types of user interactions, web developers end up writing the same code over and over again for every new site they build. Autotrack was created to solve this problem. It provides default tracking for the interactions most people care about, and it provides several convenience features (e.g. declarative event tracking) to make it easier than ever to understand how people are interacting with your site.

kandi-support Support

  • autotrack has a medium active ecosystem.
  • It has 4855 star(s) with 593 fork(s). There are 198 watchers for this library.
  • It had no major release in the last 12 months.
  • There are 42 open issues and 126 have been closed. On average issues are closed in 21 days. There are 4 open pull requests and 0 closed requests.
  • It has a neutral sentiment in the developer community.
  • The latest version of autotrack is current.

quality kandi Quality

  • autotrack has 0 bugs and 0 code smells.


  • autotrack has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
  • autotrack code analysis shows 0 unresolved vulnerabilities.
  • There are 0 security hotspots that need review.

license License

  • autotrack has a Non-SPDX License.
  • Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.


  • autotrack releases are not available. You will need to build from source code and install.
  • Deployable package is available in npm.
  • Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA

Coming Soon for all Libraries!

Currently covering the most popular Java, JavaScript and Python libraries. See a SAMPLE HERE.
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.

autotrack Key Features

Automatic and enhanced Google Analytics tracking for common user interactions on the web.

autotrack Examples and Code Snippets

  • Installation and usage
  • Loading autotrack via npm
  • Custom builds
  • Using autotrack with multiple trackers
  • Universal Sentence Encoder TypeError prunded(text) expected Tensor
  • How to load GUSE v1 with Tensorflow 2?
  • How to reach data from Intent in Android
  • Retrieve data to ListView from API in android
  • Making predictions with loaded Estimator in Tensorflow 2.0
  • "TypeError: unsupported callable" when saving keras model using tensorlow
  • mapping a keras model over a list of tibbles
  • TF2: Add preprocessing to pretrained saved model for tensorflow serving (Extending the graph of a savedModel)

Installation and usage

window.ga=window.ga||function(){(ga.q=ga.q||[]).push(arguments)};ga.l=+new Date;
ga('create', 'UA-XXXXX-Y', 'auto');

// Replace the following lines with the plugins you want to use.
ga('require', 'eventTracker');
ga('require', 'outboundLinkTracker');
ga('require', 'urlChangeTracker');
// ...

ga('send', 'pageview');
<script async src="https://www.google-analytics.com/analytics.js"></script>
<script async src="path/to/autotrack.js"></script>

Community Discussions

Trending Discussions on autotrack
  • Best approach to caching in Ember Octane
  • Celery with Scrapy don't parse CSV file
  • Universal Sentence Encoder TypeError prunded(text) expected Tensor
  • How to load GUSE v1 with Tensorflow 2?
  • Problem getting parameter value in Android
  • How to reach data from Intent in Android
  • Retrieve data to ListView from API in android
  • Making predictions with loaded Estimator in Tensorflow 2.0
  • "TypeError: unsupported callable" when saving keras model using tensorlow
  • mapping a keras model over a list of tibbles
Trending Discussions on autotrack


Best approach to caching in Ember Octane

Asked 2021-Jun-29 at 21:23

I have a project running Ember@3.20. We are currently in the process of migrating from classic to glimmer based components and have come across some expensive computational patterns which would benefit from caching.

My question is, what is the best approach to caching functionality to getters for glimmer components? It looks like there are currently a few ways to do this:

  1. @cached via tracked-toolbox - I believe this was released prior to the ember cached api. I didn't peek under the hood but it has the has a @cached decorator which might collide with future ember @cached.
  2. ember-cache-primitive-polyfill - Mentioned in the Ember docs as a polyfill for the ember cached API (3.22) but the syntax isn't as concise as the @cached decorator
  3. ember-cached-decorator-polyfill - related to RFC566 appears to be based on option 2 with a more ergonomic syntax
  4. Upgrade to 3.22 - Trying to avoid bumping ember unless there is a significant benefit. At a glance, I didn't see @cached included here though.

Any additional insight/guidelines into how expensive a getter should be to warrant it being cached? For example, preventing re-renders seems a fairly obvious use case but there can be a wide range of what developers might consider an "expensive" computation.


Answered 2021-Jun-29 at 20:12

There are two categories of things here:

  1. The two @cached decorators.
  2. The caching primitives introduced via RFC 0566.

In the vast majority of Ember or Glimmer app or normal library code, you’ll just be using the decorator. You’d only ever really reach for the caching primitives if you were building some low-level library code yourself (not never, but not exactly common, either).

As for the @cached decorators, they have basically the same semantics. The tracked-toolbox version was research that fed into the the development of the primitive that Glimmer ships (and Ember uses), and so ember-cached-decorator-polyfill is implemented using the actual public API—polyfilling it via ember-cache-primitive-polyfill if necessary.

In terms of the performance characteristics, you don’t even actually need to think about it in terms of preventing re-renders: that’s not how the system works anyway. (See this blog post I wrote last year (2020) for a deep dive on how re-rendering gets scheduled in Ember and Glimmer using the autotracking concepts.) It’s also worth remembering that caching is not free! So it’s not as simple as “this thing costs something, so I should cache it”—the caching has to pay for itself to be worth it, and it costs both memory use and CPU time to create and to check caches.

With that caveat firmly in mind, I tend to think of “expense” here in the following categories:

  • am I rendering this hundreds or thousands of times?
  • does rendering this cause a long-running computation that will impact render (i.e. on the order of multiple milliseconds)
  • does this trigger asynchronous behavior?
  • (especially) does this trigger an API call?

In a lot of normal app code, the only getters you’ll really need to decorate with @cached are getters which produce API calls based on the components’ arguments. Since the getter will otherwise be invoked every time it is referenced, you will end up with multiple API calls, which can produce a situation where the apparent state in the UI flips back and forth as references to different promises resolve.

Source https://stackoverflow.com/questions/68184843

Community Discussions, Code Snippets contain sources that include Stack Exchange Network


No vulnerabilities reported

Install autotrack

To add autotrack to your site, you have to do two things:.
Load the autotrack.js script file included in this repo (or a custom build) on your page.
Update your tracking snippet to require the various autotrack plugins you want to use on the tracker.
Replace UA-XXXXX-Y with your tracking ID
Replace the sample list of plugin require statements with the plugins you want to use.
Replace path/to/autotrack.js with the actual location of the autotrack.js file hosted on your server.


Autotrack will safely run in any browser without errors, as feature detection is always used with any potentially unsupported code. However, autotrack will only track features supported in the browser running it. For example, a user running Internet Explorer 8 will not be able to track media query usage, as media queries themselves aren't supported in Internet Explorer 8.

Build your Application

Share this kandi XRay Report

Reuse Pre-built Kits with autotrack