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

node-google-analytics

v5.0.1

Published

A library for reporting Google Analytics 4 events from Node.js

Downloads

46

Readme

Google Analytics for Node

Report Google Analytics 4 events from a Node server.

Prerequisites

This library reads a _ga cookie from a { cookes } object, and relies on this being available. This will typically involve adding Google Analytics to your client-side, extracting the cookies from the request in your endpoint, and passing them to the await ga({ cookies, ... }) function (see Usage below).

If you're using Next, nextjs-google-analytics is recommended for the client-side. User requests to your API routes will then contain the necessary _ga cookie, and you can send server-side GA4 events.

Usage

await googleAnalytics(
  { 
    cookies: {},
    measurementId = process.env.GA_MEASUREMENT_ID,
    apiSecret = process.env.GA_API_SECRET
  }, 
  ...events,
);

Whenever you send an event, the following will be needed:

  1. an API secret, provided via ga({ apiSecret }, ...events) or process.env.GA_API_SECRET.

    To create a new secret, navigate to: Admin > Data Streams > choose your stream > Measurement Protocol > Create.

  2. a measurement ID associated with a data stream, provided via ga({ measurementId }, ...events) or process.env.GA_MEASUREMENT_ID env var.

    Found in the Google Analytics UI under: Admin > Data Streams > choose your stream > Measurement ID.

  3. a cookies object of form { [key: string]: string | undefined }, from which the Google Analytics ID will be extracted.

  4. an events array, of form { name: ..., params: { ... } }[].

E.g., the following Next API route handler:

import { googleAnalytics } from "ga4-node"

/**
 * GA_API_SECRET and GA_MEASUREMENT_ID provided via process.env.
 */
export default async function handler(req, res) {
  /**
   * Do something.
   */
  await makeOfflinePurchase(/* ... */);
  /**
   * Send GA events.
   */
  const { cookies } = req;
  await googleAnalytics(
    { cookies },
    {
      name: "offline_purchase",
      params: {
        engagement_time_msec: "100",
        session_id: "123",
      },
    },
    // ...,
  );
}

Resources