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

@builder.io/persist-attribution

v0.0.1-beta-2

Published

Persist attribution info between visits

Downloads

7

Readme

@builder.io/persist-attribution

Persist attribution info between visits.

This package is intended to be published to NPM and used with a JS delivery CDN, so it can be included in any of our sites with a simple script tag.

Developing

Run tests with:

yarn test

Publishing

(TODO)

Usage in sites

Include this script tag in your HTML:

<script src="//cdn.jsdelivr.net/npm/@builder.io/persist-attribution@latest/dist/persist-attribution.min.js" async defer></script>

You coul also change persist-attribution@latest with [email protected] (for example) to explicitly use version 0.1.3 of this script.

By default, that will:

  • Persist as cookies most utm_* query params in the current window.location (configurable with data-persist-utms):
  • Persist as cookie the visitor ID assigned to this session (cookie is only written if it doesn't exist) (configurable with data-persist-visitor-id):
  • Persist as cookie the current value of document.referrer (configurable with data-persist-referrer):
  • Persist as cookie the current value of document.referrer as "initial referrer" if the corresponding cookie is not send. (configurable with data-persist-initial-referrer):

All those options are enabled by default (true). There's another configurable option named data-send-page-view-events (disabled by default) that when enabled will send pageView events to our internal analytics endpoint. However it will only send events if there's a visitor ID (cookie) already present, so most likely you will need data-persist-visitor-id to be true as well.

For example, let's say we only care about pageView events (we don't care about utm_* stuff) we would tweak the script tag like:

<script
  src="//cdn.jsdelivr.net/npm/@builder.io/persist-attribution@latest/dist/persist-attribution.min.js"
  async
  defer

  id="persist-attribution-init"

  data-persist-visitor-id="true"
  data-send-page-view-events="true"

  data-persist-utms="false"
  data-persist-visitor-id="false"
  data-persist-referrer="false"
  data-persist-initial-referrer="false"
></script>

Note that id="persist-attribution-init" is required for configuration to work; the code will look for the HTML element with this ID and read the data-* attributes from it. If no element with this ID is found the default config will be used. Using an id attribute is necessary so we can define configuration using data-* attributes on the same element AND also being able to use async and defer.