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

@stackflow/plugin-google-analytics-4

v1.1.15

Published

Add Google analytics 4 script to current service.

Downloads

17

Readme

@stackflow/plugin-google-analytics-4

Add Google analytics 4 script to current service.

Usage

Inatallation

yarn add @stackflow/plugin-google-analytics-4

Initialize

import { stackflow } from "@stackflow/react";
import { googleAnalyticsPlugin } from "@stackflow/plugin-google-analytics-4";

const { Stack, useFlow } = stackflow({
  activities: {
    // ...
  },
  plugins: [
    googleAnalyticsPlugin({
      trackingId: "G-XXXXXXXXXX", // Required. Your Google Analytics 4 Tracking ID
      userInfo: {
        // optional
        userId: "test123", // Your own user distinguishable id. (https://bit.ly/3VGu04K)
        userProperties: {
          // ...
          // You can add additional event parameters. This value will collected as a user properties of "Custom Dimension" in GA.
          // https://bit.ly/3uQbriR
        },
      },
      useTitle: true, // Optional. If true, the title of the current screen will be sent to GA. if false, ActivityName will be sent to GA.(default false).
    }),
  ],
});

Set config

import { useGoogleAnalyticsContext } from "@stackflow/plugin-google-analytics-4";

const App = () => {
  const { setConfig } = useGoogleAnalyticsContext();

  useEffect(() => {
    setConfig({
      user_id: "test123",
      user_properties: {
        // ...
      },
      // ...
      //  GA4 config values.
      // https://bit.ly/3Y7IXhV
    });
  }, []);

  return <div>...</div>;
};

send event

Every stack has wrapped as a context, you can use useGoogleAnalyticsContext hook to send event.

import { useGoogleAnalyticsContext } from "@stackflow/plugin-google-analytics-4";

const { sendEvent } = useGoogleAnalyticsContext();

return (
  <>
    <button
      onClick={() => {
        sendEvent("click_ad_creaet_new_ad", {
          advertiser_id: "DEBUG_AARON",
        });
      }}
    >
      광고 만들기
    </button>
  </>
);

Here's an example capture of custom GA4 event sent from the above code.

Note that the second parameter object is sent as a custom event parameter.

image

FAQ

Pageview event is triggered twice.

Unckeck "Page changes based on browser history events" in GA4 settings (Web Stream>Enhanced Measurement>Pageviews>Advanced)

This plugin trigger pageview event manually using stackflow's "Effect Hook". You don't have to trigger it again.

image