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

ng-gtag

v10.0.4

Published

A simple and easy solution for adding google analytics page tracking to your angular project

Downloads

14

Readme

ng-gtag

A simple and easy solution for adding google analytics page tracking to your angular project

Installation

npm install ng-gtag

Setup

In your root module import GtagModule

import { GtagModule } from 'ng-gtag';

@NgModule({
  imports: [
    GtagModule.forRoot({trackingId: 'UA-<YOUR-GA-TRACKINGID>'})
  ]
})

Additionally you can pass options to the forRoot function. For example:

GtagModule.forRoot({
  trackingId: "UA-<YOUR-GA-TRACKINGID>",
  options: { send_page_view: false },
});

Then in your app.component.html add the tags

<ng-gtag></ng-gtag>

You will not need to add any additional code, this package will inject the correct <script> tags for you into the head section.

This package is also designed to work with Angular Universal projects.

Events

Service

GtagEventService.event({
  action: "sale",
  options: { event_category: "engagement" },
});

Directive

<button
  ngGtagEvent
  gtagOn="click"
  gtagAction="sale"
  [gtagOptions]="{ event_category: 'engagement' }"
>
  Purchase
</button>

Multiple Tracking ID's

It is as simple as passing array to the forRoot function when importing

GtagModule.forRoot([
  {
    trackingId: "UA-<YOUR-GA-TRACKINGID1>",
    options: { send_page_view: false },
  },
  {
    trackingId: "UA-<YOUR-GA-TRACKINGID2>",
    options: { send_page_view: true },
  },
]);

If you then want to specify a trackingId for an event you can use the option send_to as per the gta.js API

<button
  ngGtagEvent
  gtagOn="click"
  gtagAction="sale"
  [gtagOptions]="{ send_to: 'UA-<YOUR-GA-TRACKINGID1>' }"
>
  Purchase
</button>

FAQ

Why?
The move to gtag.js was a fairly significant API change and I was tired of having to add script tags to my index.html along with additional code to get page views to work correctly with Angular. I am also a strong believer in using server side rendering (SSR) and ran into numerous issues with some other packages.